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

DB HUNG DURING CRASH RECOVERY DUE TO CORRUPTED/NOT FOUND HISTORY FILE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The following is the snippet of the symptom in db2diag.log: 
 
2010-08-10-10.40.22.084754-240 I108980421A590     LEVEL: Severe 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, oper system services, sqloNLCKInit, probe:100 
MESSAGE : ZRC=0x800F00AE=-2146500434=SQLO_NLCK_PATH_ERROR 
"Unknown" 
DATA #1 : String, 57 bytes 
/db1/xxxxx/dbdir/xxxxx/NODE0000/SQL00001/db2rhist.asc 
DATA #2 : unsigned integer, 4 bytes 
1 
 
2010-08-10-10.40.22.371333-240 E108981012A907     LEVEL: Error 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, probe:768 
MESSAGE : SQL2161N  A damaged recovery history file could not be 
fixed.  The specified action failed. 
DATA #1 : String, 60 bytes 
Error parsing history entry: invalid number of fields found. 
DATA #2 : String, 23 bytes 
Number of fields read: 
DATA #3 : signed integer, 4 bytes 
-1 
DATA #4 : String, 32 bytes 
Expected number of fields read: 
DATA #5 : signed integer, 4 bytes 
24 
DATA #6 : Dumped object of size 512 bytes at offset 0, 58 bytes 
/export/home/xxxxx/sqllib/db2dump/24331.160.000.dump.bin 
 
2010-08-10-10.40.22.376468-240 E108981920A586     LEVEL: Error 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, 
probe:1142 
MESSAGE : SQL2161N  A damaged recovery history file could not be 
fixed. The specified action failed. 
DATA #1 : <preformatted> 
Error reading history entry at file offset 1024. 
 
2010-08-10-10.40.22.377027-240 E108982507A560     LEVEL: Warning 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, 
probe:1147 
MESSAGE : ADM8500W  DB2 has failed to read from the history file 
because of a possible data corruption.  Ensure that the file 
exists and is intact. 
 
 
2010-08-10-10.40.22.378066-240 I108983068A687     LEVEL: Error 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, 
probe:1152 
MESSAGE : SQL2161N  A damaged recovery history file could not be 
fixed.  The specified action failed. 
 
DATA #1 : String, 18 bytes 
History File Entry 
DATA #2 : Dumped object of size 2107648 bytes at offset 632, 58 
bytes 
/export/home/xxxxx/sqllib/db2dump/24331.160.000.dump.bin 
 
2010-08-10-10.40.22.390635-240 I108983756A508     LEVEL: Error 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, database utilities, sqluhUpdate, probe:321 
MESSAGE : SQL2161N  A damaged recovery history file could not be 
fixed.  The specified action failed. 
 
 
2010-08-10-10.40.22.391330-240 I108984265A514     LEVEL: Error 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, database utilities, sqluhUpdateSingle, 
probe:663 
MESSAGE : SQL2161N  A damaged recovery history file could not be 
fixed.  The specified action failed. 
 
 
2010-08-10-10.40.22.391919-240 I108984780A555     LEVEL: Severe 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, data management, sqldCommitHistoryEntry, 
probe:10 
MESSAGE : Error commiting history entry, RC = -2161 
DATA #1 : Hexdump, 8 bytes 
0xFFFFFFFDBBDCFFAC : 0000 0000 0000 0000 
........ 
 
2010-08-10-10.40.22.392444-240 I108985336A635     LEVEL: Severe 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, data management, sqldmpnd, probe:189 
MESSAGE : Error executing pending list log record. Trace data: 
DATA #1 : Hexdump, 24 bytes 
0xFFFFFFFC48FF8F30 : FFFF F78F 0000 0DCF 0000 000B 0000 0041 
...............A 
0xFFFFFFFC48FF8F40 : 0000 0020 B857 D71B 
... .W.. 
 
2010-08-10-10.40.22.392940-240 I108985972A1455    LEVEL: Severe 
PID     : 24331                TID  : 160         PROC : db2sysc 
INSTANCE: xxxxx              NODE : 000         DB   : TESTDB 
APPHDL  : 0-7                  APPID: *LOCAL.xxxxx.100810144004 
AUTHID  : xxxxx 
EDUID   : 160                  EDUNAME: db2redom (TESTDB) 
FUNCTION: DB2 UDB, data management, sqldCriticalSectionEnd, 
probe:9298 
CALLED  : DB2 UDB, data management, sqldmpnd 
RETCODE : ZRC=0xFFFFF78F=-2161 
CALLSTCK: 
  [0] 0xFFFFFFFF77B43D98 
__1cIsqldmpnd6FpnIsqeAgent_ipcpnJSQdDLP_LSN8_pnPSQdDLD_RECOV_INF 
O__i_  + 0x1CD0 
  [1] 0xFFFFFFFF793EC930 __1cIsqlptppl6FpnIsqeAgent__i_ + 0x538 
  [2] 0xFFFFFFFF794A4FB0 
__1cKsqlpRFWppl6FpnIsqeAgent_pnJSQdDLP_DBCB_pnLSQdDLP_TENTRY_pnK 
SQdDLP_FRAPP_pnKSQdDLP_FRSCB_pnJSQdDLP_LSN8_I_i_  + 0x190 
  [3] 0xFFFFFFFF794A67BC 
__1cNsqlpRecDbRedo6FpnIsqeAgent_pnISQdDLP_ACB_pnJSQdDLP_DBCB_pnK 
SQdDLP_FRAPP_pnLSQdDLP_TENTRY_pnQSQdDLPR_LOGREC_DIS_pnKREDO_INP 
+ 0x12EC 
  [4] 0xFFFFFFFF794A84A0 
__1cPsqlprProcDPSrec6FpnKSQdDLPR_PRCB_IpnUSQdDLPR_PR_QdDUEUE_ENT 
RY__i_  + 0x2B8 
  [5] 0xFFFFFFFF794B0D6C 
__1cPsqlpPRecReadLog6FpnIsqeAgent_pnISQdDLP_ACB_pnJSQdDLP_DBCB__ 
i_ + 0x6EE4 
  [6] 0xFFFFFFFF7949A084 
__1cUsqlpParallelRecovery6FpnIsqeAgent_pnFsqlca__i_ + 0x904 
  [7] 0xFFFFFFFF77D417C0 
__1cbAsqleSubCoordProcessRequest6FpnIsqeAgent__v_ + 0xE8 
  [8] 0xFFFFFFFF77D757E0 __1cIsqeAgentGRunEDU6M_v_ + 0x708 
  [9] 0xFFFFFFFF7A7ED588 __1cKsqlzRunEDU6FpcI_v_ + 0xD0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If we are in crash recovery, and the sub-agents that are     * 
* doing the parallel recovery encounters a problem such as     * 
* corrupted or not-found history file, this could caused the   * 
* DB hung.                                                     * 
* The db2diag.log should mention about corrupted or not-found  * 
* history file. For more information, please see the "Error    * 
* Description" section above.                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 fp 3a                             * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 97 Fix Pack 3a
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.09.2010
04.11.2010
07.12.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)