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

INSTANCE TRAPS AT FUNCTION SQLPENDUOWRUNTIME DUE TO OUT OF MEMORY
FAILURE FOR DATABASE HEAP

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
During application initialization certain database components 
are initialized using db heap memory. If the database runs out 
of this db heap memory the application initialization would fail 
and these database components would be terminated and freed. 
This particular error is due to a logic error in which a certain 
component is not terminated and cleaned up properly when the 
application initialization fails and leaves certain freed memory 
to be de-referenced later. 
 
The following db2diag.log snippet can be seen before the trap 
occurs. 
 
[...] 
 
2116556 2010-04-13-04.49.27.641871-240 E94769794E721      LEVEL: 
Warning 
2116557 PID    : 28617                TID  : 47708077287744PROC 
: db2sysc 
2116558 INSTANCE: svtdbm2              NODE : 000          DB  : 
ADD 
2116559 APPHDL  : 0-4924              APPID: 
*LOCAL.svtdbm2.100413084944 
2116560 AUTHID  : SVTDBM2 
2116561 EDUID  : 3495                EDUNAME: db2agent (ADD) 
2116562 FUNCTION: DB2 UDB, SQO Memory Management, 
sqloMemLogPoolConditions, probe:30 
2116563 DATA #1 : <preformatted> 
2116564 Out of memory failure for Database Heap (DBHEAP). 
2116565 Requested block size          : 7952 bytes. 
2116566 Physical heap size            : 48431104 bytes. 
2116567 Configured heap size          : 48431104 bytes. 
2116568 Unreserved memory used by heap : 0 bytes. 
2116569 Unreserved memory left in set  : 14680064 bytes. 
 
 
2117067 2010-04-13-04.49.28.707575-240 I94791120E492      LEVEL: 
Warning 
2117068 PID    : 28617                TID  : 47708077287744PROC 
: db2sysc 
2117069 INSTANCE: svtdbm2              NODE : 000          DB  : 
ADD 
2117070 APPHDL  : 0-4924              APPID: 
*LOCAL.svtdbm2.100413084944 
2117071 AUTHID  : SVTDBM2 
2117072 EDUID  : 3495                EDUNAME: db2agent (ADD) 
2117073 FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:600 
2117074 DATA #1 : String, 22 bytes 
2117075  _Z17sqlpEndUowRuntime 
2117076 DATA #2 : String, 4 bytes 
2117077 sqlp 
2117078 
2117079 2010-04-13-04.49.28.708031-240 I94791613E558      LEVEL: 
Severe 
2117080 PID    : 28617                TID  : 47708077287744PROC 
: db2sysc 
2117081 INSTANCE: svtdbm2              NODE : 000          DB  : 
ADD 
2117082 APPHDL  : 0-4924              APPID: 
*LOCAL.svtdbm2.100413084944 
2117083 AUTHID  : SVTDBM2 
2117084 EDUID  : 3495                EDUNAME: db2agent (ADD) 
2117085 FUNCTION: DB2 UDB, RAS/PD component, 
pdResilienceIsSafeToSustain, probe:800 
2117086 DATA #1 : String, 37 bytes 
2117087 Trap Sustainability Criteria Checking 
2117088 DATA #2 : Hex integer, 8 bytes 
2117089 0x0000000000023840 
2117090 DATA #3 : Boolean, 1 bytes 
2117091 false 
 
2117093 2010-04-13-04.49.28.709538-240 I94792172E556      LEVEL: 
Error 
2117094 PID    : 28617                TID  : 47708077287744PROC 
: db2sysc 
2117095 INSTANCE: svtdbm2              NODE : 000          DB  : 
ADD 
2117096 APPHDL  : 0-4924              APPID: 
*LOCAL.svtdbm2.100413084944 
2117097 AUTHID  : SVTDBM2 
2117098 EDUID  : 3495                EDUNAME: db2agent (ADD) 
2117099 FUNCTION: DB2 UDB, base sys utilities, 
sqleagnt_sigsegvh, probe:1 
2117100 MESSAGE : Error in agent servicing application with 
coor_node: 
2117101 DATA #1 : Hexdump, 2 bytes 
2117102 0x00002B63E6C0F912 : 0000 
      .. 
 
2117197 2010-04-13-04.49.28.710505-240 I94797825E570      LEVEL: 
Error 
2117198 PID    : 28617                TID  : 47708077287744PROC 
: db2sysc 
2117199 INSTANCE: svtdbm2              NODE : 000          DB  : 
ADD 
2117200 APPHDL  : 0-4924              APPID: 
*LOCAL.svtdbm2.100413084944 
2117201 AUTHID  : SVTDBM2 
2117202 EDUID  : 3495                EDUNAME: db2agent (ADD) 
2117203 FUNCTION: DB2 UDB, base sys utilities, 
sqleagnt_sigsegvh, probe:10 
2117204 MESSAGE : Error in agent servicing application with 
APPLICATION NAME: 
2117205 DATA #1 : Hexdump, 8 bytes 
2117206 0x00000002010A6412 : 666C 7461 626C 6573 
       fltables 
 
[...] 
 
A trap file can be generated. One instance of a stack trace is 
the following: 
 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00002B63DC3CF7FF ossDumpStackTraceEx + 0x01ef 
                (/home/svtdbm2/sqllib/lib64/libdb2osse.so.1) 
0x00002B63DC3CA5C6 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00cc 
                (/home/svtdbm2/sqllib/lib64/libdb2osse.so.1) 
0x00002B63D96EE7A9 sqlo_trce + 0x03fb 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D9732D09 sqloEDUCodeTrapHandler + 0x0243 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D6F01C00 address: 0x00002B63D6F01C00 ; dladdress: 
0x00002B63D6EF4000 ; offset in lib: 0x000000000000DC00 ; 
                (/lib64/libpthread.so.0) 
0x00002B63D8263018 _Z17sqlpEndUowRuntimeP8sqeAgentP9SQLP_DBCB + 
0x00c6 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D825F178 address: 0x00002B63D825F178 ; dladdress: 
0x00002B63D700D000 ; offset in lib: 0x0000000001252178 ; 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D825DD14 
_Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOPiP9SQLP_GXIDPP11sqlo_xla 
tch 
+ 0x03dc 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D8260FC4 _Z8sqlptfrgP8sqeAgentm + 0x0764 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D8266395 _Z8sqlpdenvP8sqeAgentb + 0x01bd 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E49EF7 
_ZN16sqeLocalDatabase13TermDbConnectEP8sqeAgentP5sqlcai + 0x03e1 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D8B4EB09 
_ZN14sqeApplication21HandleStartUsingErrorEP8sqeAgentP8SQLE_BWAP 
5sqlcaP22SQLESRSU_STATUS_VECTOR 
+ 0x0547 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E30B7E 
_ZN14sqeApplication13AppStartUsingEP8SQLE_BWAP8sqeAgentccP5sqlca 
Pc 
+ 0x06a4 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E2C97E address: 0x00002B63D7E2C97E ; dladdress: 
0x00002B63D700D000 ; offset in lib: 0x0000000000E1F97E ; 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E2B7B0 
_ZN14sqeApplication13AppLocalStartEP14db2UCinterface + 0x01b8 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E8720D _Z11sqlelostWrpP14db2UCinterface + 0x001d 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E88942 _Z14sqleUCengnInitP14db2UCinterfacet + 0x051a 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E87835 sqleUCagentConnect + 0x02b5 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7F187D2 
_Z18sqljsConnectAttachP13sqljsDrdaAsCbP14db2UCinterface + 0x0086 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7EF5D17 
_Z16sqljs_ddm_accsecP14db2UCinterfaceP13sqljDDMObject + 0x007f 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7EED262 
_Z17sqljsParseConnectP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCint 
erface 
+ 0x0068 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7EED783 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x035b 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7EE2AC3 address: 0x00002B63D7EE2AC3 ; dladdress: 
0x00002B63D700D000 ; offset in lib: 0x0000000000ED5AC3 ; 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7EE99B2 address: 0x00002B63D7EE99B2 ; dladdress: 
0x00002B63D700D000 ; offset in lib: 0x0000000000EDC9B2 ; 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7EE7341 address: 0x00002B63D7EE7341 ; dladdress: 
0x00002B63D700D000 ; offset in lib: 0x0000000000EDA341 ; 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7EE70D0 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x0102 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D7E221D9 _ZN8sqeAgent6RunEDUEv + 0x09f7 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D84CD2BC _ZN9sqzEDUObj9EDUDriverEv + 0x00a6 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D84CD213 _Z10sqlzRunEDUPcj + 0x0009 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D8246702 sqloEDUEntry + 0x02f4 
                (/home/svtdbm2/sqllib/lib64/libdb2e.so.1) 
0x00002B63D6EFA143 address: 0x00002B63D6EFA143 ; dladdress: 
0x00002B63D6EF4000 ; offset in lib: 0x0000000000006143 ; 
                (/lib64/libpthread.so.0) 
0x00002B63DCD708CD __clone + 0x006d 
                (/lib64/libc.so.6) 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During application initialization certain database           * 
* components                                                   * 
* are initialized using db heap memory. If the database runs   * 
* out                                                          * 
* of this db heap memory the application initialization would  * 
* fail                                                         * 
* and these database components would be terminated and freed. * 
*                                                              * 
* This particular error is due to a logic error in which a     * 
* certain                                                      * 
* component is not terminated and cleaned up properly when the * 
*                                                              * 
* application initialization fails and leaves certain freed    * 
* memory                                                       * 
* to be de-referenced later.                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW V9.5 FP6 or higher                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Instance won't trap at sqlpenduowruntime when an out of memory 
failure occurs for the database heap.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.04.2010
22.06.2010
22.06.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)