IBM Support

IT37671: TABLE SPACE ROLLFORWARD CAN FAIL UNDER ADVANCED LOG SPACE MANAGEMENT

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 a database is configured with Advanced Log Space Management
    (ALSM) a table space rollforward may fail with a data page
    error.  If a table space rollforward fails, one possible
    db2diag.log entry can look like the following:
    
    EDUID   : 35469                EDUNAME: db2agent (FITDB) 0
    FUNCTION: DB2 UDB, data management, sqldFetchDirect, probe:5715
    RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
    Page"
              DIA8500C A data file error has occurred, record id is
    "".
    
    But there could be other functions reporting a data page error
    or a table space container error.
    

Local fix

  • 1. Set DB2_COLLECT_TS_REC_INFO=OFF.
    2. Restore all table spaces involved in the failing rollforward
    operation.
    3. Re-issue the failing table space rollforward operation.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Databases enabled with Advanced Log Space Management.        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 Version 11.5.7.0.                             *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Db2 Version 11.5.7.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT37671

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-07-16

  • Closed date

    2021-08-09

  • Last modified date

    2021-08-09

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5"}]

Document Information

Modified date:
10 August 2021