| Author |
Message
|
| Shalini |
 Posted: Wed May 08, 2002 2:44 am Post subject: |
 |
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hi,
Iam using MQSI2.1 Config Mgr(NT) & MQSI2.0.2 on AIX
When I have deleted my AIX Broker from Config Mgr & again tried redploying my NT Broker It gives me following error as below
BIP1510E: Unable to deploy configuration data.
An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker QM_MQSIAIX_BROKER. You can not deploy to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy operation was not performed.
Wait for the outstanding deploy to complete before retrying the operation. The Log view may be used to check that all responses to the outstanding deploy have been received and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers exist and are running, all MQSeries queue managers are running, and that all channels between queue managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then retry the deploy operation specifying the 'Forced' option which overrides any outstanding deploy. Note that 'Forced' causes all configuration throughout the entire domain to be re-deployed so you may not have authority to perform this. The 'Forced' option may only be selected when deploying 'Complete configuration (all types)' from the File menu.
Note:
1) But the broker is not in the operation Pane nor in AssignmentPane nor in Topolgy Pane
2) All MQSeries queue managers are running, and that all channels between queue managers are Active.
3) No message in Dead Letter Queue
4) No Error shown by Event Viewer
How to solve this problem please if any one can help me out
|
|
| Back to top |
|
 |
| kirani |
| Posted: Wed May 08, 2002 8:13 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
1. Have you removed the reference to your broker before running mqsidelebroker command on AIX box?
2. Did you perform complete deploy of the Topology after deleting the broker?
3. Have you tried doing a force deploy of the complete configuration?
4. Do a refresh on your Operations view and see if the AIX broker is still showing up there.
_________________
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 |
|
|
| Shalini |
| Posted: Wed May 08, 2002 9:44 pm Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Have you removed the reference to your broker before running mqsidelebroker command on AIX box?
Yes , actually I have given mqsistop & mqsideletebroker
2. Did you perform complete deploy of the Topology after deleting the broker?
Yes but it is failing
3. Have you tried doing a force deploy of the complete configuration?
Yes it is sucessfull telling that the broker is deleted
4. Do a refresh on your Operations view and see if the AIX broker is still showing up
I did the refresh view on Operation Pane but Broker is not present there
|
|
| Back to top |
|
|
| kirani |
| Posted: Thu May 09, 2002 8:19 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Since your broker is not showing up in operations pane, looks like it has been deleted successfully.
To delete a broker you should do following,
1. Checout the topology.
2. click on the broker you want to delete and select Delete from popup menu.
3. Checkin the topology.
4. Do a complete deploy of the topology.
5. Stop the broker.
6. issue mqsideletebroker command.
See if your NT broker is deploying successfully.
_________________
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 |
|
|
| jimtg |
| Posted: Thu May 09, 2002 8:31 am Post subject: |
|
|
Guest
|
Hello .. the problem could be with the data retained in the configmgr db.
Certainly for 2.0.1 the configmgr db entries had to be "manualy" deleted
via the following
To clean up the configmgr database of old broker entries.
.
At a command prompt - type db2cmd - This will open a DBCLP command
window
On the DB2CLP command window type in db2 # This should give you a
db2 => prompt
Connect to MQSICMDB user (<dbuserid>) using (<dbpasswd>)
# This should give you the connection information
# Note the dbuserid/dbpasswd are the values used
# to connect to MQSICMDB when creating the configmgr
select * from CBROKER where CNAME like 'MQSI_AIX_BROKER'
# I expect this to show 2 or more records selected.
# use own broker name for MQSI_AIX_BROKER
delete from CBROKER where CNAME like 'MQSI_AIX_BROKER'
# deletes the hanging entries in configmgr db for old
broker
quit
At the same time check for the following
Check CBROKER table of configmgr database :
a. Any containing DPLING in the CSECTION column for the old broker (outstanding deploymet)
b. Any containing GRAVEY in the CSECTION column for the old broker (graveyard)
Remove these entries if they exist.
|
|
| Back to top |
|
|
| Shalini |
| Posted: Thu May 09, 2002 8:42 am Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Really Good Solution
I have succesfully done after removing the old broker from the ConfigMgr db
This is really good solution
Thanks jimtg
|
|
| Back to top |
|
|
|
|
