DB2 FOR LUW / DB2FORLUW / A50 - DB2

This applies to any databases with the above specific condition. 
 
The problem can happen only if the index in question is defined 
with the "PCTFREE 0" 
option.  Then an online incremental load must be performed. 
During a very specific internal error scenario  and recovery, 
there is a chance that the index page could get corrupted 
and we end up with duplicate keys  on the page. 
 
Symptoms may include index-data mismatch or incorrect results. 
 
Running db2dart or inspect may be able to detect the problem. 
Look for duplicate key or key data mismatch error messages.

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

To avoid hitting this problem as opposed to undo the corruption, 
the user can use db2dart /mi option to mark the index bad before 
recovering the failed load command. 
 
Applying the APAR fix will prevent the problem from occurring. 
 
If this problem is hit and the index is corrupted, then the 
solution is to use db2dart /mi to mark the index invalid and 
then the next access to the table will rebuild the index.

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
 

The problem is first fixed in DB2 version 10.5.0.4.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

11.07.2014
08.09.2014
26.10.2015