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

SQL0901N RETURNED WHEN >=4 QUERY ORDER BY COLUMNS ARE EQUIVALENT TO
CONSTANTS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
To hit the problem, a query needs satisfy all the following 
characteristics: 
(1) Query has UNION ALL or LEFT OUTER JOIN construct. 
(2) Query has ORDER BY clause applied on the result of UNION ALL 
or 
    LEFT OUTER JOIN 
(3) At least two columns in ORDER BY clause are equivalent. 
(4) The Fetch First N rows clause is used. 
 
The problem symptom is one of two SQL0901N errors: 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason 
"this->qclqclord.pp() != 
NULL".)  SQLSTATE=58004 
 
or 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason 
"sqlno_int_order_opr_req 
[400]:rc(-2144272209) Sibling order r".)  SQLSTATE=58004 
 
An example query is 
select * from table (select * from t1 union all select * from 
t2) 
where c1 = 1 and c2 = 2 and c3 = 1 and c4 = 4 
order by c1, c2, c3, c4 
fetch first row only;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL0901N error may be returned on some very specific         * 
* SQLstatements.See long description in apar text for a detail * 
* on theconditions.                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the server to V9.5 Fix Pack 6, or apply one of       * 
* theworkarounds mentioned.                                    * 
****************************************************************
Local Fix:
Remove the ORDER BY columns that equal to constants. 
Or change predicate "c3=1" to "c3=1.0".
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The problem was first fixed in V9.5 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66189 IC66190 IC66191 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.02.2010
22.06.2010
28.07.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6,
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)