Oracle 11g replicuard configuration learning Summary

After half a month of configuration and learning about the physical standby database of Oracle replicaset uard, although the version uses Oracle 11g (11.2.0.3), the configuration process still applies to Oracle 10g. During the last 10 dataguard configurations, it was found that using rman duplicate to create a physical standby database is very convenient and fast. Gradually, the physical standby database will not be created in the cold standby mode. Through rman duplicate, you can not only create a replica uard, but also clone the database, which is powerful.

The following methods are used to create a consumer uard.

 

1. Configure Dataguard in cold standby mode

The cold standby mode configuration is skipped.

Features:
1) manual configuration of Dataguard is suitable for a small number of databases.
2) It is suitable for beginners to learn how to configure, test, and understand Dataguard principles.

Ii. Configure Dataguard in RMAN Duplicate Mode

RMAN Duplicate can be used not only to create a replica uard slave database, but also to clone a database. You can just modify the parameters to directly clone the database.

RMAN duplicate has the following configuration methods:

 

Method 1: connect the target master database to the local auxiliary database through RMAN, and clone the slave database directly by capturing data from the master database (Active Database.

Configuration document example:

 

Advantages:
1) No downtime required for the master database
2) You do not need to perform RMAN backup in the master database.
3) There is no need to replicate the control file of the slave database in the master database
4) No parameter files need to be prepared for the standby database in the master database
4) when the target is sent to the master database, you can directly apply the rule logs and redo logs sent from the master database.

Disadvantages:
1) the data files and logs of the master database are all copied to the slave database over the network. This method will take a long time. If the master database is large, this method is not suitable.
2) When duplicate affects the performance and network pressure of the master database, You must select a time when the database pressure is relatively small.

Method 2: connect the target master database to the local auxiliary database through RMAN, create a backup database through local backup and recovery data files, and then re-apply the archiving and redo logs during this period.

Configuration document example:

 

Advantages:
1) No downtime required for the master database
2) compared with ACTIVE duplicate, the Network Pressure and database pressure are much lower.
3) using the RMAN backup set duplicate to clone the slave database will greatly shorten the creation time, especially when the database is particularly large.
4) when the target is sent to the master database, you can directly apply the rule logs and redo logs sent from the master database.

Disadvantages:
1) RMAN backup must be performed in the master database in advance.
2) Transfer the backup set to the standby database.

 

Duplicate another application:

Connect to the local auxiliary database through RMAN and restore the RMAN backup set copied from the target database (the target database is not connected ).

This method is not applicable to the creation of recovery uard, and is applicable to the recovery of databases from different machines by RMAN backup.

RMAN backup duplicate recovery database configuration.