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

EMFILE error due to a file handle leak may happen and can cause DBMarkedBad
error

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The customer got database marked bad error because DB2 could not 
drop a temporary file due to EMFILE error at a file open. 
EMFILE error was caused by opening /var/db2/global.reg file. 
When db2sysc attempted to access global registry file, it could 
open it but got the following error.  When db2 gets this error, 
it does not close the opened file descriptor and a file handle 
leak occurs.  When this error happens repeatedly, it results in 
EMFILE error. 
 
From db2diag.log, 
2010-06-30-09.00.58.626926+540 I3582A1357         LEVEL: Error 
PID     : 454956               TID  : 6099        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 3-44174              APPID: *N3.db2inst1.100707013023 
AUTHID  : db2inst1 
EDUID   : 6099                 EDUNAME: db2agntp (SAMPLE) 99 
FUNCTION: DB2 Common, Generic Registry, GenRegFile::OpenScan, 
probe:20 
MESSAGE : 
ECF=0x900001BF=-1879047745=ECF_GENREG_OPEN_INPUT_FILE_FAILED 
          Failed to open the input registry 
CALLED  : OS, -, fopen 
RETCODE : ECF=0x9000002D=-1879048147=ECF_FILE_PROCESS_MAX 
          The maximum number of file per process has already 
been reached 
DATA #1 : String, 19 bytes 
/var/db2/global.reg 
CALLSTCK: 
  [0] 0x0900000002FEAEFC pdOSSeLoggingCallback + 0x34 
  [1] 0x0900000000624424 oss_log__FP9OSSLogFacUiN32UlN26iPPc + 
0x1C4 
  [2] 0x0900000000624810 ossLogRC + 0xD0 
  [3] 0x09000000010CEF6C OpenScan__10GenRegFileFv + 0x3CC 
  [4] 0x09000000010E928C ossOpenInstanceList__FPcPPvCb + 0x8C 
  [5] 0x0900000001811950 @71@EnvRegRefresh__FP12SEnvRegistry + 
0x2C4 
  [6] 0x0900000001811578 @71@EnvRegOpen__FPP12SEnvRegistry + 
0x84 
  [7] 0x09000000017A9160 @71@sqloPRegQueryDefaultValue__FiPcPCc 
+ 0xC 
  [8] 0x0900000001816420 @71@EnvGetDB2SysVar__FiPcUl + 0x110 
  [9] 0x0900000001811118 @71@EnvQueryDB2SystemVariables__Fv + 
0x80 
 
 
 
Then, you got the following using lsof. 
COMMAND    PID     USER   FD   TYPE             DEVICE 
SIZE/OFF                NODE NAME 
db2sysc 229436 db2inst1    3r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
... snip ... 
db2sysc 229436 db2inst1   22r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
db2sysc 229436 db2inst1   23r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
... snip ... 
db2sysc 229436 db2inst1  999r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
db2sysc 229436 db2inst1 1000r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
... snip ... 
db2sysc 229436 db2inst1 *484r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
db2sysc 229436 db2inst1 *485r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
db2sysc 229436 db2inst1 *486r  VREG               10,6 
  0 XXX /var (/dev/hd9var) 
 
 
This problem also caused instance crash with the following error 
in the db2diag.log. 
 
2010-07-01-05.31.23.892274+540 I23479979A1362     LEVEL: Severe 
 
PID     : 454956               TID  : 3503        PROC : db2sysc 
99 
INSTANCE: db2inst1             NODE : 099         DB   : SAMPLE 
 
APPHDL  : 3-19801              APPID: 
12.26.3.148.54848.100708075435 
AUTHID  : EDWETL 
 
EDUID   : 3503                 EDUNAME: db2agntp (SLSIYMS) 99 
 
FUNCTION: DB2 UDB, data management, sqldCriticalSectionEnd, 
probe:9323 
CALLED  : DB2 UDB, data management, sqldDropTable 
 
RETCODE : ZRC=0x85020087=-2063466361=SQLB_NO_HANDLES 
 
          "SqlbFileTbl out of file handles."
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A File handle will leak, if GenRegFile::OpenScan , probe:20  * 
* is recorded in db2diag.log                                   * 
*                                                              * 
* From db2diag.log,                                            * 
*                                                              * 
* 2010-06-30-09.00.58.626926+540 I3582A1357        LEVEL:Error * 
* PID    : 454956              TID  : 6099        PROC         * 
* :db2sysc 0                                                   * 
* INSTANCE: db2inst1            NODE : 000        DB  : SAMPLE * 
* APPHDL  : 3-44174                                            * 
* APPID:*N3.db2inst1.100707013023                              * 
* AUTHID  : db2inst1                                           * 
* EDUID  : 6099                EDUNAME: db2agntp (SLSIYMS) 99  * 
* FUNCTION: DB2 Common, Generic Registry,                      * 
* GenRegFile::OpenScan,probe:20                                * 
*                                                              * 
* MESSAGE :                                                    * 
* ECF=0x900001BF=-1879047745=ECF_GENREG_OPEN_INPUT_FILE_FAILED * 
*                                                              * 
* Failed to open the input registry                            * 
* CALLED  : OS, -, fopen                                       * 
* RETCODE : ECF=0x9000002D=-1879048147=ECF_FILE_PROCESS_MAX    * 
* The maximum number of file per process has already been      * 
* reached                                                      * 
* DATA #1 : String, 19 bytes                                   * 
* /var/db2/global.reg                                          * 
*                                                              * 
* CALLSTCK:                                                    * 
*                                                              * 
* [0] 0x0900000002FEAEFC pdOSSeLoggingCallback + 0x34          * 
* [1] 0x0900000000624424 oss_log__FP9OSSLogFacUiN32UlN26iPPc   * 
* + 0x1C4                                                      * 
* [2] 0x0900000000624810 ossLogRC + 0xD0                       * 
* [3] 0x09000000010CEF6C OpenScan__10GenRegFileFv + 0x3CC      * 
* [4] 0x09000000010E928C ossOpenInstanceList__FPcPPvCb + 0x8C  * 
* [5] 0x0900000001811950 @71@EnvRegRefresh__FP12SEnvRegistry   * 
* + 0x2C4                                                      * 
* [6] 0x0900000001811578 @71@EnvRegOpen__FPP12SEnvRegistry +   * 
* 0x84                                                         * 
* [7] 0x09000000017A9160@71@sqloPRegQueryDefaultValue__FiPcPCc * 
* + 0xC                                                        * 
* [8] 0x0900000001816420 @71@EnvGetDB2SysVar__FiPcUl + 0x110   * 
* [9] 0x0900000001811118 @71@EnvQueryDB2SystemVariables__Fv    * 
* + 0x80                                                       * 
*                                                              * 
* In this case, opened file descriptor was not closed.         * 
*                                                              * 
* Then, you got the following using lsof.                      * 
* COMMAND    PID    USER  FD  TYPE            DEVICE           * 
* SIZE/OFF                NODE NAME                            * 
* db2sysc 229436 db2inst1    3r  VREG              10,6        * 
* 0 XXX /var (/dev/hd9var)                                     * 
* ... snip ...                                                 * 
* db2sysc 229436 db2inst1  22r  VREG              10,6         * 
* 0 XXX /var (/dev/hd9var)                                     * 
* db2sysc 229436 db2inst1  23r  VREG              10,6         * 
* 0 XXX /var (/dev/hd9var)                                     * 
* ... snip ...                                                 * 
* db2sysc 229436 db2inst1  999r  VREG              10,6        * 
* 0 XXX /var (/dev/hd9var)                                     * 
* db2sysc 229436 db2inst1 1000r  VREG              10,6        * 
* 0 XXX /var (/dev/hd9var)                                     * 
* ... snip ...                                                 * 
* db2sysc 229436 db2inst1 *484r  VREG              10,6        * 
* 0 XXX /var (/dev/hd9var)                                     * 
* db2sysc 229436 db2inst1 *485r  VREG              10,6        * 
* 0 XXX /var (/dev/hd9var)                                     * 
* db2sysc 229436 db2inst1 *486r  VREG              10,6        * 
* 0 XXX /var (/dev/hd9var)                                     * 
*                                                              * 
* db2sysc was TOO MANY opened /var... files due to the         * 
* above(open was successful, but lock file was error.          * 
* if this case was occurred, opened file descriptor was not    * 
* closed)                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.5 fix pack 8.                   * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.5 FixPack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.10.2010
24.05.2011
24.05.2011
Problem solved at the following versions (IBM BugInfos)
9.5.,
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList