Databases Reference
In-Depth Information
Solution
Use the
report unrecoverable
command to find out which data files in the database have been marked
unrecoverable because they're part of an unrecoverable operation. Here's an example showing how to use the
report
unrecoverable
command:
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
----- --------------- ----------------------------------------
1 full /u01/app/oracle/data/prod1/example01.dbf
RMAN>
The
report unrecoverable
command reveals that the example01.dbf file is currently marked unrecoverable and
that it needs a full backup to make it recoverable if necessary.
How It Works
If you perform a nonrecoverable operation, such as a direct load insert, the changes made won't be logged in the redo
log files. You must, therefore, immediately perform either a full backup or an incremental backup of the data files
involved in the nonrecoverable operation.
The
report unrecoverable
command tells you both the names of the data files that were part of a nonlogged
operation (and therefore nonrecoverable by normal media recovery) and the type of backup (full or incremental)
required to recover the data file from an RMAN backup.
Identifying Obsolete Backups
Problem
You want to find out whether any backups are obsolete according to the retention policy you configured.
Solution
The
report obsolete
command reports on any obsolete backups. Always run the
crosscheck
command first to
update the status of the backups in the RMAN repository to that on disk and tape. In the following example,
the
report obsolete
command shows no obsolete backups:
RMAN> crosscheck backup;
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
