Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC62426 Status: Closed

XQUERY with a substring() function can not retrieve any row due to an
XMLRN_PRG_ERR error.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
If you run a XQUERY with a substring function as below example 
to a table which has multi-byte charactors, you may see below 
messages at db2diag.log and the associated trap file 
(t4539.000) has similar stack trace (CALLSTCK) as belows. 
The XQUERY can not be run and will not return rows but SQL901N 
error. 
 
An example XQUERY: 
--------------------------------------------------------------- 
XQUERY (for $a in db2-fn:xmlcolumn("REPORT.REPORTDOC")/ 
reportdoc where $a/status = "AAA" and $a/approve_info/ 
appCurrentInfo[@userID = "BBB" and @domain = "BPR"] 
order by $a/date/sDate descending return <doc> {$a/@pdocID} 
{$a/contents/subject} <body>{substring($a/contents/body, 1, 
100)}</body> {$a/owner_info/name} {$a/date/sDate} </doc> ) 
[position() <= 50]; 
--------------------------------------------------------------- 
 
From the db2diag.log: 
--------------------------------------------------------------- 
  <snip> 
 
2009-07-13-12.51.21.397989+540 I35764911E4623   LEVEL: Severe 
PID : 4539         TID  : 18303452064 : db2agent () 
INSTANCE: db2inst1        NODE : 000   DB   : DB 
APPHDL : 0-314         APPID: 9.224.18.56.58768.0907151 
AUTHID : DB2INST1 
FUNCTION: DB2 UDB, XML Node Manager, 
XmlrnSerializerSerializeFragmentForError, probe:887 
MESSAGE : ZRC=0x82A40001=-2103181311=XMLRN_PRG_ERR 
  "XMRN unexpected system error" 
 DIA8532C An internal processing error has occurred. 
DATA #1 : String, 35 bytes 
FragmentForErrorMsg already visited 
DATA #2 : Xmlrn Serializer object, PD_TYPE_XMRN_SERIALIZER, 
896 bytes 
XmlrnSerializer: 
 
 <snip> 
 
CALLSTCK: 
 [0] ... _ZN15XmlrnSerializer28serializeFragmentForErrorMs... 
[1] ... _ZN15XmlrnSerializer9serializeERjRtP24sqlriXmlSerial 
[2] ... _ZN15XmlrnSerializer28serializeFragmentForErrorMsgER 
[3] ... _ZN15XmlrnSerializer9serializeERjRtP24sqlriXmlSerial 
[4] ... _Z19sqlriMaterializeXmlP8sqlrr_cbP10sqlz_valuePhPjPP 
[5] ... _Z23sqljsDrdaAsCBPutXmlDataP14db2UCinterfaceP10sqlz_ 
[6] ... _Z17sqlribnoLobCbDrdaP14db2UCinterface + 0x38B 
[7] ... _Z8sqlribnoP8sqlrr_cb + 0x3E6 
[8] ... _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0xBD 
[9] ... _Z27sqlrr_process_fetch_requestP14db2UCinterface + 0 
 
<snip> 
 
2009-07-13-12.51.21.452658+540 I35779693E4446   LEVEL: Severe 
PID : 4539         TID  : 18303452064 : db2agent () 
INSTANCE: db2inst1        NODE : 000   DB   : DB 
APPHDL : 0-314         APPID: 9.224.18.56.58768.0907151 
AUTHID : DB2INST1 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 
MESSAGE : section stmt 
DATA #1 : Hexdump, 785 bytes 
... : 5851 5545 5259 2028 6C65 7420 2470 6461  XQUERY (let 
$pda 
... : 7465 203A 3D20 666E 3A64 6174 6554 696D  te := 
fn:dateTim 
... : 6528 7873 3A64 6174 6528 2732 3030 392D 
e(xs:date('2009- 
... : 3037 2D31 3327 292C 7873 3A74 696D 6528 
07-13'),xs:time( 
 
 <snip> 
 
2009-07-13-12.51.21.452970+540 I35784140E178   LEVEL: Severe 
PID:4539 TID:183034520640 NODE:000 Title: section stmt 
Dump File:/home/db2speed/sqllib/db2dump/45392645894208.000 
............................................................... 
 
From t4539.000................................................. 
  <snip> 
 
<StackTrace> 
---FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0000002A9AE45766 ossDumpStackTrace + 0x0186 
        (/home/db2speed/sqllib/lib64/libdb2osse.so.1) 
0000002A9AE43324 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00aa 
        (/home/db2speed/sqllib/lib64/libdb2osse.so.1) 
0000002A97F180E3 sqlo_trce + 0x033b 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
0000002A96D97668 sqloDumpDiagInfoHandler + 0x0098 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
00000036E460C4F0 address: 0x00000036E460C4F0 ; dladdress: 0x000 
        (/lib64/tls/libpthread.so.0) 
00000036E3D2E829 kill + 0x0009 
        (/lib64/tls/libc.so.6) 
0000002A96D97B83 sqloDumpEDU + 0x000b 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
0000002A96AA13A4 _Z15sqldDumpContextP20sqle_agent_privatecbiiii 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
0000002A9670887F _Z15sqlrr_dump_ffdcP8sqlrr_cbii + 0x03c7 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
0000002A9683F571 _Z13sqlzeDumpFFDCP20sqle_agent_privatecbjP5sql 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
0000002A9683F992 _Z11sqlzeMapZrcP20sqle_agent_privatecbjmjP5sql 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
0000002A967247ED _Z11sqlrrMapZrcP8sqlrr_cbjmi + 0x002d 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
0000002A977C59DA _Z19sqlriMaterializeXmlP8sqlrr_cbP10sqlz_value 
        (/home/db2speed/sqllib/lib64/libdb2e.so.1) 
 
<snip> 
...............................................................
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.1                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.1 FixPack 9.                            * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.1 FixPack 9.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC62849 IC62873 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.08.2009
13.04.2010
13.04.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.