IBM Support

IC70431: ABEND ON HADR PRIMARY DUE TO BADLOG ERROR IN SQLPGWRITETODISK

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A HADR primary database can fail with the following message :
    
    EDUID   : 23                   EDUNAME: db2loggw (SAMPLE)
    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 0015AD388052 and firstlsn
    0015AE388000
    
    This is typically seen after a non forced takeover and when
    mirrored logging is enabled. ( mirrorlogpath set in the db cfg
    ).
    
    Another eyecatcher is the following error that may happen some
    time prior to this during the takeover :
    
    2010-06-17-15.55.59.401076+120 I125515E447         LEVEL: Severe
    PID     : 21100                TID  : 183236553056 PROC :
    db2sysc
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 39                   EDUNAME: db2hadrs (SAMPLE)
    
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrAddLogFiles, probe:10150
    RETCODE : ZRC=0x071000E3=118489315=SQLP_RETRY_GADF
    "sqlpgCallGIFL: block on log disk.  sqlpgReuseCAL: log file
    deleted"
    

Local fix

  • The primary database recovers from this after a database
    restart.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * HADR users                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Potential outage on the hadr primary with a BADLOG error.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade DB2 server to V9.7 Fixpak 4                          *
    ****************************************************************
    

Problem conclusion

  • This problem has been fixed in V9.7 Fixpak 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC70431

  • 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-08-06

  • Closed date

    2011-05-24

  • Last modified date

    2011-05-24

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

    IC69321

  • 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 #: IC70431

Modified date: 24 May 2011