Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT05044 Status: Geschlossen

INCORRECT RESULTS MIGHT BE RETURNED FOR A QUERY INVOLVING AN AGGREGATION
FUNCTION AND AN OUTER JOIN OPERATOR

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5 or later.             * 
****************************************************************
Local-Fix:
Use the DB2_REDUCED_OPTIMIZATION=NO_PEA registry variable to 
pick plans that avoid the issue.
Lösung
Problem has been fixed in DB2 Version 10.5 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.10.2014
15.12.2014
09.04.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList