MQSeries.net :: View topic

venkat kurra · Posted: Thu Oct 23, 2003 2:13 pm Post subject:

I created a broker(BROKER) on Server1 and configuration manager on an other server 'Server2'. Connected to Configmgr

through my CC and deployed the BROKER(tested flows too). Some other reason we need to connect to other configserver(it is

brand new) . This is a test environemt so that i stoped the broker and deleted broker with -w (workpath) option and

recreated again. Now i connected to new config manager and create broker image and deployed. These are CC errors...

Error 1:
( ConfigMgr ) Broker BROKER was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

The internal configuration message failed to be processed, use the messages following this message to determine the

reasons for the failure.

Error 2:
( ConfigMgr ) Broker BROKER (UUID 0d862b5f-f800-0000-0080-cf98cb708fe4) running on WebSphere MQ queue manager 'BROKER'

could not process an internal configuration message because the broker identity received in the message (UUID

57c86169-f800-0000-0080-81f507a13439) did not match that of this broker.

An internal configuration message could not be processed and was rejected. Each broker is identified by a universally

unique identifier called a UUID which is allocated when the Control Center user creates a definition for the broker. The

configuration message received contained a broker UUID (57c86169-f800-0000-0080-81f507a13439) that does not match the

UUID of broker BROKER running on WebSphere MQ queue manager BROKER. There are two possible reasons for this. Either a

Control Center user has accidentally specified queue manager BROKER when defining another broker so that messages

destined for the other broker have arrived at this broker, or the definition for broker BROKER was deleted and recreated

on the Control Center which has the effect of giving broker BROKER a new, different UUID.

If the queue manager name specified in the Control Center was incorrect then use the Control Center to correct the broker

definition in error. The mqsilist command may be used to display broker queue manager names. Otherwise, if the broker

definition was deleted and recreated, you must use the mqsideletebroker and mqsicreatebroker commands to recreate the

broker, then redeploy the configuration for the broker in order to reestablish the correct broker identity. To avoid loss

of data when recreating the broker, make sure that you follow the sequence of actions defined in the WebSphere MQ

Integrator Administration Guide section 'Recovery and restart'.

Error 3:
( ConfigMgr ) Configuration Manager unable to register for internal subscriptions with broker BROKER.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for

internal subscriptions with broker BROKER was not successful. This means that the Control Center Operations view may not

reliably show the correct status of the resources assigned to broker BROKER. The Configuration Manager also writes this

message to the system event log, accompanied by other messages giving details of the problem.

Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before

attempting to deploy to this broker again. If this problem persists, contact your IBM support center.

Next step i deleted cleanly...
On Config server
1) Stop the config manager
2) stop the queue manager
3) mqsideleteconfigmgr -w -n -m
4) Drop the database tables MQSICMDB and MQSIMRDB(removed ODBC connection also) from DB2 cc.
5) Create database tables MQSIMRDB and MQSICMDB. Configure ODBC connection for MQSIMRDB.
6) start queue manager.
7) Create configuration manager

Start Configuration manager.

On broker
1) Stop the broker and queue manager
2) mqsideletebroker BROKER -w
3) Drop MQSIBKDB from DB2 cc and removed ODBC connection.
4) Create MQSIBKDB and establish ODBC connection.
5) Start Queue manager
6) Create the broker and started.

connected to configuration manager and deployed the BROKER and getting same errors. I repeated all above steps except the

queue manager stop(config step 2 and broker step 1),but no use.

How can i delete broker UUID from the MQSICMDB? Any other solution with out droping the database tables?
_________________
Thanks,

Venkat Kurra

IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin