DB2 - Problem description
Problem IC66189 | Status: Closed |
SQL0901N RETURNED WHEN >=4 QUERY ORDER BY COLUMNS ARE EQUIVALENT TO CONSTANTS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - 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: * * users with queries as per apar description criteria * **************************************************************** * PROBLEM DESCRIPTION: * * A query which satisfies the criteria outlined in the apar * * description may incorrectly return error code -901 * **************************************************************** * RECOMMENDATION: * * Upgrade to the V9.5 or V9.7 fixpak that addresses this * * problem. * **************************************************************** | |
Local Fix: | |
Remove the ORDER BY columns that equal to constants. Or change predicate "c3=1" to "c3=1.0". | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.02.2010 23.02.2010 29.07.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5., 9.7. | |
Problem solved according to the fixlist(s) of the following version(s) |