DB2 FOR LUW / DB2FORLUW / 910 - 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. 
 
Issue is first fixed in DB2 Version 9.1 Fix Pack 12.

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.

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

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

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

19.12.2011
19.04.2013
19.04.2013