|
Problem IC65748
|
Status: Geschlossen |
DB2 INSTANCE CRASH DURING SELECT ON XMLTABLE TRIGGERED BY XML NAVIGATION RESETTING INVALID RESULTCURSOR BUFFER ARRAYS. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
In certain Application driven sql/xml queries (non CLP) such a
select on xmltable which uses a hash or merge join we are seeing
a db2 instance crash with the stack trace below. This is because
during XML navigation we are resetting memory
used for the resultCursor bufferArrays which has become stale.
It is possible that the section is being reused and we
are not properly re-initializing this chunk of memory needed to
hold the xml navigation results.
<StackTrace>
---FUNC-ADDR---- ------FUNCTION + OFFSET------
00000200049ADDC6 ossDumpStackTrace + 0x00d6
00000200049A9652 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00c2
0000020001DFF342 sqlo_trce + 0x05fa
0000020001E8DD26 sqloEDUCodeTrapHandler + 0x011e
000002027C809DF0 address: 0x2027c809df0
0000020002DC724A _ZN15XmlnvBasicArray5resetEv + 0x002a
0000020002DDCAC0
_ZN21XmlnvTupleConstructor21resetTupleConstructorEb + 0x00a0
0000020002DC4FF8 _ZN14XmlnvAutomaton14resetAutomatonEbb + 0x0040
0000020002DC65BC _ZN14XmlnvAutomaton13startFragmentEb + 0x0040
0000020002DD1554
_ZN14XmlnvNavigator19m_startNavOnContextEP17xmlDataDescriptorb +
0x0268
0000020002DD423E
_ZN14XmlnvNavigator13openNavigatorEP17xmlDataDescriptorP8sqlrr_c
b + 0x018e
0000020002492588 _Z12sqlriXMLScanP8sqlrr_cb + 0x0368
000002000243F590 _Z8sqlri_mjP8sqlrr_cb + 0x05a8
00000200024693FE _Z9sqlriPSetP8sqlrr_cb + 0x0272
00000200023EA8B2 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm +
0x00c2
000002000213562C
_Z27sqlrr_process_fetch_requestP14db2UCinterface + 0x0c90
00000200021387A0
_Z11sqlrr_fetchP14db2UCinterfaceP15db2UCCursorInfo + 0x01d0
00000200010638EE
_Z16sqljs_ddm_cntqryP14db2UCinterfaceP13sqljDDMObject + 0x01ba
0000020001051432
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0x0426
0000020001050612 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface
+ 0x0246
000002000104A0DE address: 0x000002000104A0DE ; dladdress:
0x000002000004A000 ; offset in lib: 0x00000000010000DE ;
000002000104E584 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T +
0x02e4
0000020000DEFC5A _ZN8sqeAgent6RunEDUEv + 0x014e
0000020002D23D08 _ZN9sqzEDUObj9EDUDriverEv + 0x0198
0000020002D23D22 _Z10sqlzRunEDUPcj + 0x0016
0000020001E8EE98 sqloEDUEntry + 0x0320
0000020000034A5C address: 0x0000020000034A5C ; dladdress:
0x000002000002D000 ; offset in lib: 0x0000000000007A5C ;
0000020004E6FF06 address: 0x0000020004E6FF06 ; dladdress:
0x0000020004D7D000 ; offset in lib: 0x00000000000F2F06 ;
</StackTrace> |
| Problem-Zusammenfassung: |
DB2 INSTANCE CRASH DURING SELECT ON XMLTABLE TRIGGERED BY XML
NAVIGATION RESETTING INVALID RESULTCURSOR BUFFER ARRAYS.
In certain Application driven sql/xml queries (non CLP) such a
select on xmltable which uses a hash or merge join we are seeing
a db2 instance crash with the stack trace below. This is because
during XML navigation we are resetting memory
used for the resultCursor bufferArrays which has become stale.
It is possible that the section is being reused and we
are not properly re-initializing this chunk of memory needed to
hold the xml navigation results.
<StackTrace>
---FUNC-ADDR---- ------FUNCTION + OFFSET------
00000200049ADDC6 ossDumpStackTrace + 0x00d6
00000200049A9652 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00c2
0000020001DFF342 sqlo_trce + 0x05fa
0000020001E8DD26 sqloEDUCodeTrapHandler + 0x011e
000002027C809DF0 address: 0x2027c809df0
0000020002DC724A _ZN15XmlnvBasicArray5resetEv + 0x002a
0000020002DDCAC0
_ZN21XmlnvTupleConstructor21resetTupleConstructorEb + 0x00a0
0000020002DC4FF8 _ZN14XmlnvAutomaton14resetAutomatonEbb + 0x0040
0000020002DC65BC _ZN14XmlnvAutomaton13startFragmentEb + 0x0040
0000020002DD1554
_ZN14XmlnvNavigator19m_startNavOnContextEP17xmlDataDescriptorb +
0x0268
0000020002DD423E
_ZN14XmlnvNavigator13openNavigatorEP17xmlDataDescriptorP8sqlrr_c
b + 0x018e
0000020002492588 _Z12sqlriXMLScanP8sqlrr_cb + 0x0368
000002000243F590 _Z8sqlri_mjP8sqlrr_cb + 0x05a8
00000200024693FE _Z9sqlriPSetP8sqlrr_cb + 0x0272
00000200023EA8B2 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm +
0x00c2
000002000213562C
_Z27sqlrr_process_fetch_requestP14db2UCinterface + 0x0c90
00000200021387A0
_Z11sqlrr_fetchP14db2UCinterfaceP15db2UCCursorInfo + 0x01d0
00000200010638EE
_Z16sqljs_ddm_cntqryP14db2UCinterfaceP13sqljDDMObject + 0x01ba
0000020001051432
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0x0426
0000020001050612 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface
+ 0x0246
000002000104A0DE address: 0x000002000104A0DE ; dladdress:
0x000002000004A000 ; offset in lib: 0x00000000010000DE ;
000002000104E584 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T +
0x02e4
0000020000DEFC5A _ZN8sqeAgent6RunEDUEv + 0x014e
0000020002D23D08 _ZN9sqzEDUObj9EDUDriverEv + 0x0198
0000020002D23D22 _Z10sqlzRunEDUPcj + 0x0016
0000020001E8EE98 sqloEDUEntry + 0x0320
0000020000034A5C address: 0x0000020000034A5C ; dladdress:
0x000002000002D000 ; offset in lib: 0x0000000000007A5C ;
0000020004E6FF06 address: 0x0000020004E6FF06 ; dladdress:
0x0000020004D7D000 ; offset in lib: 0x00000000000F2F06 ;
</StackTrace> |
| Local-Fix: |
n/a |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 UDB Version 9.7, FixPak 2 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 21.01.2010
13.07.2010
13.07.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
