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 » General IBM MQ Support » Having Issue Bringing Queue manager when perform a failover

Post new topic  Reply to topic
 Having Issue Bringing Queue manager when perform a failover « View previous topic :: View next topic » 
Author Message
Mrthimi80
PostPosted: Sun Dec 12, 2010 12:51 pm    Post subject: Having Issue Bringing Queue manager when perform a failover Reply with quote

Newbie

Joined: 12 Dec 2010
Posts: 2

Hi,

I am currently running MQ V 7 on lInux environement. We have a specific queue manager when we failover from one server to another that is not comming up properly


The channel stay in retrying mode... and the following error is found in the log. When we fail back to the primary server; it is working as normal

Any pointers on how to fix this is appreciated

-------------------------------------------------------------------------------
12/12/2010 02:04:52 PM - Process(7700.1) User(mqm) Program(amqzmgr0)
AMQ6184: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 10006184, with inserts 7700, 0, , ,
and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ6184
----- amqxfdcx.c : 822 --------------------------------------------------------
Back to top
View user's profile Send private message
Vitor
PostPosted: Sun Dec 12, 2010 2:55 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

That error indicates that the file system containing the message catalog can't be opened; from this we can infer that other parts of that file system (including the queue manager software and configuration files) can't be opened. This would explain why the queue manager isn't starting.

However you've got the failover configured isn't right at a file system level (at least).
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Mrthimi80
PostPosted: Sun Dec 12, 2010 3:10 pm    Post subject: Reply with quote

Newbie

Joined: 12 Dec 2010
Posts: 2

I am adding soem additonal erro messages that I found: How do I fix it




-------------------------------------------------------------------------------
12/12/2010 12:29:01 PM - Process(2005.4) User(mqm) Program(amqzmuc0)
AMQ5037: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 5037, with inserts 2005, 1, LOGGER-IO,
Critical, and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ5037
-------------------------------------------------------------------------------
12/12/2010 12:29:20 PM - Process(1995.1) User(mqm) Program(amqzxma0)
AMQ7229: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 7229, with inserts 5, 0, EUHUB, ,
and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ7229
-------------------------------------------------------------------------------
12/12/2010 12:29:43 PM - Process(1995.1) User(mqm) Program(amqzxma0)
AMQ7230: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 7230, with inserts 5, 0, AEUHUB, ,
and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ7230
-------------------------------------------------------------------------------
12/12/2010 12:29:53 PM - Process(1995.1) User(mqm) Program(amqzxma0)
AMQ7231: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 7231, with inserts 0, 0, AEUHUB, ,
and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ7231
-------------------------------------------------------------------------------
12/12/2010 12:30:00 PM - Process(1995.1) User(mqm) Program(amqzxma0)
AMQ7232: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 7232, with inserts 0, 0, AEUHUB, ,
and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ7232
-------------------------------------------------------------------------------
12/12/2010 12:30:03 PM - Process(1995.1) User(mqm) Program(amqzxma0)
AMQ7233: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 7233, with inserts 0, 0, AEUHUB, ,
and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ7233
-------------------------------------------------------------------------------
12/12/2010 12:30:06 PM - Process(2005.5) User(mqm) Program(amqzmuc0)
AMQ5037: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 5037, with inserts 2005, 1, CHECKPOINT,
Critical, and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ5037
-------------------------------------------------------------------------------
12/12/2010 12:30:07 PM - Process(2799.5) User(mqm) Program(amqzmur0)
AMQ5037: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 5037, with inserts 2799, 1, APP-SIGNAL,
Restartable, and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ5037
-------------------------------------------------------------------------------
12/12/2010 12:30:07 PM - Process(1995.1) User(mqm) Program(amqzxma0)
AMQ8003: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 8003, with inserts 0, 0, , , and
AEUHUB.
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ8003
-------------------------------------------------------------------------------
12/12/2010 12:30:07 PM - Process(2799.4) User(mqm) Program(amqzmur0)
AMQ5037: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 5037, with inserts 2799, 1, ERROR-LOG,
Restartable, and .
The following command, issued on a system that does not have message catalog
difficulties, may provide more information about that message: mqrc AMQ5037
-------------------------------------------------------------------------------
12/12/2010 12:30:20 PM - Process(2005.16) User(mqm) Program(amqzmuc0)
AMQ5037: WebSphere MQ was unable to open a message catalog to display an error
message for message id hexadecimal 5037, with inserts 2005, 1, ASYNCQ,



Now, please note when I fail back to the primary server it is working fine; but when I fail to my back up; the Queue Manager come up but the channel is staying in "Retrying" mode


We also have SSL configure

ANy help on how to get this workign is appreciated
Back to top
View user's profile Send private message
Vitor
PostPosted: Sun Dec 12, 2010 3:16 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Mrthimi80 wrote:
Now, please note when I fail back to the primary server it is working fine; but when I fail to my back up; the Queue Manager come up but the channel is staying in "Retrying" mode


I stand by my previous comment; when you're doing the failover you're making a mess of the file system. It works when you fail it back because the file system is properly mounted there.

As you've not seen fit to post the channel logs on the primary server I can only speculate on why the channel is in retry, but I suspect corrupt channel files are to blame.

Mrthimi80 wrote:
We also have SSL configure


I doubt that's your problem. But it might be a problem once you've got this working.

Mrthimi80 wrote:
ANy help on how to get this workign is appreciated


Do the failover correctly.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Sun Dec 12, 2010 4:06 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You did actually install the software on both machines, correct?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Dec 12, 2010 11:25 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

mqjeff wrote:
You did actually install the software on both machines, correct?

And the numeric ids of the users and groups are the same on both machines?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Having Issue Bringing Queue manager when perform a failover
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.