|
Problem IC70951
|
Status: Closed |
SQL0901N WHEN RUNNING PSM/XML QUERIES IN DPF |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The following error can be encountered in PSM/XML queries when
running in DPF. This is because when we are RPC'ing references
between nodes we end up reading from section temp when we should
be reading from PSM temp.
SQL0901N The SQL statement failed because of a non-severe
system error.
Subsequent SQL statements can be processed. (Reason "Expected
TEMP TCB".)
SQLSTATE=58004
Db2diag.log
2010-08-16-18.06.31.613565-420 I1710E1479 LEVEL: Severe
PID : 12434 TID : 47588719978816PROC :
db2sysc 0
INSTANCE: apaniag NODE : 000 DB : XMLDB
APPHDL : 0-51 APPID: *N0.apaniag.100817010442
AUTHID : APANIAG
EDUID : 64 EDUNAME: db2agntp (XMLDB) 0
FUNCTION: DB2 UDB, data management, sqldFixExistingTCB,
probe:8061
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
"non-severe dms programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 17 bytes
Expected TEMP TCB
DATA #2 : String, 18 bytes
sqldFixExistingTCB
CALLSTCK:
[0] 0x00002B4805882F98 pdLog + 0x18C
[1] 0x00002B4809683D29 sqlzSetAndLog901 + 0x395
[2] 0x00002B4805FFE76D
_Z18sqldFixExistingTCBP8sqeAgentP16sqeLocalDatabaseP9SQLP_LSN8ii
iiPP8SQLD_TCB
+ 0x5E9
[3] 0x00002B4809A9D558
_Z23xmlsFixXDATempTCBForRPCP11XMLSTORE_CBtt + 0x6E
[4] 0x00002B48083A84AB
_Z24xmlrnFixXDATempTCBForRPCP11XMLSTORE_CBP17xmlDataDescriptor +
0x995
[5] 0x00002B480839D792
_Z21sqlrk_RPCRecvFetchXDMP8sqlrr_cbjR16SqlrkXmlRpcReply + 0x760
[6] 0x00002B480839E7E4
_Z16sqlrk_xml_routerP8sqlrr_cbR16SqlrkXmlRpcReplyP16sqlkdRqstRpl
yFmtP15SQLR_RPCMESSAGEb
+ 0x29C
[7] 0x00002B48082238D3 _Z16sqlrr_rpc_routerP8sqlrr_cb + 0x14D7
[8] 0x00002B4808221840
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x1BBA
[9] 0x00002B4806175272 _Z20sqleSubRequestRouterP8sqeAgentPjS1_
+ 0xAEC
Example procedure:
CREATE procedure xmlproc()
SPECIFIC xmlproc
LANGUAGE SQL
MODIFIES SQL DATA
begin
DECLARE SQLSTATE CHAR(5);
declare stmt_txt varchar(1024);
declare myres xml;
declare v1 xml;
declare stmt STATEMENT;
declare cur1 CURSOR FOR stmt;
set stmt_txt = 'xquery for $i in
db2-fn:xmlcolumn("BOOKSTORE.AUTHORDETAILS")/authors/author/addr
order by $i/city return <myinfo>{$i/city}</myinfo>';
PREPARE stmt FROM stmt_txt;
OPEN cur1;
FETCH cur1 INTO myres;
WHILE (SQLSTATE = '00000') DO
SET v1 = XMLCONCAT(v1, myres);
FETCH cur1 INTO myres;
END WHILE;
CLOSE cur1;
INSERT INTO t4 VALUES(1, XMLSERIALIZE(v1 as varchar(1000)));
end% |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Refer to Error Description in APAR information tag. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97 FP4 or newer release. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
Fix delivered in v97 FP4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.09.2010
28.04.2011
28.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
