Here is an example of a query that might fail:
UPDATE XXXXXX.XXXXXXXXXXXX x SET x.REQ_XML = ( SELECT xmlquery(
'copy $newx := $REQ_XML modify for $j in
$xxxx/xxxxxxxxxxxxxx/xxxxxxxxxxxxxxx/xxxxxxxx/xxxxxxxxxxxx
[@subTermId=$SUB_TERM_ID] return do insert $ADDX1 as last into
$j return $newx' PASSING x.REQ_XML as REQ_XML, T.ADDX1 as
ADDX1, T.SUB_TERM_ID as SUB_TERM_ID ) FROM ( SELECT
SLT2.REQ_ID, SUB_TERM_ID, XMLELEMENT(NAME "swapTermInt") addx1
FROM (SELECT distinct SLT.REQ_ID, SUB_TERM_ID FROM
xxxxxx.xxxxxxxxxxxxxxxxxxxxxxxxxx SLT)as SLT2 ) AS T );
In the db2diag.log, you might see the following logs:
2010-11-22-21.51.50.800749+000 E19878090E552 LEVEL: Severe
PID : 12205 TID : 47478405589312PROC :
db2sysc 0
INSTANCE: XXXXXXXX NODE : 000 DB : EDEDB
APPHDL : 0-189 APPID:
*LOCAL.xxxxxxxx.xxxxxxxxxxxx
AUTHID : MSDB2
EDUID : 116 EDUNAME: db2agent (xxxxx) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:200
MESSAGE : ADM0001C A severe error has occurred. Examine the
administration
notification log and contact IBM Support if necessary.
.....
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: 23
sqlerrmc: curQncp is not XML type
sqlerrp : SQLNQA6A
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFF38 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
****************************************************************
* USERS AFFECTED: *
* XQuery users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Without this APAR, customer is exposed to the issue as *
* described in the "ERROR DESCRIPTION" section. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5, Fixpack 8. *
**************************************************************** |
