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

DB2 MAY HANG DUE TO LATCH ON SQLO_LT_SQLE_FEDFMP_APP_CB__FMPAPPL ATCH AFTER
-1131 AND -1042 ERRORS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 might experience a hung in which an agent is holding 
SQLO_LT_SQLE_FEDFMP_APP_CB__FMPAPPLATCH latch.  It can happen 
that other agents waiting on this latch will be holding crucial 
latches (example SQLO_LT_sqeLocalDatabase__dblatch or 
SQLO_LT_SQLP_TENTRY__tranEntryLatch) for database functioning, 
halting the whole system. 
 
The db2diag.log might show errors like: 
 
sqleFedFMPManager::disconnect, probe:30 
RETCODE : ZRC=0xFFFFFB95=-1131 
 
and 
 
sqleFedFMPManager::returnFmpToPool, probe:30 
RETCODE : ZRC=0xFFFFFBEE=-1042 
 
 
 
 
The following is an example of stacks of holder and waiter when 
this problem happens: 
 
EDU name     : db2agntdp (DW      ) 0 
EDU ID       : 348 
<LatchInformation> 
Holding Latch type: (SQLO_LT_SQLE_FEDFMP_APP_CB__fmpAppLatch) - 
Address: (0x200dfc4a8), Line: 481, File: sqle_fed_fmp.C 
HoldCount: 2 
</LatchInformation> 
0x00002AAAABF43973 sqloWaitEDUWaitPost + 0x0195 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABB58298 _ZN8sqeAgent14WaitAgentEventEPji + 0x0012 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABB7576B 
_ZN16sqeAgentServices14GetNextRequestEPjP8sqeAgent + 0x034d 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABB556DD _ZN8sqeAgent6RunEDUEv + 0x0443 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC2249C0 _ZN9sqzEDUObj9EDUDriverEv + 0x00a6 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC224917 _Z10sqlzRunEDUPcj + 0x0009 
 
 
EDU name     : db2agent (DW) 0 
EDU ID       : 313 
 
<LatchInformation> 
 
Waiting on latch type: (SQLO_LT_SQLE_FEDFMP_APP_CB__fmpAppLatch) 
- Address: (0x200dfc4a8), Line: 481, File: sqle_fed_fmp.C 
 
Holding Latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch) - 
Address: (0x2aaad4138268), Line: 748, File: 
/view/db2_v97fp4_linuxamd64_s110330/vbs/engn/include/sqlpi_inlin 
es.h HoldCount: 1 
Holding Latch type: (SQLO_LT_SQLP_SAVEPOINTS__spLatch) - 
Address: (0x2aaad4137d40), Line: 851, File: 
/view/db2_v97fp4_linuxamd64_s110330/vbs/engn/include/sqlpi_inlin 
es.h HoldCount: 1 
</LatchInformation> 
0x00002AAAAC8F27E5 
_ZN17sqleFedFMPManager14getFmpAppLatchEP18sqle_FedFMP_app_cbj + 
0x0063 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC8F24DB 
_ZN17sqleFedFMPManager14validateFedFmpEP18sqle_FedFMP_app_cbbP14 
sqlqg_Fmp_InfoP13sqlerFmpParmsP14sqlerFmpHandlePi + 0x006b 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC8F2027 
_ZN17sqleFedFMPManager14getFmpFromPoolEP13sqlerFmpParmsP14sqlqg_ 
Fmp_InfoP14sqlerFmpHandle + 0x0081 
  (/db2home/db2inst1/sqllib/lib64/libdb2e.so.1) 
 
 
A trace when the issue occurs might show the following: 
 
 
17170      | | | | sqlerFedInvokeFencedRoutine entry [eduid 7457 
eduname db2agent] 
17172       | | | | | sqleFedFMPManager::getFmpFromPool entry 
[eduid 7457 eduname db2agent] 
17174       | | | | | | sqleFedFMPManager::validateFedFmp entry 
[eduid 7457 eduname db2agent] 
17176       | | | | | | | sqleFedFMPManager::getFmpAppLatch 
entry [eduid 7457 eduname db2agent] 
17179       | | | | | | | sqleFedFMPManager::getFmpAppLatch exit 
17180       | | | | | | sqleFedFMPManager::validateFedFmp data 
[probe 1] 
17183       | | | | | | | sqleFedFMPManager::addLogRecord entry 
[eduid 7457 eduname db2agent] 
17185       | | | | | | | sqleFedFMPManager::addLogRecord exit 
17187       | | | | | | sqleFedFMPManager::validateFedFmp exit 
[rc = 1] 
17189       | | | | | sqleFedFMPManager::getFmpFromPool exit 
17191       | | | | | sqlerSendFmpStart entry [eduid 7457 
eduname db2agent] 
17227       | | | | | | sqlerRtnWriteFencedArgData entry [eduid 
7457 eduname db2agent] 
17232       | | | | | | sqlerRtnWriteFencedArgData exit 
17238       | | | | | sqlerSendFmpStart data [probe 42] 
17243       | | | | | sqlerSendFmpStart exit 
17247       | | | | | sqeAgent::AgentBreathingPoint entry [eduid 
7457 eduname db2agent] 
17249       | | | | | | sqeAgent::QueryInterrupt entry [eduid 
7457 eduname db2agent] 
17253       | | | | | | sqeAgent::QueryInterrupt data [probe 70] 
17255       | | | | | | sqeAgent::QueryInterrupt exit 
17257       | | | | | sqeAgent::AgentBreathingPoint exit [rc = 
1] 
17259       | | | | | sqlerInterruptFmp entry [eduid 7457 
eduname db2agent] 
17261       | | | | | | sqlerInterruptThreadedFmp entry [eduid 
7457 eduname db2agent] 
17264       | | | | | | | sqlerMasterThreadReq entry [eduid 7457 
eduname db2agent] 
17268       | | | | | | | sqlerMasterThreadReq exit [rc = 
0xFFFFFBEE = -1042] 
17270       | | | | | | sqlerInterruptThreadedFmp error [probe 
10] [ ZRC = 0xFFFFFBEE = -1042] 
17272       | | | | | | sqlerInterruptThreadedFmp exit [rc = 
0xFFFFFBEE = -1042] 
17274       | | | | | sqlerInterruptFmp exit [rc = 0xFFFFFBEE = 
-1042] 
17276       | | | | sqlerFedInvokeFencedRoutine error [probe 70] 
17281       | | | | sqlerFedInvokeFencedRoutine exit [rc = 
0xFFFFFBEE = -1042] 
17284       | | | sqlriFedInvokeInvoker exit [rc = 0x8012006D = 
-2146303891 = SQLR_CA_BUILT] 
 
 
Note that this might look similar to APAR IC83795, but with the 
fix for IC83795 this problem can still occur. 
 
This APAR only applies to Federated environments.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 and Fix Pack 7                    * 
****************************************************************
Local Fix:
available fix packs:
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 DB2 Version 9.7 and Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2012
20.10.2012
20.10.2012
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList