home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC64772 Status: Geschlossen

Query that uses OLAP specification OVER clause with 0 FOLLOWING might
return wrong results.

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* OLAP SQL with 0 FOLLOWING                                    * 
**************************************************************** 
* 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.          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* rewrite the query to not use 0 FOLLOWING or install this     * 
* APAR                                                         * 
****************************************************************
Local-Fix:
rewrite the query to not use 0 FOLLOWING or install this APAR
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Lösung
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
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC64826 IC65715 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.11.2009
14.04.2010
14.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.1.0.9 FixList