DB2 - Problem description
Problem IC80536 | Status: Closed |
QUERY RETURNS INCORRECT RESULTS FOR A CORRELATED SUBQUERY AGAINST A DATA PARTITIONED TABLE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
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. First fixed in DB2 Version 9.7 Fix Pack 6 | |
Local Fix: | |
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. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
Since the problem is dependent upon access plan, it may be possible to get an alternate access plan that avoids the problematic codepath in runtime. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.12.2011 19.04.2013 19.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |