| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Hurdles when replacing one box in a domain |
« View previous topic :: View next topic » |
| Author |
Message
|
| mattfarney |
 Posted: Tue Aug 25, 2009 3:05 pm Post subject: Hurdles when replacing one box in a domain |
 |
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
I have two windows boxes in a Broker Domain (v5). Each has a broker, one also has the Config Manager for the domain.
We are in the process of replacing the hardware on these machines. So, the secondary box was removed and switched out for a new one. The config manager would not talk to the new BRK2 (I assume due to mismatching UUIDs). I went ahead and deleted the image of BRK2 from the topology section of the toolkit and did a complete deployment.
Even after this completed, I continue to get the following message when I try to add BRK2 back. In the event log, I also see most of the messages showing
Active Brokers: BRK1, Deleted Brokers: BRK2
| Quote: |
BIP1511E: Queue manager 'QM2' cannot be associated with broker 'BRK2'; it is already associated with broker 'BRK2'.
An attempt was made to associate broker BRK2 with WebSphere MQ queue manager QM2, but broker BRK2 already has this association. A WebSphere MQ queue manager can only have one broker associated with it.
Change the queue manager for one of the brokers. If this problem occurs after you have deleted broker BRK2 then tried to recreate it, you must first initiate a deploy operation to automatically delete the configuration from the real broker. It is only after all types of configuration data (message flows, message sets, topology, topics) have been successfully deleted from the real broker that the broker document is finally deleted from the configuration repository. Until that time the queue manager can not be associated with another broker. Once this has been done, you must also physically delete and recreate the real broker using the mqsideletebroker and mqsicreatebroker commands. |
I'm at a loss on how to deal with this. I have seen other posts suggest going into DB2 and removing the offending lines from the CBROKER table.
While this is potentially doable, that seems an odd solution.
From the sounds of the error message, if you have a remote broker that disappears, it is impossible to ever have another with the same name, since you can never
| Quote: |
| initiate a deploy operation to automatically delete the configuration from the real broker |
Am I missing something painfully obvious?
Thanks.
-mf |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Aug 25, 2009 3:23 pm Post subject: Re: Hurdles when replacing one box in a domain |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mattfarney wrote: |
| Am I missing something painfully obvious? |
You missed removing the broker from the topology before deleting the broker.
The best way forward is to delete the DB2 as indicated. It's an odd solution, and one that v6 doesn't require due to improvements in the config mgr.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
