[Dg] Configuration parameters explanation Dataguard

1. DB_NAME, database name, a need to maintain the same DB_NAME DataGuard all main libraries and libraries of the same physical apparatus

end of the same primary and standby side:

*.DB_NAME='WENDING'

2. DB_UNIQUE_NAME, each database you need to specify a unique name (can be easily defined, does not affect the db_name and instance_name)

primary端:
*.DB_UNIQUE_NAME=WENDING

standby端:
*.db_unique_name=WDSTD

3. LOG_ARCHIVE_CONFIG, the same parameter lists all the DB_UNIQUE_NAME DataGuard (including the master library and library equipment) by DG_CONFIG property, separated by commas

primary side and standby side before the comma in the same :( who, who does not affect the comma)
* .LOG_ARCHIVE_CONFIG = '= the DG_CONFIG (Wending, WDSTD)'

Generating path 4. LOG_ARCHIVE_DEST_n, archive, on behalf of the local LOCATION machine, specified in the SERVICE on another machine, the value of the service is an alias tns

primary端:
*.LOG_ARCHIVE_DEST_1='LOCATION=/u01/arch/WENDING VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=WENDING'
*.LOG_ARCHIVE_DEST_2='SERVICE=DB_WDSTD LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=WDSTD'

standby端:
*.LOG_ARCHIVE_DEST_1='LOCATION=/u01/arch/WDSTD VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=WDSTD'
*.LOG_ARCHIVE_DEST_2='SERVICE=DB_WENDING LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=WENDING'

5. AFFIRM、NOAFFIRM 、VALID_FOR

AFFIRM: Before LogWriter carried out, so the archive log and backup log database must be synchronized to finish
NOAFFIRM: write in the log process ranging from the main library to complete all disk IO

The default is ANOFFIRM

VALID_FOR attribute specifies the transmission and reception objects

redo_log_type can be set to: ONLINE_LOGFILE, STANDBY_LOGFILE, ALL_LOGFILES

database_role can be set to: PRIMARY_ROLE, STANDBY_ROLE, ALL_ROLES

Default: valid_for = (ALL_LOGFILES, ALL_ROLES)

6. LOG_ARCHIVE_DEST_STATE_n, the ENABLE specified parameter value, activating defined archive log directory, allowing redo redo data transmission service transmitted to the specified path

primary端:
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE

standby端:
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE

7. REMOTE_LOGIN_PASSWORDFILE, the parameter value recommended EXCLUSIVE or SHARED, the same care to ensure that all of the same configuration DataGuard db server password sys

end of the same primary and standby side:
* = EXCLUSIVE .REMOTE_LOGIN_PASSWORDFILE

8. LOG_ARCHIVE_FORMAT, archive specified file format, the same format is preferably maintained where the primary and secondary side

end of the same primary and standby side:
* = .LOG_ARCHIVE_FORMAT LOG_ T_%%% r.arc S_ 

 

9. db_file_name_convert、log_file_name_convert

 

*.db_file_name_convert:

And the primary standby inconsistent datafile and tempfile path, can let it automatically switched by setting this parameter, the other in front of a front conversion path, behind a rear convert their path. It was prepared by the library parameters

If the primary library data file a plurality of paths, is set as follows

* .Db_file_name_convert = 'main path 1', 'backup path 1', 'main path 2', 'backup path 2'

If the master has the file path db01.dbf 1 2 includes a main path, such as / master / db case, there is the document db02.dbf / master / db / db2, or is provided as described above, not only set * .db_file_name_convert = 'main path 1 ',' equipment path 1 ', because the backup path 1 below does not automatically re-establish / db2 directory, because this parameter is for the file, not your directory terms

 

*.log_file_name_convert:

It was prepared by the library parameters

And the primary standby inconsistent online redo log file (excluding archive log) path, may be allowed to automatically converted by the parameter setting, the other in front of a front conversion path, behind a rear convert their path.

If each group online redo log of a plurality of main library member, is set as follows

* .Log_file_name_convert = 'main path 1', 'backup path 1', 'main path 2', 'backup path 2'

*.log_file_name_convert='+DATA/testdb/onlinelog','/orasoft/ora11g/log','+ARCH/testdb/onlinelog','/orasoft/ora11g/log2’

 

db_file_name_convert: Data File (dba_data_files contain undo) and temporary data files

LOG_FILE_NAME_CONVERT : online log does not contain the archive log

db_file_name_convert parameter only applies to physical standby and RMAN Duplicate , for logical standby and normal rman restore invalid;

log_file_name_convert parameter only applies to physical standby and rman duplicate, but can not duplicate the run command directly run

 

* .Fal_client and * .fal_server

Was prepared by the library parameter, the value of their own former, the latter value is the other side, the value is an alias tns

 

 

*.STANDBY_FILE_MANAGEMENT

Library is prepared parameter set to * .STANDBY_FILE_MANAGEMENT = 'AUTO'

Guess you like

Origin blog.csdn.net/viviliving/article/details/91868373