DB2 - Problem description
Problem IC88499 | Status: Closed |
DB2 CAN RETURN A SQL0901N ERROR WITH REASON "SQLNO_ITR_PLAN::NEXT [300]:RC( 0)" | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
On rare occasions, when compiling a query, DB2 can return the following SQL0901N error: SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "sqlno_itr_plan::next [300]:rc( 0) ".) SQLSTATE=58004 When the SQL0901N occurred, you can also observe an entry similar to the following in db2diag.log: 2012-10-29-03.21.01.792075-240 E1747E4958 LEVEL: Error PID : 361 TID : 47125681400128PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-34179 APPID: 169.81.40.31.29706.121029072101 AUTHID : DB2INST1 EDUID : 1771 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, SW- optimizer, sqlno_plan_compare, probe:220 MESSAGE : Winning plan still needs GLUE | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to IBM DB2 version 9.7 Fix Pack 8 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
Problem is first fixed in DB2 v9.7 Fix Pack 8. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC91291 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.11.2012 01.04.2013 01.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |