Shulou(Shulou.com)06/01 Report--

Deployment of Data Guard-related parameters, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Compare and describe the parameters used by the master and slave libraries in the process of deploying Data Guard.

1.DB_NAME, database name, needs to keep all databases in the same Data Guard the same DB_NAME

The primary end is the same as the standby side

* .DB_NAME='ora10g'

* .DB_NAME='ora10g'

2.DB_UNIQUE_NAME, which corresponds to the instance name of the database. Each database needs to specify a unique name.

Primary side:

* .DB_UNIQUE_NAME=ora10g

Standby side:

* .db_unique_name=ora10gdg

3.LOG_ARCHIVE_CONFIG, which lists all DB_UNIQUE_NAME (including primary db and standby db) in the same Data Guard by the DG_CONFIG attribute, separated by commas

The primary end is the same as the standby side

* .LOG_ARCHIVE_CONFIG='DG_CONFIG= (ora10g,ora10gdg)'

* .LOG_ARCHIVE_CONFIG='DG_CONFIG= (ora10g,ora10gdg)'

4.CONTROL_FILES, control file location description, pay attention to modify to specific control file location

Primary side:

* .control_files='/oracle/u02/oradata/ORA10G/controlfile/o1_mf_4srph8fv_.ctl','/oracle/u01/app/oracle/flash_recovery_area/ORA10G/controlfile/o1_mf_4srph96b_.ctl'

Standby side:

* .control_files='/oracle/u02/oradata/ORA10GDG/controlfile/o1_mf_4srph8fv_.ctl','/oracle/u01/app/oracle/flash_recovery_area/ORA10GDG/controlfile/o1_mf_4srph96b_.ctl'

5.LOG_ARCHIVE_DEST_n, the generation path of the archive file. Location represents the local machine, and service indicates that it is on another machine.

Primary side:

* .LOG_ARCHIVE_DEST_1='LOCATION=/oracle/u02/oradata/ORA10G VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ora10g'

* .LOG_ARCHIVE_DEST_2='SERVICE=ora10gdg LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ora10gdg'

Standby side:

* .LOG_ARCHIVE_DEST_1='LOCATION=/oracle/u02/oradata/ORA10GDG VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ora10gdg'

* .LOG_ARCHIVE_DEST_2='SERVICE=ora10g LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ora10g'

6.LOG_ARCHIVE_DEST_STATE_n, specify the parameter value as ENABLE, activate the defined archive log directory, and allow the redo transport service to transfer redo data to the specified path

Primary side:

* .LOG_ARCHIVE_DEST_STATE_1=ENABLE

* .LOG_ARCHIVE_DEST_STATE_2=ENABLE

Standby side:

* .LOG_ARCHIVE_DEST_STATE_1=ENABLE

* .LOG_ARCHIVE_DEST_STATE_2=ENABLE

7.REMOTE_LOGIN_PASSWORDFILE. It is recommended to set the parameter value to EXCLUSIVE or SHARED. Make sure that all db servers in the same Data Guard configuration have the same sys password.

Primary side:

* .REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE

Standby side:

* .REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE

8.LOG_ARCHIVE_FORMAT, which specifies the format of the archive file. Here, the same format should be maintained on the master / slave end.

Primary side:

* .LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc

Standby side:

* .LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc

9.LOG_ARCHIVE_MAX_PRODUC, which specifies the number of archiving processes (1-30). The default value is usually 4

This parameter is not modified in this experiment.

10.COMPATIBLE, the oracle version of the primary database and standby database must be the same. This parameter indicates the version number of the oracle.

Primary side:

* .COMPATIBLE='10.2.0.3.0'

Standby side:

* .COMPATIBLE='10.2.0.3.0'

11.FAL_SERVER, the parameter of the slave database, and the Oracle network service name, which is usually the connection string pointing to the main library.

Primary side (the master database is set up for the exchange of master and slave roles after switching):

* .FAL_SERVER=ora10gdg

Standby side:

* .FAL_SERVER=ora10g

12.FAL_CLIENT, the parameter of slave end, and the name of Oracle network service, which is usually the connection string pointing to slave database.

Primary side (the master database is set up for the exchange of master and slave roles after switching):

* .FAL_CLIENT=ora10g

Standby side:

* .FAL_CLIENT=ora10gdg

13.DB_FILE_NAME_CONVERT, data file conversion directory mapping of the primary database and standby database (if the directory structure of the two databases is different), if there are multiple mappings, indicate the mapping relationship one by one

Format: * .db _ file_name_convert= main database data file directory, standby database data file directory

Primary side (the master database is set up for the exchange of master and slave roles after switching):

* .DB_FILE_NAME_CONVERT='/oracle/u02/oradata/ORA10GDG/datafile','/oracle/u02/oradata/ORA10G/datafile'

Standby side:

* .DB_FILE_NAME_CONVERT='/oracle/u02/oradata/ORA10G/datafile','/oracle/u02/oradata/ORA10GDG/datafile'

14.LOG_FILE_NAME_CONVERT, indicating the log file conversion directory mapping of the primary and standby databases

Format: *. Log_file_name_convert= primary database log directory, standby database directory

Primary side (the master database is set up for the exchange of master and slave roles after switching):

* .LOG_FILE_NAME_CONVERT='/oracle/u02/oradata/ORA10GDG/onlinelog','/oracle/u02/oradata/ORA10G/onlinelog'

Standby side:

* .LOG_FILE_NAME_CONVERT='/oracle/u02/oradata/ORA10G/onlinelog','/oracle/u02/oradata/ORA10GDG/onlinelog'

15.STANDBY_FILE_MANAGEMENT, if the primary database data file is modified (such as new, renamed, etc.), it will be modified in standby according to the settings of this parameter. Set to AUTO to indicate automatic management. Setting it to MANUAL means manual management is required.

Primary side (the master database is set up for the exchange of master and slave roles after switching):

* .STANDBY_FILE_MANAGEMENT=AUTO

Standby side:

* .STANDBY_FILE_MANAGEMENT=AUTO

16.STANDBY_ARCHIVE_DEST, the archive log archive directory of the standby database

Primary side (the master database is set up for the exchange of master and slave roles after switching):

* .standby_archive_dest='/ora10g_arch'

Standby side:

* .standby_archive_dest='/ora10gdg_arch'

17. Summary

For more parameter description of Data Guard, please refer to the official Oracle document: http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/init_params.htm#i88512

An in-depth and detailed understanding of the database parameters used to deploy Data Guard not only helps us understand the principles of physical Data Guard, but also helps us to troubleshoot Data Guard-related problems.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.