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

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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:                                         * 
* Under very specific query conditions detailed in the apar    * 
* problem description, SQL error -901 can incorrectly be       * 
* returned by the database server                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to release to V9.7 Fix Pack 3    * 
****************************************************************
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.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem has first been fixed in DB2 V9.7 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.02.2010
24.09.2010
24.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList