home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC77641 Status: Closed

WHEN DB2_MEMORY_PROTECT IS SET TO YES, XML QUERY FOR LARGE XML DATA MIGHT
CRASH THE INSTANCE AND RETURN CLI Driver failure

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
WHEN DB2_MEMORY_PROTECT IS SET TO YES, XML QUERY FOR LARGE XML 
DATA MIGHT CRASH THE INSTANCE AND RETURN  CLI Driver failure. 
The error message is as below: 
[IBM][CLI Driver] CLI0108E  Communication link failure. 
SQLSTATE=40003 Native Error Code = -99999 SQLSTATE = 40003 
 
 
An example of the query that might cause the problem is: 
db2-fn:sqlquery("SELECT X1 FROM MBENCH.T1 WHERE DOCID=1")// 
(if (@aLevel=2 or @aUnique1=4) (: at level 2 :) 
 then eNest (: move to level 3 :) 
 else if (@aUnique1=1) then eNest/eNest (: move to level 3 :) 
else . (: at level 3 :))/ 
fn:distinct-values(..[eNest]) (: distinct all the parents of 
level 3 :); 
 
 
The trap file generated, and the stack trace might look like the 
following: 
 
<?xml version="1.0" encoding="ISO-8859-1"?> 
<?xml-stylesheet 
href="http://raspd.torolab.ibm.com/db2trapfile.xsl" 
type="text/xsl"?> 
<DB2TrapFile version="1.0"> 
<Trap> 
<Header> 
DB2 build information: DB2 v9.7.0.4 s110302 SQL09074 
timestamp: 2011-03-11-15.23.17.151957 
instance name: regress1.000 
EDU name     : db2agent (XMLDB) 
EDU ID       : 6752 
Signal #11 
uname: S:AIX R:1 V:6 M:00056E62D900 N:regraix02 
process id: 10092698 
thread id : 6752 (0x1A60) 
kthread id : 21823627 
</Header> 
<SignalDetails> 
<Siginfo_t length="64"> 
0000000B 00000000 00000034 00000000 
00000000 00000000 07000000 3479BF04 
00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000000 
</Siginfo_t> 
Signal #11 (SIGSEGV): si_addr is 0x070000003479BF04, si_code is 
0x00000034 
</SignalDetails> 
<ResourceLimits> 
Data seg top [sbrk(0)] = 0x0000000115C82320 
Cur cpu time limit (seconds)  = 0x7FFFFFFFFFFFFFFF 
Cur file limit (bytes)  = 0x7FFFFFFFFFFFFFFF 
Cur data size (bytes)  = 0x7FFFFFFFFFFFFFFF 
Cur stack size (bytes) = 0x0000000002000000 
Cur core size (bytes)  = 0x7FFFFFFFFFFFFFFF 
Cur nofiles (descriptors)  = 0x7FFFFFFFFFFFFFFF 
Cur memory size (bytes)  = 0x7FFFFFFFFFFFFFFF 
</ResourceLimits> 
<Registers> 
    IAR: 0900000008BB474C     MSR: A00000000200D032      LR: 
0900000008BB4620 
    CTR: 0000000000000000     XER: 20000004           FPSCR: 
82004000 
     CR: 42244280 
GPR[00]: 0000000000000238 GPR[01]: 070000000AFF7420 GPR[02]: 
09001000A3825958 
GPR[03]: 0000000000000001 GPR[04]: 0000000000000239 GPR[05]: 
0000000000000238 
GPR[06]: 070000003479BF04 GPR[07]: 0000000000000000 GPR[08]: 
0000000000000031 
GPR[09]: 070000000AFF764C GPR[10]: 070000000AFF7648 GPR[11]: 
0000000000000239 
GPR[12]: 0900000008BB4620 GPR[13]: 0000000110A67800 GPR[14]: 
0000000000002774 
GPR[15]: 09001000A2716338 GPR[16]: 0000000000000018 GPR[17]: 
000000000000FFFF 
GPR[18]: 0000000010000030 GPR[19]: 000000001D200000 GPR[20]: 
0000000000000239 
GPR[21]: 0000000000000239 GPR[22]: 070000003479BCCC GPR[23]: 
0000000000000000 
GPR[24]: 0000000000000000 GPR[25]: 0000000000000000 GPR[26]: 
0000000000000000 
GPR[27]: 0000000000000000 GPR[28]: 0000000000000000 GPR[29]: 
070000000AFF7648 
GPR[30]: 070000000AFF764C GPR[31]: 000000011255C500 
FPR[00]: 0000000000000000 FPR[01]: 4000000000000000 FPR[02]: 
41F0000000000000 
FPR[03]: 4330080000000000 FPR[04]: 0000000082004000 FPR[05]: 
C32FFFFFFFFFFF9F 
FPR[06]: 4330080000000002 FPR[07]: 40EDAE2000000000 FPR[08]: 
0000000000000000 
FPR[09]: 3FF0000000000000 FPR[10]: 40EDAE2000000000 FPR[11]: 
43380000000003FF 
FPR[12]: 3FE0000000000000 FPR[13]: 0000000000000000 FPR[14]: 
0000000000000000 
FPR[15]: 0000000000000000 FPR[16]: 0000000000000000 FPR[17]: 
0000000000000000 
FPR[18]: 0000000000000000 FPR[19]: 0000000000000000 FPR[20]: 
0000000000000000 
FPR[21]: 0000000000000000 FPR[22]: 0000000000000000 FPR[23]: 
0000000000000000 
FPR[24]: 0000000000000000 FPR[25]: 0000000000000000 FPR[26]: 
0000000000000000 
FPR[27]: 0000000000000000 FPR[28]: 0000000000000000 FPR[29]: 
0000000000000000 
FPR[30]: 0000000000000000 FPR[31]: 0000000000000000 
</Registers> 
<POFDisassembly> 
     0x0900000008BB472C : EAC101E0 ld r22,480(r1) 
     0x0900000008BB4730 : 56A4043E rlwinm        r4,r21,0,0xFFFF 
# 16:31 
     0x0900000008BB4734 : 7C942379 or. r20,r4,r4 
     0x0900000008BB4738 : 41820068 beq        cr0,0x8BB47A0 # 
12,bit2 
     0x0900000008BB473C : 3804FFFF addi r0,r4,-1 
     0x0900000008BB4740 : 38600001 li r3,0x1 
     0x0900000008BB4744 : 5405003E rlwinm 
r5,r0,0,0xFFFFFFFFFFFFFFFF # 0:31 
     0x0900000008BB4748 : 7CD62A14 add r6,r22,r5 
>>>> 0x0900000008BB474C : 7C1628AE lbzx r0,r22,r5 
     0x0900000008BB4750 : 54000632 rlwinm        r0,r0,0,0xC0 # 
24:25 
     0x0900000008BB4754 : 2C200080 cmpi cr0,r0,128 
     0x0900000008BB4758 : 4082003C bne        cr0,0x8BB4794 # 
4,bit2 
     0x0900000008BB475C : 60C50000 ori r5,r6,0x0 
     0x0900000008BB4760 : 60000000 ori r0,r0,0x0 
</POFDisassembly> 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000008BB474C 
addAtomicNode__17xmlDataDescriptorFPcUsP18XmlrnTempRecordMgrbUcR 
UsT6PUcT2P18XmlrnDanglingBytesT8T2 
+ 0x32C 
0x0900000008BB85E8 
packAtomicValue__17xmlDataDescriptorFP11XMLSTORE_CBUcPUcUiT3UsT4 
+ 0xB68 
0x0900000008BB7914 
packAtomicValue__17xmlDataDescriptorFP11XMLSTORE_CBPcT2 + 0xD4 
0x090000000ACE9448 
packResult__17XmlrnGenSeqCursorFP17xmlDataDescriptor + 0x408 
0x090000000ACE7B3C 
fetch__17XmlrnGenSeqCursorFP10sqlz_valuePUsUsUcPFP19sqlri_PredFu 
ncParamPi_iP19sqlri_PredFuncParam 
+ 0x35C 
0x090000000C1B50C4 sqlriXmlIterate__FP8sqlrr_cb + 0x584 
0x090000000980C0F8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x298 
0x090000000AA33D9C 
sqlrr_process_fetch_request__FP14db2UCinterface + 0xC3C 
0x090000000AA2E64C 
sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x1B2C 
0x090000000BE4F528 
sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0x1908 
0x090000000BDE5CF8 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface 
+ 0x1B8 
0x090000000BDE8230 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x18F0 
0x090000000BDCD52C sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 
0x98C 
0x090000000BDD24E0 
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x160 
0x090000000BDCBEC0 
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x520 
0x090000000BDCAF10 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x310 
0x090000000886A384 RunEDU__8sqeAgentFv + 0xB04 
0x090000000885CBE4 EDUDriver__9sqzEDUObjFv + 0x284 
0x090000000885C910 sqlzRunEDU__FPcUi + 0x10 
0x09000000087CB04C sqloEDUEntry + 0x2CC 
</StackTrace> 
<ProcessObjects> 
Entry 0:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See APAR description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users need to upgrade to V97 fp5.                            * 
****************************************************************
Local Fix:
available fix packs:
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
With the fix for this APAR, users will not have experience the 
ABEND as described in the APAR.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.07.2011
09.12.2011
09.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList