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

ADM1552E ROLLFORWARD BACKWARD RECOVERY PHASE NOT USING OVERFLOW LOG PATH
SPECIFIED IN ROLLFOWARD COMMAND WHEN LOGSECOND = -1

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
During the backward phase of recovery rollfoward db2 is not 
looking in the overflow log path for log files 
 
This  message repeats every 5 minutes even though the logs are 
in the overflow log path specified 
 
 ADM1552E  DB2 is unable to open active logfile "......"  This 
          could be caused by problem in retrieving the log file 
from archive. 
          DB2 will try again every 5 minutes. 
 
 
Messages seen in db2diag.log file during rollforward 
 
2010-10-25-09.10.44.535533-300 I141182E401         LEVEL: Info 
PID     : 8457                  TID  : 47714544904512PROC : 
db2sysc 0 
INSTANCE: db2inst1         NODE : 000          DB   : SAMPLE 
EDUID   : 303                  EDUNAME: db2loggr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgPostLogMgrToRetrieve, probe:1050 
DATA #1 : <preformatted> 
RTStatus is in state 16 at index 0. 
 
2010-10-25-09.10.44.535753-300 I141584E178        LEVEL: Error 
PID:8457 TID:47714544904512 NODE:000 Title: SQLP_DBCB 
Dump File:/home/db2inst1/sqllib/db2dump/8457.303.000.dump.bin 
 
2010-10-25-09.10.44.536127-300 I141763E377         LEVEL: Error 
PID     : 8457                 TID  : 47714544904512PROC : 
db2sysc 0 
INSTANCE: db2inst1        NODE : 000          DB   : SAMPLE 
EDUID   : 303                 EDUNAME: db2loggr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgOpenCAL, 
probe:120 
MESSAGE : Retrieved failed with error -2146434659 
 
2010-10-25-09.10.44.536413-300 E142141E533         LEVEL: Error 
PID     : 8457                  TID  : 47714544904512PROC : 
db2sysc 0 
INSTANCE: db2inst1         NODE : 000          DB   : SAMPLE 
EDUID   : 303                  EDUNAME: db2loggr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgOpenCAL, 
probe:200 
MESSAGE : ADM1552E  DB2 is unable to open active log file 
"S0000309.LOG".  This 
          could be caused by problem in retrieving the log file 
from archive. 
          DB2 will try again every 5 minutes. 
 
 
This occurs during backward phase with logsecond set to -1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During the backward phase of recovery rollfoward db2 is not  * 
* looking in the overflow log path for log files               * 
*                                                              * 
*                                                              * 
*                                                              * 
* This  message repeats every 5 minutes even though the logs   * 
* are in the overflow log path specified                       * 
*                                                              * 
*                                                              * 
*                                                              * 
* ADM1552E  DB2 is unable to open active logfile "......"      * 
* This  could be caused by problem in retrieving the log file  * 
* from archive.                                                * 
*                                                              * 
*           DB2 will try again every 5 minutes.                * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* Messages seen in db2diag.log file during rollforward         * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2010-10-25-09.10.44.535533-300 I141182E401        LEVEL:     * 
* Info                                                         * 
* PID    : 8457                  TID  : 47714544904512PROC :   * 
*                                                              * 
* db2sysc 0                                                    * 
*                                                              * 
* INSTANCE: db2inst1        NODE : 000          DB  : SAMPLE   * 
*                                                              * 
* EDUID  : 303                  EDUNAME: db2loggr (SAMPLE) 0   * 
*                                                              * 
* FUNCTION: DB2 UDB, data protection services,                 * 
* sqlpgPostLogMgrToRetrieve, probe:1050                        * 
*                                                              * 
* DATA #1 : <preformatted>                                     * 
*                                                              * 
* RTStatus is in state 16 at index 0.                          * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2010-10-25-09.10.44.535753-300 I141584E178        LEVEL:     * 
* Error                                                        * 
* PID:8457 TID:47714544904512 NODE:000 Title: SQLP_DBCB        * 
*                                                              * 
* Dump                                                         * 
* File:/home/db2inst1/sqllib/db2dump/8457.303.000.dump.bin     * 
*                                                              * 
*                                                              * 
* 2010-10-25-09.10.44.536127-300 I141763E377        LEVEL:     * 
* Error                                                        * 
* PID    : 8457                TID  : 47714544904512PROC :     * 
* db2sysc 0                                                    * 
*                                                              * 
* INSTANCE: db2inst1        NODE : 000          DB  : SAMPLE   * 
*                                                              * 
* EDUID  : 303                EDUNAME: db2loggr (SAMPLE) 0     * 
*                                                              * 
* FUNCTION: DB2 UDB, data protection services, sqlpgOpenCAL,   * 
* probe:120                                                    * 
*                                                              * 
* MESSAGE : Retrieved failed with error -2146434659            * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2010-10-25-09.10.44.536413-300 E142141E533        LEVEL:     * 
* Error                                                        * 
* PID    : 8457                  TID  : 47714544904512PROC :   * 
*                                                              * 
* db2sysc 0                                                    * 
*                                                              * 
* INSTANCE: db2inst1        NODE : 000          DB  : SAMPLE   * 
*                                                              * 
* EDUID  : 303                  EDUNAME: db2loggr (SAMPLE) 0   * 
*                                                              * 
* FUNCTION: DB2 UDB, data protection services, sqlpgOpenCAL,   * 
* probe:200                                                    * 
*                                                              * 
* MESSAGE : ADM1552E  DB2 is unable to open active log file    * 
*                                                              * 
* "S0000309.LOG".  This   could be caused by problem in        * 
* retrieving the log file from archive.                        * 
*  DB2 will try again every 5 minutes.                         * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* This occurs during backward phase with logsecond set to -1   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 Fixpack 8                                    * 
****************************************************************
Local Fix:
Move logs to the active log directory
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
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 V9.5 Fixpack 8
Workaround
Copy log files into active log directory
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2010
15.07.2011
15.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList