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

WRONG RESULTS MIGHT BE OBSERVED WHEN RUNNING QUERIES WITH OUTER JOINS AND
GROUP BY OPERATIONS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
A query might generate wrong results when the query contains the
following characteristics:
1) it contains at least one outer join
2) on the null producing side of this outer join, there is at
least one aggregation and this null producing side at most
produces one row
3) the row preserving side of this outer join also at most
produces one row

Ex.
select A.a1, B.sum
from a
A              -- row preserving side
left join
(select sum(B.b3) as sum from b B where B.b1=1 and B.b2=2) B  --
null producing side
on 1=1
where A.a1=1

Where A.a1 contains unique key so the predicate - "A.a1=1"
ensures that there is at
most one row output from A, and the row preserving side also
only outputs at most one row due to the aggregation.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description and install the fix.                   *
****************************************************************
* RECOMMENDATION:                                              *
* See Error Description and install the fix.                   *
****************************************************************
Local Fix:
db2set -im DB2COMPOPT=NO_GBPU
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.04.2019
29.11.2019
23.03.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)