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

INSTANCE PANICS WITH ERROR "EXPECTED LATCH TO BE HELD"

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
Instance panics and crashes with the following message in the 
db2diag.log 
 
2010-07-27-12.25.44.623481+120 E58407708A2265     LEVEL: Severe 
(OS) 
PID     : 2302062              TID  : 1           PROC : 
db2pfchr 1 
INSTANCE: dwhprod              NODE : 001 
FUNCTION: DB2 UDB, SQO Latch Tracing, 
SQLO_SLATCH_CAS64::releaseConflictComple, probe:330 
MESSAGE : 
ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD 
          "expected latch to be held." 
CALLED  : OS, -, unspecified_system_function 
DATA #1 : String, 39 bytes 
Attempting to unlock an invalid latch: 
DATA #2 : File name, 16 bytes 
sqloLatchCAS64.C 
DATA #3 : Source file line number, 8 bytes 
980 
DATA #4 : Codepath, 8 bytes 
4 
DATA #5 : String, 125 bytes 
0x0000000000000000: { 
   held X: 0 
   reserved for X: 0 
   shared holders: 0 
   firstSharIndex: 0x0 
   firstExclIndex: 0x0 
} 
DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes 
0x0 (invalid mode) 
DATA #7 : String, 394 bytes 
{ 
   state         = 0x0000000000000000 
                 = { 
                       held X: 0 
                       reserved for X: 0 
                       shared holders: 0 
                       firstSharIndex: 0x0 
                       firstExclIndex: 0x0 
                   } 
   starve X mode = true 
   xWaitCount    = 0 
   requestCount  = 0 
   identity      = SQLB_BPD::bpdLatch (38) 
} 
DATA #8 : Hexdump, 16 bytes 
0x0780000222E869D0 : 0002 2600 0001 0000 0026 0001 0000 0000 
..&......&...... 
CALLSTCK: 
  [0] 0x090000000305FEC0 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7 
+ 0x298 
  [1] 0x090000000305FB44 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7@glueA3 
+ 0x98 
  [2] 0x0900000002F0A308 
releaseConflictComplex__17SQLO_SLATCH_CAS64Fv + 0x33C 
  [3] 0x09000000027989A4 
sqlbBlockAreaErrorUnchain__FP20SQLB_BLOCK_VICTIM_CBUiP11SQLB_pfM 
isc 
+ 0x10 
  [4] 0x0900000002798888 
sqlbBlockAreaErrorHandler__FiP20SQLB_BLOCK_VICTIM_CBUiPcP16SQLB_ 
OBJECT_DESCP11SQLB_pfMisc 
+ 0x24C 
  [5] 0x0900000003308260 
sqlbProcessRange__FP16SQLB_OBJECT_DESCUiT2P11SQLB_pfMisc + 0x50C 
  [6] 0x0900000005A62E00 
.sqlbServiceRangeRequest__FP11SQLB_pfMisc_fdprpro_clone_263 + 
0x11C 
  [7] 0x09000000036B58BC sqlbPFPrefetcherEntryPoint__FPcUi + 
0x6C 
  [8] 0x09000000035FB668 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270 
  [9] 0x09000000035F9AF0 @49@sqloRunGDS__Fv + 0xDC 
 
Trap file shows the following function stack trace 
 
</Siginfo_t> 
Signal #36 (SIGPRE): si_code is 0 (SI_USER:Sent by kill, 
sigsend, raise.) si_pid is 2302062, si_uid is 18, si_value is 
00000000 
</SignalDetails> 
 
0x09000000033F7200 sqloDumpEDU + 0x14 
0x090000000275546C sqle_panic__Fv + 0x34 
0x090000000305FEC8 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7 
+ 0x2A0 
0x090000000305FB44 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7@glueA3 
+ 0x98 
0x0900000002F0A308 releaseConflictComplex__17SQLO_SLATCH_CAS64Fv 
+ 0x33C 
0x09000000027989A4 
sqlbBlockAreaErrorUnchain__FP20SQLB_BLOCK_VICTIM_CBUiP11SQLB_pfM 
isc 
+ 0x10 
0x0900000002798888 
sqlbBlockAreaErrorHandler__FiP20SQLB_BLOCK_VICTIM_CBUiPcP16SQLB_ 
OBJECT_DESCP11SQLB_pfMisc 
+ 0x24C 
0x0900000003308260 
sqlbProcessRange__FP16SQLB_OBJECT_DESCUiT2P11SQLB_pfMisc + 0x50C 
0x0900000005A62E00 
.sqlbServiceRangeRequest__FP11SQLB_pfMisc_fdprpro_clone_263 + 
0x11C 
0x09000000036B58BC sqlbPFPrefetcherEntryPoint__FPcUi + 0x6C 
 
<LatchInformation> 
Holding Latch type: 
(SQLO_LT_SQLB_HASH_BUCKET_GROUP_HEADER__groupLatch) - Address: 
(780000245873d00), Line: 2802, File: sqlbpfchr.C 
Holding Latch type: (SQLO_LT_SQLD_TCB__datExist) - Address: 
(7800002a1ff28f0), Line: 7786, File: sqldtcb.C 
</LatchInformation>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V9.1 FixPack 10 or below.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Instance panics and crashes with the following message in    * 
* the                                                          * 
* db2diag.log                                                  * 
*                                                              * 
* 2010-07-27-12.25.44.623481+120 E58407708A2265    LEVEL:      * 
* Severe                                                       * 
* (OS)                                                         * 
* PID    : 2302062              TID  : 1          PROC :       * 
* db2pfchr 1                                                   * 
* INSTANCE: dwhprod              NODE : 001                    * 
* FUNCTION: DB2 UDB, SQO Latch Tracing,                        * 
* SQLO_SLATCH_CAS64::releaseConflictComple, probe:330          * 
* MESSAGE :                                                    * 
* ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD    * 
*           "expected latch to be held."                       * 
* CALLED  : OS, -, unspecified_system_function                 * 
* DATA #1 : String, 39 bytes                                   * 
* Attempting to unlock an invalid latch:                       * 
* DATA #2 : File name, 16 bytes                                * 
* sqloLatchCAS64.C                                             * 
* DATA #3 : Source file line number, 8 bytes                   * 
* 980                                                          * 
* DATA #4 : Codepath, 8 bytes                                  * 
* 4                                                            * 
* DATA #5 : String, 125 bytes                                  * 
* 0x0000000000000000: {                                        * 
*   held X: 0                                                  * 
*   reserved for X: 0                                          * 
*   shared holders: 0                                          * 
*   firstSharIndex: 0x0                                        * 
*   firstExclIndex: 0x0                                        * 
* }                                                            * 
* DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes             * 
* 0x0 (invalid mode)                                           * 
* DATA #7 : String, 394 bytes                                  * 
* {                                                            * 
*   state        = 0x0000000000000000                          * 
*                 = {                                          * 
*                       held X: 0                              * 
*                       reserved for X: 0                      * 
*                       shared holders: 0                      * 
*                       firstSharIndex: 0x0                    * 
*                       firstExclIndex: 0x0                    * 
*                   }                                          * 
*   starve X mode = true                                       * 
*   xWaitCount    = 0                                          * 
*   requestCount  = 0                                          * 
*   identity      = SQLB_BPD::bpdLatch (38)                    * 
* }                                                            * 
* DATA #8 : Hexdump, 16 bytes                                  * 
* 0x0780000222E869D0 : 0002 2600 0001 0000 0026 0001 0000 0000 * 
* ..&......&......                                             * 
* CALLSTCK:                                                    * 
*   [0] 0x090000000305FEC0                                     * 
* dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3C * 
* iT1T                                                         * 
* 3T7                                                          * 
* + 0x298                                                      * 
*   [1] 0x090000000305FB44                                     * 
* dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3C * 
* iT1T                                                         * 
* 3T7@glueA3                                                   * 
* + 0x98                                                       * 
*   [2] 0x0900000002F0A308                                     * 
* releaseConflictComplex__17SQLO_SLATCH_CAS64Fv + 0x33C        * 
*   [3] 0x09000000027989A4                                     * 
* sqlbBlockAreaErrorUnchain__FP20SQLB_BLOCK_VICTIM_CBUiP11SQLB * 
* _pfM                                                         * 
* isc                                                          * 
* + 0x10                                                       * 
*   [4] 0x0900000002798888                                     * 
* sqlbBlockAreaErrorHandler__FiP20SQLB_BLOCK_VICTIM_CBUiPcP16S * 
* QLB_                                                         * 
* OBJECT_DESCP11SQLB_pfMisc                                    * 
* + 0x24C                                                      * 
*   [5] 0x0900000003308260                                     * 
* sqlbProcessRange__FP16SQLB_OBJECT_DESCUiT2P11SQLB_pfMisc +   * 
* 0x50C                                                        * 
*   [6] 0x0900000005A62E00                                     * 
* .sqlbServiceRangeRequest__FP11SQLB_pfMisc_fdprpro_clone_263  * 
* +                                                            * 
* 0x11C                                                        * 
*   [7] 0x09000000036B58BC sqlbPFPrefetcherEntryPoint__FPcUi + * 
* 0x6C                                                         * 
*   [8] 0x09000000035FB668                                     * 
* sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270       * 
*   [9] 0x09000000035F9AF0 @49@sqloRunGDS__Fv + 0xDC           * 
*                                                              * 
* Trap file shows the following function stack trace           * 
*                                                              * 
* </Siginfo_t>                                                 * 
* Signal #36 (SIGPRE): si_code is 0 (SI_USER:Sent by kill,     * 
* sigsend, raise.) si_pid is 2302062, si_uid is 18, si_value   * 
* is                                                           * 
* 00000000                                                     * 
* </SignalDetails>                                             * 
*                                                              * 
* 0x09000000033F7200 sqloDumpEDU + 0x14                        * 
* 0x090000000275546C sqle_panic__Fv + 0x34                     * 
* 0x090000000305FEC8                                           * 
* dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3C * 
* iT1T                                                         * 
* 3T7                                                          * 
* + 0x2A0                                                      * 
* 0x090000000305FB44                                           * 
* dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3C * 
* iT1T                                                         * 
* 3T7@glueA3                                                   * 
* + 0x98                                                       * 
* 0x0900000002F0A308                                           * 
* releaseConflictComplex__17SQLO_SLATCH_CAS64Fv                * 
* + 0x33C                                                      * 
* 0x09000000027989A4                                           * 
* sqlbBlockAreaErrorUnchain__FP20SQLB_BLOCK_VICTIM_CBUiP11SQLB * 
* _pfM                                                         * 
* isc                                                          * 
* + 0x10                                                       * 
* 0x0900000002798888                                           * 
* sqlbBlockAreaErrorHandler__FiP20SQLB_BLOCK_VICTIM_CBUiPcP16S * 
* QLB_                                                         * 
* OBJECT_DESCP11SQLB_pfMisc                                    * 
* + 0x24C                                                      * 
* 0x0900000003308260                                           * 
* sqlbProcessRange__FP16SQLB_OBJECT_DESCUiT2P11SQLB_pfMisc +   * 
* 0x50C                                                        * 
* 0x0900000005A62E00                                           * 
* .sqlbServiceRangeRequest__FP11SQLB_pfMisc_fdprpro_clone_263  * 
* +                                                            * 
* 0x11C                                                        * 
* 0x09000000036B58BC sqlbPFPrefetcherEntryPoint__FPcUi + 0x6C  * 
*                                                              * 
* <LatchInformation>                                           * 
* Holding Latch type:                                          * 
* (SQLO_LT_SQLB_HASH_BUCKET_GROUP_HEADER__groupLatch) -        * 
* Address:                                                     * 
* (780000245873d00), Line: 2802, File: sqlbpfchr.C             * 
* Holding Latch type: (SQLO_LT_SQLD_TCB__datExist) - Address:  * 
* (7800002a1ff28f0), Line: 7786, File: sqldtcb.C               * 
* </LatchInformation>                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.1 FixPack 11 or higher                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem first fixed in DB2 V9.1 FixPack 11
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC71476 IC71477 IC71478 IC74158 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.09.2010
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.11 FixList