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

POSSIBLE PERFORMANCE REGRESSION FROM SCALAR SUBQUERY PUSH DOWN INTO OUTER
JOIN

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A SQL staement containing a scalar subquery used in the context 
of >=, >, <=, <, !=, or as an expression of other expression 
rather than an equality predicate may be pushed down under an 
Outer Join operation. If the whole expression results in an 
expanding join because of the push down, it could potentially 
degrade the performance of the statement.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A SQL statement containing a scalar subquery used in the     * 
* context                                                      * 
* of >=, >, <=, <, !=, or as an expression of other expression * 
*                                                              * 
* rather than an equality predicate may be pushed down under   * 
* an                                                           * 
* Outer Join operation. If the whole expression results in an  * 
*                                                              * 
* expanding join because of the push down, it could            * 
* potentially                                                  * 
* degrade the performance of the statement.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 2                        * 
****************************************************************
Local Fix:
Upgraded to DB2 Version 9.1 Fix Pack 9
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 version 9.7 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.01.2010
17.05.2010
15.06.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 FixList