home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT05436 Status: Geschlossen

IN A RARE CONDITION, A QUERY AGGREGATING WITHOUT GROUP BY CLAUSE ON A
PROVABLE 0-ROW STREAM CAN RETURN INCORRECT RESULT

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The problem can happen in DPF environment only. Queries that 
aggregate on a provable 0 row stream without group by 
clause can return incorrect result when DB2 optimizer uses the 
"0 row" property to optimize query plans, such as removing 
duplicate-eliminating sort. 
 
For example: 
 
select max(IBMREQD) from sysibm.sysdummy1 where 0=1 
union 
select max(IBMREQD) from sysibm.sysdummy1 where 0=1 
; 
 
 
In this query, each union leg should return 1 row of "NULL" 
value. Since this is a distinct UNION, the final result should 
still be 1 row of "NULL" value. 
 
But because DB2 optimizer thinks that each union leg returns 0 
row, it removes the duplicate-eliminating sort that should have 
been done after "UNION ALL". So the final returned result is 2 
rows of "NULL" value, which is incorrect.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF (Database Partitioning Feature)                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 5                               * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 10.5 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.11.2014
15.12.2014
15.12.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList