IBM Support

IT31315: DATABASE ERROR AFTER TABLESPACE I/O ERROR DURING RECOVERY WHEN DB2_ONLINERECOVERY IS ON.

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

  • This problem only occurs when DB2_ONLINERECOVERY is set to YES.
    Under this configuration, if database recovery encounters an IO
    error on a tablespace (typically caused by not able to access
    the container, or reading bad data due to disk corruption), the
    following message can be seen in db2diag.log
    
    2019-12-17-10.05.33.575220-300 I131131E905           LEVEL: Info
     PID     : 28964                TID : 139783854614272 KTID :
     30935
     PROC    : db2sysc
     INSTANCE: instance             NODE : 000            DB   :
     DBNAME
     APPHDL  : 0-55                 APPID:
    *LOCAL.userid.191217150532
     AUTHID  : authid             HOSTNAME: host
     EDUID   : 104                  EDUNAME: db2agent (DBNAME)
     FUNCTION: DB2 UDB, data protection services, sqlprudm,
     probe:5110
     DATA #1 : <preformatted>
     "Transaction with tid <TID1> requires synchronous rollback due
     to  tablespace in offline state. Change undoSyncPoint
     from  <LSO1> to <LSO2>"
    
    
    If you notice the value of LSO1 is smaller than LSO2 in this
    message, it might result in application able to access data that
    is still being recovered asynchronously.  This could cause
    various outcomes including but not limited to:
     - query getting incorrect result
     - database failure due to inconsistent data
     - failure in subsequent database recovery or HADR standby log
    replay
    

Local fix

  • Turn off DB2_ONLINERECOVERY and re-start the database.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users that have DB2_ONLINERECOOERY=ON                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 V11.1.4.6                                     *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 V11.1.4.6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31315

  • 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-12-17

  • Closed date

    2021-03-19

  • Last modified date

    2021-03-19

  • 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 & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
20 March 2021