IBM Support

IC79713: IF A LOG FULL IS HIT BY LOAD, BLANK PAGES COULD REMAIN IN BUFFER POOL CAUSING DATABASE TO BE MARKED BAD IF REUSED BY LOAD RESTART

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If LOAD operation hits log full situation, it can leave some
    blank data pages in bufferpool after it rollback transaction.
    When subsequent LOAD RESTART operation reuses them, bad data
    page is encountered and database is marked as bad. The
    db2diag.log can have the following message showing blank PAGE
    HEADER:
    
    20xx-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxxxx     LEVEL: Severe
    PID     : 24000                TID  : 47390123878720PROC :
    db2sysc 2
    INSTANCE: xxxxxxxx             NODE : 002          DB   : xxxxxx
    APPHDL  : 1-10058              APPID:
    xx.xxx.xx.xxx.xxxx.xxxxxxxxxxxx
    AUTHID  : xxxxxxx
    EDUID   : 67082                EDUNAME: db2linit 2
    FUNCTION: DB2 UDB, data management, sqldReadTableInfo,
    probe:9416
    RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
    Page"
              DIA8500C A data file error has occurred, record id is
    "".
    
    ..................
    
    20xx-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxxxx     LEVEL: Severe
    PID     : 24000                TID  : 47390123878720PROC :
    db2sysc 2
    INSTANCE: xxxxxxxx             NODE : 002          DB   : xxxxxx
    APPHDL  : 1-10058              APPID:
    xx.xxx.xx.xxx.xxxx.xxxxxxxxxxxx
    AUTHID  : xxxxxxx
    EDUID   : 67082                EDUNAME: db2linit 2
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
    logging func, probe:0
    MESSAGE : SQD PAGE HEADER
    DATA #1 : Hexdump, 22 bytes
    0x00002B16758DC030 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x00002B16758DC040 : 0000 0000 0000
    ......
    
    .............
    

Local fix

  • The page is only corrupted in bufferpool and not on disk.
    Terminating all connections to the database, deactivating, and
    reactivating the database should make the problem go away.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 LUW Version 9.7 Fix Pack 6                    *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.7 Fix Pack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC79713

  • 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

    2011-11-09

  • Closed date

    2012-06-11

  • Last modified date

    2012-06-11

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

    IC74247

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

Modified date: 11 June 2012