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

INSTANCE HUNG AT FUNCTION SQMFASTWRITERQUEUEMGR::ALLOCFASTWRITER RECORDS
WHEN LOCKING EVENT MONITORS ARE ENABLE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When a locking event monitor is active and activity collection 
is enabled for deadlock, lock timeout or lock wait events, 
agents generating locking records may block waiting for records 
while holding latches sqlrr_curr_activity_cb_latch or 
sqlrr_past_activity_cb_latch.  This can result in a hang as the 
fast writers (which release records for reuse) end up waiting on 
those latches.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users that use locking event monitors                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* 1) The majority of EDUs (including the PMODEL ones) are      * 
* waiting for (SQLO_LT_sqeAppServices__m_appServLatch) -       * 
* Address: (c0000000246d04d8). The holder is doing an index    * 
* scan, and it is waiting for                                  * 
* (SQLO_LT_sqlrr_past_activity_cb__sqlrr_past_activity_cb_latc * 
* h) - Address: (c00000005f4653c8).                            * 
*                                                              * 
* EDU name     : db2agent (SB27069)                            * 
* EDU ID       : 590                                           * 
*                                                              * 
* (5)  0xc000000000419a70  nanosleep_sys                       * 
* (6)  0xc000000000429950  nanosleep                           * 
* (7)  0xc000000017dafab0  sqloSpinLockConflict                * 
* (8)  0xc00000001d2948a0  sqlplDumpLockTimeoutInfo            * 
* (9)  0xc000000017cfb9b0  sqlplnfd                            * 
* (10) 0xc000000017825910  sqlplrqWithAttr                     * 
* (11) 0xc00000001f39ca20  sqliLockUncond                      * 
* (12) 0xc000000017797f10  sqliLockRec2                        * 
* (13) 0xc00000001733c850  sqliProcLeafNotNorm                 * 
* (14) 0xc00000001781fad0  sqlischf                            * 
* (15) 0xc0000000177e54d0  sqliFirstTreeSearch                 * 
* (16) 0xc000000017bca120  sqlirdk                             * 
* (17) 0xc000000017d88320  sqldIndexFetch                      * 
* (18) 0xc00000001799bd50  sqldRowFetch                        * 
* (19) 0xc000000017999d10  sqlritaSimplePerm                   * 
*                                                              * 
* Waiting on latch type:                                       * 
* (SQLO_LT_sqlrr_past_activity_cb__sqlrr_past_activity_cb_latc * 
* h) - Address: (c00000005f4653c8), Line: 1615, File:          * 
* sqlpldwi.C                                                   * 
* Holding Latch type: (SQLO_LT_SQLP_LHSH__xhshlatch) -         * 
* Address: (c0000000818788c8), Line: 550, File:                * 
* /view/db2_v97fp5_hpipf64_s110814/vbs/engn/sqp/inc/sqlpLockIn * 
* ternal.h HoldCount: 1                                        * 
* Holding Latch type: (SQLO_LT_sqeAppServices__m_appServLatch) * 
* - Address: (c0000000246d04d8), Line: 1366, File: sqlpldwi.C  * 
* HoldCount: 1                                                 * 
* Holding Latch type: (SQLO_LT_sqeApplication__masterAppLatch) * 
* - Address: (c00000005f4601c4), Line: 1383, File: sqlpldwi.C  * 
* HoldCount: 1                                                 * 
*                                                              * 
* =====                                                        * 
*                                                              * 
* 2) The holder of                                             * 
* (SQLO_LT_sqlrr_past_activity_cb__sqlrr_past_activity_cb_latc * 
* h) - Address: (c00000005f4653c8) is another index scan. This * 
* EDU is waiting for fast writer records but none are          * 
* available and so it blocks on a waitpost (which will be      * 
* posted by a fast writer when it returns records back to the  * 
* fast writer record pool):                                    * 
*                                                              * 
* EDU name     : db2agent (SB27069)                            * 
* EDU ID       : 121                                           * 
*                                                              * 
* // looks like waiting for fast writers                       * 
* (5)  0xc00000000041ac70  semtimedop_sys                      * 
* (6)  0xc00000000042c7c0  semtimedop                          * 
* (7)  0xc0000000172f49f0  sqloWaitEDUWaitPost                 * 
* (8)  0xc00000001abe7ad0                                      * 
* sqmLockEvents::collectRequestorActivities                    * 
* (9)  0xc000000017e4ba20  sqmLockEvents::collectLockEvent     * 
* (10) 0xc000000017df0580  sqlplfnd                            * 
* (11) 0xc000000017a46f10  sqlplrq                             * 
* (12) 0xc00000001f39c660  sqliLockUncond                      * 
* (13) 0xc000000017dc7f40  sqliScanLeaf2                       * 
* (14) 0xc0000000178099b0  sqlifnxt                            * 
* (15) 0xc000000017bc94f0  sqlirdk                             * 
* (16) 0xc000000017d88320  sqldIndexFetch                      * 
* (17) 0xc00000001799bd50  sqldRowFetchP8                      * 
* (18) 0xc000000017999d10  sqlritaSimplePerm                   * 
*                                                              * 
* Holding Latch type:                                          * 
* (SQLO_LT_sqlrr_past_activity_cb__sqlrr_past_activity_cb_latc * 
* h) - Address: (c00000005f4653c8), Line: 1262, File:          * 
* sqlm_lock_events.C HoldCount: 1                              * 
*                                                              * 
* =====                                                        * 
*                                                              * 
* 3) This instance has five fast writers.  The first four have * 
* the same stack, but the fifth one is diffent. In fact, the   * 
* first four are waiting for the fifth one which is waiting on * 
* a SQLO_LT_SQLP_LHSH__xhshlatch:                              * 
*                                                              * 
* EDU name     : db2fw0 (SB27069)                              * 
* EDU ID       : 52                                            * 
*                                                              * 
* EDU name     : db2fw1 (SB27069)                              * 
* EDU ID       : 59                                            * 
*                                                              * 
* EDU name     : db2fw2 (SB27069)                              * 
* EDU ID       : 56                                            * 
*                                                              * 
* EDU name     : db2fw3 (SB27069)                              * 
* EDU ID       : 55                                            * 
*                                                              * 
* (5)  0xc00000000041abf0  semop_sys                           * 
* (6)  0xc00000000042c560  semop                               * 
* (7)  0xc000000017d982d0                                      * 
* SQLO_SLATCH_CAS::getConflictComplexEm                        * 
* (8)  0xc000000017e839c0  SQLO_SLATCH_CAS64::getConflictEm    * 
* (9)  0xc0000000179a6000  sqloltch_notrack                    * 
* (10) 0xc000000017e2f040  sqlbVerifyAndLatchPage              * 
* (11) 0xc000000017b01c40  sqlbfix                             * 
* (12) 0xc000000017e20020  sqldGetPageForAppend                * 
* (13) 0xc00000001783b250  sqldInsertRow                       * 
* (14) 0xc00000001789d3e0  sqldRowInsert                       * 
* (15) 0xc000000017810ed0  sqlrinsr                            * 
* (16) 0xc00000001aae0f00  sqmRecordTypeArray::processRecord   * 
*                                                              * 
* EDU name     : db2fw4 (SB27069)                              * 
* EDU ID       : 57                                            * 
*                                                              * 
* (5)  0xc000000000419a70  nanosleep_sys                       * 
* (6)  0xc000000000429950  nanosleep                           * 
* (7)  0xc000000017dafab0  sqloSpinLockConflict                * 
* (8)  0xc000000017a45380  sqlplrq                             * 
* (9)  0xc0000000197b5830  sqldFindSlotOnPage                  * 
* (10) 0xc000000017e209c0  sqldFindAndLockSlotIfSpaceAvail     * 
* (11) 0xc000000017e1f6d0  sqldGetPageForAppend                * 
* (12) 0xc00000001783b250  sqldInsertRow                       * 
* (13) 0xc00000001789d3e0  sqldRowInsert                       * 
* (14) 0xc000000017810ed0  sqlrinsr                            * 
* (15) 0xc00000001aae0f00  sqmRecordTypeArray::processRecord   * 
*                                                              * 
* Waiting on latch type: (SQLO_LT_SQLP_LHSH__xhshlatch) -      * 
* Address: (c0000000818788c8), Line: 505, File:                * 
* /view/db2_v97fp5_hpipf64_s110814/vbs/engn/sqp/inc/sqlpLockIn * 
* ternal.h                                                     * 
*                                                              * 
* =====                                                        * 
*                                                              * 
* 4) The holder of the SQLO_LT_SQLP_LHSH__xhshlatch - Address: * 
* (c0000000818788c8) - is waiting for                          * 
* (SQLO_LT_sqlrr_past_activity_cb__sqlrr_past_activity_cb_latc * 
* h) - Address: (c00000005f4653c8), which is being held by the * 
* EDU described in step 1). So, 1) wants something that 4)     * 
* has, and 4) is waiting for something owned by 1). DEADLATCH! * 
*                                                              * 
* EDU name     : db2agent (SB27069)                            * 
* EDU ID       : 590                                           * 
*                                                              * 
* (5)  0xc000000000419a70  nanosleep_sys                       * 
* (6)  0xc000000000429950  nanosleep                           * 
* (7)  0xc000000017dafab0  sqloSpinLockConflict                * 
* (8)  0xc00000001d2948a0  sqlplDumpLockTimeoutInfo            * 
* (9)  0xc000000017cfb9b0  sqlplnfd                            * 
* (10) 0xc000000017825910  sqlplrqWithAttr                     * 
* (11) 0xc00000001f39ca20  sqliLockUncond                      * 
* (12) 0xc000000017797f10  sqliLockRec2                        * 
* (13) 0xc00000001733c850  sqliProcLeafNotNorm                 * 
* (14) 0xc00000001781fad0  sqlischf                            * 
* (15) 0xc0000000177e54d0  sqliFirstTreeSearch                 * 
* (16) 0xc000000017bca120  sqlirdk                             * 
* (17) 0xc000000017d88320  sqldIndexFetch                      * 
* (18) 0xc00000001799bd50  sqldRowFetch                        * 
* (19) 0xc000000017999d10  sqlritaSimplePerm                   * 
*                                                              * 
* Waiting on latch type:                                       * 
* (SQLO_LT_sqlrr_past_activity_cb__sqlrr_past_activity_cb_latc * 
* h) - Address: (c00000005f4653c8), Line: 1615, File:          * 
* sqlpldwi.C                                                   * 
* Holding Latch type: (SQLO_LT_SQLP_LHSH__xhshlatch) -         * 
* Address: (c0000000818788c8), Line: 550, File:                * 
* /view/db2_v97fp5_hpipf64_s110814/vbs/engn/sqp/inc/sqlpLockIn * 
* ternal.h HoldCount: 1                                        * 
* Holding Latch type: (SQLO_LT_sqeAppServices__m_appServLatch) * 
* - Address: (c0000000246d04d8), Line: 1366, File: sqlpldwi.C  * 
* HoldCount: 1                                                 * 
* Holding Latch type: (SQLO_LT_sqeApplication__masterAppLatch) * 
* - Address: (c00000005f4601c4), Line: 1383, File: sqlpldwi.C  * 
* HoldCount: 1                                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 5                            * 
****************************************************************
Local Fix:
For deadlock collection use the DEADLOCKS WITH DETAILS event 
monitor rather than the LOCKING event monitor.  For lock timeout 
collection set the DB2_CAPTURE_LOCKTIMEOUT registry variable to 
ON to generate a report file about lock timeouts rather than the 
LOCKING event monitor.
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.08.2011
21.12.2011
09.08.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList