| Author |
Message
|
| kumarp |
 Posted: Tue Mar 30, 2004 9:02 am Post subject: Can't remove broker from WBIMB 5.0 config repository! |
 |
|
Novice
Joined: 20 May 2003
Posts: 23
|
Hi,
I'm fairly new to the Integrator, so please bear with me!
I'm running WBIMB 5.0 (CSD 01), workbench and config mgr. on my Windows XP machine, and WBIMB 5.0 (CSD 01)and WMQI 2.1 (CSD05) brokers on z/OS.
I am trying to delete a z/OS broker and then I want to recreate it (same name, same queue manager, just made some changes to the database naming comventions).
I followed the WBIMB help documentation that basically said to:
1) Remove broker from broker domain in workbench and deploy
2) stop broker
3) delete broker database
4) mqsideletebroker on z/os
The part I'm having trouble with is removing the broker from the broker domain. I right clicked on the broker name, chose delete, and then deployed. All of my brokers (including the one that I am trying to delete) replied that the deploy was successful, and the broker is no longer shown in the broker domains view or in the topology. I did not get any messages back from the configuration manager saying that the broker has been deleted from there.
so then I went on and deleted the physical broker itstelf on z/OS and then recreated it. The last step in recreating it is to create the broker in the broker domain on the workbench...but when I try to do that, I get the following messages:
================================================
--------------------------------------------------------------------------------------
================================================
BIP1511E: Queue manager 'CSQ3' cannot be associated with broker 'CSQ3BRK'; it is already associated with broker 'CSQ3BRK'.
An attempt was made to associate broker CSQ3BRK with WebSphere MQ queue manager CSQ3, but broker CSQ3BRK 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 CSQ3BRK 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.
____________________________________________________________
BIP1711W: Broker is not accessible or does not exist.
An attempt was made to register for information on the Broker with UUID '6a4eb59c-fb00-0000-0080-ce5543798705', but either the user who asked for the information does not have sufficient authority to do so or the Broker does not exist.
Ensure that the user of the application that issued the request has sufficient authority to view the Broker. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1711W: ExecutionGroup is not accessible or does not exist.
An attempt was made to register for information on the ExecutionGroup with UUID '6b4eb59c-fb00-0000-0080-ce5543798705', but either the user who asked for the information does not have sufficient authority to do so or the ExecutionGroup does not exist.
Ensure that the user of the application that issued the request has sufficient authority to view the ExecutionGroup. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1520I: Deploy operations successfully initiated.
The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers: CSQ1BRK, CSQ2BRK, CSQABRK . Deleted brokers: CSQ3BRK .
Open the Event Log Editor to check the outcome of the operations. There will be a separate set of log messages for each broker.
================================================
--------------------------------------------------------------------------------------
================================================
Apparently, the config mgr still has information about the old broker...but I don't know how to delete it!
Any suggestions? I would really appreciate any help I can get!!!
Thanks! |
|
| Back to top |
|
 |
| morpheus |
| Posted: Tue Mar 30, 2004 12:01 pm Post subject: delete broker from the database |
|
|
Acolyte
Joined: 08 Mar 2003
Posts: 72
Location: Austin, TX
|
I had the same problem in WMQI2.1 control center. I had to delete the broker from the configuration manager database.
You need to delete the rows that belong to this broker from the CBROKER table in Config mgr database.
The sql statement looks like this
delete from CBROKER where CNAME = 'YOURBROKER';
-Morpheus |
|
| Back to top |
|
|
| kumarp |
| Posted: Wed Mar 31, 2004 10:45 am Post subject: |
|
|
Novice
Joined: 20 May 2003
Posts: 23
|
Thanks for your help; that worked perfectly!
Does anyone know why sometimes you have to go into the config. manager tables and delete entries? Seems like the user shouldn't ever have to go into those tables...just wondering if this is a valid problem that should be reported to IBM.
Thanks! |
|
| Back to top |
|
|
| waugh |
| Posted: Wed Mar 31, 2004 10:49 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
STEP1 : delete broker from broker topology and do a complete deployment
STEP2: delete broker using mqsideletebroker
if above both steps went successful, then you dont need to do delete anything in database tables..
hope this helps |
|
| Back to top |
|
|
| kumarp |
| Posted: Wed Mar 31, 2004 11:02 am Post subject: |
|
|
Novice
Joined: 20 May 2003
Posts: 23
|
Hi,
Yes I understand that the steps you mentioned:
| Quote: |
STEP1 : delete broker from broker topology and do a complete deployment
STEP2: delete broker using mqsideletebroker
|
need to be completed in that order. That is the normal and desired case. But I found that I followed those steps and the broker still wasn't removed from the config manager until I deleted entries in the CBROKER table in config. manager database, as instructed by Morpheus above (thanks Morpheus!). What I would like to know is if many others have had this trouble in the past besides Morpheus and me, and if anyone has any idea why this happens sometimes or if it is a valid problem that should be opened with IBM.
Thanks! |
|
| Back to top |
|
|
| morpheus |
| Posted: Wed Mar 31, 2004 12:38 pm Post subject: Happened only once. |
|
|
Acolyte
Joined: 08 Mar 2003
Posts: 72
Location: Austin, TX
|
I wasn't sure whether I followed the exact steps when this problem occurred for the first time. Later on I followed the instructions exactly and never had this problem. Are you sure that you followed the steps described in the manual?
If I were you I would simulate the scenario and see how it works.
-Morpheus |
|
| Back to top |
|
|
| waugh |
| Posted: Thu Apr 01, 2004 7:33 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
Kumar,
I had the similar problem with broker and even with one of our execution groups and had to go to database and delete the records.
spoke to IBM a couple of times, they do not have a answer what causes this .. the only thing i remember is check the communication between broker and configmgr (channels). if your deploy is taking more time than it would normally takes, (to record in error logs...)
Solution:
stop start channels
it looked like a solution coz my broker delete and deploy took more time and received errors at that time.
but, thats not the case always...other deploys worked fine while i had problem with execution group... |
|
| Back to top |
|
|
| waugh |
| Posted: Thu Apr 01, 2004 7:58 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
You might want to check on rows in tables CBROKER, CEG for
WHERE CSECTION = 'DPLING'; (deploying and never completed)
and delete those rows...then redeploy... |
|
| Back to top |
|
|
|
|
