DB2 FOR LUW / DB2FORLUW / A50 - DB2

Query performance may be poor when the query contains at least 
three (3) tables joined together using INNER or OUTER joins and 
there are at least 2 equal join predicates and at least two 
local equality predicate. 
 
  The last table in the join sequence must have multicolumn 
index covering the columns involved in the predicates. The 
equality join predicates must be applicable on the first and 
last columns of the index with the local eer quality predicate 
applicable on the intermediate columns of the index. 
 
  Under these conditions the optimizer may incorrect calculate 
the cost of the joins leading to a poorly performing plan.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 fixpack 4                        * 
****************************************************************

Use an optimization profile to obtain a better join order 
  or 
  Change the index definition so that the join predicate are 
applicable to either the leading or trailing columns of the 
index without any intermediate local equality predicates.

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 version 10.5 fixpack 4

keiner bekannt / siehe Local-Fix

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

27.08.2013
08.09.2014
08.09.2014