DB2 FOR LUW / DB2FORLUW / 970 - DB2

The error might occur when the following criteria are met: 
 
1) The table is an MDC table with at least two RID indexes. 
2) A deferred cleanup rollout delete is performed on that MDC 
table. 
3) Before the asynchronous index cleanup operation completes, it 
suspends due to lock timeout or deadlock, and another deferred 
cleanup rollout delete is performed on the table. 
4) As a result, it updates the block map incorrectly marking all 
rolled-out blocks as free even though the index cleanup is not 
complete. This might result in a variety of different index 
errors.  The problem can be detected by running the INSPECT 
command with the INDEXDATA option. 
 
You can see following output in db2diag.log when the async index 
cleanup suspends(3): 
 
EDUID   : 543210               EDUNAME: db2taskp (SAMPLE) 0 
FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:2075 
MESSAGE : ADM9514I  BEGIN async index cleanup on table 
"DB2INST1.T1" 
          (ID "123") and table space "TS1" (ID "5"). 
  ... 
 
 
EDUID   : 543210               EDUNAME: db2taskp (SAMPLE) 0 
FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:4318 
MESSAGE : ZRC=0x82A90066=-2102853530=ABP_SUSPEND_TASK_PRO 
          "Suspend the task processor" 
CALLED  : DB2 UDB, AIC, aicRolloutIndexCleanup

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7.0.11.                             * 
****************************************************************

If the problem occurs, rebuild the indexes.  To avoid the 
problem do not use deferred index cleanup. 
db2set DB2_MDC_ROLLOUT=IMMEDIATE

The problem is first fixed in DB2 version 9.7.0.11.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

20.08.2015
06.10.2015
06.10.2015

9.7.0.11