IBM Support

IT29381: A FAILURE WHILE REPLAYING A TABLE SPACE LOG RECORD MAY CAUSE SUBSEQUENT ROLLFORWARDS TO CORRUPT THE TABLE SPACE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If an error is encountered when rollforwarding through a table
    space specific log record (i.e. ALTER_POOL, FREE_PENDDEL,
    GET_ONE_EXT, ect.) the table space rollforward is supposed to
    stop and put the table space in the ROLLFORWARD_PENDING state.
    The table space state may not be written to disk and subsequent
    rollforwards will continue assuming the table space is in a
    NORMAL state. This causes the rollforward to start at the wrong
    log sequence number (LSN) and may corrupt the table space.
    
    This error can go undetected and can lead to various other
    errors such as:
    
    FUNCTION: DB2 UDB, buffer pool services, sqlbRedoGetOneExt,
    probe:460
    MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
    error detected"
              DIA8501C A buffer pool logic error has occurred.
    
    db2dart or INSPECT will be able to identify that the table space
    is corrupted.
    
    LOCAL FIX:
    None.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29381

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-10

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

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

  • 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

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 January 2020