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

USING SOURCEUSEREXIT WHEN LOADING WILL LEAK FILE DESCRIPTOR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When using a load with 'sourceuserexit', DB2 might end up 
leaking file descriptors because 
it 'unlink' the named pipe used to read data from the 
'sourceuserexit' program without 
closing it first. 
Finally it reaches the limit for opened file descriptors and 
start putting follwing 
OS error messages in the db2diag.log. 
 
db2diag.log : 
---------------------------------------------------------------- 
------------------------------------- 
 
2011-02-06-11.28.37.848709-300 I4048694A573       LEVEL: Error 
PID     : 201224               TID  : 32003       PROC : db2sysc 
1 
INSTANCE: xxxxxxxx             NODE : 001         DB   : 
xxxxxxxx 
APPHDL  : 1-45212              APPID: *N1.xxxxxxxx.110206162803 
AUTHID  : LOADPROD 
EDUID   : 32003                EDUNAME: db2agntp (xxxxxxxx) 1 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 
DATA #1 : String, 144 bytes 
LOADID: 4208.2011-02-06-11.28.06.289044.1 (70;1578) 
Reading db2nodes because of error  , -2062614522, 0, Detected in 
file:sqluSocket.C, Line:615 
 
2011-02-06-11.28.37.854981-300 E4049268A987       LEVEL: Error 
(OS) 
PID     : 201224               TID  : 32003       PROC : db2sysc 
1 
INSTANCE: xxxxxxxx             NODE : 001         DB   : 
xxxxxxxx 
APPHDL  : 1-45212              APPID: *N1.xxxxxxxx.110206162803 
AUTHID  : LOADPROD 
EDUID   : 32003                EDUNAME: db2agntp (xxxxxxxx) 1 
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 
MESSAGE : ZRC=0x850F0006=-2062614522=SQLO_FHNL "TOO MANY OPEN 
FILES" 
          DIA8306C Too many files were opened. 
CALLED  : OS, -, open 
OSERR   : EMFILE (24) "Too many open files" 
DATA #1 : Codepath, 8 bytes 
4:12:18:20:23:24:37 
DATA #2 : File name, 33 bytes 
/db2home/xxxxxxxx/sqllib/db2systm 
DATA #3 : Bitmask, 4 bytes 
0x00000354 
DATA #4 : Hex integer, 4 bytes 
0x000001A0 
DATA #5 : signed integer, 4 bytes 
0 
DATA #6 : signed integer, 4 bytes 
0 
DATA #7 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
2011-02-06-11.28.37.861916-300 I4050256A2203      LEVEL: Error 
(OS) 
PID     : 201224               TID  : 32003       PROC : db2sysc 
1 
INSTANCE: xxxxxxxx             NODE : 001         DB   : 
xxxxxxxx 
APPHDL  : 1-45212              APPID: *N1.xxxxxxxx.110206162803 
AUTHID  : LOADPROD 
EDUID   : 32003                EDUNAME: db2agntp (xxxxxxxx) 1 
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100 
CALLED  : OS, -, open 
OSERR   : EMFILE (24) "Too many open files" 
DATA #1 : String, 140 bytes 
A total of 3 analysis will be performed : 
 - User info 
 - ulimit info 
 - Target file info 
 
 Target file = /db2home/xxxxxxxx/sqllib/db2systm 
DATA #2 : String, 190 bytes 
  Real user ID of current process       = 46602 
  Effective user ID of current process  = 46602 
  Real group ID of current process      = 6548 
APPHDL  : 1-45212              APPID: *N1.xxxxxxxx.110206162803 
AUTHID  : LOADPROD 
EDUID   : 32003                EDUNAME: db2agntp (xxxxxxxx) 1 
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100 
CALLED  : OS, -, open 
OSERR   : EMFILE (24) "Too many open files" 
DATA #1 : String, 140 bytes 
A total of 3 analysis will be performed : 
 - User info 
 - ulimit info 
 - Target file info 
 
 Target file = /db2home/xxxxxxxx/sqllib/db2systm 
DATA #2 : String, 190 bytes 
  Real user ID of current process       = 46602 
  Effective user ID of current process  = 46602 
  Real group ID of current process      = 6548 
  Effective group ID of current process = 6548 
DATA #3 : String, 381 bytes 
Current process limits (unit in bytes except for nofiles) : 
  mem     (S/H) = unlimited / unlimited 
  core    (S/H) = 8589934590 / 8589934590 
  cpu     (S/H) = unlimited / unlimited 
  data    (S/H) = unlimited / unlimited 
  fsize   (S/H) = unlimited / unlimited 
  nofiles (S/H) = unlimited / unlimited 
  stack   (S/H) = unlimited / unlimited 
  rss     (S/H) = unlimited / unlimited 
DATA #4 : String, 260 bytes 
Target File Information : 
  Size               = 4096 
  Link               = No 
  Reference path     = N/A 
  Type               = 0x8000
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When using a load with 'sourceuserexit', DB2 might end up    * 
* leaking file descriptors because                             * 
* it 'unlink' the named pipe used to read data from the        * 
* 'sourceuserexit' program without                             * 
* closing it first.                                            * 
* Finally it reaches the limit for opened file descriptors and * 
* start putting follwing                                       * 
* OS error messages in the db2diag.log.                        * 
*                                                              * 
* db2diag.log :                                                * 
* ------------------------------------------------------------ * 
* ----                                                         * 
* -------------------------------------                        * 
*                                                              * 
* 2011-02-06-11.28.37.848709-300 I4048694A573      LEVEL:      * 
* Error                                                        * 
* PID    : 201224              TID  : 32003      PROC :        * 
* db2sysc                                                      * 
* 1                                                            * 
* INSTANCE: xxxxxxxx            NODE : 001        DB  :        * 
* xxxxxxxx                                                     * 
* APPHDL  : 1-45212              APPID:                        * 
* *N1.xxxxxxxx.110206162803                                    * 
* AUTHID  : LOADPROD                                           * 
* EDUID  : 32003                EDUNAME: db2agntp (xxxxxxxx) 1 * 
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0   * 
* DATA #1 : String, 144 bytes                                  * 
* LOADID: 4208.2011-02-06-11.28.06.289044.1 (70;1578)          * 
* Reading db2nodes because of error  , -2062614522, 0,         * 
* Detected in                                                  * 
* file:sqluSocket.C, Line:615                                  * 
*                                                              * 
* 2011-02-06-11.28.37.854981-300 E4049268A987      LEVEL:      * 
* Error                                                        * 
* (OS)                                                         * 
* PID    : 201224              TID  : 32003      PROC :        * 
* db2sysc                                                      * 
* 1                                                            * 
* INSTANCE: xxxxxxxx            NODE : 001        DB  :        * 
* xxxxxxxx                                                     * 
* APPHDL  : 1-45212              APPID:                        * 
* *N1.xxxxxxxx.110206162803                                    * 
* AUTHID  : LOADPROD                                           * 
* EDUID  : 32003                EDUNAME: db2agntp (xxxxxxxx) 1 * 
* FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 * 
* MESSAGE : ZRC=0x850F0006=-2062614522=SQLO_FHNL "TOO MANY     * 
* OPEN                                                         * 
* FILES"                                                       * 
*           DIA8306C Too many files were opened.               * 
* CALLED  : OS, -, open                                        * 
* OSERR  : EMFILE (24) "Too many open files"                   * 
* DATA #1 : Codepath, 8 bytes                                  * 
* 4:12:18:20:23:24:37                                          * 
* DATA #2 : File name, 33 bytes                                * 
* /db2home/xxxxxxxx/sqllib/db2systm                            * 
* DATA #3 : Bitmask, 4 bytes                                   * 
* 0x00000354                                                   * 
* DATA #4 : Hex integer, 4 bytes                               * 
* 0x000001A0                                                   * 
* DATA #5 : signed integer, 4 bytes                            * 
* 0                                                            * 
* DATA #6 : signed integer, 4 bytes                            * 
* 0                                                            * 
* DATA #7 : String, 105 bytes                                  * 
* Search for ossError*Analysis probe point after this log      * 
* entry                                                        * 
* for further                                                  * 
* self-diagnosis of this problem.                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 6                               * 
****************************************************************
Local Fix:
avoid using sourceuserexit to load the data.
available fix packs:
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
First fixed in DB2 V9.7 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91874 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.10.2011
06.06.2012
06.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList