IBM Support

LI73359: Crash recovery fails after crash due to invalid free_blk_ptr

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If crash recovery also fails,  recover the DB by a restore and
    then  roll forward to point in time before the failing log
    record is read.
    
    After an instance crash due to a problem with the free_blk_ptr
    (see APAR IZ20872). Crash recovery may fail due to an invalid
    value in the associated log record.
    
    The system cannot continue with crash recovery
    because of a validation check that finds the log record values
    do not match the current target page. The db2diag.log will
    indicate the following message.
    
    
    2008-03-28-12.22.37.287849-240 I187556927E591     LEVEL: Severe
    PID     : 26449                TID  : 183030155104PROC :
    db2redow (SAMPLE) 0
    INSTANCE: DB2INST1             NODE : 000         DB   :
    NAGCPI01
    APPHDL  : 0-7                  APPID:
    *LOCAL.DB2INST1.080328162202
    AUTHID  : DB2INST1
    FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:1897
    MESSAGE : Free Space does not match during redo!
    DATA #1 : Hexdump, 26 bytes
    0x0000000DB37FA8A0 : 01A2 0700 0500 0000 CD00 B0FF A200 1E2B
    ...............+
    0x0000000DB37FA8B0 : 1201 F600 0000 CD00 8100
    
    
    This issue can happen on the following platforms;
    LinuxAMD64
    Windows x86 -64bit
    

Local fix

  • If this occurs during crash recovery, recover the DB by
    restoring and then rolling forward to a point in time prior to
    the invalid log record.
    

Problem summary

  • ERROR DESCRIPTION:
    If crash recovery also fails,  recover the DB by a restore and
    then  roll forward to point in time before the failing log
    record is read.
    
    After an instance crash due to a problem with the free_blk_ptr
    (see APAR IZ20872). Crash recovery may fail due to an invalid
    value in the associated log record.
    
    The system cannot continue with crash recovery
    because of a validation check that finds the log record values
    do not match the current target page. The db2diag.log will
    indicate the following message.
    
    
    2008-03-28-12.22.37.287849-240 I187556927E591     LEVEL: Severe
    PID     : 26449                TID  : 183030155104PROC :
    db2redow (SAMPLE) 0
    INSTANCE: DB2INST1             NODE : 000         DB   :
    NAGCPI01
    APPHDL  : 0-7                  APPID:
    *LOCAL.DB2INST1.080328162202
    AUTHID  : DB2INST1
    FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:1897
    MESSAGE : Free Space does not match during redo!
    DATA #1 : Hexdump, 26 bytes
    0x0000000DB37FA8A0 : 01A2 0700 0500 0000 CD00 B0FF A200 1E2B
    ...............+
    0x0000000DB37FA8B0 : 1201 F600 0000 CD00 8100
    
    
    This issue can happen on the following platforms;
    LinuxAMD64
    Windows x86 -64bit
    
    LOCAL FIX:
     If this occurs during crash recovery, recover the DB by
    restoring and then rolling forward to a point in time prior to
    the invalid log record.
    

Problem conclusion

  • First Fixed in DB2 UDB Version 9.5, FixPak 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI73359

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-17

  • Closed date

    2008-08-27

  • Last modified date

    2008-08-27

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

    LI73356

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

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 August 2008