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

COMMAND "DB2STOP FORCE" MAY CAUSE A TRAP

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Issuing db2stop force command may cause a trap on db2 
v9.7. 
 
The trap occurred immediately after sqleKillNode sent SIGDUMP 
to all processes which. The following may appear in the 
 db2diag.log: 
 
2009-01-27-12.10.19.234088-300 I32874473E296 LEVEL: Severe 
PID : 2158 TID : 183095683680 PROC : db2stop2 
INSTANCE: db2inst1 NODE : 014 
FUNCTION: DB2 UDB, base sys utilities, sqleKillNode, probe:90 
MESSAGE : Sending sigdump and waiting for 1 min to complete 
 
2009-01-27-12.10.19.302308-300 E32874770E1515 LEVEL: Critical 
PID : 30054 TID : 183106529632 PROC : db2ckpwd 14 
INSTANCE: db2inst1 NODE : 014 
EDUID : 1 EDUNAME: db2sysc 14 
FUNCTION: DB2 UDB, oper system services, 
sqloEDUCodeTrapHandler,probe: 10 
MESSAGE : ADM14001C An unexpected and critical error has 
occurred: 
"Trap". The instance may have been shutdown as a result. 
"Automatic" FODC 
(First Occurrence Data Capture) has been invoked and diagnostic 
information 
has been recorded in directory 
"/var/ibmdb2/nyqxt150/sqllib/db2dump/". Please look in this 
directory 
for detailed evidence about what happened and contact IBM 
support if 
necessary to diagnose the problem. 
 
DATA #1 : 
Signal Number Recieved, 4 bytes 11 
 
From trap 
file 30054.1.014.trap.txt: 
*************************************** 
DB2 build information: DB2 v9.5.0.3 s081118 SQL09053 
timestamp: 2009-01-27-12.10.19.247235 
instance name: db2inst1.014 
EDU name : db2sysc 14 
EDU ID : 1 
Signal #11 
uname: S:Linux R:2.6.9-68.9.ELmsdwlargesmp V:#1 SMP Fri Feb 22 
18:47:03 
EST 2008 M:x86_64 N:np737c3n5 
process id: 30054 
thread id : 183106529632 (0x2AA1FFE960) 
</Header> 
<SignalDetails> 
. . . 
<StackTrace> 
---FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0000002A9B7E6047 ossDumpStackTraceEx + 0x01f7 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A9B7E1BBC _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00b4 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A9B7E1C83 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A97C93F5D sqlo_trce + 0x03f3 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A97CD9337 sqloEDUCodeTrapHandler + 0x0107 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A956784F0 address: 0x0000002A956784F0 ; dladdress: 
0x0000002A9566C000 ; offset in lib: 0x000000000000C4F0 ; 
(/lib64/tls/libpthread.so.0) 
0000002A956757C0 pthread_kill + 0x0000 
(/lib64/tls/libpthread.so.0) 
0000002A97CD9129 sqloUNIXSignalEDU + 0x0127 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A97CD9868 sqloDumpInstanceHandler + 0x003e 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A956784F0 address: 0x0000002A956784F0 ; dladdress: 
0x0000002A9566C000 ; offset in lib: 0x000000000000C4F0 ; 
(/lib64/tls/libpthread.so.0) 
0000002A9C16D326 msgrcv + 0x0066 
(/lib64/tls/libc.so.6) 
0000002A969FD0C2 
_Z16sqlorqueInternalP13SQLO_QUE_DESCP12SQLO_MSG_HDRii + 0x020e 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A969FCD71 sqlorque2 + 0x00c5 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A163F1 address: 0x0000002A96A163F1 ; dladdress: 
0x0000002A95782000 ; offset in lib: 0x00000000012943F1 ; 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A15E49 _Z20sqlockpw_daemon_initv + 0x0165 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A3729C address: 0x0000002A96A3729C ; dladdress: 
0x0000002A95782000 ; offset in lib: 0x00000000012B529C ; 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A36587 sqloRunInstance + 0x00cb 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
000000000040732F DB2main + 0x06cb 
(db2ckpwd 14) 
0000002A96A38F05 _Z16sqloEDUMainEntryPcj + 0x000f 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A39DCA sqloEDUEntry + 0x07fe 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A95672137 address: 0x0000002A95672137 ; dladdress: 
0x0000002A9566C000 ; offset in lib: 0x0000000000006137 ; 
(/lib64/tls/libpthread.so.0) 
0000002A9C16C113 __clone + 0x0073 
(/lib64/tls/libc.so.6) 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB version v9.5 or above installed systems.             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Issuing db2stop force command may cause a trap on db2        * 
* v9.7.Detailed Information:The trap might occur immediately   * 
* after sqleKillNode sendingSIGDUMP to all processes. The      * 
* following may appear in                                      * 
* thedb2diag.log:2009-01-27-12.10.19.234088-300 I32874473E296  * 
* LEVEL:SeverePID : 2158 TID : 183095683680 PROC               * 
* :db2stop2INSTANCE: nyqxt150 NODE : 014FUNCTION: DB2 UDB,     * 
* base sys utilities, sqleKillNode,probe:90MESSAGE : Sending   * 
* sigdump and waiting for 1 min to                             * 
* complete2009-01-27-12.10.19.302308-300 E32874770E1515        * 
* LEVEL:CriticalPID : 30054 TID : 183106529632 PROC :db2ckpwd  * 
* 14INSTANCE: nyqxt150 NODE : 014EDUID : 1 EDUNAME: db2sysc    * 
* 14FUNCTION: DB2 UDB, oper system                             * 
* services,sqloEDUCodeTrapHandler,probe:10MESSAGE : ADM14001C  * 
* An unexpected and critical error hasoccurred:"Trap". The     * 
* instance may have been shutdown as a result."Automatic" FODC * 
* (First Occurrence Data Capture) has beeninvoked and          * 
* diagnostic information has been recorded indirectory         * 
* "/var/ibmdb2/nyqxt150/sqllib/db2dump/". Pleaselook in this   * 
* directory for detailed evidence about whathappened and       * 
* contact IBM support ifnecessary to diagnose the              * 
* problem.<StackTrace>---FUNC-ADDR---- ------FUNCTION +        * 
* OFFSET------0000002A9B7E6047 ossDumpStackTraceEx +           * 
* 0x01f7(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2osse 
* _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm                       * 
* +0x00b4(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2oss 
* _ZN11OSSTrapFile4dumpEmiP7siginfoPv                          * 
* +0x0009(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2oss 
* sqlo_trce +                                                  * 
* 0x03f3(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* sqloEDUCodeTrapHandler +                                     * 
* 0x0107(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A956784F0 ; dladdress:0x0000002A9566C000 ; * 
* offset in lib: 0x000000000000C4F0                            * 
* ;(/lib64/tls/libpthread.so.0)0000002A956757C0 pthread_kill + * 
* 0x0000(/lib64/tls/libpthread.so.0)0000002A97CD9129           * 
* sqloUNIXSignalEDU +                                          * 
* 0x0127(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* sqloDumpInstanceHandler +                                    * 
* 0x003e(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A956784F0 ; dladdress:0x0000002A9566C000 ; * 
* offset in lib: 0x000000000000C4F0                            * 
* ;(/lib64/tls/libpthread.so.0)0000002A9C16D326 msgrcv +       * 
* 0x0066(/lib64/tls/libc.so.6)0000002A969FD0C2_Z16sqlorqueIntern 
* +0x020e(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.s 
* sqlorque2 +                                                  * 
* 0x00c5(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A96A163F1 ; dladdress:0x0000002A95782000 ; * 
* offset in lib: 0x00000000012943F1                            * 
* ;(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so.1)00 
* _Z20sqlockpw_daemon_initv +                                  * 
* 0x0165(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A96A3729C ; dladdress:0x0000002A95782000 ; * 
* offset in lib: 0x00000000012B529C                            * 
* ;(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so.1)00 
* sqloRunInstance +                                            * 
* 0x00cb(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* DB2main + 0x06cb(db2ckpwd 14)0000002A96A38F05                * 
* _Z16sqloEDUMainEntryPcj +                                    * 
* 0x000f(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* sqloEDUEntry +                                               * 
* 0x07fe(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A95672137 ; dladdress:0x0000002A9566C000 ; * 
* offset in lib: 0x0000000000006137                            * 
* ;(/lib64/tls/libpthread.so.0)0000002A9C16C113 __clone +      * 
* 0x0073(/lib64/tls/libc.so.6)</StackTrace>                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrading to DB2 UDB v9.7fp1 resolves this issue.            * 
****************************************************************
Local Fix:
There is no workaround, but as this problem occurred while DB2 
was shutting down, there is no harm done to your database. 
First Fixed in DB2 9.5 Fix Pack 5.
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 6 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 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 UDB v95fp5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.09.2009
17.02.2010
17.02.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP5,
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList