|
Problem IC64826
|
Status: Closed |
Query that uses OLAP specification OVER clause with 0 FOLLOWING might return wrong results. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
A query that uses the OLAP specification "OVER" clause and also
contains "0 FOLLOWING" might give wrong results.
The following is an example query that can give wrong results:
SELECT C1, C2, COUNT(C2) OVER (ORDER BY C1 ROWS BETWEEN 0
FOLLOWING AND 1 FOLLOWING) from t1
In the case of wrong results, for the above query the 3rd column
that is output (i.e. count(c2)) might show an incorrect number
for the count.
To workaround you can rewrite your query to not use "0
FOLLOWING".
"CURRENT ROW" or "0 PRECEDING" can be used instead. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* OLAP SQL with 0 FOLLOWING *
****************************************************************
* PROBLEM DESCRIPTION: *
* A query that uses the OLAP specification "OVER" clause *
* andalsocontains "0 FOLLOWING" might give wrong results.The *
* following is an example query that can give *
* wrongresults:SELECT C1, C2, COUNT(C2) OVER (ORDER BY C1 ROWS *
* BETWEEN 0FOLLOWING AND 1 FOLLOWING) from t1In the case of *
* wrong results, for the above query the 3rdcolumnthat is *
* output (i.e. count(c2)) might show an incorrectnumberfor the *
* count.To workaround you can rewrite your query to not use *
* "0FOLLOWING"."CURRENT ROW" or "0 PRECEDING" can be used *
* instead. *
****************************************************************
* RECOMMENDATION: *
* rewrite the query to not use 0 FOLLOWING or install thisAPAR *
**************************************************************** |
| Local Fix: |
rewrite the query to not use 0 FOLLOWING or install this APAR |
| available fix packs: |
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 |
A query that uses the OLAP specification "OVER" clause and
also
contains "0 FOLLOWING" might give wrong results.
The following is an example query that can give wrong results:
SELECT C1, C2, COUNT(C2) OVER (ORDER BY C1 ROWS BETWEEN 0
FOLLOWING AND 1 FOLLOWING) from t1
In the case of wrong results, for the above query the 3rd
column
that is output (i.e. count(c2)) might show an incorrect number
for the count.
To workaround you can rewrite your query to not use "0
FOLLOWING".
"CURRENT ROW" or "0 PRECEDING" can be used instead. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.11.2009
31.05.2010
31.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
