ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Errors following restoring a Queue manager with saveqmgr MQS

Post new topic  Reply to topic
 Errors following restoring a Queue manager with saveqmgr MQS « View previous topic :: View next topic » 
Author Message
rathi_ann
PostPosted: Sun Jun 10, 2007 11:02 pm    Post subject: Errors following restoring a Queue manager with saveqmgr MQS Reply with quote

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
View user's profile Send private message
Vitor
PostPosted: Mon Jun 11, 2007 12:05 am    Post subject: Re: Errors following restoring a Queue manager with saveqmgr Reply with quote

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
View user's profile Send private message
rathi_ann
PostPosted: Mon Jun 11, 2007 12:31 am    Post subject: Reply with quote

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
View user's profile Send private message
Vitor
PostPosted: Mon Jun 11, 2007 12:36 am    Post subject: Reply with quote

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
View user's profile Send private message
fjb_saper
PostPosted: Mon Jun 11, 2007 11:57 am    Post subject: Reply with quote

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
View user's profile Send private message Send e-mail
Vitor
PostPosted: Mon Jun 11, 2007 3:02 pm    Post subject: Reply with quote

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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Errors following restoring a Queue manager with saveqmgr MQS
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.