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

QUERIES CONTAINING MULTIPLE OUTER JOIN OPERATIONS AND NESTED EXPRESSIONS
MAY PRODUCE INCORRECT RESULTS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Queries containing multiple outer join operation may produce 
incorrect results under certain conditions. 
 
An OUTER JOIN used in a view, common table expression or nested 
sub-select and contains expressions that do not reference the 
input operands of the OUTER JOIN or complex scalar expressions 
such as 
- CASE expressions 
- COALESCE 
- DECODE 
- VALUE 
- or external user defined functions which are not defined as 
'RETURNS NULL ON NULL INPUT'. 
 
When such an view, common table expression, or nested sub-select 
is used as the NULL producing operand of a higher level OUTER 
JOIN then the query may produce incorrect results.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP8                                      * 
****************************************************************
Local Fix:
The following registry can be used to avoid the potential wrong 
result: 
db2set -im DB2COMPOPT=NO_OJLINEAR
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.05.2016
10.01.2017
22.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)