DB2 FOR LUW / DB2FORLUW / 950 - DB2

A calculation problem affects UNION ALL join UNION ALL scenario. 
There is a calculation error in the checks which leads to a 
scenario of not detecting too many joins below the UNION. 
 
 
You can workaround this problem by reducing the 
MAX_JOINS_IN_UNION parameter to a set value and/or reducing the 
query optimization level to 0 or 1.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 users V9.5 FP7 and below                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* There is a calculation error in the checks which leads to a  * 
* scenario of not detecting too many joins below the UNION.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V9.5 FP8 or use work around by         * 
* reducing the MAX_JOINS_IN_UNION parameter to a set value     * 
* and/or reducing the                                          * 
* query optimization level to 0 or 1.                          * 
****************************************************************

(i) db2set DB2_UNION_OPTIMIZATION='MAX_JOINS_IN_UNION <value>' 
 
(ii) You could also reduce the optimization level that the query 
is compiled with to 0 or 1

DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

This fix is first available in DB2 V9.5 FP8

not known / see Local fix

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

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

30.09.2010
30.06.2011
30.06.2011

9.5.FP8