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

LOG FILE MAY GET ARCHIVED AT UNEXPECTED PATH DURING HADR FORCE TAKEOVER

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Redo phase after forced takover, may put log file at unexpected 
log chain. This can cause problem when old primary requests to 
rejoin HADR pair as a standby as it does not find log file at 
expected log chain. 
 
Here are messages dumped in new primary indication change in log 
chain for archiving logs. 
 
2012-09-27-18.11.12.048410+540 E7148849A462       LEVEL: Info 
PID     : 4653426              TID  : 4885        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 4885                 EDUNAME: db2logmgr (inst) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3180 
DATA #1 : <preformatted> 
Completed archive for log file S0010494.LOG to 
/db2/inst/log_archive/db2inst/inst/NODE0000/C0000039/ from 
/db2/inst/log_dir/NODE0000/. 
 
 
2012-09-27-18.11.17.321304+540 E7149687A462       LEVEL: Info 
PID     : 4653426              TID  : 4885        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 4885                 EDUNAME: db2logmgr (inst) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3180 
DATA #1 : <preformatted> 
Completed archive for log file S0010495.LOG to 
/db2/inst/log_archive/db2inst/inst/NODE0000/C4967295/ from 
/db2/inst/log_dir/NODE0000/. 
 
Now, when old primary tries to rejoin HADR, it fails to do so, 
as it can not find log file S0010495.log at expected location. 
 
 
2012-09-27-18.13.08.809540+540 I7156576A367       LEVEL: Warning 
PID     : 4653426              TID  : 5656        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 5656                 EDUNAME: db2lfr (inst) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, 
probe:5120 
MESSAGE : Return code for LFR opening file S0010495.LOG was 
-2146434659 
 
 
2012-09-27-18.13.08.809943+540 I7156944A481       LEVEL: Error 
PID     : 4653426              TID  : 16193       PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 16193                EDUNAME: db2hadrp (inst) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP, 
probe:20590 
MESSAGE : HADR primary database failed to read log pages for 
remote catchup. 
          sqlplfrScanNext returned rc = 0x860f000a, scanPages = 
0, scanFlagsOut 
          = 0x2 
 
2012-09-27-18.14.52.088747+540 I7161882A367       LEVEL: Warning 
PID     : 4653426              TID  : 5656        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 5656                 EDUNAME: db2lfr (inst) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, 
probe:5120 
MESSAGE : Return code for LFR opening file S0010495.LOG was 
-2146434659 
 
2012-09-27-18.14.52.088997+540 I7162250A481       LEVEL: Error 
PID     : 4653426              TID  : 16193       PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 16193                EDUNAME: db2hadrp (inst) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP, 
probe:20590 
MESSAGE : HADR primary database failed to read log pages for 
remote catchup. 
          sqlplfrScanNext returned rc = 0x860f000a, scanPages = 
0, scanFlagsOut 
          = 0x2
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users below Db2 v97fp8                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v97fp8                                        * 
****************************************************************
Local Fix:
Manually ship the missing log file at expected location.
available fix packs:
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
Issues fixed in DB2 v97fp8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.11.2012
05.04.2013
05.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList