|
Problem IT05812
|
Status: Closed |
INCORRECT RESULTS MIGHT BE RETURNED FOR COLUMN-ORGANIZED TABLES WITH AN ENFORCED PRIMARY KEY OR UNIQUE CONSTRAINTS |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Column-organized tables in 10.5.0.4 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5.0.5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
The problem is first fixed in DB2 version 10.5.0.5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.11.2014
18.12.2014
09.04.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
