Using the RMAN Recovery Catalog - OCP: Oracle Database 12c Administrator Certified Professional - page 175

All rights reserved.
connected to target database: ORCL (DBID=1190537904, not open)
connected to recovery catalog database
RMAN> unregister database;
database name is "ORCL" and DBID is 1190537904
Do you really want to unregister the database (enter YES or NO)? yes
database unregistered from the recovery catalog

Unregistering a database from the recovery catalog will cause all recovery catalog-
related records to be removed from the recovery catalog. Control-file records for that data-
base will be retained, of course. You might have had older backup records stored in the
recovery catalog, though. When you unregister a database, those old records will be lost if
the age of the backups exceeds the setting of the CONTROL_FILE_RECORD_KEEP_TIME param-
eter. Also, any scripts related to the database in the recovery catalog will be lost (we will
talk more about scripting next).

Using Scripts in the RMAN
Recovery Catalog

One benefit of the recovery catalog is the ability to store RMAN scripts. In the following
sections, these topics will be addressed:

Executing external scripts

■

Creating stored scripts

■

Replacing stored scripts

■

Removing stored scripts

■

Executing stored scripts

■

Printing stored scripts

■

Using script-substitution variables

■

Executing External Scripts

RMAN provides the ability to execute external scripts. You can do so from the RMAN
command line using the CMDFILE option, as shown here:

Rman target=/ cmdfile=run_me.rman

You can also run an external script from within RMAN using the @ command, as
shown here:

RMAN> @run_me.rman