Backing Up Oracle - Computing at Cornell

RMAN> report need backup redundancy 3;
RMAN-03022: compiling command: report
Report of files with less than 3 redundant backups
File #bkps Name
---- ----- -----------------------------------------------------
1 2 C:\ORACLE\ORADATA\BEACH\SYSTEM01.DBF
5 2 C:\ORACLE\ORADATA\BEACH\TOOLS01.DBF
7 2 C:\ORACLE\ORADATA\BEACH\DR01.DBF
8 2 C:\ORACLE\ORADATA\BEACH\OEM_REPOSITORY.ORA
11.3.1.3 Report on obsolete backups
You can report on obsolete backups in order to determine which backups can
be deleted.
This example shows that any backup having more than four copies is
considered obsolete.
RMAN> report obsolete redundancy 4 device type 'sbt_tape';
RMAN-03022: compiling command: report
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 3269 02-APR-01
Backup Piece 3272 02-APR-01 BEACH/426013509/40/1
Backup Set 3271 02-APR-01
Backup Piece 3274 02-APR-01 BEACH/426013509/41/1
Backup Set 3292 02-APR-01
Backup Piece 3295 02-APR-01 BEACH/426013718/43/1
This example shows backups that are obsolete because there is at least
one backup and they were made no more than 3 days ago:
RMAN> report obsolete redundancy 1 until time 'sysdate-3' device type 'sbt_tape'
;
RMAN-03022: compiling command: report
RMAN-06147: no obsolete backups found
This example shows orphaned backups that are unusable because they
belong to incarnations of the database that are not direct ancestors of the
current incarnation:
180 Backing Up Oracle using Tivoli Storage Management