Direct link to fix
APAR status
Closed as program error.
Error description
After upgrading an HA queue manager from MQ 9.1 LTS or CD level to MQ 9.2.0.6 on IBM MQ appliance, the queue manager might not start. The status command will show the following: mqa(mqcli)# status -a QM(QM1) Status(Ended normally) HA role: UNKNOWN HA status: Resource failed HA control: Enabled HA preferred location: This appliance HA last in sync: 2022-07-19 01:00:00.000 The pcs-status in the runmqras shows the following failed resources: Failed Resource Actions: * QM1_drbd_start_0 on SM-MQAPP01 'unknown error' (1): call=16, status=complete, exitreason='failed to attach', last-rc-change='Wed Jul 20 15:23:25 2022', queued=0ms, exec=1135ms * QM1_drbd_start_0 on SM-MQAPP02 'unknown error' (1): call=58, status=complete, exitreason='failed to attach', last-rc-change='Wed Jul 20 15:15:54 2022', queued=0ms, exec=1106ms The initHA log will output the following message indicating "<qmname>.res.backup" file not found and no DRBD resource migration required for the queue manager. 2022-07-20 15:23:16.816620578+01:00:13524: cat /var/mqm/QM1.res.backup | grep '# Generated at ' | sed -n 1p | sed 's/# Generated at \(\S*\)/\1/' 2022-07-20 15:23:16.820605853+01:00:13524: cat: /var/mqm/QM1.res.backup: No such file or directory 2022-07-20 15:23:16.822739870+01:00:13524: rc(0) 2022-07-20 15:23:16.826669244+01:00:13524: No DRBD resource migration required for QM1 2022-07-20 15:23:16.828826526+01:00:13524: cp /var/mqm/QM1.res.backup /etc/drbd.d/QM1.res 2022-07-20 15:23:16.839453655+01:00:13524: rc(0) 2022-07-20 15:23:16.843182339+01:00:13524: } Leaving updateDrbdResources 0
Local fix
Workaround 1: Remove the QM from HA or HA+DR and add it back to HA or HA+DR Workaround 2: Apply any available 9.2.0.x LTS firmware other than 9.2.0.6, preferably higher 9.2.0.x version or 9.2.0.5. If the user has applied 9.2.0.6 and encountered this issue then the 9.2.0.x firmware can be applied on top of 9.2.0.6 Workaround 3: Contact IBM Support for assistance with correcting the internal state using the IBM MQ appliance service console.
Problem summary
**************************************************************** USERS AFFECTED: Users migrating MQ appliance from a MQ 9.1 CD or LTS firmware level to MQ 9.2.0.6, who have an HA queue manager defined. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: A defect introduced by the APAR IT40628 prevented the queue manager from completing its migration from a 9.1 queue manager and resulted in failure in startup.
Problem conclusion
MQ appliance code has been modified to fix the defect introduced by the APAR IT40628 and resolve the migration issue. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.2 LTS 9.2.0.7 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
IT41581
Reported component name
MQ APPL M2002 V
Reported component ID
5737H4701
Reported release
920
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-07-21
Closed date
2022-10-24
Last modified date
2022-10-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
MQ APPL M2002 V
Fixed component ID
5737H4701
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
27 October 2022