DB2 FOR LUW / DB2FORLUW / A50 - DB2

In DB2 version 10.5 Fix Pack 4, SQL against a column-organized 
table might produce an incorrect result if all of the following 
conditions are met: 
- There is an index defined on the table 
- A single row update is performed against the table such that 
an index scan was used to locate the row being updated 
- Lock escalation occurred or the LOCK TABLE command was 
executed resulting in an exclusive lock on the table 
 
Any SQL statements subsequently issued against this table could 
result in the row that was previously updated being incorrectly 
skipped.  The row will continue to be skipped until the fix is 
applied.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Column-organized tables in 10.5.0.4                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.5.                             * 
****************************************************************

The problem is first fixed in DB2 version 10.5.0.5.

keiner bekannt / siehe Local-Fix

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

27.11.2014
18.12.2014
09.04.2015