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 IC78931 Status: Geschlossen

UNABLE TO SORT DESC ORDER OLAP FUNCTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
When using the DESC or ASC clause within an SQL statement 
containing an OLAP function, the order may not be enforced 
giving unordered results 
 
e.g. 
db2 "select row_number() over() as num, tabname from 
syscat.tables order by num desc" 
gives an unordered result although DESC is specified.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.5 fp9 or later.                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 v9.5 fp9.
Workaround
There are 2 possible workarounds: 
 
1)"order by 1" 
 
db2 "select row_number() over() as num, tabname from 
syscat.tables 
order by 1 desc" 
 
 
 
2)the OLAP query can be moved into a nested subquery 
 
db2 "select num, tabname from ( select row_number() over() as 
num, 
tabname from syscat.tables ) T order by num desc"
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.09.2011
13.03.2012
13.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList