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 IT08591 Status: Closed

ORDER BY ON COLUMN NOT INCLUDED IN SELECTED COLUMNS IS NOT SHIPPED TO
FEDERATED SOURCE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When running a query that uses an ORDER BY on a Federated table 
the data may not be ordered correctly. This will occur when the 
ORDER BY is performed on multiple columns and one of them is not 
included in the list of columns in the Select. 
 
For example, the following query will not order the data by 
column 'c': 
    db2 "select a,b from testtab order by a,c" 
 
Changing the Select to include all the columns in the Order By 
then displays the data with the correct ordering. e.g.: 
    db2 "select a,b,c from testtab order by a,c"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Federated Users                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 10.5 Fix Pack 7                                   * 
****************************************************************
Local Fix:
Include all the columns in the Order By in the Select or set 
PUSHDOWN to 'N' in the server options for the Federated server 
e.g.: 
    db2 "ALTER SERVER <servername> OPTIONS (add PUSHDOWN 'N')"
Solution
First fixed in DB2 LUW 10.5 Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.04.2015
19.01.2017
19.01.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList