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

When using Infinite Logging, the only copy of an active log file can be
pruned

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
db2 prune history and delete deletes first active log. 
 
db2start 
db2 -v " drop db INFLOG" 
db2  -v "create db INFLOG" 
db2 -v " connect to  INFLOG" 
db2 -v " update db cfg for INFLOG using LOGARCHMETH1 
DISK:/home/db2inst1/ARCHLOC" 
db2 -v "terminate" 
db2 -v "backup db INFLOG to /dev/null" 
db2 -v " update db cfg for INFLOG using SOFTMAX 1" 
db2 -v " update db cfg for INFLOG using LOGPRIMARY 2 LOGSECOND 
-1 LOGFILSIZE 4" 
db2 get db cfg for INFLOG |grep -i LOG 
db2 -v "terminate" 
db2 -v "connect to INFLOG" 
db2 -v "create table test1 (I int, v1 varchar(200), v2 
varchar(200), v3 varchar(200))" 
 
db2 connect to INFLOG; db2 +c delete from test1 where i = 2; cd 
; db2 get db cfg for INFLOG |grep -i FIRST;   loop_insert3.pl 
 
Where loop_insert3.pl is a perl script that loads data into a 
table called test1 and causes log files to get generated and 
wait till they get deleted from the active log path and are only 
existing in the archive log path (prove with ls) 
 
 ls /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/ 
and 
 ls /home/db2inst1/ARCHLOC/db2inst1/INFLOG/NODE0000/C0000000 
 
Then from different window 
db2 connect to INFLOG; db2 prune history 20101007 with force 
option and delete 
 
then do the ls to confirm the missing files that are active logs 
and now no longer exist anywhere 
 
ls /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/ 
and 
ls /home/db2inst1/ARCHLOC/db2inst1/INFLOG/NODE0000/C0000000 
 
In cases where infinite logging is used, the active log can be 
archived to the archive path and removed from the active log 
path. 
If a prune is chosen with the delete option and a timestamp more 
recent than the active log is chosen, the active log would be 
deleted making it impossible to rollback the transaction and 
causing a potential database corruption.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2 prune history and delete deletes first active            * 
* log.db2startdb2 -v " drop db INFLOG"db2  -v "create db       * 
* INFLOG"db2 -v " connect to  INFLOG"db2 -v " update db cfg    * 
* for INFLOG using LOGARCHMETH1DISK:/home/db2inst1/ARCHLOC"db2 * 
* -v "terminate"db2 -v "backup db INFLOG to /dev/null"db2 -v " * 
* update db cfg for INFLOG using SOFTMAX 1"db2 -v " update db  * 
* cfg for INFLOG using LOGPRIMARY 2LOGSECOND-1 LOGFILSIZE      * 
* 4"db2 get db cfg for INFLOG |grep -i LOGdb2 -v               * 
* "terminate"db2 -v "connect to INFLOG"db2 -v "create table    * 
* test1 (I int, v1 varchar(200), v2varchar(200), v3            * 
* varchar(200))"db2 connect to INFLOG; db2 +c delete from      * 
* test1 where i = 2;cd; db2 get db cfg for INFLOG |grep -i     * 
* FIRST;  loop_insert3.plWhere loop_insert3.pl is a perl       * 
* script that loads data intoatable called test1 and causes    * 
* log files to get generated andwait till they get deleted     * 
* from the active log path and areonlyexisting in the archive  * 
* log path (prove with ls)ls                                   * 
* /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/andls     * 
* /home/db2inst1/ARCHLOC/db2inst1/INFLOG/NODE0000/C0000000Then * 
* from different windowdb2 connect to INFLOG; db2 prune        * 
* history 20101007 with forceoption and deletethen do the ls   * 
* to confirm the missing files that are activelogsand now no   * 
* longer exist anywherels                                      * 
* /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/andls     * 
* /home/db2inst1/ARCHLOC/db2inst1/INFLOG/NODE0000/C0000000In   * 
* cases where infinite logging is used, the active log         * 
* canbearchived to the archive path and removed from the       * 
* active logpath.If a prune is chosen with the delete option   * 
* and a timestampmorerecent than the active log is chosen, the * 
* active log wouldbedeleted making it impossible to rollback   * 
* the transaction andcausing a potential database corruption.  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.5 fix pack 7.                   * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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
Problem was first fixed in DB2 UDB Version 9.5 Fix Pack 7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC71752 IC71753 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.06.2010
15.11.2010
15.11.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList