Databases Reference
In-Depth Information
Solution
Oracle recommends several specific configurations for RMAN for the primary database. The following steps show how
to configure RMAN for the primary database:
1.
Connect to the primary database, as well as to the recovery catalog.
2.
Configure the backup retention policy for the primary database:
RMAN>configure retention policy to recovery window of 14 days.
In this example, we chose 14 days as an example—you can set to the exact number of days dictated by
your retention requirements.
3.
Configure an archive log deletion policy. There are two basic archive log retention-related
configuration settings you can choose. The first deletes all archive logs after they're
shipped to all destinations, as shown here:
RMAN> configure archivelog deletion policy to shipped to all standby;
Alternatively the following archive log-related configuration directive ensures that logs are deleted only
after they're applied on all standby destinations:
RMAN> configure archivelog deletion policy to applied on all standby;
4.
You must also configure the connect identifiers for the primary database and all standby
databases in your Data Guard configuration:
RMAN> configure db_unique_name boston connect identifier 'boston_conn_str';
Once you're done, issue the
list db_unique_name
command to verify that connect identifiers for all the
standby databases have been configured.
How It Works
The configuration of the primary database described here assumes that you're taking backups only on the standby
database. Oracle also requires you to use a recovery catalog so you can restore backups taken on one database server
on a different database server.
Oracle recommends that you
•
Configure a fast recovery area local to each database
•
Use a server parameter file (SPFILE)
•
Enable Flashback Database on both the primary and the standby databases
Configuring RMAN in a Standby Database
Problem
You want to configure RMAN in a standby database.
