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

DB2 CRASH WHEN CTRL+C IS PRESSED DURING MDC REFRESHING, WHEN NOT LOGGED
INITIALLY IS ACTIVATED

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
DB2 might crash when interrupt is received during MDC 
refreshing, when NOT LOGGED INITIALLY is activated. 
One of the symptom is showing the following stack in db2diag.log 
(or in trap file) 
2010-03-24-13.46.03.808277-240 I2069921E1331       LEVEL: Error 
PID     : 20752                TID  : 198499625312 PROC : 
db2sysc 5 
INSTANCE: nypxt400             NODE : 005          DB   : C1RISK 
APPHDL  : 1-37312              APPID: 
10.163.26.167.16280.10032417454 
AUTHID  : CPGDBPRD 
EDUID   : 267757               EDUNAME: db2agnta (C1RISK) 5 
FUNCTION: DB2 UDB, sqldb, sqldb_purgeAllRolloutCBsFromTENTRY, 
probe:548 
MESSAGE : Rollout CB list is not empty at tx boundary! 
DATA #1 : Pointer, 8 bytes 
0x0000002df3433080 
CALLSTCK: 
  [0] 0x0000002A966E4509 pdLog + 0xD7 
  [1] 0x0000002A97113363 
_Z34sqldb_purgeAllRolloutCBsFromTENTRYP8sqeAgent + 0x16F 
  [2] 0x0000002A96AD7FAB 
_Z17sqlpEndUowRuntimeP8sqeAgentP9SQLP_DBCB + 0x7E7 
  [3] 0x0000002A96AD3A22 
/ms/dist/ibmdb2/PROJ/ds/9.5.4.10/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1 
+ 0x1351A22 
  [4] 0x0000002A96AD202F 
_Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOPiP9SQLP_GXIDPP11sqlo_xla 
tch 
+ 0x497 
  [5] 0x0000002A96B3F6CC 
_Z12sqlrrbck_dpsP8sqlrr_cbiiiP15SQLXA_CALL_INFOP9SQLP_GXID + 
0x106 
  [6] 0x0000002A97F35F13 _Z17sqlrr_tran_routerP8sqlrr_cb + 0x85F 
  [7] 0x0000002A97F20F5C 
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0xB42 
  [8] 0x0000002A971B51D1 _Z20sqleSubRequestRouterP8sqeAgentPjS1_ 
+ 0xA83 
  [9] 0x0000002A971B4147 _Z21sqleProcessSubRequestP8sqeAgent + 
0x5F 
 
The problem is that sqldRolloutBlocksOfCell passes the master 
TCB to sqldb_allocateAndLinkRolloutCB, which then uses it to 
check if Not Logged Initially is activated for the table. 
However the TCB_D_NOLOG is not stored in the master TCB, only in 
the TCB for the partitions.
Problem Summary:
Problem Description: 
DB2 CRASH WHEN CTRL+C IS PRESSED DURING MDC REFRESHING, WHEN NOT 
LOGGED INITIALLY IS ACTIVATED 
Problem Summary: 
DB2 might crash when interrupt is received during MDC 
 
refreshing, when NOT LOGGED INITIALLY is activated. 
One of the symptom is showing the following stack in db2diag.log 
(or in trap file) 
2010-03-24-13.46.03.808277-240 I2069921E1331       LEVEL: Error 
PID     : 20752                TID  : 198499625312 PROC : 
db2sysc 5 
INSTANCE: nypxt400             NODE : 005          DB   : C1RISK 
APPHDL  : 1-37312              APPID: 
10.163.26.167.16280.10032417454 
AUTHID  : CPGDBPRD 
EDUID   : 267757               EDUNAME: db2agnta (C1RISK) 5 
FUNCTION: DB2 UDB, sqldb, sqldb_purgeAllRolloutCBsFromTENTRY, 
probe:548 
MESSAGE : Rollout CB list is not empty at tx boundary! 
DATA #1 : Pointer, 8 bytes 
0x0000002df3433080 
CALLSTCK: 
  [0] 0x0000002A966E4509 pdLog + 0xD7 
  [1] 0x0000002A97113363 
_Z34sqldb_purgeAllRolloutCBsFromTENTRYP8sqeAgent + 0x16F 
  [2] 0x0000002A96AD7FAB 
_Z17sqlpEndUowRuntimeP8sqeAgentP9SQLP_DBCB + 0x7E7 
  [3] 0x0000002A96AD3A22 
/ms/dist/ibmdb2/PROJ/ds/9.5.4.10/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1 
+ 0x1351A22 
  [4] 0x0000002A96AD202F 
_Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOPiP9SQLP_GXIDPP11sqlo_xla 
tch 
+ 0x497 
  [5] 0x0000002A96B3F6CC 
_Z12sqlrrbck_dpsP8sqlrr_cbiiiP15SQLXA_CALL_INFOP9SQLP_GXID + 
0x106 
  [6] 0x0000002A97F35F13 _Z17sqlrr_tran_routerP8sqlrr_cb + 0x85F 
  [7] 0x0000002A97F20F5C 
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0xB42 
  [8] 0x0000002A971B51D1 _Z20sqleSubRequestRouterP8sqeAgentPjS1 
+ 0xA83 
  [9] 0x0000002A971B4147 _Z21sqleProcessSubRequestP8sqeAgent + 
0x5F 
 
The problem is that sqldRolloutBlocksOfCell passes the master 
TCB to sqldb_allocateAndLinkRolloutCB, which then uses it to 
check if Not Logged Initially is activated for the table. 
However the TCB_D_NOLOG is not stored in the master TCB, only in 
the TCB for the partitions.
Local Fix:
n/a
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
Problem is first fixed in Version 9.5 Fix Pack 6
Workaround
n/a
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67554 IC67634 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.03.2010
13.05.2010
13.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)