IBM Support

IT17618: MQ APPLIANCE: FAIL BACK TO DISCONNECTED HA GROUP - UNABLE TO START QUEUE MANAGER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Two appliances are configured in an high availability group with
    a third appliance configured for disaster recovery. The queue
    manager's disaster recovery role is changed while connectivity
    for the HA primary and secondary interfaces is broken. The
    disaster recovery state of the queue manager becomes
    inconsistent on the two HA appliances and this state is not
    automatically resolved when connectivity is restored.
    

Local fix

  • Users who have configured appliances for both high availability
    and disaster recovery should avoid changing the disaster
    recovery role when connectivity between the HA appliances is
    broken.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the IBM MQ Appliance who have established two
    appliances in a high availability configuration plus a third
    appliance for disaster recovery.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The HA appliances stored the disaster recovery role in both the
    HA subsystem and in an separate local data store. These two
    copies of the state information were not consistently updated
    when connectivity between the HA appliances was interrupted.
    

Problem conclusion

  • The use of a separate local data store to track the disaster
    recovery role has been removed so there is now one copy of the
    state information managed by the HA subsystem.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.6
    
    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

    IT17618

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725S1400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-24

  • Closed date

    2016-11-18

  • Last modified date

    2017-03-10

  • 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 APPL M20

  • Fixed component ID

    5725S1400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
10 March 2017