home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC86917 Status: Geschlossen

INSTANCE TRAP OR -901 WHEN INSERT OR QUERY LARGE XML DOC

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When insert large XML documents, DB2 fails with SQL0901N error 
or instance crash. 
 
The problem is due to a memory corruption where XML data block 
is being overwritten. 
This cause SQL0901N or instance crash.  Trap stacks can look 
different but in general they're all in XML processing. 
Samples are pasted below: 
 
For -901 error, sample db2diag.log shows: 
 
-901 error: 
FUNCTION: DB2 UDB, XML Node Manager, 
XmlrnConstructorEndDocument, probe:668 
MESSAGE : ZRC=0x82A40001=-2103181311=XMLRN_PRG_ERR 
          "XMRN unexpected system error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : String, 64 bytes 
EndDocument must be called with only document node on the stack. 
DATA #2 : Xmlrn Fragment Writer object, 
PD_TYPE_XMRN_FRAGMENT_WRITER, 824 bytes 
XmlrnConstructorWriter: 
   m_flags:               0x498 
   m_bufferSize:          32640 
   m_inlineOffset:        0 
   m_nodeMgr address:     0x07000000e1ffb560 
   m_xmlDD address:       0x07000000e1ffb860 
   m_nsHdr address:       0x0000000000000000 
   m_node address:        0x0000000000000000 
   m_preserveNids:        true 
   m_localBuffer address: 0x07000000337f7080 
   m_stack address:       0x0700000033c93d00 
   m_stackSize:           16 
   m_stackPos:            1 
   m_tempRecordLength:    32640 
   XmlrnConstructorWriter m_updateState follows: 
   XmlrnConstructorState: 
  .. 
 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x090000000AFED2D4 endDocument__16XmlrnConstructorFv + 
0x258 
  [1] 0x090000000A25E61C 
addDescendantSubtree__16XmlrnConstructorFP17xmlDataDescriptorb + 
0x924 
  [2] 0x090000000A25DB98 
copySubtree__16XmlrnConstructorFP17xmlDataDescriptorP12XmlrnNode 
MgrUlUsT1bP17XmlsNidDescriptor + 0x17C 
  [3] 0x090000000A2AE988 
deepCopy__17xmlDataDescriptorFP11XMLSTORE_CBP17xmlDataDescriptor 
Ui + 0x9D8 
  [4] 0x090000000AF255DC 
prepareForTransport__17xmlDataDescriptorFP11XMLSTORE_CBUiUsP25sq 
lktLargeObjCacheGatewayi + 0xB04 
  [5] 0x0900000009DFEA84 
sqlrk_RPCRecvFetchXDM__FP8sqlrr_cbUiR16SqlrkXmlRpcReply + 0x538 
  [6] 0x0900000009DFB088 
sqlrk_xml_router__FP8sqlrr_cbR16SqlrkXmlRpcReplyP16sqlkdRqstRply 
FmtP15SQLR_RPCMESSAGEb + 0x400 
  [7] 0x09000000099844C0 sqlrr_rpc_router__FP8sqlrr_cb + 0xECC 
  [8] 0x090000000998160C 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x848 
  [9] 0x0900000009982368 
@82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x3B4 
  [10] 0x0900000009B66684 sqleProcessSubRequest__FP8sqeAgent + 
0x470 
  [11] 0x09000000096F9858 RunEDU__8sqeAgentFv + 0x680 
  [12] 0x09000000096F33CC EDUDriver__9sqzEDUObjFv + 0x13C 
  [13] 0x09000000096F3254 sqlzRunEDU__FPcUi + 0x10 
  [14] 0x0900000009706000 sqloEDUEntry + 0x264 
  [15] 0x090000000079AC90 _pthread_body + 0xF0 
  [16] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
 
FUNCTION: DB2 UDB, XML Node Manager, 
XmlrnConstructorEndDocument, probe:668 
MESSAGE : ZRC=0x82A40001=-2103181311=XMLRN_PRG_ERR 
          "XMRN unexpected system error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : String, 4 bytes 
none 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x0900000009B97470 xmlrnLogErrorRc__FUliT2Pc + 0xFC 
  [1] 0x090000000AFED2E8 endDocument__16XmlrnConstructorFv + 
0x26C 
  [2] 0x090000000A25E61C 
addDescendantSubtree__16XmlrnConstructorFP17xmlDataDescriptorb + 
0x924 
  [3] 0x090000000A25DB98 
copySubtree__16XmlrnConstructorFP17xmlDataDescriptorP12XmlrnNode 
MgrUlUsT1bP17XmlsNidDescriptor + 0x17C 
  [4] 0x090000000A2AE988 
deepCopy__17xmlDataDescriptorFP11XMLSTORE_CBP17xmlDataDescriptor 
Ui + 0x9D8 
  [5] 0x090000000AF255DC 
prepareForTransport__17xmlDataDescriptorFP11XMLSTORE_CBUiUsP25sq 
lktLargeObjCacheGatewayi + 0xB04 
  [6] 0x0900000009DFEA84 
sqlrk_RPCRecvFetchXDM__FP8sqlrr_cbUiR16SqlrkXmlRpcReply + 0x538 
  [7] 0x0900000009DFB088 
sqlrk_xml_router__FP8sqlrr_cbR16SqlrkXmlRpcReplyP16sqlkdRqstRply 
FmtP15SQLR_RPCMESSAGEb + 0x400 
  [8] 0x09000000099844C0 sqlrr_rpc_router__FP8sqlrr_cb + 0xECC 
  [9] 0x090000000998160C 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x848 
  [10] 0x0900000009982368 
@82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x3B4 
  [11] 0x0900000009B66684 sqleProcessSubRequest__FP8sqeAgent + 
0x470 
  [12] 0x09000000096F9858 RunEDU__8sqeAgentFv + 0x680 
  [13] 0x09000000096F33CC EDUDriver__9sqzEDUObjFv + 0x13C 
  [14] 0x09000000096F3254 sqlzRunEDU__FPcUi + 0x10 
  [15] 0x0900000009706000 sqloEDUEntry + 0x264 
  [16] 0x090000000079AC90 _pthread_body + 0xF0 
  [17] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
 
 
Since the root cause is memory corruption, it might cause 
instance trap with different 
stacks like below: 
 
  0x09000000093B69D0 sqlofmblkEx + 0x168 
 
0x0900000009DDC3B0 __dt__16XmlrnConstructorFv + 0x124 
 
0x090000000A25DB64 
 
copySubtree__16XmlrnConstructorFP17xmlDataDescriptorP12XmlrnNode 
MgrUlUsT 
1bP17XmlsNidDescriptor + 0x148 
 
0x090000000A2AE988 
 
deepCopy__17xmlDataDescriptorFP11XMLSTORE_CBP17xmlDataDescriptor 
Ui + 
0x9D8 
 
0x090000000AF255DC 
 
prepareForTransport__17xmlDataDescriptorFP11XMLSTORE_CBUiUsP25sq 
lktLarge 
ObjCacheGatewayi + 0xB04 
 
0x0900000009DFEA84 
 
sqlrk_RPCRecvFetchXDM__FP8sqlrr_cbUiR16SqlrkXmlRpcReply + 0x538 
 
0x0900000009DFB088 
 
sqlrk_xml_router__FP8sqlrr_cbR16SqlrkXmlRpcReplyP16sqlkdRqstRply 
FmtP15SQ 
LR_RPCMESSAGEb + 0x400 
 
0x09000000099844C0 sqlrr_rpc_router__FP8sqlrr_cb + 0xECC 
 
0x090000000998160C 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 
0x848 
 
0x0900000009982368 @82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 
0x3B4 
0x0900000009B66684 sqleProcessSubRequest__FP8sqeAgent + 0x470 
 
0x09000000096F9858 RunEDU__8sqeAgentFv + 0x680
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fix pack 3                              * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 v10.1 Fix pack 3
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC88217 IC95379 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.10.2012
24.10.2013
24.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList