Monitoring RMAN Backups / List and Report commands

Monitoring RMAN Backups
Monitoring actual sessions during RMAN backups or recoveries can be performed utilizing RMAN dynamic views.

V$RMAN_OUTPUT Displays messages reported by an RMAN job in progress

V$RMAN_STATUS Displays the success or failure of all completed RMAN jobs

V$RECOVER_FILE Shows the datafiles that require recovery

An incarnation is a unique backup of the target database that is identified by a unique DB_KEY value. A new incarnation is generated each time a database is opened with RESETLOGS or BACKUP CONTROLFILE.

SQL> select dbid from V$database;
SQL> conn rman_user/rman_user@ora101rc
SQL> select db_key from rc_database where dbid=72737292;

Using LIST Commands
Is used to query the RMAN repository and get the data regarding the BACKUP command, COPY command, and database incarnations. The output of LIST commands displays the files that the CHANGE, CROSSCHECK, and DELETE commands have used.
LIST command displays backup information by using the BY BACKUP and BY FILE options. There are also SUMMARY and VERBOSE options to condense or expand the output.

RMAN> list backupset by backup summary;

RMAN> list backupset by file;

Using REPORT commands
Used to query RMAN repository and get the data regarding which need a backup, unneeded backups, database physical schema, and whether or not unrecoverable operations were performed on files. The output of REPORT commands will generate more detailed information from RMAN repository.

NOTE: The RMAN repository must synchronize with the controlfile. In addition, the CHANGE, UNCATALOG, and CROSSCHECK commands should have been recently executed for the report to be completely accurate.

The REPORT command options include REPORT NEED BACKUP, REPORT OBSOLETE, and REPORT SCHEMA.

RMAN> report obsolete;
RMAN> report schema;