home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC95716 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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"
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
This problem has first been fixed in V10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.09.2013
26.06.2014
26.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList