Database Reference
In-Depth Information
Dropping a Recovery Catalog
If you determine that you're not using a recovery catalog and that you no longer need the data, you can drop it. To do
so, connect to the recovery catalog database as the catalog owner, and issue the DROP CATALOG command:
$ rman catalog rcat/foo
RMAN> drop catalog;
You're prompted as follows:
recovery catalog owner is RCAT
enter DROP CATALOG command again to confirm catalog removal
If you enter the DROP CATALOG command again, all the objects in the recovery catalog are removed from the
recovery catalog database.
The other way to drop a catalog is to drop the owner. To do so, connect to the recovery catalog as a user with DBA
privileges, and issue the DROP USER statement:
$ sqlplus system/manager
SQL> drop user rcat cascade;
SQL*Plus doesn't prompt you twice; it does as you instructed and drops the user and its objects. Again, the only
reason to do this is when you're certain you don't need the recovery catalog or its data any longer. Use caution when
dropping a user or the recovery catalog: I recommend that you take a Data Pump export of the recovery catalog owner
before dropping it.
Logging RMAN Output
When troubleshooting RMAN output or checking the status of a backup job, it's essential to have a record of what
RMAN ran and the status of each command. There are several methods for logging RMAN output. Some are built-in
aspects of the Linux/Unix OS. Others are RMAN-specific features:
Linux/Unix redirect output to file
Linux/Unix logging commands
SPOOL LOG command
RMAN
V$RMAN_OUTPUT view
These logging features are discussed in the next sections.
Redirecting Output to a File
I run almost all RMAN backup jobs from shell scripts. The shell scripts are usually run automatically from a
scheduling tool such as cron . When running RMAN commands in this fashion, I always capture the output by
instructing the shell command to redirect standard output messaging and standard error messaging to a log file. This
is done with the redirection ( > ) character. This example runs a shell script ( rmanback.bsh ) and redirects both standard
output and standard error output to a log file named rmanback.log :
$ rmanback.bsh 1>/home/oracle/bin/log/rmanback.log 2>&1
 
Search WWH ::




Custom Search