DB2 FOR LUW / DB2FORLUW / 950 - DB2

Under rare scenarios, DB2 might produce incorrect results. 
 
1. The query has a NOT IN predicate 
2. The NOT IN predicate references 2 or more nullable columns 
from either parent or subselect tables or both. 
 
eg. 
create table t1 (c1 int, c2 varchar(10), c3 char(1), c4 
decimal); 
create table t4 (c1 int NOT NULL, c2 varchar(10) NOT NULL, c3 
char(1) NOT NULL, c4 decimal NOT NULL); 
 
insert into t1(c1) values NULL, NULL, 100, 200, 1000; 
insert into t4 values (1,'a', 'a', 1.0),(2,'b','b',2.0); 
 
select t1.* from t1 where (c1,c2) not in (select c1, c2 from 
t4); 
 
Correct result is 3 rows.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See description                                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 950 fixpack 9                          * 
****************************************************************

for DPF, db2set DB2_ANTIJOIN=NO followed by restart instance 
for serial, None

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

Fix is fixed included in DB2 950 fixpack 9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC78767 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

19.09.2011
12.03.2012
12.03.2012

9.0.,
9.5.0