| Author |
Message
|
| rmah |
 Posted: Wed Feb 27, 2008 1:57 pm Post subject: BIP1533E: Broker confusion!!! |
 |
|
Centurion
Joined: 04 May 2007
Posts: 142
|
I'm sorry if I've posted this before, but I'm getting this error message when deploying configuration topology:
BIP1533E: Unable to deploy configuration data: unknown WebSphere MQ queue manager VXTAP004 associated with broker mqbroker_01.
An attempt was made to deploy configuration data to one or more brokers. The WebSphere MQ queue manager VXTAP004 associated with broker mqbroker_01 is not known to the Configuration Manager's WebSphere MQ queue manager. The deploy operation was not performed.
Check that the name of the queue manager is spelled correctly. Note that WebSphere MQ queue manager names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager VXTAP004, or a transmission queue called VXTAP004, is defined to the Configuration Manager's queue manager. For more information on this error see the WebSphere MQ Application Programming Reference manual, code {2}.
mqbroker_01's queue manager is mqbroker_01, not VXTAP004. Is there anyway to fix this issue without deleting the broker/config. manager? Edit the registry somehow?
Thanks in advanced!
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux
Last edited by rmah on Wed Feb 27, 2008 2:15 pm; edited 1 time in total |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Feb 27, 2008 1:58 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
CMP API Exerciser.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Feb 27, 2008 2:00 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| jefflowrey wrote: |
| CMP API Exerciser. |
Thanks! I've been explorering this tool.
This is what's listed for mqbroker_01:
getQueueManagerName(): mqbroker_01
Not VXTAP004.
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 27, 2008 3:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What Jeff meant is that you probably have a reference for a deleted broker which used to have said qmgr as qmgr.
You need to remove all references to a previously deleted broker...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Feb 27, 2008 3:41 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| fjb_saper wrote: |
What Jeff meant is that you probably have a reference for a deleted broker which used to have said qmgr as qmgr.
You need to remove all references to a previously deleted broker...
Enjoy |
So currently, I have a message broker mqbroker_01 with qmgr mqbroker_01. In the past, there probably was mqbroker_01 with qmgr VXTAP004. Could I safely remove references to previously deleted broker mqbroker_01 (old one) without affecting the current one?
Thanks
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 27, 2008 3:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
only if you can use the deleted broker's uid for the deletion... and if it has not been reused since...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Feb 27, 2008 3:57 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| fjb_saper wrote: |
| only if you can use the deleted broker's uid for the deletion... and if it has not been reused since... |
Ah, of course.
Any way to find out the UUID of the previous deleted broker? I've been exploring the API proxy and can't find it...
Thanks for all the help!
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Feb 28, 2008 4:34 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
If you have your old event logs, the UUID should be listed in BIP2201 messages for the old broker.
If you can't find it there, you can browse for the old UUID in the Config Manager's repository by using (and apologies in advance, this is a bit hard core  )
| Code: |
| mqsicmdt CONFIG CBROKER |
where CONFIG is the name of your Config Manager.
Alternatively in the remove-deleted-references option in the API Exerciser, just specify the name of the broker rather than the UUID - though that will delete the new broker defined with that name in addition to the old one. |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Mar 12, 2008 4:17 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| mqmatt wrote: |
If you have your old event logs, the UUID should be listed in BIP2201 messages for the old broker.
If you can't find it there, you can browse for the old UUID in the Config Manager's repository by using (and apologies in advance, this is a bit hard core )
| Code: |
| mqsicmdt CONFIG CBROKER |
where CONFIG is the name of your Config Manager.
Alternatively in the remove-deleted-references option in the API Exerciser, just specify the name of the broker rather than the UUID - though that will delete the new broker defined with that name in addition to the old one. |
I get this error 
SQL Exception: Failed to start database '/var/mqsi/components/mqconfig_01/BERNARD', see the next exception for details.
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java)
at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection20.<init>(EmbedConnection20.java)
at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(EmbedConnection30.java)
at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Driver30.java)
at org.apache.derby.jdbc.Driver169.connect(Driver169.java)
at java.sql.DriverManager.getConnection(DriverManager.java:559)
at java.sql.DriverManager.getConnection(DriverManager.java:211)
at com.ibm.broker.config.util.DisplayTable.main(DisplayTable.java:52)
Exit
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| dswift |
| Posted: Wed Jul 02, 2008 8:25 am Post subject: mqsicmdt command fails |
|
|
Newbie
Joined: 19 Feb 2003
Posts: 2
|
| The configuration manager cannot be running when you execute the mqsicmdt command |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Jul 02, 2008 9:25 am Post subject: Re: mqsicmdt command fails |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| dswift wrote: |
| The configuration manager cannot be running when you execute the mqsicmdt command |
Thanks! It works 
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
|
|
