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

SQL0901 REASON "ORDER COLS REMOVED FROM SORT OUTPUT COLS." WITH
DB2_WORKLOAD=PUREDATA_OLAP

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When the registry variable :  DB2_WORKLOAD=PUREDATA_OLAP  is 
set, a heuristic that is applied during query compilation can 
lead to error : 
 
SQL0901 Reason "Order cols removed from sort output cols." 
 
for statements that have no group by clause nor distinct 
aggregate and that use the min/max aggregate. 
 
This also only occurs in DPF or SMP environments. 
 
This particular problem does not happen in versions below V10.1 
Fix Pack 2.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* users with DB2_WORKLOAD=PUREDATA_OLAP set                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade the database server to V10.1 Fix Pack 4              * 
****************************************************************
Local-Fix:
enable this registry setting : 
db2set DB2_EXTENDED_OPTIMIZATION="ON,COMPLETE_GB,TQPERF 30"
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
This problem has first been fixed in V10.1 Fix Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.09.2013
26.06.2014
26.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList