DB2 FOR LUW / DB2FORLUW / A10 - 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:                                              * 
* UNKNOWN                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 101 fix pack 5                        * 
****************************************************************

The problem was first fixed in DB2 version 101 fix pack 5

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.11.2014
12.08.2015
12.08.2015