home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT03388 Status: Closed

INCORRECT INDEX SCAN OUTPUT AFTER ROLLFORWARD OF LOAD ... INDEXI NG MODE
REBUILD FOLLOWED BY LOAD ... INDEXING MODE INCREMENTAL.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* 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.                    * 
****************************************************************
Local Fix:
Force index rebuild. Either drop/recreate index, or mark index 
bad explicitly.
Solution
Firstly fixed in DB2 V10.1 Fixpack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.07.2014
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList