IBM Support

IZ20871: free_blk_ptr overlaps slot directory causing instance crash

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An instance crash occurs and the db2diag.log message indicates
    "free_blk_ptr overlaps slot directory". The subsequent crash
    recovery attempts can also fail (see APAR LI73356)because of
    an invalid log record that is written just before the crash.
    The following entries are logged  in the db2diag.log file at
    point of failure.
    
    2008-04-18-11.30.18.225371+060 I2272993E502 LEVEL: Severe
    PID : 4755 TID : 183035222336PROC :
    db2agent (SAMPLE) 0
    INSTANCE: DB2INST1 NODE : 000 DB :
    SAMPLE
    APPHDL : 0-1179 APPID: PA014D3B.A5C7.0E9C08050158
    AUTHID : DB2ADMIN
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0
    MESSAGE : free_blk_ptr overlaps slot directory.
    DATA #1 : Hexdump, 8 bytes
    0x0000007FBFFEDED0 : 5402 0000 0000 0000
    T.......
    
    2008-04-18-11.30.18.298150+060 I2273496E486 LEVEL: Severe
    PID : 4755 TID : 183035222336PROC :
    db2agent (SAMPLE) 0
    INSTANCE: DB2INST1 NODE : 000 DB :
    SAMPLE
    APPHDL : 0-1179 APPID: PA014D3B.A5C7.0E9C08050158
    AUTHID : DB2ADMIN
    FUNCTION: DB2 UDB, data management, sqldAddRow, probe:5483
    RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
    Page"
    DIA8500C A data file error has occurred, record id is
    "".
    
    This issue can happen on the following platforms;
    LinuxAMD64
    Windows x86 -64bit
    

Local fix

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

Problem summary

  • ERROR DESCRIPTION:
    An instance crash occurs and the db2diag.log message indicates
    "free_blk_ptr overlaps slot directory". The subsequent crash
    recovery attempts can also fail (see APAR LI73356)because of
    an invalid log record that is written just before the crash.
    The following entries are logged in the db2diag.log file at
    point of failure.
    
    2008-04-18-11.30.18.225371+060 I2272993E502 LEVEL: Severe
    PID : 4755 TID : 183035222336PROC :
    db2agent (SAMPLE) 0
    INSTANCE: DB2INST1 NODE : 000 DB :
    SAMPLE
    APPHDL : 0-1179 APPID: PA014D3B.A5C7.0E9C08050158
    AUTHID : DB2ADMIN
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0
    MESSAGE : free_blk_ptr overlaps slot directory.
    DATA #1 : Hexdump, 8 bytes
    0x0000007FBFFEDED0 : 5402 0000 0000 0000
    T.......
    
    2008-04-18-11.30.18.298150+060 I2273496E486 LEVEL: Severe
    PID : 4755 TID : 183035222336PROC :
    db2agent (SAMPLE) 0
    INSTANCE: DB2INST1 NODE : 000 DB :
    SAMPLE
    APPHDL : 0-1179 APPID: PA014D3B.A5C7.0E9C08050158
    AUTHID : DB2ADMIN
    FUNCTION: DB2 UDB, data management, sqldAddRow, probe:5483
    RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
    Page"
    DIA8500C A data file error has occurred, record id is
    "".
    
    This issue can happen on the following platforms;
    LinuxAMD64
    Windows x86 -64bit
    LOCAL FIX:
    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.
    

Problem conclusion

  • The problem is first fixed in DB2 UDB version 9.1 fixpak 5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ20871

  • Reported component name

    DB2 UDB ESE SOL

  • Reported component ID

    5765F4102

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-23

  • Closed date

    2008-07-07

  • Last modified date

    2008-07-07

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

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

    IZ20872

Fix information

  • Fixed component name

    DB2 UDB ESE SOL

  • Fixed component ID

    5765F4102

Applicable component levels

  • R910 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
03 October 2021