|
Problem IC91291
|
Status: Closed |
DB2 CAN RETURN A SQL0901N ERROR WITH REASON "SQLNO_ITR_PLAN::NEXT [300]:RC( 0)" |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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: *
* DB2 LUW 10.1 FP 2 and below *
****************************************************************
* 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 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW 10.1 FP3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.04.2013
03.10.2013
03.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
