IBM Support

IT23205: ASYNCHRONOUS INDEX CLEANUP FAILS WHEN DB2LOCK_TO_RB IS SET TO STATEMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During a MDC index cleanup ABP task process it may get a
    locktimeout error(-911).  The can get changed to
    SQLP_LTIMEOUT_STMT_RB return code when the registry variable
    DB2LOCK_TO_RB is set to STATEMENT.  This can cause the task to
    be left in the list utilities output.
    
    db2diag.log:
    
    2017-09-26-18.21.34.046413+120 I51344509A651        LEVEL: Error
    PID     : 14091090             TID : 22741          PROC :
    db2sysc 10
    INSTANCE: db2inst1             NODE : 010           DB   :
    SAMPLE
    APPHDL  : 10-4034              APPID: *N10.DB2.170926161833
    AUTHID  : DB2INST1             HOSTNAME: db2host
    EDUID   : 22741                EDUNAME: db2taskp (SAMPLE) 10
    FUNCTION: DB2 UDB, AIC, aicTaskProcessorCleanup, probe:846
    MESSAGE : ZRC=0x80100050=-2146434992=SQLP_LTIMEOUT_STMT_RB
              "LockTimeOut - statement rollback Reason code 80"
    RETCODE : ZRC=0x82A90067=-2102853529=ABP_TASK_PRO_ERROR
              "Task processor encountered an error"
    
    list utilities:
    ID = 39404
    Type = MDC ROLLOUT INDEX CLEANUP
    Database Name = SAMPLE
    Member Number = 2
    Description = TABLE: DB2INST1 .STAFF
    Start Time = 09/26/2017 18:18:33.693137
    State = Error
    Invocation Type = Automatic
    Throttling:
    Priority = 50
    Progress Monitoring:
    Estimated Percentage Complete = 1
    
    ID = 5772
    Type = MDC ROLLOUT INDEX CLEANUP
    Database Name = SAMPLE
    Member Number = 129
    Description = TABLE: DB2INST1 .STAFF
    Start Time = 09/26/2017 18:18:33.695764
    State = Error
    Invocation Type = Automatic
    Throttling:
    Priority = 50
    

Local fix

  • Deactivate and then reactivate the database to remove the task
    and then access the table with any SELECT, INSERT, UPDATE, or
    DELETE statement to restart the outstanding asynchronous index
    cleanup.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Platforms                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 LUW v11.1 Mod 3 Fixpack 3                     *
    ****************************************************************
    

Problem conclusion

  • First Fixed in Db2 LUW v11.1 Mod 3 Fixpack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT23205

  • 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

    2017-11-17

  • Closed date

    2018-03-16

  • Last modified date

    2018-03-16

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

    IT23166

  • 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 March 2018