DB2 - Problem description
Problem IC65344 | Status: Closed |
WRONG RESULTS MAY OCCUR IF THE QUERY CONTAINS EXISTENTIAL SUBQUE RIES AND A CORRELATED UNION ALL CONSUMED IN THE SAME SUBSELECT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Wrong results have been noted on all version of DB2 if the following conditions are true: 1. There are two or more existential subqueries present in the query. 2. There is a UNION ALL with the following characterstics: a. One arm of the UNION ALL has less number of tables as compared to other arm(s) b. The UNION ALL is correlated to the subqueries. 3. The existential subqueries are consumed in the same subselect that consumes the Union ALL | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users using subqueries and union all views in * * theirqueries * **************************************************************** * PROBLEM DESCRIPTION: * * Wrong results have been noted on all version of DB2 if * * thefollowing conditions are true:1. There are two or more * * existential subqueries presentinthe query.2. There is a * * UNION ALL with the following characterstics:a. One arm of * * the UNION ALL has less number of tables ascompared to other * * arm(s)b. The UNION ALL is correlated to the subqueries.3. * * The existential subqueries are consumed in the samesubselect * * that consumes the Union All * **************************************************************** * RECOMMENDATION: * * Update to Version 9.7 Fix Pack 2 * **************************************************************** | |
Local Fix: | |
Change the value of CURRENT QUERY OPTIMIZATION special register to 0 SET CURRENT QUERY OPTIMIZATION 0; | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.12.2009 25.05.2010 25.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |