| Author |
Message
|
| prk |
 Posted: Fri Sep 16, 2005 7:07 pm Post subject: BIP2045E - Can it be solved without deleting the Broker |
 |
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
WBIMB 5.0 CSD03
Production Broker on AIX and ConfigMgr on Windows 2000
Current ConfigMgr server is going to be taken away, so I am installing a new configmgr on a new server and this has to connect to the existing Broker on Production AIX.
-------------------------- From old machine -------------
Deleted the Broker from Toolkit and did a complete deploy but it failed with BIP2045E
Cannot delete and re-create the Broker as it is in Production
-------------------------- New machine -------------------
Tried to connect the old Production Broker to the new ConfigMgr but fails with BIP2045E
--------------------------------------------------------------
Are there any other options other than me deleting the Production Broker to get it to work properly with the new server. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Sep 17, 2005 6:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Quote: |
| Are there any other options other than me deleting the Production Broker to get it to work properly with the new server. |
No.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sjensen |
| Posted: Sun Sep 18, 2005 1:28 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Well if you are feeling brave you could change the Broker UUID using mqsiservice.
| Code: |
mqsiservice ${BrokerName}> ${broker_name}.old_services
stop broker
mqsiservice ${BrokerName} -r BrokerUUID=${UUID_CfgMgrExpect}
start broker |
As this is production you need to check with IBM - I am not convinced this is supported.
Cheers
Stefan |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Sep 19, 2005 6:56 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Correct - mqsiservice is not supported. The official route is to delete and recreate the broker.
In v6 it will be possible to set the UUID of a broker reference in the Config repository. This will allow the Config Manager to start deploying to the broker, but the Config Manager will not then find out what was already running on that broker.
-Matt |
|
| Back to top |
|
|
| prk |
| Posted: Mon Sep 19, 2005 10:34 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Thanks for your replies..
I guess I will have to delete the Broker, Broker database, recreate the Broker database, the Broker and try to connect with the new ConfigMgr. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 19, 2005 11:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't need to delete the broker database.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prk |
| Posted: Mon Sep 19, 2005 11:15 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
ok,
So I can just do a mqsideletebroker Broker, reacreate the Broker. All the channels are already defined with the new configmgr. So, I should be able to add the new Broker to the Toolkit once its created right ?
Do I need to re-create the ConfigMgr database and recreate the new configmgr ?
_________________
Thank You,
Varma |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 19, 2005 11:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You shouldn't need to touch the new configmgr...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prk |
| Posted: Mon Sep 19, 2005 11:22 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Thanks for your help. will give it a try once I can get a scheduled outage for Production.
_________________
Thank You,
Varma |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 19, 2005 11:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Actually, you might need to delete the bad registration for the broker on the new configmgr before you try again. This would be just deleting it from the toolkit... but the registration shouldn't have gone through.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prk |
| Posted: Sun Sep 25, 2005 12:10 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Actually this did not work
Deleting the broker
Re-creating the broker
Connecting from the Configmgr to the new Broker failed with BIP2045E.
I had to follow these steps to resolve it.
stop the newly re-created broker on AIX
cd /var/mqsi/registry/(Brokername)
check that the BrokerUUID file size is 36 bytes
mqsiservice Brokername -r BrokerUUID=""
check that the BrokerUUID file size is 0 bytes
grab the second UUID (36 characters) from the BIP2045E error message description from the Toolkit
mqsiservice Brokername -r BrokerUUID="put the second 36 character UUID from the toolkit 2045 error message"
start the broker
Try connecting to the broker from the toolkit and perform complete deploy
Deploy MSGFlows, MSGSets, etc.. |
|
| Back to top |
|
|
| tanbsj |
| Posted: Fri Oct 20, 2006 2:40 am Post subject: BIP2045E - Can it be solved without deleting the Broker |
|
|
Novice
Joined: 08 Jun 2003
Posts: 16
|
Hi Prk,
Read your posting regarding delete and recreate broker also
cannot solved the BIP2045E problem.
Therefore you use another method by changing the registry of
broker in AIX. Thereafter you are able to deploy your workflow.
Need to ask whether will there be any inpact on the AIX side, as
our CM win2k server was down due to harddisk error, we need to
setup a new CM to connect with the Broker in AIX, however we encountered the following error in CM
BIP1536S
BIP2087E
BIP2045E
Please kindly advise me what I should do.
Thank you. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Oct 20, 2006 5:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Start a new thread with a new problem.
If you've lost your ConfigMgr entirely, with no backups, you will need to delete and recreate your brokers (without deleting the database for the brokers!) and then re-register them to the new configmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
