IBM Support

IC68899: HADR STANDBY MAY PANIC WITH SQLP_BADLOG ERROR 'TAILPAGE 0 DOES NOT PAGELSN XXXXXXXXXXXX AND FIRSTLSN XXXXXXXXXXXX'

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • An HADR Standby may experience a problem in the following
    situation
    
    1) The HADR pair is in Peer state and on the last log page of a
    log file
    This can be observed using 'db2pd -hadrdb -db db1' under
    PrimaryPg or StandbyPg.  The value will be 1 less than
    LOGFILSIZ.
    
    2) The HADR pair is disconnected
    This could be for any reason including network glitch, HADR
    timeout, or deactivation and reactivation of the Standby
    
    3) The HADR Primary does not generate any log records while the
    HADR pair reconnects.
    
    
    In this situation, the Standby may panic with an entry in the
    diag.log similar to the following:
    
    2010-01-20-05.51.00.822571+540 I125712485A542     LEVEL: Severe
    PID     : 156072               TID  : 12500       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 12500                EDUNAME: db2hadrs (DB1) 0
    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>
    TailPage 0 does not match pagelsn 0356CCBA76B4 and firstlsn
    0356CCBA8000
    
    
    The signature of the this problem is:
     - TailPage 0
     - firstlsn is the first lsn of the next log file
     - pagelsn is less than firstlsn (and is the pagelsn of the last
    page on the prior log file)
    
    Additionally, in the HADR Primary's db2diag.log, there will be
    an entry similar to the following
    
    2010-01-20-05.50.57.554083+540 I101672740A382     LEVEL: Warning
    PID     : 1343502              TID  : 14394       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 14394                EDUNAME: db2hadrp (DB1) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrTransitionPtoNPeer, probe:10645
    MESSAGE : near peer catchup starts at 00000356CCBA800C
    
    Where the reported number is slightly past the firstlsn value
    reported from the Standby's diag.log
    (00000356CCBA800C vs 00000356CCBA8000)
    

Local fix

  • Restart the HADR Standby after primary has moved to next log
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 V9.7 FP2                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An HADR Standby may experience a problem in the following    *
    *                                                              *
    * situation                                                    *
    *                                                              *
    *                                                              *
    *                                                              *
    * 1) The HADR pair is in Peer state and on the last log page   *
    * of a                                                         *
    * log file                                                     *
    *                                                              *
    * This can be observed using 'db2pd -hadrdb -db db1' under     *
    *                                                              *
    * PrimaryPg or StandbyPg.  The value will be 1 less than       *
    *                                                              *
    * LOGFILSIZ.                                                   *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2) The HADR pair is disconnected                             *
    *                                                              *
    * This could be for any reason including network glitch, HADR  *
    *                                                              *
    * timeout, or deactivation and reactivation of the Standby     *
    *                                                              *
    *                                                              *
    *                                                              *
    * 3) The HADR Primary does not generate any log records while  *
    * the                                                          *
    * HADR pair reconnects.                                        *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    * In this situation, the Standby may panic with an entry in    *
    * the                                                          *
    * diag.log similar to the following:                           *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2010-01-20-05.51.00.822571+540 I125712485A542    LEVEL:      *
    * Severe                                                       *
    * PID    : 156072              TID  : 12500      PROC :        *
    * db2sysc                                                      *
    * 0                                                            *
    *                                                              *
    * INSTANCE: db2inst1            NODE : 000                     *
    *                                                              *
    * EDUID  : 12500                EDUNAME: db2hadrs (DB1) 0      *
    *                                                              *
    * 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>                                     *
    *                                                              *
    * TailPage 0 does not match pagelsn 0356CCBA76B4 and firstlsn  *
    *                                                              *
    * 0356CCBA8000                                                 *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    * The signature of the this problem is:                        *
    *                                                              *
    * - TailPage 0                                                 *
    *                                                              *
    * - firstlsn is the first lsn of the next log file             *
    *                                                              *
    * - pagelsn is less than firstlsn (and is the pagelsn of the   *
    * last                                                         *
    * page on the prior log file)                                  *
    *                                                              *
    *                                                              *
    *                                                              *
    * Additionally, in the HADR Primary's db2diag.log, there will  *
    * be                                                           *
    * an entry similar to the following                            *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2010-01-20-05.50.57.554083+540 I101672740A382    LEVEL:      *
    * Warning                                                      *
    * PID    : 1343502              TID  : 14394      PROC :       *
    * db2sysc                                                      *
    * 0                                                            *
    *                                                              *
    * INSTANCE: db2inst1            NODE : 000                     *
    *                                                              *
    * EDUID  : 14394                EDUNAME: db2hadrp (DB1) 0      *
    *                                                              *
    * FUNCTION: DB2 UDB, High Availability Disaster Recovery,      *
    *                                                              *
    * hdrTransitionPtoNPeer, probe:10645                           *
    *                                                              *
    * MESSAGE : near peer catchup starts at 00000356CCBA800C       *
    *                                                              *
    *                                                              *
    *                                                              *
    * Where the reported number is slightly past the firstlsn      *
    * value                                                        *
    * reported from the Standby's diag.log                         *
    *                                                              *
    * (00000356CCBA800C vs 00000356CCBA8000)                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V9.7 FP3                                      *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 V9.7 FP3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68899

  • 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

    2010-05-27

  • Closed date

    2010-09-24

  • Last modified date

    2010-09-24

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

    IC66108

  • 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 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC68899

Modified date: 24 September 2010