DB2 - Problem description
Problem IC97915 | Status: Closed |
QUERY MAY RETURN INCORRECT RESULTS WHEN IT CONTAINS A SUB-SELECT WITH CORRELATION AND A FETCH FIRST N ROWS CLAUSE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
A query may return wrong results under certain condition. The characteristics of the affected query are: a) it will contain a FETCH FIRST n ROWS clause b) the sub-select or full-select containing the FETCH FIRST n ROWS clause from (a) will contain a nested sub-select or EXISTS predicate or IN subquery predicate. c) The nested sub-select from (b) will contain an outer-reference to another input to the sub-select or full-select from (a) After gathering the db2exfmt output for potential queries that may be impacted, it will typically contain a SORT operator that reduces the stream cardinality to the value specified in the FETCH FIRST n ROW clause and a NLJOIN operator without predicates above the SORT, one of whose inputs is the sub-select containing the outer-reference. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 fix pack 4. * **************************************************************** | |
Local Fix: | |
Rewrite the query to eliminate the outer-reference in the sub-select. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
The fix will be included in DB2 Version 10.1 fix pack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.11.2013 24.03.2014 24.03.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |