| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster repository program failing to retrieve messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqoncs |
 Posted: Wed Jun 01, 2016 10:33 pm Post subject: Cluster repository program failing to retrieve messages |
 |
|
Novice
Joined: 23 Dec 2014
Posts: 17
|
Hello ,
We are receiving the below errors in our logs and the queue manager is getting down frequently. I have tried to recreate the damaged system objects with strmqm -c but still no luck.
Can someone please help in resolving the issue.
AMQ9601: Program could not inquire on queues on this queue manager.
EXPLANATION:
The WebSphere MQ clustering repository program was attempting to find out about
the queues on queue manager 'GTM123'. One of the calls failed with reason code
2101. The repository command was backed out and the repository process went
into a timed wait.
AMQ9448: Repository manager failed due of errors. Retry in 10 minutes, queue
manager will terminate in 3330 minutes
EXPLANATION:
Repository manager encountered a severe problem. See the earlier messages in
the queue manager or system error logs for details. The repository manager will
retry the command in 10 minutes. If the problem is not rectified in 3330
minutes the queue manager will terminate. Until this problem is rectified no
further cluster management activity will occur, this will effect the
availability of cluster resources accessed or hosted by this queue manager.
ACTION:
If possible, rectify the identified problem, otherwise contact your IBM support
center. To postpone the queue manager from terminating due to this problem set
the SYSTEM.CLUSTER.COMMAND.QUEUE queue to be GET(DISABLED). Once the problem
has been rectified, set the queue to be GET(ENABLED) and wait for the
repository manager to retry the command or restart the queue manager. |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Jun 02, 2016 12:13 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
When you state you tried to recreate "...damaged system objects with strmqm -c..." do you mean:
1. More than one object is damaged, and if so, which particular objects?
2. What do the queue manager logs state after the restart with -c ?
3. Have you tried deleting the object(s), ending the queue manager, then issuing the restart with -c ?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 02, 2016 5:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
And if you use linear logging have you tried to recover the damaged object(s) first? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jun 02, 2016 5:10 am Post subject: Re: Cluster repository program failing to retrieve messages |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| mqoncs wrote: |
We are receiving the below errors in our logs and the queue manager is getting down frequently. |
What other errors are in the error logs? Which error immediately precedes your qmgr abnormally terminating?
What version of MQ?
Is this a new qmgr? Is the qmgr an FR or PR? Is this the only qmgr in the cluster?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
