Very Computer

Hi,

There is a tool dbverify ('dbv') which could be used to check datafiles
for corrupted blocks.

Is there also a tool to check archived log files for corrupted entries ?

Which possibilities exist to ensure the archived log files are not
corrupted ?

Thanks,
Gerald

The short answer is that if ARCH manages to write the archived files, they
are clear of corruption.  ARCH doesn't just do an O/S-style copy, but an
intelligent read of the logs, and an intelligent write of the archives.
It's its own policeman as far as detecting corruption is concerned.

The slightly longer answer is that you can run log miner (assuming an 8i or
above database).  In 8i, if the analysis of a log encounters corruption, it
bombs out with spectacular errors (in 9i, it can keep going, but you'll
still know it encountered corruption).

If you've got an Oracle 8 database, log miner can be run from an 8i database
against archives produced by Oracle 8.  But if you're on Oracle 7, forget
it.  Incidentally, when you post, version numbers are helpful -there are
rather a lot of them out there now!

Regards
HJR
--
Resources for OracleT: www.geocities.com/howardjr2000
=========================================

Quote:> Hi,

> There is a tool dbverify ('dbv') which could be used to check datafiles
> for corrupted blocks.

> Is there also a tool to check archived log files for corrupted entries ?

> Which possibilities exist to ensure the archived log files are not
> corrupted ?

> Thanks,
> Gerald

Hi there,

  I remember from Oracle 7.2 onwards the DB_BLOCK_CHECKSUM can be set to true.
You can enable logfile block checksumming. Enabling log block checksumming
will force Oracle to compute a checksum and place it in the header of each
redo block. When the block is read by ARCH processs, the checksum is checked.
Archiving process will stop if there is checksum error due to corrupted redo
block.

Allan W. Tham
DBA