|
Problem IC61960
|
Status: Closed |
GROUPING SETS SHOULD NOT BE ALLOWED IN AN ORDER BY CLAUSE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
An ORDER BY clause should not allow grouping sets. This is
correctly documented but not properly enforced. The following
invalid query should return SQLSTATE 42803:
SELECT SALES_PERSON,
MONTH(SALES_DATE) AS MONTH,
SUM(SALES) AS UNITS_SOLD
FROM SALES
GROUP BY SALES_PERSON, MONTH(SALES_DATE)
ORDER BY GROUPING SETS( SALES_PERSON, MONTH(SALES_DATE) ) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* An ORDER BY clause should not allow grouping sets. This is *
* correctly documented but not properly enforced. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 version v9.5 fp5 *
**************************************************************** |
| Local Fix: |
Remove GROUPING SETS from the ORDER BY clause |
| available fix packs: |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.5 FixPak 5 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC61992 IC61993
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.07.2009
23.12.2009
23.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.,
9.5.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.5
|
 |
