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 IC96254 Status: Closed

LOCAL PREDICATES MAY NOT BE PUSHED DOWN BELOW A UNION OPERATOR WHEN THE
UNION OPERATOR IS REFERENCED MORE THAN ONCE.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When a UNION operator is part of a view or a common table 
expression (CTE) and the view or the CTE 
is referenced more than once in the query, local predicates may 
not be pushed down below the UNION 
if there are subqueries with correlation within the view or CTE. 
 
 
The following describes the problem from an SQL perspective and 
correlates the relevant parts to the 
5 conditions required to encounter this problem listed below: 
 
with CTE as 
(select c1,c2 from t1 
union all 
/* [1] */ 
select c1,c2 from t1_archive t2 
where not exists (select 1 from t1 where t1.c0=t2.c0)    /* [2] 
*/ 
select ... 
from   CTE parent 
where parent.c1 = all (select c1 from CTE subq             /* 
[3] */ 
                                 where subq.c2=parent.c2) 
/* [4] */ 
          parent.c2 = <const>) 
/* [5] */ 
 
 
 
[1] The CTE has a UNION operator. 
[2] The CTE contain a subquery (not exists) with a correlation. 
[3] The CTE is referenced twice in the query. 
[4] There is a correlation from one reference of the CTE to 
another reference of the CTE. 
[5] There is a local predicate referencing the same column from 
[4].
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 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
Upgrade to DB2 version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.09.2013
17.10.2013
17.10.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