DB2 FOR LUW / DB2FORLUW / A10 - DB2

If the access plan for a correlated subquery contains a nested 
loop join with a partitioned table on the inner side of the 
join, and if the join predicate AND the correlated predicate are 
pushed down into the scan of the partitioned table, then it's 
possible that wrong results may occur. 
 
The defect is a logic problem during query runtime where data 
partitions are incorrectly eliminated from the scan, resulting 
in the scan failing to qualify records that should have 
otherwise been found.

If the access plan for a correlated subquery contains a nested 
loop join with a partitioned table on the inner side of the 
join, and if the join predicate AND the correlated predicate are 
pushed down into the scan of the partitioned table, then it's 
possible that wrong results may occur. 
 
The defect is a logic problem during query runtime where data 
partitions are incorrectly eliminated from the scan, resulting 
in the scan failing to qualify records that should have 
otherwise been found.

Since the problem is dependent upon the above mentioned access 
plan, it may be possible to get an alternate access plan that 
avoids the problematic codepath in runtime.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 1.

Since the problem is dependent upon the above mentioned access 
plan, it may be possible to get an alternate access plan that 
avoids the problematic codepath in runtime.

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

13.06.2012
02.11.2012
02.11.2012