home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT05307 Status: Closed

BACKUP utility does not detect corrupted database files when COMPRESS
option is used and is successful

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Backup with compression does not detect corrupted database files 
and succeeds where as backup without compression may fail with 
-902 error. 
 
The following entries may be seen in db2diag.log: 
 
 
 
2014-07-02-11.15.05.494701-240 E9939A509            LEVEL: Info 
 
PID     : 24969250             TID : 23689          PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 23689                EDUNAME: db2agent (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, 
probe:1687 
MESSAGE : Starting an online db backup. 
 
 
 
2014-07-02-11.15.10.258370-240 I10449A667           LEVEL: 
Severe 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, 
sqlubValidateOrReReadSinglePage, probe:2691 
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not 
exist" 
          DIA8506C Unexpected end of file was reached. 
 
DATA #1 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes 
 
116 
 
 
 
2014-07-02-11.15.10.259133-240 I11117A648           LEVEL: 
Severe 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1541 
 
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not 
exist" 
          DIA8506C Unexpected end of file was reached. 
 
DATA #1 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes 
 
116 
 
 
 
2014-07-02-11.15.10.259697-240 E11766A507           LEVEL: Error 
 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1675 
 
DATA #1 : unsigned integer, 2 bytes 
 
253 
 
 
 
2014-07-02-11.15.10.260111-240 E12274A505           LEVEL: Error 
 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1676 
 
DATA #1 : unsigned integer, 2 bytes 
 
2 
 
 
 
2014-07-02-11.15.10.260558-240 E12780A505           LEVEL: Error 
 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1677 
 
DATA #1 : unsigned integer, 1 bytes 
 
1 
 
 
 
2014-07-02-11.15.10.261161-240 E13286A507           LEVEL: Error 
 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1678 
 
DATA #1 : unsigned integer, 4 bytes 
 
116 
 
 
 
2014-07-02-11.15.10.261572-240 E13794A510           LEVEL: Error 
 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1679 
 
DATA #1 : unsigned integer, 4 bytes 
 
737280 
 
 
 
2014-07-02-11.15.10.262080-240 E14305A617           LEVEL: 
Severe 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1687 
 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
 
-902 
 
DATA #2 : Hexdump, 8 bytes 
 
0x00000001BDB30A18 : 870F 0009 0000 0009 
........ 
 
 
2014-07-02-11.15.10.262509-240 E14923A1028          LEVEL: 
Severe 
PID     : 24969250             TID : 212842         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
sample 
APPHDL  : 0-49517              APPID: 
*LOCAL.db2inst1.140702151504 
AUTHID  : db2inst1             HOSTNAME: localhost 
EDUID   : 212842               EDUNAME: db2bm.23689.8 (sample) 0 
 
FUNCTION: DB2 UDB, database utilities, sqlubReadReg, probe:1687 
 
MESSAGE : SQL0902C  A system error occurred. Subsequent SQL 
statements cannot 
          be processed. IBM software support reason code: "". 
 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -902   sqlerrml: 1 
 
 sqlerrmc: 9 
 
 sqlerrp : sqlubRea 
 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 
 sqlstate: 
 
However, backup with compression does not fail and is 
successful. 
 
The reason for the regular backup failure is the corrupted 
index/table container files which are not detected by compressed 
backup. The issue may not be detected till uncompressed backup 
is run and/or a sql is run that access the corrupted 
indexes/tables.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V101 FP4 and lower                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v101 FP5                                      * 
****************************************************************
Local Fix:
As a temporary workaround, the explanation of SQL1655C code can 
be tried: 
 
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com. 
ibm.db2.luw.messages.sql.doc/doc/msql01655c.html?lang=en 
 
NOTE: If AUTO_DEL_REC_OBJ database configuration parameter is 
set to delete old backup images when new ones are created then 
good backups may be deleted and only backups with missing pages 
on disk are present then recovering data may not be possible.
Solution
First Fixed in DB2 v101 FP5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

31.10.2014
15.07.2015
15.07.2015
Problem solved at the following versions (IBM BugInfos)


Problem solved according to the fixlist(s) of the following version(s)


10.1.0.5

FixList