IBM Support

IC80590: DB2 HADR STANDBY COULD BE BROUGHT DOWN AFTER TAKEOVER OPERATION IN SUPER ASYNC MODE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • HADR standby could be brought down on receiving the first log
    page after a takeover due to standby being at wrong position in
    log stream.
    
    This will happen only at a specific scenario where a takeover is
    issued when the old primary wrote a partial page with one free
    byte.
    
    The DB2 diaglog on standby will contain diagnostic messages
    similar to the below ones:
    
    2011-12-23-01.11.32.840859-480 I5466492E484        LEVEL: Error
    PID     : 24906                TID  : 47433094523200PROC :
    db2sysc
    INSTANCE: db2inst1        NODE : 000
    EDUID   : 444                  EDUNAME: db2hadrs (DBNAME)
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrAddDataBlock, probe:40012
    MESSAGE : Primary/standby mismatch. RCUStartLSO 77692636 not on
    record
              boundary. RCU first page bytecount 162, firstIndex
    130, pageLso
              77692798.
    
    Or:
    2011-12-24-18.20.59.771695-480 I124574E542         LEVEL: Severe
    PID     : 20239                TID  : 47073726556480PROC :
    db2sysc
    INSTANCE: db2inst1           NODE : 000
    EDUID   : 53                   EDUNAME: db2hadrs (DBNAME)
    FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk,
    probe:909
    MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
    cannot be used"
              DIA8414C Logging can not continue due to an error.
    DATA #1 : <preformatted>
    diffPage 1 TailPage 0 does not match pagePso 41106566 and
    firstLso 41102385
    

Local fix

  • restart standby by "db2 activate db hadrdb"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 LUW HADR users on all platforms                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Without the fix, customer could  hit the problem described   *
    * in the error description                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to v97fp6                                            *
    ****************************************************************
    

Problem conclusion

  • After applying v97fp6, the problem in error description can be
    avoided. Standby will not be brought down after takeover even
    with the condition described in error description.
    

Temporary fix

  • restart standby once hit the problem
    

Comments

APAR Information

  • APAR number

    IC80590

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-26

  • Closed date

    2012-06-05

  • Last modified date

    2012-06-05

  • 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

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC80590

Modified date: 05 June 2012