IBM Support

IT25994: HADR GRACEFUL TAKEOVER ON PURESCALE COULD FAIL WITH SQL1770N RC7WHILE OLD PRIMARY DATABASE IS SWITCHING ROLE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • It's possible that during HADR graceful takeover in pureScale
    environment, standby database could timeout and fail with
    SQL1770 reason code 7, after the primary has processed the
    graceful takeover and switched its role to standby.  This
    results in both clusters having the HADR role as STANDBY.  The
    following diagnostic message can be found in db2diag.log on
    standby:
    
    2018-07-17-02.51.23.583987-240 I429271E669           LEVEL:
    Error
    PID     : 28043                TID : 140391936419584 PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000            DB   : LIVE
    APPHDL  : 0-40808              APPID: *N0.db2inst1.180717064855
    AUTHID  : DB2INST1             HOSTNAME: host2
    EDUID   : 5388                 EDUNAME: db2agent (LIVE) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrCoordinateTakeover, probe:47150
    MESSAGE : ZRC=0x8280001B=-2105540581=HDR_ZRC_COMM_CLOSED
             "Communication with HADR partner was lost"
    DATA #1 : String, 54 bytes
    No viable members found for commit, aborting takeover.
    

Local fix

  • To complete the failover, issue TAKEOVER BY FORCE on the
    original standby database.  This is safe because the original
    primary had completed the graceful takeover processing and
    switched its role to standby.   There will be no data lost and
    the two clusters will be able to form HADR connection after the
    forced takeover.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25994

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-16

  • Closed date

    2018-11-27

  • Last modified date

    2018-11-27

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

    IT25869

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 November 2018