DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

**************************************************************** 
* 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 * 
****************************************************************

rewrite the query to not use 0 FOLLOWING or install this APAR

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.

keiner bekannt / siehe Local-Fix

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

20.01.2010
24.06.2010
24.06.2010