su - oracle <<EOF
cd /home/oracle
. RMAN.ksh
cd /home/oracle/rman_scripts
rman target system/tommy nocatalog

run {
allocate channel c1 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel c2 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
backup
incremental level 0
format '/tmp/rman_%s.bak'
(database include current controlfile ) ;
change archivelog all crosscheck;
backup archivelog all
delete input
format 'RMAN_%s.arch';
sql 'alter system archive log current';
}
EOF

If the recovery catalog database is lost or damaged, and recovery of the recovery catalog database through the normal Oracle recovery procedures is not possible, then you must re-create the catalog. Examples of this worst-case scenario include:

    * A catalog database that has never been backed up
    * A catalog database that has been backed up, but cannot be recovered because the datafile backups or archived logs are not available

You have these options for partially re-creating the contents of the missing catalog:

    * Issue CATALOG commands to recatalog archived redo logs, backup control files, and datafile copies. Because the CATALOG command does not support recataloging of backup pieces or backup sets, you can re-create information about backup sets only by using the RESYNC CATALOG command.
    * Use the RESYNC CATALOG command to extract metadata from a control file and rebuild the recovery catalog. Note that you automatically lose any metadata that was contained in old control file records that aged out of the control file.

      Depending on the state of the target control file, you can:
          o Resynchronize from the current control file
          o Resynchronize from a control file copy