DB2 FOR LUW / DB2FORLUW / A50 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 version 10.5 fixpack 4                 * 
****************************************************************

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in DB2 version 10.5 fixpack 4

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

20.05.2014
11.11.2014
09.04.2015