List of initialization parameter settings configured in the Data Guard Environment

Initialization parameters related to the Primary role

Db_name	Db_name must be the same in the same DG Environment
Db_unique_name	The db_unique_name parameter is an added parameter for the coexistence of multiple instances with the same db_name on the same computer. If the primary and standby databases of dataguard are installed on different computers, you do not need to set this parameter. If it is installed on the same computer, you need to set it. If this parameter is not set for the instance, after the first instance is started, when the second instance is restarted, the lk <Oracle_sid> file cannot be locked and the second instance cannot be started.
Log_archive_config	It is mainly for redo log transfer and receiving, in maximum availability and maximum protection mode setting will have an impact, not set in switchover switch will report ORA-16047. Use dg_config to list all db_unique_name in the DG Environment: Master database: *. Log_archive_config = 'dg _ config = (master, stdby )' Slave database: *. Log_archive_config = 'dg _ config = (stdby, master )' Note that you are in the front, while others are in the back
Log_archive_dest_n	Define the destination for sending redo. When specifying the location, it indicates that the archiving path is local; when specifying the service, it indicates that the standby database receives the redo. this parameter is the most important! Configuration case: LOG_ARCHIVE_DEST_N = 'service = stdby lgwr sync affrem valid_for = (ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME = stdby'
Log_archive_dest_state = n	Whether redo can be transferred to a specified destination
Remote_login_passwordfile	It is recommended to set exclusive or shared to ensure that the sys password in the same DG Environment is the same

 

 

 

Standby role-related parameters (it is recommended that you set the parameters in the Primary database, so that the new standby can run normally even if the role is changed)

Fal_server Fal_client	FAL_SERVER: used to specify where the archive log is obtained when archive gap occurs. FAL_CLENT: used to automatically send the gap to the location. Client, server at the far end
Db_file_name_convert	When standby and primary have different data file paths, you can set this parameter to enable automatic conversion. This parameter should appear in pairs. The preceding parameter indicates the format before conversion, and the following parameter indicates the format after conversion. That is, the other party is in the front: Db_file_name_convert = '/u01/app/orcl/oradata','/home/oracle'
Log_file_name_convert	The preceding parameter is used only to convert the log file path.
Standby_file_management	If the data file of the master database is modified (such as adding, deleting, or rename), the slave database also makes the corresponding modification. There are two values: auto and manual.

 

 

In DG, the master database and slave database are only role concepts and are not fixed on a database.

Therefore, we recommend that you set the preceding parameters in both the active and standby modes.