Databases Reference
In-Depth Information
When you apply the same command to each of the other standby databases where you're taking backups,
the archived logs on the standby database that have been applied to all other remote standby destinations are
automatically deleted. You must connect to each of the other standby databases and to the recovery catalog when
issuing the command.
When you switch over to the secondary, or when a failover occurs, database roles will change and, therefore, you
must re-execute the appropriate
configure
commands on the new primary and the new standby databases.
If you haven't set up the automatic deletion of archived logs at any standby database, you can execute the
delete
archivelog
command shown under “Manually Deleting Archived Redo Logs” to explicitly delete archive logs that
you've backed up to tape one or more times. The
backed up
clause ensures that you don't delete any archived logs
that you haven't already backed up first.
You can also remove expired archived logs with the
delete
command, as shown here:
RMAN> delete expired archivelog like '/archivelog/SF%';
In this case, we specify the
like
option to select appropriate archived logs for deletion.
If you've configured the fast recovery area, any archived logs that aren't required to satisfy your retention
period, or those you've already backed up to tape, will automatically be deleted when the FRA needs space for
accommodating new files. In this case, you need to execute the
delete
command manually only if you want to
immediately free up some space in the FRA.
Instantiating a Standby Database with RMAN
Problem
You want to instantiate a standby database with RMAN.
Solution
Follow these steps to instantiate a standby database with RMAN. Before you start to create the standby database,
ensure that the correct Oracle database binaries are installed on the target server.
1.
Create a standby database initialization parameter file. In this example we restore the SPFILE:
RMAN> restore spfile;
2.
Start the standby instance in the
nomount
mode, using the SPFILE.
3.
Configure Oracle Net to connect to the standby database host.
4.
Connect to the primary database as the target and to the recovery catalog as well, and back
up the control file by issuing the following command.
RMAN> backup current controlfile for standby;
5.
Connect to the primary database, the recovery catalog, and the standby database instance as follows:
$ rman target <primary_db> catalog <catalog_db> auxiliary <standby_db>
6.
Create the standby database with the
duplicate database
command as shown here.
RMAN> duplicate target database for standby
nofilenamecheck dorecover;
