|
Problem IC77680
|
Status: Closed |
WHEN DB2_MEMORY_PROTECT IS SET TO YES, XML QUERY MIGHT CAUSE THE INSTANCE TO PANIC |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
An example of a query that might cause the problem is:
xquery transform copy $i :=
db2-fn:xmlcolumn("NEWTON.UT03.DOC")/purchaseOrder/shipTo,
$j :=
db2-fn:xmlcolumn("NEWTON.UT03.DOC")/purchaseOrder/shipTo,
$k := transform copy $x := transform copy
$z := <nested/>
modify
()
return $z
modify ()
return $x
modify ()
return ($i,$j,$k);
The stack trace from the trap might look similar to the
following:
<StackTrace>
-------Frame------ ------Function + Offset------
0x0900000015314960
enterNode__27XmlrnDocumentHandlerVisitorFP19XmlrnNodeDescriptorR
Us
+ 0x32C
0x09000000152CE6A8 visitSubtree__17XmlrnXTransformerFRb + 0xD84
0x09000000145436F4
xmlrnApplyPUL__FP11XMLSTORE_CBP11XmlrnIUD_CBP17xmlDataDescriptor
b
+ 0x904
0x0900000014542D84 xmlrnInsertDocument__FP11XmlrnIUD_CB + 0xCAC
0x0900000014D5260C sqlriXmlMergeApply__FP8sqlrr_cb + 0xB68
0x09000000155E70E8 sqlriNljnPiped__FP8sqlrr_cb + 0x4C4
0x09000000155E8704 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x2C
0x09000000157C50F8
sqlrr_process_fetch_request__FP14db2UCinterface + 0x184
0x090000001563F86C
sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x318
0x090000001563E824
sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0x9E8
0x0900000015623110
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface
+ 0x134
0x0900000015623544
.sqljsParse.fdpr.clone.226__FP13sqljsDrdaAsCbP14db2UCinterfaceP8
sqeAgentb
+ 0x260
0x0900000015589CA0 @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0xAF0
0x0900000015422D54
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xE0
0x0900000015422B5C
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x268
0x090000001542262C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
0xE4
0x0900000015470E6C RunEDU__8sqeAgentFv + 0x84
0x0900000015474D78 EDUDriver__9sqzEDUObjFv + 0xD4
0x090000001546D1F0 sqloEDUEntry + 0x270
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See APAR description *
****************************************************************
* RECOMMENDATION: *
* Users should upgrade to V97 fp5 *
**************************************************************** |
| Local Fix: |
Users might want to set DB2_MEMORY_PROTECT to NO |
| 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 this fix, users will not experience the problem described
in the APAR description |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.07.2011
07.12.2011
07.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
|
 |
