DB2 FOR LUW / DB2FORLUW / B50 - DB2

When running a query that qualifies for a zigzag join, it is
possible that the explain format information suggests to add
indexes in order to be able to run zigzag join as part of the
access plan even though an index might already fulfill this
request.

A message similar to the following will be put out:

Extended Diagnostic Information:
--------------------------------

Diagnostic Identifier: 1
Diagnostic Details: EXP0039I Query complexity measure. Highest
number
of joins in any query block: "6".
Diagnostic Identifier: 2
Diagnostic Details: EXP0256I Analysis of the query shows that
the
query might execute faster if an additional index
was created to enable zigzag join. Schema name:
"RUW_APP ". Table name: "TABLENAME". Column list:
"(COLUMN1, COLUMN2)".

****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5 m3 fp0 or later                          *
****************************************************************

not known / see Local fix

forerunner  : IT31125 
follow-up : 

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

03.12.2019
24.04.2020
24.04.2020