|
Problem IT01899
|
Status: Closed |
DB2 MIGHT PRODUCE INCORRECT RESULT WHEN REFERENCING EMPTY TABLE WITH AGGREGATE FUNCTIONS IN SUBSELECT |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 version 10.5 fixpack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
First fixed in DB2 version 10.5 fixpack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.05.2014
11.11.2014
09.04.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
