Author |
Message
|
raghav129 |
Posted: Fri Apr 11, 2008 4:52 am Post subject: Broker accidently deleted from MB toolkit |
|
|
Novice
Joined: 30 Aug 2007 Posts: 17
|
Hi,
If we accidently delete broker from our Message broker toolkit,how can we make sure that the Broker's UUID is also deleted,So that configuration manager will allow us to add the same broker again?
Thanks, |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Apr 11, 2008 4:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
mqsideletebroker
or in v6.1, you can adopt the broker.
I'd also strongly recommend reading about "mqsisetaclentries", in order to ensure that only the right people are capable of making these mistakes. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Apr 11, 2008 2:07 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Jeff did the command change in 6.1?
I thought it was mqsicreateaclentry and mqsichangeaclentry...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Apr 11, 2008 2:17 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
fjb_saper wrote: |
Jeff did the command change in 6.1?
I thought it was mqsicreateaclentry and mqsichangeaclentry...  |
 _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
mqmatt |
Posted: Mon Apr 14, 2008 2:41 am Post subject: Re: Broker accidently deleted from MB toolkit |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
raghav129 wrote: |
how can we make sure that the Broker's UUID is also deleted |
I'm not sure what this actually means.
If you remove the broker from the toolkit (accidentally or otherwise), then if the broker is running, everything will be tidied up for you in the Config Manager; you just need to run mqsistop/mqsideletebroker to tidy everything up on the broker machine. |
|
Back to top |
|
 |
sri_csee1983 |
Posted: Mon Apr 14, 2008 4:16 am Post subject: |
|
|
 Centurion
Joined: 25 Mar 2008 Posts: 125 Location: Chennai,India
|
Dear Friends,
I am not sure abt MB 6. But MB 5, if that has happened, mqsideletbroker does not delete the broker entries in the table cbroker. if v delete the corresponding broker entry in the table 'cbroker' and delete the broker using mqsidelete broker. then after newly creating it. V can add the same in the tool kit. I dont know whether this is applicable for MB6.0 if the other soln is not working, u can try this.  _________________ With Cheers,
Sri |
|
Back to top |
|
 |
SAFraser |
Posted: Mon Apr 14, 2008 8:39 am Post subject: |
|
|
 Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
|
In 6.0, couldn't you use the Proxy Exerciser to remove all traces of the broker from Configuration Manager, and create the same broker again in the broker domain (without deleting & recreating the broker itself with mqsideletebroker)?
I'm asking, not telling. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Apr 14, 2008 9:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
SAFraser wrote: |
In 6.0, couldn't you use the Proxy Exerciser to remove all traces of the broker from Configuration Manager, and create the same broker again in the broker domain (without deleting & recreating the broker itself with mqsideletebroker)?
I'm asking, not telling. |
yes. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
mqmatt |
Posted: Mon Apr 14, 2008 9:40 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
jefflowrey wrote: |
SAFraser wrote: |
In 6.0, couldn't you use the Proxy Exerciser to remove all traces of the broker from Configuration Manager, and create the same broker again in the broker domain (without deleting & recreating the broker itself with mqsideletebroker)?
I'm asking, not telling. |
yes. |
Hmmm.. sort of. In v6.0, if you remove all traces of a broker from the CM repository (the "remove references to a previously deleted broker" thing), you'd still need to recreate the broker using mqsideletebroker/mqsicreatebroker.
You could kind-of get round this by adding the broker back to the CM and setting its UUID manually (very contact admin), but you couldn't then discover and manage any of its existing resources.
In 6.1 you can have the CM synchronize and adopt running brokers, which makes things easier - as Jeff said earlier. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Sat Dec 13, 2008 9:27 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Playing around in a Lab environment, we deleted the Broker reference via the Toolkit. The actual Broker is just fine, as is the Config Manager. Messages are flowing thru the Broker.
So now we have to get our reference back. I know we just can't add the Broker back in via the Toolkit, since the new reference will have a new UUID. We have to "adopt" the existing Broker.
I searched and searched in the Info Center and all I found was this:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/an25660_.htm
But these are instructions for if you lose your entire config manager without a config manager back up. Since I have my original config manager in a healthy state, do I just use these instructions but only do Step 4? And then eventually redeploy to pick up the missing references to Message Sets? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
mqmatt |
Posted: Mon Dec 15, 2008 6:18 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
Yes, that's fine.. To add a lost broker back to your healthy Config Mgr, follow the instructions from the an25660 topic link you gave, omitting step 1. |
|
Back to top |
|
 |
ghoshly |
Posted: Wed Dec 17, 2008 3:57 am Post subject: |
|
|
Partisan
Joined: 10 Jan 2008 Posts: 333
|
We can have a simple solution out there... In the error message of the toolkit both the Old and New UUID is present. Just take the Old UUID, go the Proxy exerciser..and there is a button to set UUID for the broker. Set that Old one copied earlier. This has worked for me..  |
|
Back to top |
|
 |
|