| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How change UUID Broker in MQIntegrator v2.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Pablo Taboada |
 Posted: Mon Dec 24, 2007 4:24 am Post subject: How change UUID Broker in MQIntegrator v2.1 |
 |
|
Apprentice
Joined: 19 Jul 2007
Posts: 36
Location: Spain - Barcelona
|
How change UUID Broker in MQIntegrator v2.1?
I have next message error, that I know in WMB v6.0 is sufficient changing UUID, but in v2.1 I don't know how can I do it.
anyone can help me?
Thanks!
_________________
Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
| Back to top |
|
 |
| Pablo Taboada |
| Posted: Mon Dec 24, 2007 4:53 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007
Posts: 36
Location: Spain - Barcelona
|
Error:
BIP2045E: Broker ESBRKF01 (UUID b8d3f469-0301-0000-0080-b871b7cf2f7e) running on WebSphere MQ queue manager 'ESBRKF01' could not process an internal configuration message because the broker identity received in the message (UUID 00ca730b-1701-0000-0080-b871b7cf2f7e) 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 (00ca730b-1701-0000-0080-b871b7cf2f7e) that does not match the UUID of broker ESBRKF01 running on WebSphere MQ queue manager ESBRKF01. There are two possible reasons for this. Either a Control Center user has accidentally specified queue manager ESBRKF01 when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker ESBRKF01 was deleted and recreated on the Control Center which has the effect of giving broker ESBRKF01 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'.
_________________
Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Mon Dec 24, 2007 5:13 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
It's not advisable to change the UUID of the broker instance at all. 
More over you're going to corrupt it.
go through the following link.
http://www.mqseries.net/phpBB2/viewtopic.php?t=3488&highlight=bip1536s
Search for BIP number you will get lots of results.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Dec 24, 2007 6:23 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
You do realise that v2.1 went out of support over a year ago?
You can't change the UUID; deploy your resources to a new broker instead. Preferably at either v6.0 or v6.1 level. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
