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

DB2 GET SIGNAL 11 DURING THE ROLLBACK PROCESS WHEN CALLING NESTED
STORE PROCEDURE IN DPF

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When customer is calling nested store procedure, some errors may 
happen (such as dead lock),  and the transaction may be rolled 
back. 
During the rollback process, DB2 may trap with signal #11 with 
below call stacks: 
... 
(4)  0xe0000001304fe900  ---- Signal 11 (SIGSEGV) delivered ---- 
(5)  0xc0000000180a9a01 
_Z19sqlri_send_dss_msgsP8sqlrr_cbP10sqlri_ssobP23connect_msg_lis 
t_anchorPsi 
+ 0x221 at sqlri_dss.C:2076 
[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so] 
(6)  0xc0000000180a5cd0  _Z9sqlri_dssP8sqlrr_cb + 0xcb0 at 
sqlri_dss.C:1219 [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so] 
(7)  0xc0000000156c6d00 
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x240 
[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so] 
(8)  0xc000000015235200 
_Z29sqlrr_process_execute_requestP8sqlrr_cbi + 0x640 at 
sqlrr_sql.C:1257 [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so] 
(9)  0xc00000001529e440 
_Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo + 0x740 
[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so] 
 
or 
 
5        sqlriecc 
6        sqlra_close_section 
7        sqlra_sqlC_free_section 
8        sqlra_sqlC_free_sibling 
9        sqlra_sqlC_rmv_invoc_siblings 
10       sqlrr_destroy_invocation_cb 
11       sqlrr_chk_destroy_invocation_cb 
12       sqlrr_end_invocation 
 
In the db2diag.log, customer may see below message indicating a 
rollback is happening: 
 
2009-01-01-00.00.00.000000+000 I111111111A111   LEVEL: Severe 
PID     : XXXXX                TID  : 1           PROC : 
db2agent (DBNAME) 0 
INSTANCE: db2inst1             NODE : 000         DB   : DBNAME 
APPHDL  : 0-XXX                APPID: XXXXXXXX 
AUTHID  : DB2INST1 
FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20 
MESSAGE : Received sqlcode -1229 (rollback) for request 80000017 
(interrupt) from node number 0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL.                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When customer is calling nested store procedure, some        * 
* errorsmayhappen (such as dead lock),  and the transaction    * 
* may berolledback.During the rollback process, DB2 may trap   * 
* with signal #11withbelow call stacks:...(4)                  * 
* 0xe0000001304fe900  ---- Signal 11 (SIGSEGV)                 * 
* delivered----(5)                                             * 
* 0xc0000000180a9a01_Z19sqlri_send_dss_msgsP8sqlrr_cbP10sqlri_ss 
* 0x221 at                                                     * 
* sqlri_dss.C:2076[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](6) * 
*  0xc0000000180a5cd0  _Z9sqlri_dssP8sqlrr_cb + 0xcb0          * 
* atsqlri_dss.C:1219                                           * 
* [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](7)                 * 
* 0xc0000000156c6d00_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
* + 0x240[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](8)          * 
* 0xc000000015235200_Z29sqlrr_process_execute_requestP8sqlrr_cbi 
* + 0x640 atsqlrr_sql.C:1257                                   * 
* [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](9)                 * 
* 0xc00000001529e440_Z13sqlrr_executeP14db2UCinterfaceP9UCstpInf 
* + 0x740[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so]or5          * 
* sqlriecc6        sqlra_close_section7                        * 
* sqlra_sqlC_free_section8        sqlra_sqlC_free_sibling9     * 
*    sqlra_sqlC_rmv_invoc_siblings10                           * 
* sqlrr_destroy_invocation_cb11                                * 
* sqlrr_chk_destroy_invocation_cb12                            * 
* sqlrr_end_invocationIn the db2diag.log, customer may see     * 
* below messageindicating arollback is                         * 
* happening:2009-01-01-00.00.00.000000+000 I111111111A111      * 
* LEVEL: SeverePID    : XXXXX                TID  : 1          * 
* PROC :db2agent (DBNAME) 0INSTANCE: db2inst1            NODE  * 
* : 000        DB  : DBNAMEAPPHDL  : 0-XXX                     * 
* APPID: XXXXXXXXAUTHID  : DB2INST1FUNCTION: DB2 UDB, base sys * 
* utilities, sqleMergeSqlca,probe:20MESSAGE : Received sqlcode * 
* -1229 (rollback) for request80000017(interrupt) from node    * 
* number 0                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to version 9.5 fix pack 6 or later.                   * 
****************************************************************
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
This problem is first fixed in version 9.5 fix pack 6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.08.2009
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)