DB2 FOR LUW / DB2FORLUW / A10 - DB2

Under rare scenarios, DB2 might produce incorrect results if the 
following conditions are true: 
1) The query contains 2 or more "IN" LIST predicates 
2) The predicates reference the same column and have at least 1 
non-matching element between them 
3) At least one of the "IN" LIST predicates has been pushed 
deeper 
into the query. 
 
Example: 
 
SELECT vv.col1, vv.col2, min (vi.col3) AS art 
FROM ( 
        SELECT v.col1 AS unr, min (v.col2) AS dat 
        FROM test.VIEW1 v 
        WHERE v.col3 IN (1, 2, 3, 4, 5, 7) 
        GROUP BY v.unr) vv, 
test.VIEW1 vi 
WHERE vv.unr = vi.col1 AND vv.dat = vi.col2 
 
 
GROUP BY vv.unr, vv.dat;

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 fixpack 4                        * 
****************************************************************

Modify the "IN" LIST predicate column to an expression. eg. 
column+0 for numeric columns

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem is fixed in DB2 version 10.1 fixpack 4

not known / see Local fix

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

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

17.02.2014
23.07.2014
23.07.2014