|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
BIP1510E Unable to deploy |
« View previous topic :: View next topic » |
Author |
Message
|
ramires |
Posted: Mon Mar 23, 2009 2:33 am Post subject: BIP1510E Unable to deploy |
|
|
Knight
Joined: 24 Jun 2001 Posts: 523 Location: Portugal - Lisboa
|
Hello all,
I'm having a BIP1510E Unable to deploy message. My Cfmgr and Broker are in AIX, each one has his queue manager and version is 6.1.0.3. I believe I did all the suggested steps to recover from this, but no success. I found an old post here about the internal Cfmgr DB and one possible solution is to remove an entry from CBROKER table, CSECTION field et to DPLING. Can this be done?
When I do a mqsimct I have two entries for the same broker, is is "normal"
Thanks!
joao
Row 1
CUUID - cc130e41-1f01-0000-0080-cea64701e98a
CSECTION - SHARED
CNAME - BRS0ENG1
CQMANAGER - MQS0BRK1
CSTATUS - 10000000
CSUBSCRIBED - N
CXMLDATA - <?xml version="1.0" encoding="UTF-8"?><Broker configMgrQMgr="MQS0CFM1"
CLASTUPDATE - 2009-03-23 09:29:47.371
Row 2
CUUID - cc130e41-1f01-0000-0080-cea64701e98a
CSECTION - DPLING
CNAME - BRS0ENG1
CQMANAGER - MQS0BRK1
CSTATUS - 10000100
CSUBSCRIBED - Y
CXMLDATA - <Broker LastBrokerRegistry="2009-03-13 16:41:59" LastConfigurableServices="2009-03-13 16:41:59"
CLASTUPDATE - 2009-03-13 17:44:07.97
Row 3
CUUID - cc130e41-1f01-0000-0080-cea64701e98a
CSECTION - DEPLED
CNAME - BRS0ENG1
CQMANAGER - MQS0BRK1
CSTATUS - 10000100
CSUBSCRIBED - Y
CXMLDATA - <Broker LastBrokerRegistry="2009-03-23 09:02:18" LastConfigurableServices="2009-03-23 09:02:17"
CLASTUPDATE - 2009-03-13 17:44:07.97 |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Mar 23, 2009 5:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Any time you find anything telling you to mess around with the configmgr's internal repository, you are looking too hard.
Don't do anything like this outside of specific instructions from IBM support received through a PMR.
Post a significantly better description of your actual problem, rather than the rather sketchy solution you think you've found.
What other messages come up when you get BIP1510? What does the documentation on BIP 1510 say to do to resolve it? What changed when you WERE able to deply so that now you aren't able to deploy? |
|
Back to top |
|
 |
ramires |
Posted: Mon Mar 23, 2009 6:51 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001 Posts: 523 Location: Portugal - Lisboa
|
|
Back to top |
|
 |
mqjeff |
Posted: Mon Mar 23, 2009 7:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
ramires wrote: |
but.. I manage to solve this! I did a config manager backup, used proxy api to delete references to a previous broker, and adopt the broker. |
Excellent! Well done
That's a very good solution, and much better than playing with the internal tables. Thanks also for posting the resolution, so that next time someone has more information to solve the same problem. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|