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

WHEN DB2_MEMORY_PROTECT IS SET TO YES, XML QUERY MIGHT CRASH THE INSTANCE
AND RETURN SQL1224N

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An example of the query that might cause the problem is: 
( 
XQUERY 
for $i in db2-fn:xmlcolumn("XSTUNIT.X") 
return 
<x:db2_xmrn_unit_test 
xmlns:x="http://www.ibm.com/xmlns/prod/db2/XSR/SchemaInfo" 
  name         = "typeinfo" 
  xml          = "{ $i }"> 
</x:db2_xmrn_unit_test>; 
 
The trap file generated, and the stack trace might look like the 
following: 
 
<?xml version="1.0" encoding="ISO-8859-1"?> 
<?xml-stylesheet 
href="http://raspd.torolab.ibm.com/db2trapfile.xsl" 
type="text/xsl"?> 
<DB2TrapFile version="1.0"> 
<Trap> 
<Header> 
DB2 build information: DB2 v9.7.0.4 n110227 SQL09074 
timestamp: 2011-03-05-16.57.14.669717 
instance name: regress9.000 
EDU name     : db2agent (XMLSTORE) 
EDU ID       : 3343 
Signal #11 
uname: S:AIX R:1 V:6 M:00056E62D900 N:regraix03 
process id: 14221412 
thread id : 3343 (0xD0F) 
kthread id : 80281817 
</Header> 
<SignalDetails> 
<Siginfo_t length="64"> 
0000000B 00000000 00000034 00000000 
00000000 00000000 07000000 43243F80 
00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000000 
</Siginfo_t> 
Signal #11 (SIGSEGV): si_addr is 0x0700000043243F80, si_code is 
0x00000034 
</SignalDetails> 
<ResourceLimits> 
Data seg top [sbrk(0)] = 0x0000000111231E80 
Cur cpu time limit (seconds)  = 0x7FFFFFFFFFFFFFFF 
Cur file limit (bytes)  = 0x7FFFFFFFFFFFFFFF 
Cur data size (bytes)  = 0x7FFFFFFFFFFFFFFF 
Cur stack size (bytes) = 0x0000000002000000 
Cur core size (bytes)  = 0x0000000000000000 
Cur nofiles (descriptors)  = 0x7FFFFFFFFFFFFFFF 
Cur memory size (bytes)  = 0x7FFFFFFFFFFFFFFF 
</ResourceLimits> 
<Registers> 
    IAR: 090000000DFDCE24     MSR: A00000000200D032      LR: 
090000000DFDCF84 
    CTR: 0000000000000000     XER: 0000000C           FPSCR: 
82004000 
     CR: 42000284 
GPR[00]: 090000000DFDCF84 GPR[01]: 070000000CFF5E40 GPR[02]: 
09001000A39D0BC8 
GPR[03]: 0700000043243F80 GPR[04]: 0000000000000007 GPR[05]: 
0900000015906EB0 
GPR[06]: 000000000000091A GPR[07]: 0900000014982430 GPR[08]: 
0000000000000001 
GPR[09]: 0700000043243F98 GPR[10]: 0000000000000400 GPR[11]: 
070000000CFF64CC 
GPR[12]: 0000000000000004 GPR[13]: 0000000110677800 GPR[14]: 
0000000000000000 
GPR[15]: 0000000000000000 GPR[16]: 0000000000000000 GPR[17]: 
0000000000000000 
GPR[18]: 0000000000000000 GPR[19]: 0000000000000000 GPR[20]: 
0000000000000000 
GPR[21]: 0000000000000000 GPR[22]: 0000000000000000 GPR[23]: 
0000000000000000 
GPR[24]: 0000000000000000 GPR[25]: 0000000000000000 GPR[26]: 
0000000000000000 
GPR[27]: 0000000000000000 GPR[28]: 000000001A580000 GPR[29]: 
000000001D200000 
GPR[30]: FFFFFFFFCBCB0000 GPR[31]: 0900000014980400 
FPR[00]: 0000000000000000 FPR[01]: 4000000000000000 FPR[02]: 
41F0000000000000 
FPR[03]: 4330080000000000 FPR[04]: 0000000082004000 FPR[05]: 
C32FFFFFFFFFFFF4 
FPR[06]: 4330080000000002 FPR[07]: 40EDF84000000000 FPR[08]: 
0000000000000000 
FPR[09]: 0000000000000000 FPR[10]: 0000000000000000 FPR[11]: 
401C000000000000 
FPR[12]: 3FF0000000000000 FPR[13]: 0000000000000000 FPR[14]: 
0000000000000000 
FPR[15]: 0000000000000000 FPR[16]: 0000000000000000 FPR[17]: 
0000000000000000 
FPR[18]: 0000000000000000 FPR[19]: 0000000000000000 FPR[20]: 
0000000000000000 
FPR[21]: 0000000000000000 FPR[22]: 0000000000000000 FPR[23]: 
0000000000000000 
FPR[24]: 0000000000000000 FPR[25]: 0000000000000000 FPR[26]: 
0000000000000000 
FPR[27]: 0000000000000000 FPR[28]: 0000000000000000 FPR[29]: 
0000000000000000 
FPR[30]: 0000000000000000 FPR[31]: 0000000000000000 
</Registers> 
<POFDisassembly> 
     0x090000000DFDCE04 : 38C00000 li r6,0x0 
     0x090000000DFDCE08 : 38E00001 li r7,0x1 
     0x090000000DFDCE0C : 39200008 li r9,0x8 
     0x090000000DFDCE10 : 39400000 li r10,0x0 
     0x090000000DFDCE14 : 4BFC23CD bl 0x90000000DF9F1E0 
     0x090000000DFDCE18 : 60000000 ori r0,r0,0x0 
     0x090000000DFDCE1C : E86100B0 ld r3,176(r1) 
     0x090000000DFDCE20 : 08430200 tdi    2,r3,512 
>>>> 0x090000000DFDCE24 : 80630000 lwz r3,0(r3) 
     0x090000000DFDCE28 : 54630036 rlwinm 
r3,r3,0,0xFFFFFFFFFFFFFFF0 # 0:27 
     0x090000000DFDCE2C : E89F03F8 ld r4,1016(r31) 
     0x090000000DFDCE30 : 7C832040 cmpl cr1,r3,r4 
     0x090000000DFDCE34 : 7C600026 mfcr r3 
     0x090000000DFDCE38 : 54633FFE rlwinm        r3,r3,7,0x1 # 
31:31 
</POFDisassembly> 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x090000000DFDCE24 codeIsValid__7SMemBlkCFv + 0x64 
0x090000000DFDCF80 isValid__7SMemBlkCFv + 0x60 
0x090000000DFDD0F0 
md_AssertMemoryBlockIsBigEnough__FPCvCUlPCcCiT3CbPcT2 + 0xF0 
0x090000000DFE7680 sqlo_md_mchk + 0xC0 
0x090000000DFE7BB4 sqlo_md_mcpy + 0x174 
0x0900000011A331C8 
__ct__18XmlrnReferenceNodeFCUcCUlT2C8XMLS_XIDN31PUc + 0xC8 
0x0900000011A3E790 
writeReferenceNode__19XmlrnSequenceWriterFUcR8XMLS_XIDT1UlT4T1PU 
cT1 
+ 0xF90 
0x0900000011AA6478 
addItemSubtree__13XmlrnSequenceFP17xmlDataDescriptor + 0xFB8 
0x0900000011AA9998 
addItemInternal__13XmlrnSequenceFP17xmlDataDescriptorUc + 0x98 
0x0900000011AA9BE4 addItems__13XmlrnSequenceFPP10sqlz_valueUs + 
0x84 
0x0900000011AAA220 
createSequence__13XmlrnSequenceFP11XMLSTORE_CBP17xmlDataDescript 
orP13XmlrnSequenceUcPP10sqlz_valueUs 
+ 0x3E0 
0x0900000013061370 sqlriXmlSequenceCreate__FP8sqlrr_cb + 0x390 
0x090000000EDE8F44 sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm + 
0x584 
0x090000000EDE9ABC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x4DC 
0x0900000010F5D1C8 
sqlrr_process_fetch_request__FP14db2UCinterface + 0xE48 
0x0900000010F63D38 
sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0xD78 
0x0900000014230AD4 
sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0x214 
0x0900000014200388 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface 
+ 0x1C8 
0x09000000141FEEBC 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x21C 
0x090000000F4B0B0C sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 
0x4AC 
0x090000000F4B293C 
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x15C 
0x090000000F4B99F4 
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x474 
0x090000000F4BBA7C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x23C 
0x090000000E23268C RunEDU__8sqeAgentFv + 0x3AC 
0x090000000E22207C EDUDriver__9sqzEDUObjFv + 0x19C 
0x090000000E22239C sqlzRunEDU__FPcUi + 0x3C 
0x090000000E0BB7C4 sqloEDUEntry + 0x6A4 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See APAR description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users need to upgrade to V97 fp5.                            * 
****************************************************************
Local Fix:
User may choose to set DB2_MEMORY_PROTECT to NO
available fix packs:
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 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
With the fix for this APAR, users will not have experience the 
ABEND as described in the APAR.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.07.2011
07.12.2011
07.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList