Important configuration parameters of Oracle Data Guard

Oracle Data Guard provides one or more slave databases for the production database (a copy of the database ), to ensure that data is not lost when the master database is unavailable or when exceptions occur, and continue to provide services through the slave database. For the configuration of Oracle DG, we can use Grid Control or Data Guard Broker and SQL * Plus. The preceding two methods can be completed on the GUI, which is easy to operate. For the SQL * Plus command line method, we need to perform a lot of configuration, especially some of these parameters. This document describes important parameters for configuring Oracle Data Guard. Next we will refer to Data Guard for short as DG.

Explore Oracle 11g elastic uard

Oracle Data Guard (RAC + DG) archive deletion policies and scripts

Role conversion for Oracle Data Guard

FAL gap in Oracle Data Guard logs

Oracle 11g Data Guard Error 16143 Heartbeat failed to connect to standby

1. Several types of parameters of DG
When configuring DG, there are several different types of parameters, which are generally divided into role-independent parameters, master database role parameters, and backup database role parameters.
Correct settings should be set for these different types of parameters. Otherwise, the DG cannot run normally or the role conversion cannot be implemented normally.
Note: parameter classification of the master and slave databases does not mean that these parameters can only be set in the master database or slave database. If some parameters are switched, the master and slave databases should be set.

2. parameters irrelevant to the role
A. COMPATIBLE = release_number
This parameter is used to set version compatibility parameters. The same value must be specified. Otherwise, the switchover fails and the redo transmission fails.

B. DB_NAME = database name
This parameter is common and must be the name of any database. Note: In the same DG, all roles have the same DB_NAME.
For example, *. db_name = 'oradb'

C. DB_UNIQUE_NAME = Unique name for the database
The unique name of the database, which corresponds to DB_NAME. This is a logical name that corresponds to the database instance name, which is equal to DB_NAME by default.
If LOG_ARCHIVE_CONFIG is configured, it is recommended to set it to a unique value. This parameter will not be changed when the primary and backup roles change.
Master Database: *. db_unique_name = 'oradb'
Slave Database: *. db_unique_name = 'oradbdg'

D. LOG_ARCHIVE_CONFIG = 'dg _ CONFIG (db_unique_name, db_unique_name ,...)'
This parameter is used to define a list of all valid DB_UNIQUE_NAME names in the DG. It is separated by commas to provide security checks for the DG. We recommend that you always configure this parameter.
The master database and slave database use the same settings.
Master Database: *. log_archive_config = 'dg _ CONFIG = (oradb, oradbdg )'
Slave Database: *. log_archive_config = 'dg _ CONFIG = (oradb, oradbdg )'

E. CONTROL_FILES = 'control _ file_name ', 'control _ file_name ','...'
This parameter is used to define the location of the control file and modify it based on the path of the master and slave databases. For more information, see Oracle control file)

F, LOG_ARCHIVE_MAX_PROCESSES = integer
This parameter defines the number of processes used for archiving.
On the master database, the archiving process is used to archive online redo log files and to process the interval between redo log streams in the slave database.
On the slave database, the archiving process archives Standby Redo logs and forwards the archived logs to the cascade slave database.
We recommend that you set the minimum value of this parameter to 4 and the maximum value to 30.

G, LOG_ARCHIVE_FORMAT = log % d _ % t _ % s _ % r. arc
This parameter is used to define the format of archived logs.

H. REMOTE_LOGIN_PASSWORDFILE = {EXCLUSIVE | SHARED}
This parameter is used to set the authentication method. We recommend that you set the parameter value to EXCLUSIVE or SHARED. Ensure that all db servers in the same Data Guard configuration have the same sys password.
For more information about this parameter, see the Oracle password file.
Master Database: *. REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE
Slave Database: *. REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE

1 2 Next Page