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

POSSIBLE MEMORY CORRUPTION - TRAP IN <SQLRAERTDESTROYTABLE>
<SQLRAERT.C:259>

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If we run out of memory while constructing a cursor variable, 
the following connection reset might fail with -1224 which 
brings down the instance. 
 
<Header> 
DB2 build information: DB2 v9.7.100.119 s090917 SQL09071 
timestamp: 2009-09-21-07.07.54.953000 
uname: S:Windows 
comment: NTX6497 
process id: 660 
thread id: 3144 
</Header> 
<POFDisassembly> 
<![CDATA[ 
Failing instruction at 000000018004801A offset: 
0000000000000A04in <sqloFreeMemChunks> <NotFound:-1> 
        ]]></POFDisassembly> 
       <StackTrace> 
      <![CDATA[ 
 
------RBP--------------RIP--------------ARGS-------------------- 
------------------------------------- 
00000000136985E0 000000018004801A 0000000001B40000 
0000000000000002 000007FFFC98EDA0 0000000001B48829 offset: 
0000000000000A04 in <sqloFreeMemChunks> <NotFound:-1> 
00000000136986E0 000000018004C581 0000000013698720 
000007FFFC98EDA0 0000000000000000 000007FFCEDF0C98 offset: 
00000000000005A3 in <sqlofmblkEx> <NotFound:-1> 
0000000013698710 0000000001B48829 0000000000000001 
000000000BD6419D 000007FF00000001 0000000001B44FB4 offset: 
0000000000000009 in <sqlofmblk> 
<E:\db2_v97fp1\ntx64\s090917\engn\include\sqlomem.h:502> 
0000000013698790 00000000030E96C8 0000000013698978 
0000000013698D14 0000000013698D18 000000000213567E offset: 
00000000000000F2 in <sqlraERTDestroyTable> <sqlraert.C:259> 
0000000013699660 0000000002F7DFFF 0000000000000040 
000000000000000B 0000000000000000 000007FF00000000 offset: 
0000000000001585 in <sqlrr_appl_term> <sqlrr.C:3754> 
00000000136998E0 0000000001F44674 0000000000000000 
0000000006540740 0000000006506D10 0000000007C3B3E0 offset: 
0000000000000492 in <sqeApplication::AppStopUsing> 
<sqle_application.C:5097> 
0000000013699C30 00000000020261A7 0000000000000000 
000007FFFDA35D00 0000000000000005 0000000000000000 offset: 
0000000000000083 in <sqlesrspWrp> <sqleu_server.C:2288> 
0000000013699CE0 0000000002025D91 0000000000000001 
000000000000025A 0000000000000000 0000000000000000 offset: 
0000000000000095 in <sqleUCagentConnectReset> 
<sqleu_server.C:2469> 
0000000013699EB0 000000000211DABD 0000000000000000 
00000002280D30D9 0000000000000000 0000000000000000 offset: 
0000000000000EA9 in <sqljsCleanup> <sqljsqam.C:4419> 
0000000013699F50 0000000002117D90 0000000000000000 
0000000000000000 0000000000000000 0000000000000000 offset: 
000000000000046E in <sqljsDrdaAsInnerDriver> <sqljsqam.C:1322> 
000000001369F870 00000000021177A3 000007FFFC248270 
000000018008D35B 000000000027C4B0 0000000007500348 offset: 
000000000000012B in <sqljsDrdaAsDriver> <sqljsqam.C:1046> 
000000001369FBD0 0000000001F4F276 0002625A00000000 
000000018001A3D6 000000734BD67DBD 000000018002C17A offset: 
0000000000000748 in <sqeAgent::RunEDU> <sqle_agent.C:3946> 
000000001369FC60 00000000038ADF35 000000000F350D98 
000000001369FCB0 0000000000000000 00000001800E007A offset: 
000000000000010F in <sqlzRunEDU> <sqlz_edu_obj.C:35> 
000000001369FF70 00000001800E0391 000000000F350D98 
0000000000000000 0000000000000000 000000001369FFA8 offset: 
000000000000042B in <sqloInitEDUServices> <NotFound:-1> 
000000001369FFA0 0000000077D0B71A 0000000000000000 
0000000000000000 0000000000000000 0000000000000000 
]]></StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW All platforms                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* the following connection reset might fail with -1224 which   * 
*                                                              * 
* brings down the instance.                                    * 
*                                                              * 
* <Header>                                                     * 
* DB2 build information: DB2 v9.7.100.119 s090917 SQL09071     * 
*                                                              * 
* timestamp: 2009-09-21-07.07.54.953000                        * 
* uname: S:Windows                                             * 
* comment: NTX6497                                             * 
* process id: 660                                              * 
* thread id: 3144                                              * 
* </Header>                                                    * 
* <POFDisassembly>                                             * 
* <![CDATA[                                                    * 
* Failing instruction at 000000018004801A offset:              * 
* 0000000000000A04in <sqloFreeMemChunks> <NotFound:-1>         * 
*        ]]></POFDisassembly>                                  * 
*      <StackTrace>                                            * 
*    <![CDATA[                                                 * 
*                                                              * 
* ------RBP--------------RIP--------------ARGS------------------ 
* -------------------------------------                        * 
* 00000000136985E0 000000018004801A 0000000001B40000           * 
* 0000000000000002 000007FFFC98EDA0 0000000001B48829 offset:   * 
*                                                              * 
* 0000000000000A04 in <sqloFreeMemChunks> <NotFound:-1>        * 
*                                                              * 
* 00000000136986E0 000000018004C581 0000000013698720           * 
* 000007FFFC98EDA0 0000000000000000 000007FFCEDF0C98 offset:   * 
*                                                              * 
* 00000000000005A3 in <sqlofmblkEx> <NotFound:-1>              * 
* 0000000013698710 0000000001B48829 0000000000000001           * 
* 000000000BD6419D 000007FF00000001 0000000001B44FB4 offset:   * 
*                                                              * 
* 0000000000000009 in <sqlofmblk>                              * 
* <E:\db2_v97fp1\ntx64\s090917\engn\include\sqlomem.h:502>     * 
*                                                              * 
* 0000000013698790 00000000030E96C8 0000000013698978           * 
* 0000000013698D14 0000000013698D18 000000000213567E offset:   * 
*                                                              * 
* 00000000000000F2 in <sqlraERTDestroyTable> <sqlraert.C:259>  * 
*                                                              * 
* 0000000013699660 0000000002F7DFFF 0000000000000040           * 
* 000000000000000B 0000000000000000 000007FF00000000 offset:   * 
*                                                              * 
* 0000000000001585 in <sqlrr_appl_term> <sqlrr.C:3754>         * 
* 00000000136998E0 0000000001F44674 0000000000000000           * 
* 0000000006540740 0000000006506D10 0000000007C3B3E0 offset:   * 
*                                                              * 
* 0000000000000492 in <sqeApplication::AppStopUsing>           * 
* <sqle_application.C:5097>                                    * 
* 0000000013699C30 00000000020261A7 0000000000000000           * 
* 000007FFFDA35D00 0000000000000005 0000000000000000 offset:   * 
*                                                              * 
* 0000000000000083 in <sqlesrspWrp> <sqleu_server.C:2288>      * 
*                                                              * 
* 0000000013699CE0 0000000002025D91 0000000000000001           * 
* 000000000000025A 0000000000000000 0000000000000000 offset:   * 
*                                                              * 
* 0000000000000095 in <sqleUCagentConnectReset>                * 
* <sqleu_server.C:2469>                                        * 
* 0000000013699EB0 000000000211DABD 0000000000000000           * 
* 00000002280D30D9 0000000000000000 0000000000000000 offset:   * 
*                                                              * 
* 0000000000000EA9 in <sqljsCleanup> <sqljsqam.C:4419>         * 
* 0000000013699F50 0000000002117D90 0000000000000000           * 
* 0000000000000000 0000000000000000 0000000000000000 offset:   * 
*                                                              * 
* 000000000000046E in <sqljsDrdaAsInnerDriver>                 * 
* <sqljsqam.C:1322>                                            * 
* 000000001369F870 00000000021177A3 000007FFFC248270           * 
* 000000018008D35B 000000000027C4B0 0000000007500348 offset:   * 
*                                                              * 
* 000000000000012B in <sqljsDrdaAsDriver> <sqljsqam.C:1046>    * 
*                                                              * 
* 000000001369FBD0 0000000001F4F276 0002625A00000000           * 
* 000000018001A3D6 000000734BD67DBD 000000018002C17A offset:   * 
*                                                              * 
* 0000000000000748 in <sqeAgent::RunEDU> <sqle_agent.C:3946>   * 
*                                                              * 
* 000000001369FC60 00000000038ADF35 000000000F350D98           * 
* 000000001369FCB0 0000000000000000 00000001800E007A offset:   * 
*                                                              * 
* 000000000000010F in <sqlzRunEDU> <sqlz_edu_obj.C:35>         * 
* 000000001369FF70 00000001800E0391 000000000F350D98           * 
* 0000000000000000 0000000000000000 000000001369FFA8 offset:   * 
*                                                              * 
* 000000000000042B in <sqloInitEDUServices> <NotFound:-1>      * 
*                                                              * 
* 000000001369FFA0 0000000077D0B71A 0000000000000000           * 
* 0000000000000000 0000000000000000 0000000000000000           * 
* ]]></StackTrace>                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v97fp1                                        * 
****************************************************************
Local Fix:
Increase application heap size
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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

Solution
First Fixed in DB2 Version 9.7 fix pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.09.2009
15.01.2010
31.08.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList