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

IMPROVE THE HANDLING OF CONVERSION TO NLJOIN FROM MULTIPLE IN PREDICATES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If a query WHERE clause contains more than one simple IN 
predicates whose IN operand is base column and IN elements are 
composed of only literals, DB2 query compiler can convert one of 
them to NLJOIN. It is possible that the compiler converts a 
suboptimal IN predicate rather than the optimal one. The fix 
makes sure the converted IN predicate is the optimal one. 
 
Local fix: Use optimizer profile option "<INLIST2JOIN 
OPTION="ENABLE" TABLE="TABLE_NAME" COLUMN="COLUMN_NAME"/>. 
Replace TABLE_NAME and COLUMN_NAME with the real name of the IN 
predicate dedicated to DB2 compiler for attempting the IN to 
NLJOIN conversion.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* V9.7 users fix pack2 and earlier                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* predicates whose IN operand is base column and IN elements   * 
* are                                                          * 
* composed of only literals, DB2 query compiler can convert    * 
* one of                                                       * 
* them to NLJOIN. It is possible that the compiler converts a  * 
*                                                              * 
* suboptimal IN predicate rather than the optimal one. The fix * 
*                                                              * 
* makes sure the converted IN predicate is the optimal one.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to fix pack 3                                        * 
****************************************************************
Local Fix:
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Workaround
Local fix: Use optimizer profile option "<INLIST2JOIN 
OPTION="ENABLE" TABLE="TABLE_NAME" COLUMN="COLUMN_NAME"/>. 
 
Replace TABLE_NAME and COLUMN_NAME with the real name of the IN 
predicate dedicated to DB2 compiler for attempting the IN to 
NLJOIN conversion.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.12.2009
24.09.2010
24.09.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList