|
Problem IC81039
|
Status: Closed |
DB2 MAY ABEND WITH SIGSEV WHEN USING XMLTABLE FUNCTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 may abend with memory corruption error while running a
PL/SQL stored procedure using XMLTABLE function.
DB2 stack dumps may look like this:
STACK 1:
resetAutomaton__14XmlnvAutomatonFbT1 + 0xEC
startFragment__14XmlnvAutomatonFb + 0x40
m_startNavOnContext__14XmlnvNavigatorFP17xmlDataDescriptorb +
0x58C
openNavigator__14XmlnvNavigatorFP17xmlDataDescriptorP8sqlrr_cb +
0x940
sqlriXMLScan__FP8sqlrr_cb + 0x530
sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm@glue14CF + 0x168
sqlrihsjn__FP8sqlrr_cb + 0x14
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x628
sqlrr_process_fetch_request__FP14db2UCinterface + 0x188
sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x408
csmDriveFetch__FP14db2UCinterfaceP15db2UCCursorInfobT3 + 0x354
csmFetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x15B4
fetchCursor__10pvmPackageFP14db2UCinterfaceCUi + 0xD4
executeSection__10pvmPackageFP5sqlcaUib + 0x260
executeQuery__3PVMFUib + 0x1A4
fetchCursorVariable__3PVMFCUiN31 + 0x3A8
run__3PVMFv + 0xCD8
pvm_entry + 0x1DC
sqloInvokeFnArgs + 0xC4
sqloInvokeFnArgs@glue4AF + 0x78
sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntf +
0x1D0
OR
STACK 2:
sqloCrashOnCriticalMemoryValidationFailure
SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash
sqloDiagnoseFreeBlockFailure
sqlofmblkEx
XmlnvTupleConstructor::destroyTupleConstructor
XmlnvAutomaton::destroyAutomaton
XmlnvNavigator::destroyNavigator
XmlnvNavigator::destroyNavigator
sqlricjpInfrequent
sqlricjp
sqlri_hsjnClose
sqlrihsjn
sqlriSectInvoke
sqlrr_process_fetch_request
sqlrr_fetch
csmDriveFetch
csmFetch
pvmPackage::fetchCursor
pvmPackage::executeSection
PVM::executeQuery
PVM::fetchCursorVariable
PVM::run
pvm_entry
sqloInvokeFnArgs
sqloInvokeFnArgs@glue4AF
sqlriInvokerTrusted
sqlriInvokeInvoker
sqlricall
sqlriSectInvoke
sqlrr_process_execute_request
sqlrr_execute.fdpr.clone.1791
sqljs_ddm_excsqlstt.fdpr.clone |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 v97 FP5 and earlier *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v97 FP6 *
**************************************************************** |
| Local Fix: |
NO LOCAL FIX |
| available fix packs: |
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 |
First Fixed in DB2 v97 FP6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC81088 IC81205 IC81207 IC84334 IC84656
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.01.2012
26.06.2012
26.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
