MQSeries.net :: View topic - Effect of Upgradation in Maintainance Level(ML)

chetu777 · Posted: Tue Sep 08, 2009 12:05 am Post subject:

Dear All,

Actully there was a upgradation of ML for the Broker AIX machine. The broker version we use is V5 and the IBM site mentioned that the new ML level is compactible with this version, but after the upgrdation the Broker Toolkit is not able to deploy nor stop/start any message flows and whenever try to deploy a message flows it thows an UUID error.
Changed the UUID in CM db, but still the problem exists.
So created a new DB and new CM and then deployed a MF, but still its throwing a UUID error as mentioned below.

[i]BIP1536S: Configuration Manager unable to register for internal subscriptions with broker BRK.VOC.TST.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker BRK.VOC.TST was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker BRK.VOC.TST. 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.

==================================================================================================

BIP2087E: Broker BRK.VOC.TST 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.

=================================================================================================

BIP2045E: Broker BRK.VOC.TST (UUID 552579d8-1601-0000-0080-d7e293118b4a) running on WebSphere MQ queue manager T.VOC.BRK.01 could not process an internal configuration message because the broker identity received in the message (UUID c103483d-2001-0000-0080-e22a15d7c28e) 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 user creates a definition for the broker. The configuration message received contained a broker UUID (c103483d-2001-0000-0080-e22a15d7c28e) that does not match the UUID of broker BRK.VOC.TST running on WebSphere MQ queue manager T.VOC.BRK.01. There are two possible reasons for this. Either a user has accidentally specified queue manager T.VOC.BRK.01 when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker BRK.VOC.TST was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker BRK.VOC.TST a new, different UUID.

If the queue manager name specified in the Message Brokers Toolkit was incorrect then use the Message Brokers Toolkit 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 re-establish 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 online documentation section "Recovery and restart".

==================================================================================================[/i]

Can someone let me know the solution