|
Problem IT01104
|
Status: Closed |
DELETE RUNNING CONCURRENTLY WITH A RUNSTATS MAY CAUSE INCORRECT QUERY RESULTS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
If a DELETE on a column-organized table has an exclusive (X)
table lock and it is deleting from the head of the table, a
concurrent RUNSTATS of the same table could incorrectly set an
internal state that affects query results. This becomes an
issue if the DELETE rolls back. It is possible that some of its
rows will not be included in subsequent queries due to the
internal state change made by RUNSTATS. In order for the DELETE
to have an exclusive (X) table lock, lock escalation must have
occurred or an explicit LOCK TABLE command was issued. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem is first fixed in DB2 UDB version 10.5 fix pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.04.2014
08.09.2014
08.09.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
|
 |
