Databases Reference
In-Depth Information
On Unix-based systems you have to escape the single quote character by a backslash (“\”) since that is
interpreted by the Unix shell:
$ rman target=/ @delete_arc_logs_pattern.rman using \'2012_08_07\'
... output truncated ...
connected to target database: IDB1 (DBID=420374953)
RMAN> run { delete archivelog like '%2012_08_07%' ; }
2>
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=261 device type=DISK
deleted archived log
archived log file name=+FRA/idb1/archivelog/2012_08_07/thread_1_seq_38.374.790678805 RECID=29
STAMP=790678805
deleted archived log
archived log file name=+FRA/idb1/archivelog/2012_08_07/thread_1_seq_39.371.790718425 RECID=30
STAMP=790718426
deleted archived log
archived log file name=+FRA/idb1/archivelog/2012_08_07/thread_1_seq_40.370.790725643 RECID=31
STAMP=790725644
Deleted 3 objects
Recovery Manager complete.
Parameterized scripts help significantly in managing the infrastructure with RMAN. You can create just one script
and then call it several times with different values of the parameter, making many routine tasks a breeze. This strategy
is especially useful in cases where the script remains the same but some output changes to match the date and month,
such as when you want to name the backup pieces with the day, month, and year when they were generated. In that
case, you can merely call the script with a parameter that accepts the output name. This will reduce the scripting time
and the possibility of errors.
