DB2 FOR LUW / DB2FORLUW / A10 - DB2

The error does not happen on HADR environments. 
 
After ROLLFORWARD, data stored in table and in index is out of 
sync. Data scan vs index scan will return different results 
(data is the correct one). Index may have some records missing, 
but all records in index are present in table. 
 
The scenario is rollforward through (both LOADs must be in 
rollforward window, and operate on same table). 
LOAD COPY YES ... INDEXING MODE REBUILD 
LOAD COPY YES ... INDEXING MODE INCREMENTAL 
 
ROLLFORWARD of LOAD COPY YES ... INDEXING MODE INCREMENTAL must 
mark indexes bad, as the COPY image does not contain any index 
data. 
Under certain scenarios (see below), index may not be marked 
bad. 
 
Rollforward window must include LOAD COPY YES ... INDEXING MODE 
REBUILD and LOAD COPY YES ... INDEXING MODE INCREMENTAL. 
At least one LOAD ... REBUILD must precede LOAD ... INCREMENTAL. 
Problem does not happen when LOAD ... REBUILD is the last LOAD.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users performing rollforward thru load copy image.       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fixpack 5 or higher.                    * 
****************************************************************

Force index rebuild. Either drop/recreate index, or mark index 
bad explicitly.

Firstly fixed in DB2 V10.1 Fixpack 5.

keiner bekannt / siehe Local-Fix

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

25.07.2014
14.07.2015
14.07.2015