Database Reference
In-Depth Information
I use SQL queries for specialized reports (not available via LIST or REPORT ) or for automating reports. For
example, I'll generally implement an automated check via a shell script and SQL that reports whether the RMAN
backups have run within the last day.
Using LIST
When investigating issues with RMAN backups, usually one of the first tasks I undertake is connecting to the target
database and running the LIST BACKUP command. This command allows you to view backup sets, backup pieces, and
the files included in the backup:
RMAN> list backup;
The command shows all RMAN backups recorded in the repository. You may want to spool the backups to an
output file so that you can save the output and then use an OS editor to search through and look for specific strings in
the output.
To get a summarized view of backup information, use the LIST BACKUP SUMMARY command:
RMAN> list backup summary;
You can also use the LIST command to report just image copy information:
RMAN> list copy;
To list all files that have been backed up, and the associated backup set, issue the following command:
RMAN> list backup by file;
These commands display archive redo logs on disk:
RMAN> list archivelog all;
RMAN> list copy of archivelog all;
And, this command lists the backups of the archive redo logs (and which archive redo logs are contained in
which backup pieces):
RMAN> list backup of archivelog all;
There are a great many ways in which you can run the LIST command (and, likewise, the REPORT command,
covered in the next section). The prior methods are the ones you'll run most of the time. See the Oracle Database
Backup and Recovery Reference Guide , available from the Technology Network area of the Oracle web site
( http://otn.oracle.com ) , for a complete list of options.
Using REPORT
The RMAN REPORT command is useful for reporting on a variety of details. You can quickly view all the data files
associated with a database, as follows:
RMAN> report schema;
 
Search WWH ::




Custom Search