corrupt datafile 2004-06-12 - By Tim Gorman
Terry,
Hopefully they have logged a TAR with Oracle Support and are working it that
way. It is possible that ?dbverify? is returning the response that every
block is corrupt simply because it cannot read the file-header information,
not because the entire file is shredded. This file might have a few bytes
out of place in the header, in which case it is possible that Oracle
Support?s Data UnLoader (DUL) utility might be able to dump the data from
the file. Otherwise, if every single block is corrupt, then even DUL
probably would not be able to retrieve the data.
A ?hot backup? from Wednesday is available but the archivelogs going back to
that backup aren?t? Other datafile backups from the ?hot backup? on
Wednesday are not available? It seems that many, many things have gone
wrong here. It would be worthwhile to dwell on why the other datafiles and
the archivelogs are not available, so that this never happens again. This
is a time for brutal honesty.
|
|
