Home

Neueste Versionen	FixList
11.1.0.7
10.5.0.9
10.1.0.6
9.8.0.5
9.7.0.11
9.5.0.10
9.1.0.12

Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren
Kontaktformular

DB2 - Problembeschreibung

Problem IT05307	Status: Geschlossen
BACKUP utility does not detect corrupted database files when COMPRESS option is used and is successful
Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** * 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.
Lösung
First Fixed in DB2 v101 FP5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung:	31.10.2014 15.07.2015 15.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)

Problem behoben lt. FixList in der Version
10.1.0.5