|
Problem IT03115
|
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 / A50 - 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: *
* EE/DPF/SD, but not HADR *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 105 fix pack 4 *
**************************************************************** |
| Local Fix: |
Force index rebuild. Either drop/recreate index, or mark index
bad explicitly. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in Version 105 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.07.2014
14.07.2014
14.07.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
