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

TRAP IN RECYCLEANDREINIT FOR AN INTERRUPTED XML QUERY IN DPF

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If ALL of the following conditions are true: 
 
1) On DPF, a query is run that flows an XML column on a TQ 
 
2) A table in the query has it's XML column defined with a 
specific inline length. 
 
For example: 
create table tester(col1 xml inline length 2000) 
 
3) The query is interrupted (for example, force applications, or 
some other event or error that interrupts the query). 
 
...then there is a chance that the cleanup logic for terminating 
the query may reference an empty internal structure, cause the 
trap/crash. 
 
The trap will be sustained by DB2.  The following is the stack 
that corresponds to this problem: 
 
 
-------Frame------ ------Function + Offset------ 
0x09000000050E2D60 
recycleAndReinit__24SqlriXmlDeferredTempListFP30SqlriXmlDeferred 
TempMemoryPool + 0x70 
0x090000000544A5F8 
m_decrDeferCount__27SqlriXmlDeferredTempManagerFP24SqlriXmlDefer 
redTempListP8sqlrr_cbb + 0x1EC 
0x0900000004D7EC48 
unDeferDeleteXTemps__27SqlriXmlDeferredTempManagerFR8XMLS_XIDP8s 
qlrr_cb + 0x194 
0x0900000004D7E924 
doGarbageCollect__29sqlktLargeObjCacheXMLValueMgrFR23sqlktLargeO 
bjCacheValue + 0xA0 
0x0900000004D7E3D8 evictionNotice__23sqlktLargeObjCacheValueFv + 
0xA4 
0x0900000004D81BF8 
evictEntry__30sqlktLargeObjCacheGatewayOnTQAFUl@AF277_219 + 
0x11C 
0x0900000004D7E110 
evictEntry__30sqlktLargeObjCacheGatewayOnTQAFUl + 0x1C 
0x0900000004D4791C 
destroyLargeObjCacheGateway__25sqlktLargeObjCacheGatewayFRP25sql 
ktLargeObjCacheGateway + 0x88 
0x0900000004764654 sqlktdrp__FP8sqeAgentP9sqlri_taoi + 0x704 
0x0900000004766794 sqlktdrp__FP8sqeAgentP9sqlri_taoi@glueBCB + 
0x78 
0x0900000005242E3C sqlridrp__FP8sqlrr_cbP9sqlri_tao + 0x17C 
0x0900000005ACE8E8 sqlridrp__FP8sqlrr_cbP9sqlri_tao@glueBC2 + 
0x80 
0x0900000005ACECC8 sqlricls_complex__FP8sqlrr_cbilN23 + 0x9C 
0x0900000005BDA2C8 sqlricls_complex__FP8sqlrr_cbilN23@glue8B8 + 
0x128 
0x0900000005BDE968 @44@259738@sqlricls__FP8sqlrr_cbiN32 + 0xB0 
0x0900000006C0250C sqlriecc__FP8sqlrr_cbilT3 + 0xEC4 
0x0900000006F85260 sqlriCloseExecuteSectionComplex__FP8sqlrr_cbi 
+ 0x4B8 
0x090000000991CEE4 
.sqlrr_process_execute_request.fdpr.clone.2089__FP8sqlrr_cbi + 
0xB54 
0x0900000005BB3630 
.sqlrr_execute.fdpr.clone.1820__FP14db2UCinterfaceP9UCstpInfo + 
0x208 
0x0900000005BB2FA8 
.sqljs_ddm_excsqlstt.fdpr.clone.201__FP14db2UCinterfaceP13sqljDD 
MObject + 0xB80 
0x0900000005BB1DE8 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x104 
0x0900000005BB2184 
.sqljsParse.fdpr.clone.31__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s 
qeAgentb + 0x260 
0x0900000005BB0C04 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x2EC 
0x09000000059EE608 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA4 
0x09000000049C1708 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x38C 
0x09000000059EDCE0 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x1D0 
0x0900000005A61504 RunEDU__8sqeAgentFv + 0x2F0 
0x0900000005A5B0CC EDUDriver__9sqzEDUObjFv + 0xD8 
0x0900000005AC3A10 sqloEDUEntry + 0x260
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any using XML in a DPF environment                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 Fixpack 8 or later                           * 
****************************************************************
Local Fix:
available fix packs:
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
Problem first fixed in v9.7 Fixpack 8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91741 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.12.2012
28.03.2013
28.03.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList