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

SLOW LOG REPLAY PERFORMANCE DUE TO LATCH CONTENTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During log replay (either rollforward or on a standby database), 
we may see slow performance due to a latch contention for 
transsem latch. On HADR systems, this slow performance may 
contribute congestion states. To verify this, stacks have to be 
collected for all db2redo worker processes. 
 
A typical stack for redo worker process holding the transsem 
latch is: 
 
   528654 (./t528654.000) -- Line: 156, File: sqlptinf.C 
   Agent Type:  db2redow (OB7) 
 
*** Stack *** 
 
Timestamp: 2009-05-10-14.15.56.790422 
0x0900000005107398 
sqlpReservedToBeFreed__FP20sqle_agent_privatecbP8SQLP_TIDi + 
0x3A0 
0x0900000004E7107C 
sqldConsumeSpace__FP13SQLD_DFM_WORKP13SQLD_DPG_DATAiN23 + 0x104 
0x0900000004E630F0 
@30@sqldRedoUpsert__FP13SQLD_DFM_WORKP15SQLD_INSINFO_LRP8SQLP_LS 
NUl + 0x678 
0x0900000004E600DC 
sqldRedo__FP20sqle_agent_privatecbP8SQLD_LRHP8SQLP_LSNUlN24 + 
0x484 
0x09000000047FF958 
sqldmrdo__FP20sqle_agent_privatecbP8SQLP_LSNPcUlN34P8SQLP_TIDP15 
SQLD_RECOV_INFO + 0x540 
0x090000000451DCFC 
sqlpRecDbRedo__FP20sqle_agent_privatecbP8SQLP_ACBP9SQLP_DBCBP10S 
QLP_FRAPPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT + 0x574 
0x090000000516EBD4 
sqlpPRecProcLog__FP20sqle_agent_privatecbP8SQLP_ACBP9SQLP_DBCB + 
0x640 
0x090000000451C820 
sqlpParallelRecovery__FP20sqle_agent_privatecbP5sqlca + 0x930 
0x09000000050E70B8 sqleSubCoordProcessRequest__FP13sqle_agent_cb 
+ 0x1C0 
0x0900000004E9BD14 sqleRunAgent__FPcUi + 0x95C 
0x0900000004F1BE4C 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x264 
0x0900000004F1B7F4 @49@sqloRunGDS__Fv + 0x178 
0x0900000004F3D378 sqloInitEDUServices + 0x180 
0x0900000004A15394 
@49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 0x2E8 
 
Holding Latch type: (SQLO_LT_SQLP_DBCB__transsem) - Address: 
(780000020018038), Line: 156, File: sqlptinf.C 
 
 
A typical stack for redo worker process waiting for the same 
transsem latch is: 
 
   258418 (./t258418.000) -- Line: 0, File: 
   Agent Type:  db2redow (OB7) 
 
<<< Stack >>> 
 
Timestamp: 2009-05-10-14.15.56.801798 
0x0900000004FE3854 getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 
0x4AC 
0x0900000004FE3B2C getConflict__17SQLO_SLATCH_CAS64FCUl + 0x98 
0x090000000643A05C 
sqloltch_track__FCP10sqlo_latchCUlCPCcT2C14SQLO_LT_VALUES@glue20 
8 + 0x1F8 
0x0900000005107234 
sqlpReservedToBeFreed__FP20sqle_agent_privatecbP8SQLP_TIDi + 
0x23C 
0x0900000004E714B8 
sqldReleaseSpace__FP13SQLD_DFM_WORKP13SQLD_DPG_DATAiN23 + 0x108 
0x0900000004E6CE20 
@30@sqldRedoDelete__FP13SQLD_DFM_WORKP15SQLD_DELINFO_LRP8SQLP_LS 
NUl + 0x500 
0x0900000004E600AC 
sqldRedo__FP20sqle_agent_privatecbP8SQLD_LRHP8SQLP_LSNUlN24 + 
0x454 
0x09000000047FF958 
sqldmrdo__FP20sqle_agent_privatecbP8SQLP_LSNPcUlN34P8SQLP_TIDP15 
SQLD_RECOV_INFO + 0x540 
0x090000000451DCFC 
sqlpRecDbRedo__FP20sqle_agent_privatecbP8SQLP_ACBP9SQLP_DBCBP10S 
QLP_FRAPPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT + 0x574 
0x090000000516EBD4 
sqlpPRecProcLog__FP20sqle_agent_privatecbP8SQLP_ACBP9SQLP_DBCB + 
0x640 
0x090000000451C820 
sqlpParallelRecovery__FP20sqle_agent_privatecbP5sqlca + 0x930 
0x09000000050E70B8 sqleSubCoordProcessRequest__FP13sqle_agent_cb 
+ 0x1C0 
0x0900000004E9BD14 sqleRunAgent__FPcUi + 0x95C 
0x0900000004F1BE4C 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x264 
 
Waiting on latch type: (SQLO_LT_SQLP_DBCB__transsem) - Address: 
(780000020018038), Line: 0, File:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SLOW LOG REPLAY PERFORMANCE DUE TO LATCH CONTENTION          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.7 FP1                                           * 
****************************************************************
Local Fix:
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
Problem was first fixed in Version 9.7 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.07.2009
22.12.2009
22.12.2009
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