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

SQL0970N DURING RESTORE ... WITHOUT ROLLING FORWARD WHILE THE ORIGINAL
OVERFLOWLOGPATH IS INACCESSIBLE.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Restore may fail because of inaccessible OVERFLOWLOGPATH saved 
in the backup image, i.e. the OVERFLOGLOGPATH of the source 
database where the backup was taken. This can be caused for 
example by incorrect file access permissions or a non-existent 
directory path on the target system where the restore is being 
performed. Under such conditions the restore will fail with 
SQL0970N. A good eyecatcher is error -970 from "sqludProcessLFH, 
probe:1149" reported in the DB2 diagnostic log file. 
. 
Example: 
======== 
+ db2 restore database source continue 
SQL0970N  The system attempted to write to a read-only file. 
SQLSTATE=55009 
. 
db2diag.log: 
============ 
2009-11-10-13.47.43.502353-300 I9133A578       LEVEL: Error 
PID     : 4403420           TID  : 1801        PROC : db2sysc 
INSTANCE: db2inst1          NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7               APPID: *LOCAL.db2inst1.091110184735 
AUTHID  : DB2INST1 
EDUID   : 1801            EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, data protection services, 
          sqlpRemoveRetrievedLogFiles, probe:20 
RETCODE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied" 
          DIA8701C Access denied for resource "", operating 
          system return code was "". 
. 
2009-11-10-13.47.43.508938-300 E9712A551       LEVEL: Severe 
PID     : 4403420           TID  : 1801        PROC : db2sysc 
INSTANCE: db2inst1          NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7               APPID: *LOCAL.db2inst1.091110184735 
AUTHID  : DB2INST1 
EDUID   : 1801            EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, database utilities, 
          sqludProcessLFH, probe:1149 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
-970
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users performing redirected restores and having the          * 
* OVERFLOWLOGPATH set to an inaccessible path.                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Restore may fail because of inaccessible OVERFLOWLOGPATH     * 
* saved in the backup image, i.e. the OVERFLOGLOGPATH of the   * 
* sources database where the backup was taken. This can be     * 
* caused for example by incorrect file access permissions or a * 
* non-existent directory path on the target system where the   * 
* restore is being performed. Under such conditions the        * 
* restore will fail with SQL0970N. A good eyecatcher is error  * 
* -970 from "sqludProcessLFH,probe:1149" reported in the DB2   * 
* diagnostic log file.                                         * 
*                                                              * 
* Example:                                                     * 
* ========                                                     * 
* + db2 restore database source continue                       * 
* SQL0970N  The system attempted to write to a read-only file. * 
* SQLSTATE=55009                                               * 
* .                                                            * 
* db2diag.log:                                                 * 
* ============                                                 * 
* 2009-11-10-13.47.43.502353-300 I9133A578                     * 
* LEVEL: Error  PID  : 4403420      TID  : 1801                * 
* PROC : db2sysc  INSTANCE: db2inst1      NODE : 000           * 
* DB  : SAMPLE  APPHDL  : 0-7      APPID:                      * 
* *LOCAL.db2inst1.091110184735 AUTHID  : DB2INST1              * 
* EDUID  : 1801      EDUNAME:                                  * 
* db2agent (SAMPLE)      FUNCTION: DB2 UDB, data protection    * 
* services,                                                    * 
* sqlpRemoveRetrievedLogFiles, probe:20                        * 
* RETCODE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access       * 
* Denied"                                                      * 
* DIA8701C Access denied for resource "", operating system     * 
* return code was "".        .                                 * 
*                                                              * 
* 2009-11-10-13.47.43.508938-300 E9712A551      LEVEL: Severe  * 
* PID : 4403420    TID  : 1801        PROC : db2sysc           * 
* INSTANCE: db2inst1    NODE : 000        DB  : SAMPLE         * 
* APPHDL : 0-7      APPID: *LOCAL.db2inst1.091110184735        * 
* AUTHID : DB2INST1                                            * 
* EDUID : 1801    EDUNAME: db2agent (SAMPLE)                   * 
* FUNCTION: DB2 UDB, database utilities, sqludProcessLFH,      * 
* probe:1149                                                   * 
* DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes                  * 
* -970                                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install version 9.7 FixPak 2                                 * 
****************************************************************
Local Fix:
Modify file and directory permissions at operating system level 
in order to allow the instance owner to access the path 
specified in the OVERFLOWLOGPATH.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in version 9.7 FixPak 2 
 
The fix is to ignore the value of OVERFLOWLOGPATH should it not 
be accessible to DB2 during the RESTORE process. The output will 
be as follows: 
 
 
$ db2 restore database source from /TCDIR/BKUPS taken at 
20091109181255 
on /TCDIR/TARGET_PATH dbpath on /TCDIR/TARGET_DB into source 
redirect 
without rolling forward without prompting 
 
SQL1277W  A redirected restore operation is being performed. 
Table space configuration can now be viewed and table spaces 
that do not use automatic storage can have their containers 
reconfigured. 
 
DB20000I  The RESTORE DATABASE command completed successfully. 
 
 
 
$ db2 restore database source continue 
 
DB20000I  The RESTORE DATABASE command completed successfully. 
 
 
 
 
 
and in db2diag.log: 
 
 
2009-11-10-13.56.27.903814-300 I9133A578  LEVEL: Error 
PID : 2596926  TID : 1801 PROC : db2sysc 
INSTANCE: db2inst1   NODE : 000  DB  : SOURCE 
APPHDL : 0-8  APPID:  *LOCAL.db2inst1.091110185622 
 
AUTHID : db2inst1  EDUID : 1801        EDUNAME: db2agent 
(SOURCE) 
 
FUNCTION: DB2 UDB, data protection services, 
 
 
 
 
sqlpRemoveRetrievedLogFiles, probe:20 
 
 
 
RETCODE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied" 
 
 
 
 
  DIA8701C Access denied for resource "", operating system 
 
 
return code was "". 
 
 
 
 
 
 
2009-11-10-13.56.27.921783-300 I9712A620  LEVEL: Error 
 PID : 2596926     TID  : 1801  PROC : db2sysc 
 
INSTANCE: db2inst1   NODE : 000  DB  : SOURCE 
 
APPHDL : 0-8  APPID: 
*LOCAL.db2inst1.091110185622 
AUTHID : db2inst1 
 
EDUID : 1801  EDUNAME: db2agent (SOURCE) 
 
FUNCTION: DB2 UDB, database utilities, sqludProcessLFH, 
 
 
 
probe:1159 
MESSAGE : Error -2079391743 when deleting log files in the 
 
OVERFLOWLOGPATH DB 
 
  configuration parameter /TCDIR/SOURCE/OVLOGS/. DB2 
will 
  ignore this error and continue with the restore. 
 
 
 
Please note that after the completion of the restore, the 
 
 
configuration parameter will not be blanked out and will still 
contain the original value that was stored in the backup image. 
Thus it will be up to the database administrator to ensure that 
the OVERFLOWLOGPATH value is modified to the proper value after 
completion of the redirected restore.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.11.2009
18.05.2010
18.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList