| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ9469 - any actions possible? |
« View previous topic :: View next topic » |
| Author |
Message
|
| Seaninoz |
 Posted: Tue May 31, 2022 11:43 pm Post subject: AMQ9469 - any actions possible? |
 |
|
Newbie
Joined: 31 May 2022
Posts: 2
|
All,
This error got reported and is similar to an older post in this particular forum. Looking for some guidance as to what actions can be attempted. A few subtle differences (from the previous issue posted about) is that a DR exercise was held, and I believe this occurred about 3 days later at the FR whilst trying to communicate with the PR. They already have defined explicit CLUSSDR's/RCVR's. I have asked for displays of Qmid'S associated with the cluster from each of the qmgr's involved. A last kicker is the PR's are at V8 (Z/OS) and the FR is at 9.1.
Would it be worthwhile using dmpmqmsg/QLOAD to examine the respective Repository queues (and any "stuck" xmit queue messages) to try and determine the culprit? This is short of doing rebuilds. If not possible, so be it.
TIA
Seaninoz aka ctefehinoz from a long time ago. |
|
| Back to top |
|
 |
| hughson |
| Posted: Wed Jun 01, 2022 12:45 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Have you tried all of these suggested actions?
- If the channel had been removed intentionally, and is no longer required, you should consider removing it fully via the RESET CLUSTER command.
- There is a long-running problem with the local queue manager's CLUSRCVR in the referenced cluster. If this is true, then correct the problem urgently, to ensure that updates for the cluster are received.
- There is a long-running problem on the remote queue manager's CLUSSDR in the referenced cluster. If this is true, then correct the problem urgently, to ensure that updates for the cluster are sent.
- Check that the repository manager on the remote queue manager has not ended abnormally.
- The remote queue manager is out of step with this queue manager, potentially due to a restore of the remote queue manager from a backup. The remote queue manager must issue REFRESH CLUSTER to synchronize with other queue managers in the cluster.
- The remote queue manager is out of step with this queue manager, potentially due to a disaster recovery exercise in which a replacement queue manager with the same CLUSRCVR channel name was created, was run for a while, then ended. If this has happened, then the referenced remote queue manager must now issue REFRESH CLUSTER to synchronize with other queue managers in the cluster.
- If the above items have been checked, and this problem persists over several days (causing repeats of this error message in the local queue manager's error logs) then contact your IBM support center.
Given your mention that a DR exercise was held, I might pay particular attention to #6, but you should carefully look at all of them.
You mention looking at "stuck" XmitQ messages. If you have any channels that are not running, and therefore messages sitting on XmitQs not going anywhere, you should certainly resolve those issues.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| Seaninoz |
| Posted: Wed Jun 01, 2022 3:41 pm Post subject: AMQ9469 - any actions possible? |
|
|
Newbie
Joined: 31 May 2022
Posts: 2
|
Morag,
Thanks for that list. Number 4 onwards appears to be more applicable, but will get onto the lot.
With the "stuck" messages - I'll verify too if they are in fact still present somewhere.
Regards
Seaninoz aka ctefehinoz |
|
| 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
|
|
|
|
