| Author |
Message
|
| shogan2003 |
 Posted: Mon Nov 13, 2006 8:43 am Post subject: WBIMBv6. UUID conflict. Broker already exists ?? |
 |
|
Centurion
Joined: 03 Jul 2003
Posts: 133
Location: London
|
Broker was deleted from toolkit and the broker itself also deleted, together with its database.
Have tried the Config Manager Proxy API Exerciser and would like to know what is meant by the suggestion of making the queue SYSTEM.BROKER.ADMIN.QUEUE inaccessible.
Here's the pop-up error message when I attempt to re-declare the broker within the toolkit
Thanks to all in advance
------------------------------------------------------------------------------------
BIP1506E: Queue manager 'XYZPBK01' cannot be associated with broker 'XYZPBK01'; it may still be in use by another broker 'VAAPBK01' which is pending deletion.
Broker 'XYZPBK01' has been removed from the domain of active brokers, although it may still be using its queue manager. It is not possible to associate another broker with the queue manager until the Configuration Manager can confirm that the first broker has tidied up its resources.
After successfully removing a broker from the domain, you must initiate a deploy of the topology in order to instruct the broker component to stop and tidy up its resources. This can be done using the Message Brokers Toolkit, mqsideploy utility or the Configuration Manager Proxy API. Once the deploy is successful, you must delete the broker component using the mqsideletebroker command. Only then can you associate a new broker with the queue manager.
If the runtime broker component has already been deleted and is therefore unable to cleanly tidy up its resources, you must purge any remaining references to the broker and its queue manager from the Configuration Manager's repository. To do this, either (a) make the queue manager or its SYSTEM.BROKER.ADMIN.QUEUE inaccessible to the Configuration Manager and initiate a topology deploy, or (b) use the Configuration Manager Proxy API TopologyProxy.removeDeletedBroker().
____________________________________________________________
BIP1712W: Broker not found
An attempt was made to view or modify the Broker with UUID '82fb28e2-0e01-0000-0080-c05fad536d7e', but it does not exist in the Configuration Manager's repository.
If you are trying to manipulate an object immediately after submitting a request to create it, it is likely that there was a problem creating the object. An example of this is if you attempt to create a default execution group without first ensuring that the parent broker was created successfully; this error suggests that there was a problem creating the broker.
Check the Configuration Manager's logs to see why the Broker could not be found. If the object has previously been available, the receipt of this error may indicate corruption in the Configuration Manager's repository; if this is the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager's repository, or if this is not possible, contact your IBM support center for advice.
____________________________________________________________
BIP1712W: Broker not found
An attempt was made to view or modify the Broker with UUID '82fb28e2-0e01-0000-0080-c05fad536d7e', but it does not exist in the Configuration Manager's repository.
If you are trying to manipulate an object immediately after submitting a request to create it, it is likely that there was a problem creating the object. An example of this is if you attempt to create a default execution group without first ensuring that the parent broker was created successfully; this error suggests that there was a problem creating the broker.
Check the Configuration Manager's logs to see why the Broker could not be found. If the object has previously been available, the receipt of this error may indicate corruption in the Configuration Manager's repository; if this is the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager's repository, or if this is not possible, contact your IBM support center for advice.
____________________________________________________________
BIP1520I: The Configuration Manager has initiated a deployment operation.
The Configuration Manager received a request to deploy configuration data and has consequently asked the following brokers to change their configuration: XYZPBK01, XYZPBK02, XYZPSBS01
The receipt of this message does not necessarily mean that deployment was successful; view the Event Log Editor in the Message Brokers Toolkit to check the outcome of the deployment. If you are deploying programmatically using the Config Manager Proxy, check the returned DeployResult object or LogProxy. There will be a separate set of log messages for each broker.
_________________
MQSI2 certified specialist
MQSeries certified specialist |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Nov 13, 2006 3:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Use the API Proxy to "remove all traces of a previously deleted broker"
You can only do this with the API Proxy Exerciser...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Nov 13, 2006 11:50 pm Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| fjb_saper wrote: |
| You can only do this with the API Proxy Exerciser... |
Right click on the Topology object and select 'Remove references to a previously deleted broker'.
This application is, of course, just a sample wrapper for the CMP API. The actual API that is useful here is TopologyProxy.removeDeletedBroker(String nameOrUUID).
-Matt |
|
| Back to top |
|
|
| shogan2003 |
| Posted: Tue Nov 14, 2006 4:29 am Post subject: |
|
|
Centurion
Joined: 03 Jul 2003
Posts: 133
Location: London
|
I've already used the CMP Proxy Exerciser
_________________
MQSI2 certified specialist
MQSeries certified specialist |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Tue Dec 05, 2006 7:58 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
Hi shogan2003,
were were you able to resolve this? I am having same issue and looking forward for some guidelines.
Thanks in advance.
wmqiadmin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Dec 06, 2006 3:50 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
If the removeDeletedBroker() API (or equivalent CMP Exerciser option) doesn't work then I'd be surprised and interested, because it is deliberately quite heavy handed in its approach to removing brokers.
So long as the UUID or broker name is supplied correctly to it, I've not come across a scenario where it fails to clean up a broker from the Config repository.
If the problem persists, please raise a PMR. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Dec 06, 2006 4:15 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
1. Ensure that you deleted Old Brokers database perfectly, if not remove that.
2. Are you creating the broker with same name as it was.
it is caused, when you are not deleted the broker systamatically
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Jan 11, 2007 7:06 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| If there is a UUID mismatch, from the error message try to find the previous UUID and then use Proxy API to assign that old UUID to the New Broker then it will work.. |
|
| Back to top |
|
|
| dweller |
| Posted: Thu Jan 11, 2007 11:35 am Post subject: |
|
|
Apprentice
Joined: 31 Oct 2006
Posts: 28
|
1. delete all windows registry entries associated with that broker name.
2. delete C:\Documents and Settings\All Users\Application Data\IBM\MQSI
3. reinstall wmb
cleanest way to get rid of wmb afaik  |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Jan 11, 2007 12:06 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Quote: |
1. delete all windows registry entries associated with that broker name.
2. delete C:\Documents and Settings\All Users\Application Data\IBM\MQSI
3. reinstall wmb
cleanest way to get rid of wmb afaik |
no need to do all this, just using the Proxy API to set the UUID is enough.. |
|
| Back to top |
|
|
| RatherBeGolfing |
| Posted: Fri Jan 19, 2007 1:06 pm Post subject: |
|
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
Pathipati,
Any chance you'd be willing to share a "how to" actually set the UUID within the API exerciser. We've got the exerciser dialog running, but don't know how to proceed from there to change the value of our UUID back to the older one.....
_________________
Cheers,
Larry
MQ Certifiable |
|
| Back to top |
|
|
| pathipati |
| Posted: Fri Jan 19, 2007 2:47 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| when you try to connect your new broker to configmgr you will get some exception because of UUID conflict. In that exception msg you can find old UUID, copy that go to ConfigMgr Proxy API and use SetUUID method to set it to old UUID.. |
|
| Back to top |
|
|
| broker_new |
| Posted: Sat Jan 20, 2007 12:21 pm Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
Whatever the Pathipati posted in the previous post is exactly correct..
It will work out |
|
| Back to top |
|
|
| pathipati |
| Posted: Sat Jan 20, 2007 12:24 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Jan 22, 2007 5:23 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Glad it worked for you, but do read the documentation for the setUUID() method. Importantly, any message flows that you had deployed to that broker will not be monitored by the Config Manager until you redeploy them. |
|
| Back to top |
|
|
|
|
