Backing Up Oracle - Computing at Cornell

7.2.3 Crosscheck utility
The crosscheck utility verifies whether backups still exist on disk or TSM.
RMAN does not delete backup entries that it could not find, but instead marks
them as expired. If the backup was erroneously marked expired, for example,
because TSM was unavailable or misconfigured, the crosscheck utility will
mark it available the next time it is run if the backup still exists.
Like the list utility discussed in 7.2.2.3, “List backup of certain objects” on
page 98, you can run the crosscheck utility on certain objects. See the
Oracle8i Recovery Manager User Guide and Reference, A76990-1, for the
complete syntax of the crosscheck utility.
Here is a sample script to crosscheck all backup entries in the recovery
catalog or control file:
allocate channel for maintenance type 'sbt_tape'
parms 'ENV=(DSMO_NODE=sol_oracle,DSMO_AVG_SIZE=256,
DSMI_ORC_CONFIG=/opt/tivoli/tsm/client/oracle/bin/dsm.opt,
DSMI_LOG=/usr/local/oracle/log)';
crosscheck backup;
exit;
7.3 Automatic deletion of old backups
Oracle provides a sample UNIX shell script to delete obsolete backups. The
example is in $ORACLE_HOME/rdbms/demo/rman1.sh. You can customize
the script to your needs.
Next we show a very simplified sample script to delete backups made under
TSM. It maintains copies that were created within the last three days, and at
least three copies. (Please note that great care should be taken to ensure
that any deletion of backups is planned and tested before implementation in a
production environment.)
Chapter 7. Day-to-day monitoring of Oracle backups on UNIX 101