DB2 FOR LUW / DB2FORLUW / 970 - DB2

The DB2 optimizer might generate a non-optimal access plan for 
complex queries containing one or more equality join predicates. 
This problem is more likely to occur when STMTHEAP is set to 
AUTOMATIC and after applying DB2 Version 9.7 Fix Pack 8,9, or 
10. 
 
You can identify this issue by gathering an EXPLAIN of the 
query.  If the problem is hit, you will receive a SQL0437W with 
rc=1 during query compilation, and the EXPLAIN output will 
include filter factor estimates and cardinality estimates of 0.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 v9.7 FP11 or higher                           * 
****************************************************************

You can increase the STMTHEAP to avoid the problem.  To identify 
an appropriate size, you can gather an EXPLAIN of the query and 
set it to a value larger than the one shown under the HEAPUSE 
argument of the RETURN operator.

Fixed in DB2 v9.7 FP11

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

31.03.2015
07.10.2015
07.10.2015

9.7.FP11