IT33117: IBM MQ RDQM might not switch to or start on its configured preferred node.

APAR status

• Closed as program error.

Error description

• An IBM MQ replicated data queue manager (RDQM) may not switch to
  or start on the designated primary
  node in an RDQM pacemaker cluster. The configuration
  information used to make a queue manager primary on the desired
  node may be missing. If this condition is met, the "HA current
  location" will not properly refer to that of the "HA preferred
  location" in an "rdqmstatus -m QM1" output.
  
  rdqmstatus output:
  /opt/mqm/bin/rdqmstatus -m QM1
  Node:                                   node202
  Queue manager status:                   Running
  CPU:                                    0.00%
  Memory:                                 182MB
  Queue manager file system:              4864MB used, 28.8GB
  allocated [17%]
  HA role:                                Primary
  HA status:                              Normal
  HA control:                             Enabled
  HA current location:                    This node
  HA preferred location:                  node102
  HA floating IP interface:               None
  HA floating IP address:                 None
  DR role:                                Primary
  DR status:                              Normal
  DR port:                                7056
  DR local IP address:                    10.0.1.5
  DR remote IP address list:
  10.0.1.23,10.0.1.24,10.0.17.26
  DR current remote IP address:           10.0.1.24
  
  Node:                                   node101
  HA status:                              Normal
  
  Node:                                   node102
  HA status:                              Normal
  

Local fix

• Suspend and Resume the preferred node. From the preferred node,
  execute the commands:
  rdqmadm -s
  rdqmadm -r
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the IBM MQ RDQM feature who have set a preferred HA
  node.
  
  
  Platforms affected:
  Linux on x86-64
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  As a result of a brief temporary loss of connectivity to other
  RDQM nodes (as a result of a VM scheduling issue in the observed
  case), the values of certain internal transient metadata
  attributes became out of sync with the other nodes. The loss of
  synchronization meant that the node was ineligible to run the
  active instance of the queue manager.
  

Problem conclusion

• The problem has been fixed with a new internal agent which
  periodically checks if a node rejoined the cluster after
  temporarily being disconnected, and updates the transient
  metadata attributes accordingly.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.3
  v9.x CD    9.2.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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels