home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC80745 Status: Closed

DB2LOGTS DAEMON ON HADR PRIMARY COULD BE BROUGHT DOWN DUE TO LOG INFO ARRAY
BEING OUT OF SYNC

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
On HADR primary, db2logts daemon on HADR primary could be 
brought down due to log info array being out of sync. 
The issue can be hit when following events happened: 
 
1. HADR standby restarts from last byte of a log file. When this 
event happens, we can see below message in db2diag.log: 
 
2011-12-13-18.09.58.511431+540 E920335A494        LEVEL: Warning 
PID     : 9699938              TID  : 71547       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
APPHDL  : 0-2523               APPID: *LOCAL.DB2.111213092048 
EDUID   : 71547                EDUNAME: db2shred (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:45320 
DATA #1 : <preformatted> 
Scan starting from the last byte of a truncated log file. Moving 
to next file.2130982527201 
 
2. Takeover happens on the standby, and it becomes the new 
primary. 
 
3. Transactions continue and new logs are generated on new 
primary. Finally, when log info array is full and DB2 trys to 
reuse one entry, the error will be hit, and following messages 
will appear in db2diag.log: 
 
2011-12-15-00.13.22.849529+540 I2986417A454       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:64 
MESSAGE : Extent number: 
DATA #1 : Hexdump, 4 bytes 
0x070000001EFFD460 : 0000 6E1E 
..n. 
 
2011-12-15-00.13.22.849903+540 I2986872A469       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:65 
MESSAGE : Entry number (readEntry): 
DATA #1 : Hexdump, 8 bytes 
0x07000008E0027228 : 0000 0000 0000 0034 
.......4 
 
2011-12-15-00.13.22.850071+540 I2987342A483       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:66 
MESSAGE : read entry extent number (readEntryExtNum): 
DATA #1 : Hexdump, 4 bytes 
0x07000008E0027230 : 0000 6D14 
..m. 
 
2011-12-15-00.13.22.850240+540 I2987826A1084      LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:67 
DATA #1 : String, 128 bytes 
The db2logts log info array is out of sync. 
Bringing down the db2logts daemon. 
From this point on, LOG SKIPPING is DISABLED. 
 
DATA #2 : Hexdump, 112 bytes 
0x07000008E0029BA0 : 0000 6D12 0000 0000 0000 0997 EAB2 8001 
..m............. 
0x07000008E0029BB0 : 0000 0000 0000 0000 0000 0016 0000 0000 
................ 
0x07000008E0029BC0 : 0000 0000 0000 0000 0000 0000 0165 0000 
.............e.. 
0x07000008E0029BD0 : 0700 000D 0650 AF80 0700 000D 0650 B1A0 
.....P.......P.. 
0x07000008E0029BE0 : 0700 000D 0650 B3C0 0700 000D 0650 B5E0 
.....P.......P.. 
0x07000008E0029BF0 : 0700 000D 0650 B800 0700 000D 0650 5460 
.....P.......PT` 
0x07000008E0029C00 : 0700 000D 0650 5680 0700 000D 0650 58A0 
.....PV......PX. 
 
2011-12-15-00.13.22.850416+540 I2988911A165       LEVEL: Severe 
PID:9699938 TID:5798 NODE:000 Title: SQLP_DBCB 
Dump File:/db2dump/db2inst1/9699938.5798.000.dump.bin 
 
2011-12-15-00.13.22.907328+540 I2989077A166       LEVEL: Severe 
PID:9699938 TID:5798 NODE:000 Title: SQLPG_XHDR 
Dump File:/db2dump/db2inst1/9699938.5798.000.dump.bin 
 
2011-12-15-00.13.22.907523+540 I2989244A375       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:0 
RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
Problem Summary:
On HADR primary, db2logts daemon on HADR primary could be 
brought down due to log info array being out of sync. 
The issue can be hit when following events happened: 
 
1. HADR standby restarts from last byte of a log file. When this 
event happens, we can see below message in db2diag.log: 
 
2011-12-13-18.09.58.511431+540 E920335A494        LEVEL: Warning 
PID     : 9699938              TID  : 71547       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
APPHDL  : 0-2523               APPID: *LOCAL.DB2.111213092048 
EDUID   : 71547                EDUNAME: db2shred (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:45320 
DATA #1 : <preformatted> 
Scan starting from the last byte of a truncated log file. Moving 
to next file.2130982527201 
 
2. Takeover happens on the standby, and it becomes the new 
primary. 
 
3. Transactions continue and new logs are generated on new 
primary. Finally, when log info array is full and DB2 trys to 
reuse one entry, the error will be hit, and following messages 
will appear in db2diag.log: 
 
2011-12-15-00.13.22.849529+540 I2986417A454       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:64 
MESSAGE : Extent number: 
DATA #1 : Hexdump, 4 bytes 
0x070000001EFFD460 : 0000 6E1E 
..n. 
 
2011-12-15-00.13.22.849903+540 I2986872A469       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:65 
MESSAGE : Entry number (readEntry): 
DATA #1 : Hexdump, 8 bytes 
0x07000008E0027228 : 0000 0000 0000 0034 
.......4 
 
2011-12-15-00.13.22.850071+540 I2987342A483       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:66 
MESSAGE : read entry extent number (readEntryExtNum): 
DATA #1 : Hexdump, 4 bytes 
0x07000008E0027230 : 0000 6D14 
..m. 
 
2011-12-15-00.13.22.850240+540 I2987826A1084      LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:67 
DATA #1 : String, 128 bytes 
The db2logts log info array is out of sync. 
Bringing down the db2logts daemon. 
From this point on, LOG SKIPPING is DISABLED. 
 
DATA #2 : Hexdump, 112 bytes 
0x07000008E0029BA0 : 0000 6D12 0000 0000 0000 0997 EAB2 8001 
..m............. 
0x07000008E0029BB0 : 0000 0000 0000 0000 0000 0016 0000 0000 
................ 
0x07000008E0029BC0 : 0000 0000 0000 0000 0000 0000 0165 0000 
.............e.. 
0x07000008E0029BD0 : 0700 000D 0650 AF80 0700 000D 0650 B1A0 
.....P.......P.. 
0x07000008E0029BE0 : 0700 000D 0650 B3C0 0700 000D 0650 B5E0 
.....P.......P.. 
0x07000008E0029BF0 : 0700 000D 0650 B800 0700 000D 0650 5460 
.....P.......PT` 
0x07000008E0029C00 : 0700 000D 0650 5680 0700 000D 0650 58A0 
.....PV......PX. 
 
2011-12-15-00.13.22.850416+540 I2988911A165       LEVEL: Severe 
PID:9699938 TID:5798 NODE:000 Title: SQLP_DBCB 
Dump File:/db2dump/db2inst1/9699938.5798.000.dump.bin 
 
2011-12-15-00.13.22.907328+540 I2989077A166       LEVEL: Severe 
PID:9699938 TID:5798 NODE:000 Title: SQLPG_XHDR 
Dump File:/db2dump/db2inst1/9699938.5798.000.dump.bin 
 
2011-12-15-00.13.22.907523+540 I2989244A375       LEVEL: Error 
PID     : 9699938              TID  : 5798        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 5798                 EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpInformLogTsAboutNewLogHeader, probe:0 
RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
Local Fix:
NA
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


Workaround


not known / see Local fix


BUG-Tracking


forerunner  : APAR is sysrouted TO one or more of the following: IC85207 
follow-up : 


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

10.01.2012
19.04.2013
19.04.2013


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


9.7.0.6

FixList