home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC86717 Status: Closed

PREDICATES MIGHT NOT BE PUSHED DOWN FOR QUERY containing UNION ALL and
MULTIPLE nested SUBQUERIES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Under rare scenarios, join predicates might not be pushed 
through a Union All if the following conditions are satisfied. 
 
1. The query contains 1 or more Union All. 
2. The Union All has a join to another table 
3. There are multiple subqueries present where 1 or more 
subqueries are complex. Subqueries are considered complex if 
they contain another subquery or have constructs like group by, 
outer join, Union All, etc. 
4. All the subqueries are either non-correlated or correlated to 
the same Union All. 
 
Ex. V1 is a view containing a basic UNION ALL : 
 
create view v1 as ( select * from tab1 where col1 = 0 union all 
select * from tab1 ) 
 
-- Query: 
select distinct v1.col3 
from v1, tab2 t2 
where v1.col1 = t2.col1 and 
   ( 
   exists ( select 1 from tab2 tt2 where tt2.col2 = v1.col2) 
   ) 
   or 
   ( 
   -- condition 3. Complex subquery 
   exists ( select 1 from tab2 tt2 where tt2.col2 = v1.col1 
              and not exists ( select 1 from tab2 tt3  where 
              tt3.col3 = v1.col2)) 
   )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to version 10.1 fixpack 3                            * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
first fixed in version 10.1 fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.09.2012
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList