| Author |
Message
|
| udaybho |
 Posted: Mon Jun 03, 2002 1:49 pm Post subject: BIP2045E while deploying broker |
 |
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
My broker is on AIX 4.3.3/MQSI 2.1/MQ 5.2
Configuration mgr on NT 4.0 service pack 6a/mqsi2.1/mq 5.2
When I am trying to deploy my Broker I am getting following error: BIP2045E, BIP2087E, BIP1536S
Does any one faced this problem ?
>>>>>>>>>>>
BIP2045E: Broker DQAT001.BROKER (UUID 75d57723-ee00-0000-0080-c84a08a1c93b) running on WebSphere MQ queue manager 'DQAT001' could not process an internal configuration message because the broker identity received in the message (UUID 9e6dcc37-ee00-0000-0080-c84a08a1c93b) did not match that of this broker.
An internal configuration message could not be processed and was rejected. Each broker is identified by a universally unique identifier called a UUID which is allocated when the Control Center user creates a definition for the broker. The configuration message received contained a broker UUID (9e6dcc37-ee00-0000-0080-c84a08a1c93b) that does not match the UUID of broker DQAT001.BROKER running on WebSphere MQ queue manager DQAT001. There are two possible reasons for this. Either a Control Center user has accidentally specified queue manager DQAT001 when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker DQAT001.BROKER was deleted and recreated on the Control Center which has the effect of giving broker DQAT001.BROKER a new, different UUID.
If the queue manager name specified in the Control Center was incorrect then use the Control Center to correct the broker definition in error. The mqsilist command may be used to display broker queue manager names. Otherwise, if the broker definition was deleted and recreated, you must use the mqsideletebroker and mqsicreatebroker commands to recreate the broker, then redeploy the configuration for the broker in order to re-establish the correct broker identity. To avoid loss of data when recreating the broker, make sure that you follow the sequence of actions defined in the WebSphere MQ Integrator Administration Guide section 'Recovery and restart'.
>>>>>>>>>>>>
BIP2087E: Broker DQAT001.BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
>>>>>>>>>>>
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker DQAT001.BROKER.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker DQAT001.BROKER was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker DQAT001.BROKER. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.
Thanks for your help
Uday Bhosle |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Jun 03, 2002 1:54 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Is there any message logged into NT Event Log?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| udaybho |
| Posted: Mon Jun 03, 2002 2:00 pm Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Yes three messages and all three corresponds to three errors. I can tell you because description of the events is same as I posted from LOG tab.
Thanks for quick consideration.
Uday Bhosle |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jun 03, 2002 2:41 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Uday,
By any chance did you deleted the broker DQAT001.BROKER on AIX without deleting it from the topology and recreated it with the same name (DQAT001.BROKER) on AIX?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| udaybho |
| Posted: Mon Jun 03, 2002 2:53 pm Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Kiran,
Yes I did, but I realized my mistake and to rectify this problem I did following steps:
1. Deleted the Broker (DQAT001.BROKER )form Topology. Operations tab also shows no broker.
2. Check in the Topology. Now I have no broker defined
3. Delete the Broker on AIX.
4. Recreate broker (DQAT001.BROKER ) using mqm as serviceId. (log in as mqm)
5. Use mqsichangebroker to change serviceis as mqsiuid ( log in as root)
6. Restart broker (DQAT001.BROKER )( log in as mqsiuid).
7. Add the broker (DQAT001.BROKER ) under topology.
I am still using the same workspace in control center.
Uday Bhosle |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jun 03, 2002 3:06 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Uday,
After Step 2 I don't see deploy of the topology.
You should do a complete deploy of the topology after deleting the broker from topology.
If you can, try deleting the broker from the topology again and do a complete deploy of the topology. Verify whether the broker is deleted or not by going to operation view and do a refresh. You don't have to delete the broker on AIX for doing this.
Now do following in Topology view,
1. Checkout topology.
2. Create broker (give same queue manager name and broker name).
3. Checkin the broker (in topology view.)
4. Checkin the topology.
5. Do a complete deploy of the topology.
6. Goto operation view and do a refresh. Here you should see the newly added broker.
Make sure your broker is running on AIX and the channels are up.
You should be all set after this.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| udaybho |
| Posted: Mon Jun 03, 2002 3:45 pm Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Kiran, sorry I forget to write the step in my post but I did deploy after I removed the broker reference.
Also I forget to mention when I do so I get this error again, which is obvious as the DQAT001.BROKER is never recognizing the request.
The only difference is I do not get BP1536S instead I am getting BIP1540I:
>>>>>>
BIP1540I: Broker DQAT001.BROKER has been removed from the configuration repository.
Broker DQAT001.BROKER was deleted using the Control Center and a deploy operation subsequently attempted to remove all configuration data. Either the deploy operation succeeded, or the broker was found to no longer exist on the target queue manager, as indicated by earlier messages. Accordingly the Configuration Manager has removed all trace of the broker from the configuration repository.
No user action required. If you refresh the Control Center Operations view the broker will no longer be shown.
>>>>>>
I had tried the steps you mentioned. I am getting the same result again and again.
I checked MQSICMDB CBROKER table and after every removal and I do not see any records in it. My operations tab shows no broker after I remove broker.
Thanks for your prompt reply.
Uday Bhosle |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jun 03, 2002 6:52 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Uday,
For some reason information in your broker database and configuration database is not consistent with your view.
If this is a test machine then try deleting the broker again. This time you delete the broker database also. Before your delete broker makes sure you follow above steps discussed in earlier post of deleting broker reference (from topology).
Now recreate the broker, queue manager and database again. Add the broker again to the topology and do a complete deploy of the topology.
Do you have latest CSD applied on broker machine?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| udaybho |
| Posted: Tue Jun 04, 2002 12:29 pm Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Thanks kiran,
I am running broker with CSD02. I am running on development box so I had already tried what you had suggested in last post. Still no luck
Now I am suspecting my configuration Manager. I have my MQSICMDB on Db2 6.2 Personal edition (NT workstation 6a), does anyone think that could be a problem ?
We have asked for IBM help too and waiting for their response.
Uday Bhosle |
|
| Back to top |
|
|
| v_rajasekhar |
| Posted: Tue Jun 04, 2002 12:59 pm Post subject: |
|
|
Newbie
Joined: 23 Oct 2001
Posts: 8
|
Uday,
Could you please delete the broker information from DB2 MQSICMDB repository by using DB2 control center and then try to create broker from topology panel. Lets test your luck
Go to DB2 control center-->Databases-->MQSICMDB-->Tables and then Right click on CBROKER table and check the contents and delete the appropriate records. Then restart the ConfigMgr and ControlCenter and try it again..
Raj |
|
| Back to top |
|
|
| udaybho |
| Posted: Tue Jun 04, 2002 3:01 pm Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Raj,
I can try your suggestion with two scenario.
1. When I request the complete deployment after creating Broker reference. I see two records in CBROKER ( I do not know why two records) and I do not think it is right to delete these records.
2. Second scenario is when I remove the broker and redeploy (complete delpoy). I do not see any records in CBROKER.
So at any rate second scenario is deleting all brokers records from CBROKER table.
Thanks for your suggestion.
Uday Bhosle |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Jun 04, 2002 5:39 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Uday,
This means your configuration database is correct.
Since you have already gone through the process of deleting and recreating brokers many times by now, I think you should try it one more last time by deleting all broker components (broker, database, queue manager, workpath files) once and recreate them (without using mqsichangebroker command). I would prefer to restart my machines before recreating them, just in case 
Wish you a very good luck!
Regards,
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| udaybho |
| Posted: Wed Jun 05, 2002 9:31 am Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Well I created new Broker using different name and it work. Looks like with this installation I can not use my existing name.
Thanks for all your help.
Uday Bhosle  |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Thu Jun 06, 2002 9:11 am Post subject: I am getting same problem.... |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
I got the same problem, my local machine is having two brokers..i deleted one broke with mqsidele...then deleted form topolgy, then i did complete deploy. After that i created the broker with the same name with same queuemanager name in topology, but now the quemanager and broker are running on AIX. when i did complete config deploy i am getting the error saying UUID problem. I deleted all entries in Config database before creating and deploying the broker to config. how to get rid of this problem. I cant delete the broker which is running on AIX. Is there any way to create the same broker with out deleting the ConfigMgr Database.
Thanks in advance...
Chandra. |
|
| Back to top |
|
|
| udaybho |
| Posted: Thu Jun 06, 2002 9:30 am Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
>..i deleted one broke with mqsidele...then deleted form topolgy, then i >did complete deploy.
You should do the reverse way. First you should delete from COntrol Center, do complete deploy and then delete using mqsideletebroker. The procedure is documented in "Administration" book.
>. I cant delete the broker which is running on AIX.
What do you mean by you can not delete ? Is it access problem ? Are you getting some error ?
In my case even IBM support is not able to figure out the problem, so they recommened to create different broker with different name.
Uday Bhosle |
|
| Back to top |
|
|
|
|
