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

DATABASE CRASHED WHILE CLOSING THE TEMP FILE HANDLE DURING AN UNDO
OPERATION.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
During an UNDO operation, we hit a disk full condition on the 
temporary tablespace while trying to close a file handle. 
Subsequently, database was marked bad and came down afterward. 
 
Here's an example from the db2diag.log - 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Error 
(OS) 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : xxxxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, oper system services, sqlobufreset, probe:10 
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full." 
          DIA8312C Disk was full. 
CALLED  : OS, -, fsync                            OSERR: ENOSPC 
(28) 
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
0x0000002AA2BFB328 : 8A00 0000 8002 0000 
........ 
DATA #2 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Error 
(OS) 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : xxxxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100 
CALLED  : OS, -, fsync                            OSERR: ENOSPC 
(28) 
DATA #1 : String, 132 bytes 
A total of 4 analysis will be performed : 
 - User info 
 - ulimit info 
 - Target file info 
 - File system 
 
 Target file handle = 138 
DATA #2 : String, 190 bytes 
  Real user ID of current process       = xxxxx 
  Effective user ID of current process  = xxxxx 
  Real group ID of current process      = xxxx 
  Effective group ID of current process = xxxx 
DATA #3 : String, 362 bytes 
Current process limits (unit in bytes except for nofiles) : 
  mem     (S/H) = unlimited / unlimited 
  core    (S/H) = 0 / unlimited 
  cpu     (S/H) = unlimited / unlimited 
  data    (S/H) = unlimited / unlimited 
  fsize   (S/H) = unlimited / unlimited 
  nofiles (S/H) = 65534 / 65534 
  stack   (S/H) = 10485760 / unlimited 
  rss     (S/H) = unlimited / unlimited 
DATA #4 : String, 261 bytes 
Target File Information : 
  Size               = 16384 
  Link               = No 
  Reference path     = N/A 
  Type               = 0x8000 
  Permissions        = rw------- 
  UID                = xxxxx 
  GID                = xxxx 
  Last modified time = 1298765603 
DATA #5 : String, 432 bytes 
File System Information of the target file : 
  Block size        = 32768 bytes 
  Total size        = 402653184000 bytes 
  Free size         = 32768 bytes 
  Total # of inodes = 24802560 
  FS name           = xxxxxx:/xxx/xxxxxxxx/xxxxxxxxx 
  Mount point       = /x/xxxxxx/xxx/xxxxxxxx/xxxxxxxxxxxxxxx 
  FSID              = 27 
  FS type name      = nfs 
  DIO/CIO mount opt = None 
  Device type       = N/A 
  FS type           = 0x6969 
CALLSTCK: 
  [0] 0x0000002A9684F555 pdOSSeLoggingCallback + 0x91 
  [1] 0x0000002A9BB37C0B /xxx/.exec/x86_64.linux.2.6.glibc.2.3 
/lib64/libdb2osse.so.1 + 0x1AEC0B 
  [2] 0x0000002A9BB38FEB ossLogSysRC + 0xBF 
  [3] 0x0000002A9BB2C6E0 /xxx/.exec/x86_64.linux.2.6.glibc.2.3 
/lib64/libdb2osse.so.1 + 0x1A36E0 
  [4] 0x0000002A9BB2ACF1 ossErrorAnalysis + 0x25 
  [5] 0x0000002A97EBFAC4 sqloSystemErrorHandler + 0x6C0 
  [6] 0x0000002A96C2A3A7 sqlobufreset + 0xFB 
  [7] 0x0000002A968B2A94 sqlbWritePage + 0x1E0 
  [8] 0x0000002A98A3A187 _Z19sqlbGetPageFromDiskP11SQLB_FIX_CBi 
+ 0x173D 
  [9] 0x0000002A98A2B843 _Z7sqlbfixP11SQLB_FIX_CB + 0xB73 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : xxxxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbForceNewPagesToDisk, probe:1235 
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full." 
          DIA8312C Disk was full. 
 
[...] 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : xxxxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, buffer pool services, 
SqlbFhdlTbl::closeOneFile, probe:1000 
DATA #1 : String, 38 bytes 
 Obj={pool:15;obj:2;type:16} State=x45 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : xxxxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, buffer pool services, 
SqlbFhdlTbl::closeOneFile, probe:0 
DATA #1 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 72 bytes 
    Obj: {pool:15;obj:2;type:16} Parent={9;24} 
  lifeLSN:       01EA0C9C96B2 
  tid:           0 0  0 
  extentAnchor:                   0 
  initEmpPages:                   0 
  poolPage0:                      0 
  poolflags:                    111 
  objectState:                   45 
  lastSMP:                        0 
  pageSize:                   16384 
  extentSize:                    32 
  bufferPoolID:                   4 
  partialHash:            268566543 
  bufferPool:    0x0000002ace3a3800 
 
[...] 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : xxxxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, data management, sqldReorgCleanup, probe:10 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : xxxxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, data management, sqldmund, probe:719 
RETCODE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full." 
          DIA8312C Disk was full. 
 
[...] 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : x-xxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, data management, sqldmund, probe:719 
MESSAGE : Error during UNDO of LSN: 
DATA #1 : Hexdump, 6 bytes 
0x0000002AA2BFBE12 : 01EA 0C9C 96B2 
 
2011-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : x-xxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, data management, sqldmund, probe:719 
RETCODE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full." 
          DIA8312C Disk was full. 
 
2011-0x-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxxx       LEVEL: Severe 
PID     : xxxx                 TID  : xxxxxxxxxxxx PROC : 
db2sysc xx 
INSTANCE: db2inst1             NODE : 0xx          DB   : SAMPLE 
APPHDL  : x-xxxx               APPID: 
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx 
AUTHID  : xxxxx 
EDUID   : xxxxx                EDUNAME: db2agntp (SAMPLE) xx 
FUNCTION: DB2 UDB, data management, sqldmund, probe:719 
MESSAGE : Error during UNDO of log record: 
DATA #1 : Dumped object of size 5000 bytes at offset 0, 59 bytes 
/xxx/xxxxxx/xxxxxxxx/sqllib/db2dump/xxxx.xxxxx.xxx.dump.bin 
 
 
This APAR will prevent the database from being marked bad when 
we hit a disk full condition on a temporary tablespace during an 
UNDO operation.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users with insufficient TEMP disk space.                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5, Fixpack 9.                       * 
****************************************************************
Local Fix:
Be certain to have enough TEMP disk space to eliminate the 
possibility of hitting a 'disk full' condition.
available fix packs:
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
First fixed in DB2 Version 9.5, Fixpack 9.
Workaround
Be certain to have enough TEMP disk space to eliminate the 
possibility of hitting a 'disk full' condition.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC79958 IC84087 IC84653 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.05.2011
09.03.2012
09.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList