| Author |
Message
|
| KIT_INC |
 Posted: Fri Oct 16, 2009 9:33 am Post subject: Deleting the broker Qmgr |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
Is there a way to delete and recreate the current broker Qmgr? I am running message borker V60 and V61 of AIX?
We have some problem with the existing QMgr and need to delete and recreate it. Can I delete current broker Qmgr and recreate a new one with the same name. I know that the QMID is different. I was told that there is a way (perhaps using the config proxy) to reconnect the current broker with the new Qmgr. Is that right? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Oct 16, 2009 9:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Take a good backup first using support pack MS03 and include the system objects... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Fri Oct 16, 2009 10:08 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| Thanks, I'll do that to ensure that I can restore all my Qmgr objects and authority. But I still need to know if there is a way to reconnect the current broker to the newly created Qmgrs with the same name? I am trying to avoid backup, deleting, recreate, restore the broker. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 16, 2009 10:12 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
IIRC Jeff said a few days ago that you could delete and restore/recreate the qmgr without having to touch the broker... providing that the broker is in stopped state of course...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Fri Oct 16, 2009 12:13 pm Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
Here is what I did
1. delete the broker from my toolkit and do a complete deployment. This is just in case I need to delete the broker later for whatever reason.
2. mqsistop the borker (BKR1) on AIX
3. use ms03 to asve all qmgr object (BKRQM)
4. delete and recreate BKRQM
5. mqsistart BKR1 on AIX
6. Syslog shows no error and mqsilist shows the borker and it execution groups
7. start my toolkit and add try to add the broker back to the ADM perspective. The Broker (BKR1) shows up. However there is only the default execution group under it. This is like a newly created broker.
I know that the original execution groups are there because mqsilist shows them on AIX.
Did I miss something? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Oct 16, 2009 12:19 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Only in WMB 6.1 can you delete a Broker from a Config Maanger and then later add the same Broker back in, called adopting a Broker. This capability does not exist in WMB 6.0 or earlier.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Fri Oct 16, 2009 12:53 pm Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| This is V61 that I am working on. I tried the adopt broker method using CMP with no luck. The broker was the original broker which I did not touch. So the same broker shows up under the config manager. But I still do not see the execution under it. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Oct 17, 2009 4:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
force remove the broker from the config manager. Do not add it again.
Try adopt a broker and see if the broker show up fine.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Tue Oct 20, 2009 5:13 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
I have no problem getting the broker to show up in the config manager except that it shows up like a new broker with only the default execution group under it. But as I mentioned earlier, all the execution groups are running when I do a mqsilist BKR1 on AIX.
What I was trying to avoid is re-deploying all the message flows, set under the execution groups (a total of more than a 100 resources). I must have spend more than two hours trying to get this to work with no luck.
For the sake of time, I have to give up the hope but delete and recreate a new broker with the new Qmgr. Then re-deploy all the resources. This took me less than 45 minutes. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 20, 2009 5:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The only thing you needed to do was issue mqsistop and mqsistart on the Broker.
As long as the queue manager has the same name, and is on the same machine, the Broker doesn't care about the QMID and will just use the queue manager.
You didn't need to delete the broker from the Toolkit or the ConfigMgr, at all. Again, all they know is the name of the broker qmgr. |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Thu Oct 22, 2009 1:59 pm Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
The reason I did that was because in earlier version, if you do not delete the broker from the config mgr and you end up have to delete the broker, you will have errors. (some nad experience from V2 and V5 age). I am not sure how V61 behave so I delete it from the configmgr first to be safe.
The adopt broker in 61, if I understand correctly, is suppose to allow me to pick up an existing broker from another configmgr. I did created a new configmgr and did the adopt broker. However the result is still the same.
The problem I had was not the configmgr (both the existing one and the new one I created) not recognising the broker. The broiker did show up on the toolkit. The problem is all the existing execution group were not displayed. It looks like that the configmgr treat it as a new broker, so only the default execution group shows up.
Is the execution group and deployed flow stored in the config repository? Does the configmgr use the broker name to search for those information? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 23, 2009 4:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
When you deleted the broker from the configmgr, you told it you were getting ready to delete the broker entirely. Consequently the broker threw away all of it's config, including it's EGs and deployed resources.
Again, if all you wanted to do was change the queue manager configuration, you did not have to do anything on the broker side.
If you needed to change the queue manager NAME, you did need to delete everything. Any other configuration change on the qmgr alone required no action. |
|
| Back to top |
|
|
|
|
