APAR status
Closed as program error.
Error description
In an MQ clustering environment, a partial repository (PR) queue manager will publish cluster queues it owns every 27 days to Full Repository (FR) queue managers. However, after a customer Disaster Recovery exercise, the sequence number of the cluster queue record in the PR that owns it is now older (the number is smaller) than the sequence number of same record in the FR. Therefore the publication about the cluster queue is dropped by the FR because the FR thinks that the cluster queue object updates are out of date. Afterwards, AMQ9456 errors are reported by the FRs. The explanation of this scenario is missing from the text of the AMQ9456 and AMQ9469 messages. The solution is to run REFRESH CLUSTER on the PR queue manager, to ensure the sequence numbers on its objects are brought up to date after the Disaster Recovery exercise.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This scenario occurs when a user has run a Disaster Recovery exercise that involved bringing online a replacement copy of the Partial Repository queue manager. Such exercises usually result in more up-to-date sequence numbers being attached to queue objects (etc.). Then, after the exercise is successfully completed, the normal Production Partial Repository queue manager continues, but with its objects having normal (lower) sequence numbers. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The user must run REFRESH CLUSTER in this scenario, to ensure up-to-date sequence numbers are created on the real Production queue manager, and so to avoid the other queue managers in the cluster ignoring its updates. The scenario is not described in the AMQ9456 messages or AMQ9469 that are written into the error logs.
Problem conclusion
The scenario will be described briefly in the AMQ9456 and AMQ9469 messages. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.8 v9.0 CD 9.0.4 v9.0 LTS 9.0.0.3 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT21073
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-19
Closed date
2017-07-31
Last modified date
2017-07-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI85241
Fix information
Fixed component name
WMQ BASE MULTIP
Fixed component ID
5724H7251
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 July 2017