|
Problem IT05462
|
Status: Closed |
INCORRECT RESULTS MIGHT BE RETURNED FOR A QUERY INVOLVING AN AGGREGATION FUNCTION AND AN OUTER JOIN OPERATOR |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
An outer join query may return incorrect results when all of the
following conditions are satisfied:
- The registry variable DB2COMPOPT is set to list that includes
OJLOCALPRDPLANNING either explicitly or implicitly by setting
the DB2_WORKLOAD registry variable to 1C or PUREDATA_OLAP
- There is a predicate in the ON clause of the JOIN operator
that references only columns from the row preserving side of the
join operands
- The access plan of the query has a partial GROUP BY operator
on the row preserving operand of the outer join operator |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.5. *
**************************************************************** |
| Local Fix: |
Use the DB2_REDUCED_OPTIMIZATION=NO_PEA registry variable to
pick plans that avoid the issue. |
| Solution |
The problem is first fixed in DB2 version 10.1.0.5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.11.2014
10.07.2015
10.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
