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

In DB2 LUW, DB2ADUTL VERIFY HEADONLY command and DB2ADUTL QUERY command may
show incorrect result for multi-session BACKUP.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
1. The filename returned by the db2adutl verify headeronly 
command does not match the header information when a backup is 
taken using more then one session. 
 
 
Example 
 db2 backup database sample use tsm open 8 sessions 
 db2adutl verify headeronly db sample taken at 20091119140501 
 
From below you can see it states: 
 
Verifying file: 
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001 
But in per the header the file name should be 
SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007 
 
 
Retrieving FULL DATABASE BACKUP information.  Please wait. 
 
   FULL DATABASE BACKUP image: 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001, 
DB Partition Number: 0 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.002, 
DB Partition Number: 0 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.003, 
DB Partition Number: 0 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.004, 
DB Partition Number: 0 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.005, 
DB Partition Number: 0 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.006, 
DB Partition Number: 0 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007, 
DB Partition Number: 0 
      ./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.008, 
DB Partition Number: 0 
 
   Do you wish to verify this image (Y/N)? 
   Verifying file: 
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001 
 
 
===================== 
MEDIA HEADER REACHED: 
===================== 
        Server Database Name           -- SAMPLE 
        Server Database Alias          -- SAMPLE 
        Client Database Alias          -- SAMPLE 
        Timestamp                      -- 20091119140501 
        Database Partition Number      -- 0 
        Instance                       -- db2inst1 
        Sequence Number                -- 7 
        Release ID                     -- B00 
        Database Seed                  -- DBFF1C1A 
        DB Comment's Codepage (Volume) -- 0 
        DB Comment (Volume)            -- A sample database 
        DB Comment's Codepage (System) -- 0 
        DB Comment (System)            -- A sample database 
        Authentication Value           -- -1 
        Backup Mode                    -- 0 
        Includes Logs                  -- 0 
        Compression                    -- 0 
        Backup Type                    -- 0 
 
        Backup Gran.                   -- 0 
        Status Flags                   -- 1 
        System Cats inc                -- 1 
        Catalog Partition Number       -- 0 
        DB Codeset                     -- UTF-8 
        DB Territory                   -- 
        LogID                          -- 1254882872 
        LogPath                        -- 
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/ 
        Backup Buffer Size             -- 1052672 
        Number of Sessions             -- 8 
        Platform                       -- 1E 
 
 The proper image file name would be: 
SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007 
 
2. The db2adutl query command may return several entries for the 
same backup image to TSM. 
 
   db2adutl query full db SAMPLE 
    Query for database SAMPLE 
    Retrieving FULL DATABASE BACKUP information. 
    1 Time: 20091218011337  Oldest log: S1846095.LOG  DB 
Partition Number: 0  Sessions: 2 
    2 Time: 20091218011337  Oldest log: S1846095.LOG  DB 
Partition Number: 0  Sessions: 1 
    3 Time: 20091217011235  Oldest log: S1845626.LOG  DB 
Partition Number: 0  Sessions: 3 
    4 Time: 20091216011338  Oldest log: S1845409.LOG  DB 
Partition Number: 0  Sessions: 1 
    5 Time: 20091216011338  Oldest log: S1845409.LOG  DB 
Partition Number: 0  Sessions: 1 
    6 Time: 20091216011338  Oldest log: S1845409.LOG  DB 
Partition Number: 0  Sessions: 1 
    Retrieving INCREMENTAL DATABASE BACKUP information. 
      No INCREMENTAL DATABASE BACKUP images found for SAMPLE 
    Retrieving DELTA DATABASE BACKUP information. 
      No DELTA DATABASE BACKUP images found for SAMPLE 
 
   This problem happens whenever you have more than one session 
that is required for a database. 
   This can occur even if the second session is due to an online 
include logs and the backup only was defined as single session 
(it automatically gets the second session for the logs phase). 
 
3. The db2adutl keep <N> functionality may not work when the 
images are not aggregated correctly. 
 
   Sample scenario is like this. 
 
   1) Check the backup images. 
 
   $ db2adutl query full db SAMPLE 
 
   Query for database SAMPLE 
 
   Retrieving FULL DATABASE BACKUP information. 
    1 Time: 20091218155633  Oldest log: S0004309.LOG  DB 
Partition Number: 0    Sessions: 2 (Online backup) 
    2 Time: 20091218131854  Oldest log: S0004300.LOG  DB 
Partition Number: 0    Sessions: 2 (Online backup) 
    3 Time: 20091218104953  Oldest log: S0004293.LOG  DB 
Partition Number: 0    Sessions: 1 (Offline backup) 
 
   Retrieving INCREMENTAL DATABASE BACKUP information. 
     No INCREMENTAL DATABASE BACKUP images found for SAMPLE 
 
   Retrieving DELTA DATABASE BACKUP information. 
     No DELTA DATABASE BACKUP images found for SAMPLE 
 
   The output is correct, one entry for one image. 
 
   2) Take a fourth online backup, and db2adutl delete with 
"keep 6" option. 
 
   # su - maint1 -c db2 backup db SAMPLE online use tsm buffer 
2049 include logs 
 
   Backup successful. The timestamp for this backup image is : 
20091218163950 
 
   # su - maint1 -c db2adutl delete full NONINCREMENTAL keep 6 
db SAMPLE without prompting 
 
   Query for database SAMPLE 
 
   Retrieving FULL DATABASE BACKUP information. 
     Taken at: 20091218104953  DB Partition Number: 0 
Sessions: 1 
 
   The backup image which should not be deleted was deleted. 
 
   3) Check the backup images again. 
   $ db2adutl query full db SAMPLE 
 
   Query for database SAMPLE 
 
   Retrieving FULL DATABASE BACKUP information. 
       1 Time: 20091218163950  Oldest log: S0004315.LOG  DB 
Partition Number: 0    Sessions: 1 
       2 Time: 20091218163950  Oldest log: S0004315.LOG  DB 
Partition Number: 0    Sessions: 1 
       3 Time: 20091218155633  Oldest log: S0004309.LOG  DB 
Partition Number: 0    Sessions: 1 
       4 Time: 20091218155633  Oldest log: S0004309.LOG  DB 
Partition Number: 0    Sessions: 1 
       5 Time: 20091218131854  Oldest log: S0004300.LOG  DB 
Partition Number: 0    Sessions: 1 
       6 Time: 20091218131854  Oldest log: S0004300.LOG  DB 
Partition Number: 0    Sessions: 1 
 
   Retrieving INCREMENTAL DATABASE BACKUP information. 
     No INCREMENTAL DATABASE BACKUP images found for SAMPLE 
 
   Retrieving DELTA DATABASE BACKUP information. 
     No DELTA DATABASE BACKUP images found for SAMPLE 
 
   Two entries are listed for each backup image. 
 
   This problem does not occur in V8 and V9.1.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The filename returned by the db2adutl verify                 * 
* headeronlycommand does not match theheader information when  * 
* backup taken using more then onesessionExampledb2 backup     * 
* database sample use tsm open 8 sessionsdb2adutl verify       * 
* headeronly db sample taken at 20091119140501From below you   * 
* can see it statesVerifying                                   * 
* file:./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001B 
* in per the header the file name should                       * 
* beSAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007Retrie 
* FULL DATABASE BACKUP information.  Please wait.FULL DATABASE * 
* BACKUP                                                       * 
* image:./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001 
* DBPartition Number:                                          * 
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.002,   * 
* DBPartition Number:                                          * 
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.003,   * 
* DBPartition Number:                                          * 
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.004,   * 
* DBPartition Number:                                          * 
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.005,   * 
* DBPartition Number:                                          * 
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.006,   * 
* DBPartition Number:                                          * 
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007,   * 
* DBPartition Number:                                          * 
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.008,   * 
* DBPartition Number: 0Do you wish to verify this image        * 
* (Y/N)?Verifying                                              * 
* file:./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001= 
* HEADER REACHED:=====================Server Database Name     * 
*      -- SAMPLEServer Database Alias          -- SAMPLEClient * 
* Database Alias          -- SAMPLETimestamp                   * 
*    -- 20091119140501Database Partition Number      --        * 
* 0Instance                      -- db2inst1Sequence Number    * 
*             -- 7Release ID                    -- B00Database * 
* Seed                  -- DBFF1C1ADB Comment's Codepage       * 
* (Volume) -- 0DB Comment (Volume)            -- A sample      * 
* databaseDB Comment's Codepage (System) -- 0DB Comment        * 
* (System)            -- A sample databaseAuthentication Value * 
*          -- -1Backup Mode                    -- 0Includes    * 
* Logs                  -- 0Compression                    --  * 
* 0Backup Type                    -- 0Backup Gran.             * 
*      -- 0Status Flags                  -- 1System Cats inc   * 
*              -- 1Catalog Partition Number      -- 0DB        * 
* Codeset                    -- UTF-8DB Territory              * 
*     --LogID                          -- 1254882872LogPath    * 
*                                                              * 
* --/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/Backup  * 
* Buffer Size            -- 1052672Number of Sessions          * 
*   -- 8Platform                      -- 1EThe proper image    * 
* file name would                                              * 
* be:SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 Fixpack 6                                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
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
Fixed contained in V9.5 Fixpack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.01.2010
22.06.2010
22.06.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)