DB2 - Problem description
Problem IT03642 | Status: Closed |
INCORRECT RESULTS POSSIBLE IN CASES WHERE A COLUMN ORGANIZED TABLE IS MODIFIED BY TWO TRANSACTIONS AT THE SAME TIME | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
In cases where multiple update or delete statements are occurring on a given column-organized table at the same time, one or more of the statements may not act on the correct set of rows. For example, if the following two statements are ran at the same time in different transactions: update t1 set c1 = 5 where c1 = 4; delete from t1 where c1 = 5 or c1 = 4; and the transaction performing the update statement commits first, it is expected that the delete transaction will leave the table without any rows where c1 = 5 or c1 = 4. In some circumstances, however, the table will be left with one or more rows where c1 = 5 or c1 = 4. Note that this issue ONLY affects tables which were populated using an insert-subselect statement on releases 10.5, 10.5 FP1, 10.5 FP2, or 10.5 FP3. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of column-organized tables * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
Local Fix: | |
Populate tables using either LOAD, INGEST, or an insert-values statement. Alternatively, do not run concurrent updates or delete statements against the column-organized tables in your database which were populated using insert-subselect. | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
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 : | 07.08.2014 08.09.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.4 |