suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT23349 Status: Closed

DB2 MAY RETURN SQL0901N: EMPTY PLAN LIST DETECTED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Queries that reference to columns from the objects at the same
level of the FROM clause
using the keyword TABLE in combination with the usage of LEFT
OUTER JOIN keyword
such as the example below:

SELECT
  ...
FROM
  table_1
  LEFT OUTER JOIN
  table_2
  ON 
  LEFT OUTER JOIN
  TABLE (SELECT
           ...
         FROM
           table_3
         WHERE
           [reference to table_2.columns]
        )
  ON 
...

The references to columns from table_2 which are the right
operand of the LEFT OUTER JOIN prior to the keyword TABLE
may cause "SQL0901N Empty plan list detected".

The keyword LATERAL is a synonym of TABLE.

RIGHT OUTER JOIN may cause the same problem when the references
is to the left operand of the RIGHT OUTER JOIN.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Rewrite the query such that it uses a different plan.        *
****************************************************************
Local Fix:
Rewrite the query to avoid this issue.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT23350 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.11.2017
08.01.2018
08.01.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)