Author |
Message
|
Gideon |
Posted: Sat Sep 26, 2009 11:16 am Post subject: New Broker and CGF with existing DB ? |
|
|
Chevalier
Joined: 18 Aug 2009 Posts: 403
|
Now I need to modify the qmgr, specifically, I need to craete
a new qmgr as follows:
Code: |
crtmqm -lp 10 -ls 10 -lf 65535 new_qmgr |
I checked the documentation, and apparently there is no
way to use mqsichangebroker to modify the qmgr used.
So I am planning on using the existing database, and create a new broker and configmgr using the existing database, but a new qmgr, as follows:
Code: |
mqsiprofile
mqsicreatebroker broker2 -i mqm -a pw -q new_qmgr -n DEFBKD61 -t
mqsicreateconfigmgr -i mqm -a pw -q new_qmgr cfg2 |
My question is: will this work
Do I need to create any special queues or channels in the qmgr (I don't see the need in the documentation, I hope I did not miss that) |
|
Back to top |
|
 |
mqjeff |
Posted: Sat Sep 26, 2009 12:55 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It will certainly work.
Whether it does what you want it to do is a different question.
If all you need to do is recreate the queue manager, then just stop broker and use MS03 to back up the qmgr objects you need, and then recreate it. |
|
Back to top |
|
 |
Gideon |
Posted: Mon Oct 12, 2009 3:43 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009 Posts: 403
|
mqjeff wrote: |
It will certainly work.
Whether it does what you want it to do is a different question.
If all you need to do is recreate the queue manager, then just stop broker and use MS03 to back up the qmgr objects you need, and then recreate it. |
I did not back up the objects properly,
I deleted the Qmgr, and recreated it, and now when I try to start the broker I get the following error:
Quote: |
( WBRK61_DEFAULT_CONFIGURATION_MANAGER ) Verification failed for queue ''SYSTEM.BROKER.CONFIG.QUEUE'' on queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER'' while issuing ''MQOPEN''. MQRC: 2085 MQCC: 2
The operation ''MQOPEN'' on the specified queue returned with the indicated WebSphere MQ completion and reason codes.
Typical causes of failures during queue verification are that the queue does not exist, or that the broker is unable to put or get a message.
Check the WebSphere MQ completion and reason codes in the Application Programming Reference section of the WebSphere MQ information center to establish the cause of the error, and take any appropriate action. |
What is worse, the log complains about the absense of the following queues:
Quote: |
SYSTEM.BROKER.CONFIG.QUEUE
SYSTEM.BROKER.CONFIG.REPLY
SYSTEM.BROKER.ADMIN.REPLY
SYSTEM.BROKER.SECURITY.REPLY
SYSTEM.BROKER.MODEL.QUEUE |
I recreated the queues, but the broker will not start
Is there any way to recover from this ?
Thanks |
|
Back to top |
|
 |
mqmatt |
Posted: Tue Oct 13, 2009 4:03 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
|
Back to top |
|
 |
Gideon |
Posted: Tue Oct 13, 2009 6:22 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009 Posts: 403
|
Actually it was the Configuration Manager that would not start.
The Borker starts perfectly.
The Administration Log gives me the errors in my previous post when I try to start the Configuration Manager.
Thanks for the Link. I will try to recreate those resouces and start again. |
|
Back to top |
|
 |
Gideon |
Posted: Tue Oct 13, 2009 6:40 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009 Posts: 403
|
I just read the document pointed to by the link, and it stated that:
Quote: |
The following table lists the resources created, and indicates the component queue manager with which they are associated. |
and it lists component queue managers for Configuration Mnager, Broker, and User name Server.
That confuses me, isn't there only one queue manager used between the broker and Config mgr ? |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 13, 2009 6:56 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Gideon wrote: |
That confuses me, isn't there only one queue manager used between the broker and Config mgr ? |
Depends. Each needs one. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Gideon |
Posted: Tue Oct 13, 2009 7:12 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009 Posts: 403
|
It worked perfectly.
Thank you very much |
|
Back to top |
|
 |
Gideon |
Posted: Tue Oct 13, 2009 10:02 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009 Posts: 403
|
In my last reply, I was able to start the Broker and ConfigMgr from the Services panel
I had previously deleted the qmgr
recreated it with a crtmqm command
Then I created a listener thru Explorer, with a port of 2414, and set it to start at Qmgr start
I recreated the queues used by the flows (using a predefined script)
Both the broker and configMgr start automatically
I then did a reboot of the machine
Upon reboot, the Qmgr is up and running, so is the listener
The Broker is running
The ConfigMgr is NOT
I try to start the ConfigMgr, and it starts successfully
The flows are still contained within the broker that were there before the qmgr was deleted
Meanwhile, even though the Broker is running,the flow is not draining the queue
I try to stop the broker from the Services panel, but it times out and never actually stops.
Any ideas ? |
|
Back to top |
|
 |
|