| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> DBVerify showing corruption on every block with 8,.1.7
Hello Everyone,
Recently we installed Oracle Enterprise Edition 8.1.7 on all our database
servers.
We have created new databases, as well as upgraded existing databases
from 8.1.5 to 8.1.7. While implementing RMAN on databases,
RMAN detected block corruption. Initially, it was related to a database
conversion from an older version 8.1.5 to 8.1.7 issue. This was due to the
fact
that the corruption was first detected on the converted databases.
However, the same behaviour has been noted on other databases consistently.
Since other databases are now showing the same symptons, we have used the
(dbv) database verify utility to look at various files within each of our
databases.
The output indicates block corruption in all files. Please note that this
utility
also indicates the same corruption on all Oracle database files on other
Tru64 servers.
Operations on these databases appear to be normal other than RMAN performing
checksum
verifications. Databases can be shutdown and restarted.
Meta link document states that this is an operating system corruption
problem
when running the 5.0a, or 5.1 o/s versions of Tru64. Our SA has confirmed
the following:
advfs.mod checksum/byte count is 44646/1168. He advises based on Oracle
documentation:
apply the new advfs.mod and move an odbflchk to the /sys/BINARY area and
recompile the kernel with changes.
Can you confirm this?
Also, what actions do we need to take to ensure the integrity of our databases?
The following are errors produced in the alert logs:
Corrupt block seq: 12 blocknum=12097.
Bad header found during backing up archived log
Data in bad block - seq:12. bno:12100. time:421846304
beg:336 cks:0
calculated check value: 10158
Reread of seq=12, blocknum=12097,
file=/u03/oraarchive/dbname/dbname_0001_0000000012.arc, found same
corrupt data
The following are errors reported by doing a dbv on Oracle files:
Page 76305 is marked corrupt
***
Corrupt block relative dba: 0x00012a11 (file 0, block 76305)
Bad header found during dbv:
Data in bad block -
type: 0 format: 0 rdba: 0x1c1c19c3
last change scn: 0x0005.47000106 seq: 0x16 flg: 0x00
consistency value in tail: 0x1c1c19c3
check value in block header: 0xff00, block checksum disabled
spare1: 0xff, spare2: 0x4, spare3: 0xc304
***
TAR# 13320267.600 Oracle Consultant Advised:
Corrective Actions Taken:
DBA - changed /etc/oratab file - DO NOT START DB's on server reboot
DBA - All DB's - Terminiate all user sessions DBA - alter db's enable restricted mode DBA - alter system switch logfile DBA - alter system checkpoint DBA - alter database backup controlfile to trace;
SA - Installed patch set QAR84601_v50a_b116.tar.Z
DBA - Relink 8.1.5 dbv utility:
$ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk idv
Error "Don't know how to make idv" STOP.
DBA - Performed dbv on 8.1.7 database files: errors messages as follows:
Page 1321 is marked corrupt
***
Corrupt block relative dba: 0x00000529 (file 0, block 1321)
Completely zero block found during dbv:
Page 1322 is influx - most likely media corrupt
***
Corrupt block relative dba: 0x0000052a (file 0, block 1322)
Fractured block found during dbv:
Data in bad block -
type: 0 format: 0 rdba: 0x00000000
last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
consistency value in tail: 0x00000000
check value in block header: 0x0, block checksum disabled
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
DBA - Performed sys/BINARY/odbflchk on several DB control files and redo logs
server.???.com:/u03/oradata/????> /sys/BINARY/odbflchk /u03/oradata/dbname/redo_g1r2.log
Oracle Database File Checker - V1.4
Copyright (c) 2001, Oracle Corporation. All Rights Reserved.
Checking file: /u03/oradata/????/redo_g1r2.log
Blocksize: 1024
Oracle filesize: 20971520 bytes, 20480 Oracle blocks
Oracle file header processed successfully.
????.???.com:/u04/oradata/????> /sys/BINARY/odbflchk /u03/oradata/????/control_02.ctl
Oracle Database File Checker - V1.4
Copyright (c) 2001, Oracle Corporation. All Rights Reserved.
Checking file: /u03/oradata/????/control_02.ctl
Blocksize: 8192
Oracle filesize: 7438336 bytes, 908 Oracle blocks
Oracle file header processed successfully.
Scanning blocks: 100% Completed.
Done: Processed 908 blocks; no blocks are affected
for file /u03/oradata/????/control_02.ctl
DBA - Peformed sys/BINARY/odbflchk on datafiles and returned the following:
Checking file: /u03/oradata/???/???_tools01_001.dbf
Oracle File #: 2
Blocksize: 4096
Oracle filesize: 52428800 bytes, 12800 Oracle blocks
Oracle file header processed successfully.
Scanning blocks: 100% Completed.
Done: Processed 12800 blocks; no blocks are affected
for file /u03/oradata/???/???_tools01_001.dbf
Question: The dbverify and odbflchk utilities return conflicting results:
How should we proceed?
What is the integrity state of the databases?
NOW ANYONE HAVING SIMILAR PROBLEMS. environment details
Oracle Version 8.1.7
OS VERSION COMPAQ TRU64 5.0a and 5.1
TIA Murali Vallath
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Murali Vallath INET: murali_vallath_at_hotmail.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Thu Mar 01 2001 - 10:27:04 CST
 |
 |