DB2 FOR LUW / DB2FORLUW / A50 - DB2

A DELETE statement running on a column-organized table at the 
same time as an UPDATE statement might cause the UPDATE 
statement to fail to update certain rows. 
 
Consider the following example of the problem: 
 
Suppose we have two tables, the first of which is a 
column-organized table with a primary key: 
 
create table t(k int not null primary key, p int) organize by 
column; 
insert into t values (1,1), (2,2), (3,3); 
create table t2 "(k2 int) organize by row; 
insert into t2 values (1), (2); 
 
Suppose we have two connections that execute the following SQL 
statements: 
 
Connection 1: 
update t set p = p + 1 where k in (select k2 from t2); 
 
Connection 2: 
delete from t where k = 1; 
 
If the timing is just right, the UPDATE statement might 
incorrectly fail with an SQL0100W error: 
SQL0100W  No row was found for FETCH, UPDATE or DELETE; or the 
result of a query is an empty table.  SQLSTATE=02000 
 
Then, if the same UPDATE statement is executed again, the 
following records are left in table t: 
 
K           P 
----------- ----------- 
          3           3 
          2           3 
 
We have a value of 3 for P instead of 4 for the row k = 2. Thus, 
the concurrent DELETE caused incorrect results.

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

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       :

23.04.2014
08.09.2014
08.04.2015