IBM Support

IC68210: CRASH RECOVERY FAILED WITH -1042 ERROR WHICH MARKED THE DB BAD. IT FAILED WITH "FILE COUNT <= TAILINDEX" ERROR IN DB2DIAG.LOG.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Crash recovery failes with -1042 error marking the db bad. This
    is caused
    due to crash recovery completing too early thus calculating the
    tailindex wrongly. The crash recovery ended early due to logs
    being unavailable during the crash recovery.
    
    db2diag.log entries look like this:
    
    2010-01-19-01.39.02.173625-120 I710234A341        LEVEL: Error
    PID     : 381160               TID  : 3343        PROC : db2sysc
    0
    INSTANCE: db2inst1              NODE : 000
    EDUID   : 3343                 EDUNAME: db2loggr (SAMPLE) 0
    FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo,
    probe:1820
    MESSAGE : File Count <= TailIndex
    
    2010-01-19-01.39.02.173888-120 I710576A166        LEVEL: Error
    PID:381160 TID:3343 NODE:000 Title: SQLP_DBCB
    Dump File:/db2logs/DIAG/db2inst1/381160.3343.000.dump.bin
    
    2010-01-19-01.39.02.184985-120 I710743A435        LEVEL: Error
    PID     : 381160               TID  : 3343        PROC : db2sysc
    0
    INSTANCE: db2inst1              NODE : 000
    EDUID   : 3343                 EDUNAME: db2loggr (SAMPLE) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgasn, probe:650
    RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
    Error"
              DIA8526C A fatal error occurred in data protection
    services.
    
    2010-01-19-01.39.02.201262-120 I711179A478        LEVEL: Error
    PID     : 381160               TID  : 7712        PROC : db2sysc
    0
    INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE
    APPHDL  : 0-7                  APPID:
    *LOCAL.db2inst1.100119033834
    AUTHID  : db2inst1
    EDUID   : 7712                 EDUNAME: db2redom (SAMPLE) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgPostLoggrWithoutLatching, probe:930
    MESSAGE : db2logger: rc=-2028994531 sem rc=0 type=28
    
    
    With this APAR fix, we will detect the failure and shut down
    cleanly, making it possible to correct the failure (make the
    file available) and re-issue the recovery.
    

Local fix

  • Make sure all the transaction files needed for crash recovery
    are available and re-issue the crash recovery by restarting db2.
    

Problem summary

  • CRASH RECOVERY FAILED WITH -1042 ERROR WHICH MARKED THE DB BAD.
    IT FAILED WITH "FILE COUNT <= TAILINDEX" ERROR IN DB2DIAG.LOG.
    

Problem conclusion

  • Fixed in DB2 V97FP3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68210

  • 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-04-28

  • Closed date

    2010-09-29

  • Last modified date

    2010-09-29

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

    IZ69451

  • 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

  • R950 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC68210

Modified date: 29 September 2010