Data Guard parameters Tips

Oracle Database Tips by Donald BurlesonDecember 3, 2015

Oracle Data Guard Initialization Parameters

LOG_ARCHIVE_DEST_2='SERVICE=<Name of service for standby database>
LOG_ARCHIVE_DEST_STATE_2=ENABLE

The initialization parameter file for the Data Guard Oracle instance are essentially three key Data Guard parameters that should be added. These are as follows:

lock_name_space
db_file_name_convert
log_file_name_convert

These are the primary Data Guard init.ora parameters:

lock_name_space: The lock_name_space parameter defines the namespace that the distributed lock manager uses to generate lock names. The value of the lock_name_space parameter should be set to a distinct value so that the lock names between the primary and the Oracle instance do not collide.
db_file_name_convert : The db_file_name_convert parameter is used to convert the filename on the primary database to a filename on the standby database. The value of db_file_name_convert should be set in a pair of strings. The first string should correspond to the filename pattern on the primary database and the next string of db_file_name_convert to the filename pattern on the standby database. More than one pair can be specified in db_file_name_convert if there is a need to accommodate more than one pattern in filename changes between the primary and the standby database.
log_file_name_convert: The log_file_name_convert parameter works similarly to db_nfile_name_convert on the redo log files. Thielog_file_name_convert parameter is not required until the Oracle instance is activated, but there is no harm in placing tlog_file_name_convert in your init.ora file so that during the activation there will be minimal work for you.