DB2 FOR LUW / DB2FORLUW / A50 - DB2

WRONG RESULT - QUERY ON COLUMN ORGANIZED TABLE AFTER INSERT IN 
SAME TRANSACTION MIGHT RETURN ROWS THAT WERE DELETED BY ANOTHER 
APPLICATION, OR OLD VALUES OF ROWS THAT WERE UPDATED BY ANOTHER 
APPLICATION, DESPITE THE OTHER APPLICATION HAVING COMMITTED 
PRIOR TO THE START OF SAID QUERY. 
 
The problem exists since version 10.5 (Kepler GA). 
 
Minimal example reproduction: 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
session 1 
---------- 
db2 +c 
connect to sample 
create table t (a int) organize by column 
insert into t values 1,1,1,2,2 
commit work 
insert into t values 3 
 
session 2 
----------- 
db2 +c 
connect to sample 
delete from t where a = 1 
commit work 
 
session 1 
----------- 
select * from t 
 
A 
----------- 
          1 
          1 
          1 
          2 
          2 
          3 
 
  6 record(s) selected. 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
The three "1" values returned above should not have been part of 
the result set.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 for Linux, UNIX, and Windows version          * 
* 10.5.0.4.                                                    * 
****************************************************************

Avoid running a query against a column organized table that has 
been inserted into or updated earlier in the same transaction. 
Or, if such a transaction is unavoidable, do not run it 
concurrent to other applications that perform deletes or updates 
on the same column organized table.

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
 

Problem is first fixed in DB2 for Linux, UNIX, and Windows 
version 10.5 fix pack 4.

See LOCAL FIX.

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

31.07.2014
15.09.2014
15.09.2014