suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT23205 Status: Closed

ASYNCHRONOUS INDEX CLEANUP FAILS WHEN DB2LOCK_TO_RB IS SET TO STATEMENT

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem 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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 LUW v11.1 Mod 3 Fixpack 3                     * 
****************************************************************
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.
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First Fixed in Db2 LUW v11.1 Mod 3 Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)