Database Reference
In-Depth Information
The
REPORT
command provides detailed information about backups marked obsolete via the RMAN retention
policy; for example,
RMAN> report obsolete;
You can report on data files that need to be backed up, as defined by the retention policy, like this:
RMAN> report need backup;
There are several ways to report on data files that need to be backed up. Here are some other examples:
RMAN> report need backup redundancy 2;
RMAN> report need backup redundancy 2 datafile 2;
The
REPORT
command may also be used for data files that have never been backed up or that may contain data
created from a
NOLOGGING
operation. For example, say you have direct-path loaded data into a table, and the data file
in which the table resides has not been backed up. The following command will detect these conditions:
RMAN> report unrecoverable;
Using SQL
There are a number of data dictionary views available for querying about backup information. Table
5-1
describes
RMAN-related data dictionary views. These views are available regardless of your use of a recovery catalog
(the information in these views is derived from the control file).
Table 5-1.
Description of RMAN Backup Data Dictionary Views
View Name
Information Provided
V$RMAN_BACKUP_JOB_DETAILS
RMAN backup jobs
V$BACKUP
Backup status of online data files placed in
backup mode (for hot backups)
V$BACKUP_ARCHIVELOG_DETAILS
Archive logs backed up
V$BACKUP_CONTROLFILE_DETAILS
Control files backed up
V$BACKUP_COPY_DETAILS
Control file and data file copies
V$BACKUP_DATAFILE
Control files and data files backed up
V$BACKUP_DATAFILE_DETAILS
Data files backed up in backup sets, image
copies, and proxy copies
V$BACKUP_FILES
Data files, control files,
spfile
s, and archive
redo logs backed up
V$BACKUP_PIECE
Backup piece files
V$BACKUP_PIECE_DETAILS
Backup piece details
V$BACKUP_SET
Backup sets
V$BACKUP_SET_DETAILS
Backup set details
