suche 36x36
  • CURSOR Service Distribution
           
     

    CURSOR Service Distribution

    24x7 Always Up

    pfeil
  • Logistics and transportation
           
     

    Logistics and transportation

    24x7 Always Up

    pfeil
  • Industrial environments
           
     

    Industrial environments

    24x7 Always Up

    pfeil
  • Trade and commerce
           
     

    Trade and commerce

    24x7 Always Up

    pfeil
  • Online shopping
           
     

    Online shopping

    24x7 Always Up

    pfeil
  • We care about your databases
           
     

    We care about your databases

    24x7 Always Up

    pfeil
 

Erik Stahlhut

CURSOR Service Distribution

We keep your IBM databases running

             
 

Monitoring Monitoring

Monitoring

  • Companies with existentially important databases trust in our Informix Monitoring. We prevent system failures before they occur.

  • Automated monitoring around the clock. Early detection of bottlenecks based on history data with our CURSOR Admin-Scout.

  • Administration for all installation sizes. Standard, remote or standby administration, up to 24x7 availability for systems with high availability.

  • Individual adjustments to the service levels of our customers with short response times and personal contact persons in support.

Discover more about Informix Monitoring with the CURSOR Service Distribution!
 

ServiceService

Service

  • Requirements from all areas of data management. Service packages or individually agreed projects like:
    • Setup of replications or high availability systems;
    • Performance, runtime analysis, tuning;
    • Release, platform or cloud migration;
    • Access control, encryption, archiving.
  • CURSOR Service Distribution is a long-standing IBM High-Value Service Provider for IBM Informix.

  • Specially for Informix we offer additional online seminars, workshops and training courses.

Information about service and support, so feel free to contact us with your project!
 

SupportSupport

Support

  • Request for support services for IBM databases. Our customers benefit from the competence of more than 25 years of Informix support and system-oriented development of database tools.

  • In case of support we are the first and central contact persons. We have a direct line to the IBM and HCL support departments and are available for our customers with 24x7 agreements around the clock.

  • Even Informix customers without active IBM product maintenance can take advantage of our first-aid support.

Book a support ticket on our website or just call us!
 
 
 
 

IBM Software

for manufacturers

and technology partners

IBM Embedded Solution Agreement (ESA)
integration of IBM software into your solution!

  Service
  • Integrate IBM software into your solution!

  • Benefit from the power of IBM software, take advantage of the attractive conditions for IBM licenses and maintenance!

  • The employees of CURSOR Service Distribution have twenty years of experience in indirect sales of IBM software (OEM/ASL/ESA licensing). We show you how to become an IBM ESA Business Partner!

esa bp werden blue 1000x100

 
 
 
 

CompetenceService

in Informix Administration

 
 

the CURSOR

Admin-Scout for Informix

esa bp werden blue 1000x100

esa bp werden blue 1000x100

 

 

  • The Informix tool right from CURSOR Informix Support.

  • Developed by administrators for administrators.

    With a background of over 25 years of Informix support, administration and system-oriented programming, we have been developing and distributing the Admin Scout since 2015.

  • By our Managed Service approach, the Admin Scout is suitable for almost all application areas of the Informix database system. Our customers are IT departments and administrators in commerce, banks, universities, trade and industry.

 
 
 
 

About us

the CURSOR Service Distribution

  • High-Value Service Provider for IBM Informix.

  • Distribution for IBM Data-Management Software (OEM/ASL/ESA licensing for ISVs).

CURSOR Service Distribution is a business unit of CURSOR Software AG, resulting from the acquisition of the Informix and development tool specialist "Nonne & Schneider" at the end of 2005.

We offer extensive technical services for IBM Informix, and as a high-value service provider we are the direct contact for all our customers' service needs for these databases.

Our services are independent from licensing through our company. Well-known customers rely on our monitoring and use our tools, while licensing and update maintenance are contracted directly with IBM.

 

CURSOR Software AG

For over 25 years CURSOR has been developing and marketing CRM solutions for the upper middle class and large concerns.

  • Together.
    Together with you we will lead your CRM project to success. Our experts offer comprehensive services from a single source: software development, consulting, software introduction, training, support - and the ongoing optimization of your CRM system.

  • Inspiring.
    We "live" CRM and want to inspire you with CRM software and services Made in Germany. The benchmark for this is the enthusiasm and loyalty of our customers - and their customers.

  • Successful.
    For 30 years the name CURSOR has stood for excellent customer and business process management - CRM and BPM. We measure our success by the satisfaction and market success of our customers. Learn more about successful CRM projects directly from our customers.

 
 
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 IC95379 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.5 Fixpak 3                                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem First Fixed In v10.5 Fixpak 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
10.03.2014
10.03.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList