DB2 FOR LUW / DB2FORLUW / 970 - DB2

In certain conditions, DB2 does not apply the IN-LIST-to-join 
query 
rewrite when the optimization guideline IN2JOIN is specified. 
 
For example: 
 
In the SQL statement below 
 
SELECT ... 
FROM    PARTS P, SUPPLIERS S, PARTSUPP PS 
WHERE P.PARTKEY = PS.PS_PARTKEY 
AND      S.S_SUPPKEY = PS.PS_SUPPKEY 
AND      P_SIZE IN (?, ?, ?, ...) 
AND      ... 
 
and an optimization guideline 
 
<OPTGUIDELINES><INLIST2JOIN TABLE='P' 
COLUMN='P_SIZE'/></OPTGUIDELINES> 
 
is specified. The statistics information of the table P and the 
columns in the table are not sufficient to indicate that the 
IN-LIST-to-join will outperform other optimization techniques. 
However, when the optimization guideline IN2JOIN is specified, 
DB2 should apply the optimization regardless of the outcome from 
the analysis of the statistics information.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP9                                      * 
****************************************************************

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
 

Fixed in DB2 V9.7 FP9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC91788 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.02.2013
17.12.2013
17.12.2013

9.7.FP9