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 IT33071 Status: Closed

DB2 MIGHT RETURN -901 WHEN RUNNING WITH OUTER JOINS AND INNER JOINS.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 might abend when running a query with the following
characteristics:

1. the query has at least one outer join(OJ)
2. on the row preserving(RP) side of this OJ, there are multiple
table inner join(IJ)
3. a local predicates applied on at least 2 inner joined tables
on the RP side of the OJ reference the same constants; one of
these local predicates references a column output to the OJ and
this column is also used in an OJ predicate

With the criteria above met, an invalid correlation could be
formed during Outer Join to Semi Join transformation. Depending
on when and how this bad correlation is detected, a message of
-901 and a stack can differ.

The workaround is to turn off OJSJ transformation.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2_v111m4fp6 or later                            *
****************************************************************
Local Fix:
db2set -im DB2COMPOPT=NOOJSJ
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.06.2020
14.01.2021
14.01.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)