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 IT05326 Status: Geschlossen

DB2 MIGHT PRODUCE INCORRECT RESULT WHEN REFERENCING EMPTY TABLE WITH
AGGREGATE FUNCTIONS IN SUBSELECT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Under rare scenarios, DB2 might produce incorrect results if the 
following conditions are true: 
1) The query references the SYSIBM.SYSDUMMY1 table or a VALUES 
clause. 
2) The sub-select referencing table from 1) contains an 
aggregation function. 
3) The sub-select also has some predicate, which will lead to an 
empty result set. 
4) The topmost select does not reference any column from the 
aforementioned sub-select. 
 
Example: 
select 1 from (SELECT AVG(1) FROM SYSIBM.SYSDUMMY1 where 1=0); 
1 
----------- 
 
  0 record(s) selected. 
 
The correct result is a single row with null value.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* UNKNOWN                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 101 fix pack 5                        * 
****************************************************************
Local-Fix:
Lösung
The problem was first fixed in DB2 version 101 fix pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.11.2014
12.08.2015
12.08.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList