|
Problem IC69110
|
Status: Closed |
SQL0901N MAY BE RETURNED FROM RUNNING A QUERY (this->oprprd.op()!= NULLP). |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
SQL0901N may be returned when running a query.
The complete error message may look like this:
SQL0901N The SQL statement failed because of a non-severe
system error.
Subsequent SQL statements can be processed. (Reason
"this->oprprd.op() !=
NULLP".) SQLSTATE=58004
db2diag messages may look as follows:
2010-06-08-06.03.20.903000-240 I42694F869 LEVEL: Severe
PID : 3692 TID : 2772 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : 0-2688 APPID: GA070292.HC0F.127D08100227
AUTHID : db2inst1
EDUID : 2772 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 26
sqlerrmc: this->oprprd.op() != NULLP
sqlerrp : SQLNQ0CA
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFECA (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
2010-06-08-06.03.22.950000-240 E68922F849 LEVEL: Info
(Origin)
PID : 3692 TID : 2772 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : 0-2688 APPID: GA070292.HC0F.127D08100227
AUTHID : db2inst1
EDUID : 2772 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650
MESSAGE : ZRC=0x803100AF=-2144272209=SQLNN_E_BADNEWS
"unexpected error but state is OK"
DATA #1 : String, 302 bytes
Compiler error stack for rc = -2144272209:
sqlnn_cmpl[370]
sqlnr_exe[1200]
sqlnr_rcc[100]
sqlnr_seq[100]
sqlnr_comp[110]
sqlnr_optprep_action[100]
sqlnr_optprep[660]
sqlnr_inject_sel4nonlocal[700]
sqlnq_qur::remove_orphaned[120]
sqlnq_qtb::box_drop_ts[120]
sqlnq_opr::drop[200]
sqlnq_opr::destroy[310] |
| Problem Summary: |
SQL0901N MAY BE RETURNED FROM RUNNING A QUERY (this->oprprd.op()
!= NULLP). |
| Local Fix: |
As a temporary workaround, might want to try the reduced
optimization level.
For Ex:
db2 set current query optimization 3
NOTE: This might not work for all cases. |
| 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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 V97FP3
LOCAL FIX:
As a temporary workaround, might want to try the reduced
optimization level.
For Ex:
db2 set current query optimization 3
NOTE: This might not work for all cases. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.06.2010
29.09.2010
29.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
|
 |
| 9.7.0.3
|
|
