| Author |
Message
|
| andrewhirst |
 Posted: Wed Feb 16, 2005 8:37 am Post subject: Config Manager Crash |
 |
|
Apprentice
Joined: 06 Jul 2004
Posts: 33
Location: UK
|
Hello,
The machine running my config manager in our development dept has crashed and it was not properly backed-up. The repositories were on a Solaris box and they seem to be intact.
We were planning to migrate to a suitable server, so we have set a new config manager.
I have modified the queue managers on the brokers to connect to the new server. Control centre connects to the new CfgMgr, but I cannot load my message flows.
What is the best course of action to resolve this problem.
TIA
Andrew.
_________________
Andrew Hirst |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Feb 16, 2005 9:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The repositories?
You mean the databases?
What steps did you perform to rebuild the config manager?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| andrewhirst |
| Posted: Wed Feb 16, 2005 9:58 am Post subject: |
|
|
Apprentice
Joined: 06 Jul 2004
Posts: 33
Location: UK
|
Yes, by repositories I mean databases
I have not rebuilt the config manager as such as it's now on a different machine. These are the steps that we took to build the new config manager:
Original databases exist on DEVMQ1.
Manually connect to the config manager database on DEVMQ1 using DB2's Client Configuration Assistant.
Test the connection.
Manually connect to the message repository database on DEVMQ1 using DB2's Client Configuration Assistant.
Test the connection.
Create and admin profile for WMQI and add relevant users to the MQ Broker groups.
Run the mqsicreateconfigmgr program, with the appropriate parameters.
_________________
Andrew Hirst |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Feb 16, 2005 10:07 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
What version.
| Quote: |
| I have not rebuilt the config manager |
Then what does the following do.
| Quote: |
| Run the mqsicreateconfigmgr program |
Doesn't that clear/initialise the tables in the DB.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 16, 2005 11:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| EddieA wrote: |
| What version. |
He said "control center".
Did you read the section on Backup and Recovery in the System Administration Guide for WMQI 2.1?
Do you have a backup of the configuration manager databases?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| andrewhirst |
| Posted: Thu Feb 17, 2005 6:47 am Post subject: |
|
|
Apprentice
Joined: 06 Jul 2004
Posts: 33
Location: UK
|
I have had a look at the tables in the CfgMgr's database and they look OK. I read the Backup and Recovery section and tried to redeploy the domain configuration as instructed:
File ->Deploy ->Complete configuration ->Normal
This produced the following error:
| Quote: |
BIP1205E: Unexpected exception accessing configuration repository; exception text: '[IBM][CLI Driver][DB2/SUN] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "config manager server's IP". Communication function detecting the error: "recv". Protocol specific error code(s): "10053", "*", "*". SQLSTATE=08001 '.
While attempting a database operation on the configuration repository, a SQL exception was caught by the Configuration Manager. The database operation did not complete successfully. If this message was issued by the Configuration Manager, then it will continue if it is safe to do so. The exception text is: [IBM][CLI Driver][DB2/SUN] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "config manager server's IP". Communication function detecting the error: "recv". Protocol specific error code(s): "10053", "*", "*". SQLSTATE=08001 .
For more information on this error refer to the relevant documentation for the database manager you are using for the configuration repository (for example, for DB2 refer to the DB2 SQL Reference manual). |
I suspect that the problem is a firewall issue. I'll post more as soon as our network boys have had a look.
_________________
Andrew Hirst |
|
| Back to top |
|
|
| andrewhirst |
| Posted: Thu Feb 17, 2005 8:56 am Post subject: |
|
|
Apprentice
Joined: 06 Jul 2004
Posts: 33
Location: UK
|
The ports have been opened and the Config Manager can connect.
Running the Control Centre on the same machine as the Config Manager, I can see all deployments, etc and add message flows and message sets into my workspace. However, on the client PCs, Control Centre can not see the topology, assignments, etc.
This problem is due to the wmqi user accounts employed in the mq user groups were domain accounts, rather than local accounts.
_________________
Andrew Hirst |
|
| Back to top |
|
|
|
|
