| Author |
Message
|
| rathi_ann |
 Posted: Sun Jun 10, 2007 11:02 pm Post subject: Errors following restoring a Queue manager with saveqmgr MQS |
 |
|
Newbie
Joined: 10 Jun 2007
Posts: 2
|
Hi All,
There was a power outage in the server and the QM ended abruptly..
once it is brought back up, QM failed to start..
We tried a lot of things (like clearing semaphores/shared segments, recycling, replacing the problematic queue file..) and it did not work out.
We could just bring it to a stage that QM started but with some errors.
So we generated MQS script using saveqmgr (our MQ version : 5.2 on solaris) util. Deleted the existing Qmgr and created one afresh and then run the MQS script and then started it.. There was no error on start up but we are encountering when there is a message exchange..
QM02 is the QMgr which was recreated. We created a dummy Qmgr which we later dropped but that also appears in the log still.
What could be possible reasons/resolutions for this?
06/08/07 17:58:12
AMQ9599: Program could not open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object 'QM02.DLQ' on
queue manager 'QM02' by user '' failed with reason code 2085.
ACTION:
Ensure that the queue is available and retry the operation. If the message is
from a remote Queue Manager, check the Message Channel Agent User Identifier
has the correct authority.
-------------------------------------------------------------------------------
06/08/07 17:58:12
AMQ9599: Program could not open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'SYSTEM.CLUSTER.COMMAND.QUEUE' on queue manager 'dummy' by user '' failed with
reason code 2087.
ACTION:
Ensure that the queue is available and retry the operation. If the message is
from a remote Queue Manager, check the Message Channel Agent User Identifier
has the correct authority.
-------------------------------------------------------------------------------
06/08/07 17:58:12
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.QM01' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.QM01' in the error
files to determine the cause of the failure.
_________________
Thanks
Rathi |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jun 11, 2007 12:05 am Post subject: Re: Errors following restoring a Queue manager with saveqmgr |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rathi_ann wrote: |
once it is brought back up, QM failed to start....
So we generated MQS script using saveqmgr (our MQ version : 5.2 on solaris) util. |
a) How did you generate the script if the qm won't start and b) why are you still on v5.2? It's out of support
| rathi_ann wrote: |
The attempt to open either the queue or queue manager object 'QM02.DLQ' on
queue manager 'QM02' by user '' failed with reason code 2085.
|
Your script is incomplete and has failed to recreate all the required queues and other objects.
| rathi_ann wrote: |
The attempt to open either the queue or queue manager object
'SYSTEM.CLUSTER.COMMAND.QUEUE' on queue manager 'dummy' by user '' failed with
reason code 2087.
|
Your dummy queue manager was not dropped properly. Somewhere in the "clearing semaphores" it's gone a bit funny. What does "replacing the problematic queue file" mean? What file? How did you come to the conclusion it was a queue file that was the problem? How could that have anything to do with a queue manager not starting? How did you replace it - recreate image from a linear log, or vi? 
| rathi_ann wrote: |
-------------------------------------------------------------------------------
06/08/07 17:58:12
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.QM01' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.QM01' in the error
files to determine the cause of the failure. |
What's QM01? Is it the FR of the cluster QM02 is part of? Has the "old" QM02 been removed from the cluster?
I think you've broken it. I recommend:
a) Cleanse the file system
b) Upgrade to v5.3
c) Rebuild your setup
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rathi_ann |
| Posted: Mon Jun 11, 2007 12:31 am Post subject: |
|
|
Newbie
Joined: 10 Jun 2007
Posts: 2
|
I had mentioned this stmt "We could just bring it to a stage that QM started but with some errors"
QM was up but we got some errors in log file.
And QM02 is a queue manager.
i guess i figured out the missing step..We failed to put back the authorization..
_________________
Thanks
Rathi |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 11, 2007 12:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rathi_ann wrote: |
| i guess i figured out the missing step..We failed to put back the authorization.. |
Well that'll fix the 2085 no problem... 
Glad you got it fixed. You should still upgrade to v5.3
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 11, 2007 11:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| rathi_ann wrote: |
| i guess i figured out the missing step..We failed to put back the authorization.. |
Well that'll fix the 2085 no problem...
Glad you got it fixed. You should still upgrade to v5.3 |
That would fix a 2035.
IIRC 2085 is object does not exist and 2087 is unknown remote qmgr... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 11, 2007 3:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Vitor wrote: |
| rathi_ann wrote: |
| i guess i figured out the missing step..We failed to put back the authorization.. |
Well that'll fix the 2085 no problem...
Glad you got it fixed. You should still upgrade to v5.3 |
That would fix a 2035.
IIRC 2085 is object does not exist and 2087 is unknown remote qmgr... |
Clearly the note of irony in my voice failed to translate into written form....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
