IZ25621: STANDBY FAILS DURING REMOTE CATCHUP PHASE WITH AN ERROR "HADR STANDBY FOUND BAD LOG".

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During remote catchup phase, retrieved logs on primary may get
    renamed. This will cause HADR primary daemon to dump an error
    "sqlplfrScanNext (0x860f000a) - file not found" as it cannot
    find the log extent. You will notice the following diagnostic
    entries on the db2diag.log
    
    2008-06-08-08.48.40.290552-240 E78058823A326      LEVEL: Warning
    PID     : 2175218              TID  : 1           PROC :
    db2logmgr (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4130
    MESSAGE : ADM1843I  Started retrieve for log file
    "S0002341.LOG".
    
    2008-06-08-08.48.40.730269-240 E78059150A386      LEVEL: Warning
    PID     : 2175218              TID  : 1           PROC :
    db2logmgr (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4148
    MESSAGE : ADM1845I  Completed retrieve for log file
    "S0002341.LOG" on chain "0"
              from "/db2/FOO/log_dir/NODE0000/".
    
    2008-06-08-08.48.40.730517-240 I78059537A308      LEVEL: Warning
    PID     : 2175218              TID  : 1           PROC :
    db2logmgr (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, data protection services, sqlpgole,
    probe:2700
    MESSAGE : File in the process of being renamed: extnum 2391
    
    
    2008-06-08-08.48.40.832273-240 E78060807A326      LEVEL: Warning
    PID     : 2175218              TID  : 1           PROC :
    db2logmgr (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4130
    MESSAGE : ADM1843I  Started retrieve for log file
    "S0002341.LOG".
    
    2008-06-08-08.48.41.330095-240 E78061134A386      LEVEL: Warning
    PID     : 2175218              TID  : 1           PROC :
    db2logmgr (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4148
    MESSAGE : ADM1845I  Completed retrieve for log file
    "S0002341.LOG" on chain "0" from "/db2/FOO/log_dir/NODE0000/".
    
    2008-06-08-08.48.41.330314-240 I78061521A308      LEVEL: Warning
    PID     : 2175218              TID  : 1           PROC :
    db2logmgr (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, data protection services, sqlpgole,
    probe:2700
    MESSAGE : File in the process of being renamed: extnum 2391
    
    2008-06-08-08.48.41.330628-240 I78061830A431      LEVEL: Error
    PID     : 2273488              TID  : 1           PROC :
    db2hadrp (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP,
    probe:20590
    MESSAGE : HADR primary database failed to read log pages for
    remote catchup.
              sqlplfrScanNext returned rc = 0x860f000a, scanPages =
    0, scanFlagsOut = 0x2
    
    During this time, Standby will fail with a generic message like
    "HADR standby found bad log".
    
    2008-06-08-09.23.29.688060-240 I135404A309        LEVEL: Warning
    PID     : 979074               TID  : 1           PROC :
    db2hadrs (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrSPrepareLogWrite, pro
    be:10260
    MESSAGE : RCUStartLsn 000000271E87EB2D
    
    2008-06-08-09.23.29.688240-240 I135714A387        LEVEL: Warning
    PID     : 979074               TID  : 1           PROC :
    db2hadrs (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrSPrepareLogWrite, pro
    be:10325
    MESSAGE : Incomplete log record at end, RCUStartLSN
    000000271E87EB2D
              recoveryLastPageLsn 000000271E87FFFB
    
    2008-06-08-09.24.13.953907-240 I136102A318        LEVEL: Error
    PID     : 979074               TID  : 1           PROC :
    db2hadrs (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS,
    probe:21210
    MESSAGE : HADR: Missing log on primary. Standby shutting down
    
    2008-06-08-09.24.13.954171-240 I136421A348        LEVEL: Error
    PID     : 979074               TID  : 1           PROC :
    db2hadrs (FOO) 0
    INSTANCE: db2inst1               NODE : 000
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS,
    probe:21210
    RETCODE : ZRC=0x87800148=-2021654200=HDR_ZRC_BAD_LOG
              "HADR standby found bad log"
    

Local fix

  • Transfer or ship all old logs to standby and activate the
    database. This will cause standby to apply these logs during
    local catchup pending state.
    

Problem summary

  • Users Affected:
    All HADR users
    
    Problem Description:
    STANDBY FAILS DURING REMOTE CATCHUP PHASE WITH AN ERROR "HADR
    STANDBY FOUND BAD LOG".
    
    Problem Summary:
    STANDBY FAILS DURING REMOTE CATCHUP PHASE WITH AN ERROR "HADR
    STANDBY FOUND BAD LOG".
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 4 (s090429)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ25621

  • Reported component name

    DB2 UDB ESE AIX

  • Reported component ID

    5765F4100

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-06-25

  • Closed date

    2009-06-07

  • Last modified date

    2009-06-07

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

    IZ25619

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

Fix information

  • Fixed component name

    DB2 UDB ESE AIX

  • Fixed component ID

    5765F4100

Applicable component levels

  • R950 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

950

Reference #:

IZ25621

Modified date:

2009-06-07

Translate my page

Machine Translation

Content navigation