Author |
Message
|
Atlanta06 |
Posted: Thu May 31, 2007 2:04 pm Post subject: Unable to add broker to config mgr |
|
|
Novice
Joined: 29 Nov 2006 Posts: 11
|
I deleted the broker from Config manager and tried adding it.But its not working.
Broker and its associated QM are running.I reset the MQ channels between broker and config mgr.Also deleted some rows from the config mgr tables.
Is there anything I need to do? |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu May 31, 2007 2:12 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Given that you've failed to read the documentation before starting, and that you've failed to read the documentation when you found out you did something wrong, and that you've done a few different random things....
You probably need to delete everything and start over. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Atlanta06 |
Posted: Thu May 31, 2007 2:16 pm Post subject: |
|
|
Novice
Joined: 29 Nov 2006 Posts: 11
|
jefflowrey wrote: |
Given that you've failed to read the documentation before starting, and that you've failed to read the documentation when you found out you did something wrong, and that you've done a few different random things....
You probably need to delete everything and start over. |
Thanks for the prompt response.The info center does nto provide much info on this issue.What's the other documentation that can help?
What do I need to delete?
I already deleted the broker recreated it using the create cmd.I still get the same issue. |
|
Back to top |
|
 |
gkorodi |
Posted: Thu May 31, 2007 4:49 pm Post subject: Unable to attach broker to ConfigManager |
|
|
Novice
Joined: 28 Sep 2003 Posts: 13 Location: Boston-London-Budapest
|
What is the actual error? IBM would ask you for the envionment "env | sort > environment.txt" and probably for the trace file. Where is the error generated? Can you start the broker?
Also, when deleting the broker, you should delete it from the ConfigManager first, before running mqsideletebroker.
Post some error messages from wmb or from wmq and what version are you using. _________________ Gabe "The Hun" Korodi |
|
Back to top |
|
 |
Atlanta06 |
Posted: Thu May 31, 2007 6:00 pm Post subject: |
|
|
Novice
Joined: 29 Nov 2006 Posts: 11
|
I'm getting BIP2045E which is mismatch b/w UUID's |
|
Back to top |
|
 |
gkorodi |
Posted: Thu May 31, 2007 6:08 pm Post subject: |
|
|
Novice
Joined: 28 Sep 2003 Posts: 13 Location: Boston-London-Budapest
|
Indeed, that seems to be an indication that you did not delete the broker from the ConfigMgr's domain.
You can check the UUID of the new broker in
$MQSI_REGISTRY/$BROKER_NAME/BrokerUUID file. and using the ConfigMgr proxy reset it. That is the cleanest way.
Once you use the proxy, you will see that the ConfigMgr thinks what the UUID is.
I would not mess with the derby database (which is where it is still stored as the old UUID)! _________________ Gabe "The Hun" Korodi |
|
Back to top |
|
 |
Atlanta06 |
Posted: Fri Jun 01, 2007 3:22 am Post subject: |
|
|
Novice
Joined: 29 Nov 2006 Posts: 11
|
gkorodi wrote: |
Indeed, that seems to be an indication that you did not delete the broker from the ConfigMgr's domain.
You can check the UUID of the new broker in
$MQSI_REGISTRY/$BROKER_NAME/BrokerUUID file. and using the ConfigMgr proxy reset it. That is the cleanest way.
Once you use the proxy, you will see that the ConfigMgr thinks what the UUID is.
I would not mess with the derby database (which is where it is still stored as the old UUID)! |
Thanks for the help.
This is what I did and its working for now.I went the Config mgr db and got the UID for the broker.Then I changed the UUID for the broker in the Broker UUID file using mqsiservice.and restarted the broker.The broker is now working but I still get a message in the event log that internal subscriptions are not found. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jun 01, 2007 3:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
jefflowrey wrote: |
You probably need to delete everything and start over. |
_________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
gkorodi |
Posted: Fri Jun 01, 2007 4:02 am Post subject: |
|
|
Novice
Joined: 28 Sep 2003 Posts: 13 Location: Boston-London-Budapest
|
you might want to delete everything like jeff said, but make sure you delete the broker from the config manager first. either through the toolkit, or through the proxy. Now that the ConfigManager knows about the broker again, but you probably have the subscription table under a different broker id.
It is better to change the UUID in the ConfigManager than mess with just one piece of the broker. _________________ Gabe "The Hun" Korodi |
|
Back to top |
|
 |
Atlanta06 |
Posted: Fri Jun 01, 2007 4:58 am Post subject: |
|
|
Novice
Joined: 29 Nov 2006 Posts: 11
|
Jeff,
When you say 'everything',do u mean to include the config mgr also?
By the way is there any documentation on configuration proxy? |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jun 01, 2007 5:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Atlanta06 wrote: |
When you say 'everything',do u mean to include the config mgr also? |
Why wouldn't I include configmgr in "everything", particularly when you've gone ahead and played around with the configmgr's private database?
Atlanta06 wrote: |
By the way is there any documentation on configuration proxy? |
Sure. It's in the same place as the documentation that tells you how to do this properly, and gives you at least some suggestions for what to do when you've done this incorrectly. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
gkorodi |
Posted: Fri Jun 01, 2007 6:25 am Post subject: |
|
|
Novice
Joined: 28 Sep 2003 Posts: 13 Location: Boston-London-Budapest
|
|
Back to top |
|
 |
Atlanta06 |
Posted: Sat Jun 02, 2007 7:46 am Post subject: |
|
|
Novice
Joined: 29 Nov 2006 Posts: 11
|
|
Back to top |
|
 |
|