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

DEACTIVATION OF A DATABASE MAY HANG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
There is a small timing window that can hang logger processes 
during database deactivation. You may also run into this hang on 
a standby HADR database. 
 
To verify this APAR, collect callstacks for db2redom (redo 
master) process and verify the callstacks, it should match the 
following. 
 
 0x09000000004E23D0 _p_nsleep + 0x10 
  0x090000000005D3B0 nsleep + 0xB0 
  0x090000000010746C nanosleep + 0x140 
  0x0900000000BCED0C ossSleep + 0x74 
  0x09000000052D2DF4 sqlorest + 0x38 
  0x0900000005171164 
sqlpPRecReadLog__FP20sqle_agent_privatecbP8SQLP_ACBP9SQLP_DBCB + 
0x704 
  0x090000000451E8C4 
sqlpParallelRecovery__FP20sqle_agent_privatecbP5sqlca + 0x10 
  0x09000000050E70B8 
sqleSubCoordProcessRequest__FP13sqle_agent_cb + 0x1C0 
  0x0900000004E9BD14 sqleRunAgent__FPcUi + 0x95C 
  0x0900000004F1BE4C 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x264 
  0x0900000004F1E288 sqloSpawnEDU + 0x234 
  0x0900000004F1DBB4 
sqleCreateNewAgent__FiP8sqlekrcbP17sqlcc_init_structP16sqlkdRqst 
RplyFmtP18sqle_master_app_cbT1P20agentPoolLatchVectorP16SQLO_EDU 
WAITPOSTP17sqle_connect_infoPP13sqle_agent_cb + 0x28C 
  0x0900000005082C18 
sqleGetAgentFromPool__FiP17sqlcc_init_structT1P12sqlz_app_hdlP16 
sqlkdRqstRplyFmtP17sqle_connect_info + 0x82C 
  0x0900000005427AA8 
sqleGetAgent__FiP17sqlcc_init_structT1P12sqlz_app_hdlP16sqlkdRqs 
tRplyFmtT1 + 0x44C 
  0x0000000100004F0C sqleInitSysCtlr__FPi + 0x1188 
  0x00000001000031D4 sqleSysCtlr__Fv + 0x320 
  0x0900000004A155CC 
@49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 0x520 
  0x090000000541B498 sqloRunInstance + 0xA8 
  0x00000001000029F8 DB2main + 0x930 
  0x0000000100003D50 main + 0x10
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* There is a small timing window that can hang logger          * 
* processes during database deactivation. You may also run     * 
* into this hang on a standby HADR database. To verify this    * 
* APAR, collect callstacks for db2redom (redomaster) process   * 
* and verify the callstacks, it should match the following.    * 
* 0x09000000004E23D0 _p_nsleep + 0x10                          * 
* 0x090000000005D3B0 nsleep + 0xB0                             * 
* 0x090000000010746C nanosleep + 0x140                         * 
* 0x0900000000BCED0C ossSleep + 0x74                           * 
* 0x09000000052D2DF4 sqlorest + 0x38                           * 
* 0x0900000005171164sqlpPRecReadLog__FP20sqle_agent_privatecbP8S 
* 0x090000000451E8C4sqlpParallelRecovery__FP20sqle_agent_private 
* + 0x10                                                       * 
* 0x09000000050E70B8sqleSubCoordProcessRequest__FP13sqle_agent_c 
* + 0x1C0                                                      * 
* 0x0900000004E9BD14 sqleRunAgent__FPcUi + 0x95C               * 
* 0x0900000004F1BE4CsqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFO 
* + 0x264                                                      * 
* 0x0900000004F1E288 sqloSpawnEDU + 0x234                      * 
* 0x0900000004F1DBB4sqleCreateNewAgent__FiP8sqlekrcbP17sqlcc_ini 
* + 0x28C                                                      * 
* 0x0900000005082C18sqleGetAgentFromPool__FiP17sqlcc_init_struct 
* + 0x82C                                                      * 
* 0x0900000005427AA8sqleGetAgent__FiP17sqlcc_init_structT1P12sql 
* + 0x44C                                                      * 
* 0x0000000100004F0C sqleInitSysCtlr__FPi + 0x1188             * 
* 0x00000001000031D4 sqleSysCtlr__Fv + 0x320                   * 
* 0x0900000004A155CC@49@sqloSystemControllerMain__FCUiPFv_iPFi_v 
* + 0x520                                                      * 
* 0x090000000541B498 sqloRunInstance + 0xA80x00000001000029F8  * 
* DB2main + 0x930                                              * 
* 0x0000000100003D50 main + 0x10                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fix pack 2.                   * 
****************************************************************
Local Fix:
Use db2_kill to completely stop the database and remove the IPC 
resources.
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 is first fixed in DB2 UDB version 9.7 fix pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
18.02.2010
18.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList