Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02 |
|
|
View PDF |
If media recovery encounters a problem, then obtain as much information as possible after recovery halts. You do not want to waste time fixing the wrong problem, which may in fact make matters worse.
The goal of this initial investigation is to determine whether the problem is caused by incorrect setup, corrupted redo logs, corrupted data blocks, memory corruption, or other problems. If you see a checksum error on a data block, then the data block is corrupted. If you see a checksum error on a redo log block, then the redo log is corrupted.
Sometimes the cause of a recovery problem can be difficult to determine. Nevertheless, the methods in this chapter allow you to quickly recover a database even when you do not completely understand the cause of the problem.
To investigate media recovery problems:
Examine the alert.log
to see whether the error messages give general information about the nature of the problem. For example, does the alert_
SID
.log
indicate any checksum failures? Does the alert_
SID
.log
indicate that media recovery may have to corrupt data blocks in order to continue?
Check the trace file generated by the Oracle process during recovery. It may contain additional error information.