Introduction to Data Guard Parameters

Introduction to Data Guard-related parameter description about attributes of arguments parameters the value of n ranges from 1 to 31 in 11g. The following are the attribute values of the parameters) u COMPRESSIONu DB_UNIQUE_NAMEu DELAYu LOCATION and SERVICE (LOCATION is not supported for LOG_ARCHIVE_DEST_11 through LOG_ARCHIVE_DEST_31) u MANDATORY (not supported for through LOG_ARCHIVE_DEST_31) u MAX_CONNECTI ONSu MAX_FAILUREu NET_TIMEOUTu NOREGISTERu REOPENu SYNC and ASYNC (SYNC is not supported for login through LOG_ARCHIVE_DEST_31) u TEMPLATEu VALID_FOR Usage Note: u is in data guard, the target address of the location attribute must be used as the archiving of online and standby redo logs. A remote archiving address is also required. U each LOG_ARCHIVE_DEST_1 to LOG_ARCHIVE_DEST_10 must contain a LOCATION or SERVICE attribute to specify a local disk or remote database for access. Each LOG_ARCHIVE_DEST_11 to LOG_ARCHIVE_DEST_31 must contain a SERVICE attribute. You cannot specify the ALTERNATE redo transport locationu LOG_ARCHIVE_DEST_11 to LOG_ARCHIVE_DEST_31 attribute from u quota to LOG_ARCHIVE_DEST_31. You can only set the parameter to 11.2.0.0 or later in compatible initialization. Affsert and noaffirmaffrem: Specify the target to accept the redo log after writing to the standby redo log. Noaffrem: The redo transfer log can be transferred to the destination before being written to the standby redo log. NOTE: If SYNC is set to affsert as the default value, ASYNC is set to noaffrem as the default value. For example, LOG_ARCHIVE_DEST_3 = 'service = stby1 SYNC affir' ALTERNATE. When the source target address fails, this parameter takes effect to set an archiving target. LOG_ARCHIVE_DEST_1 = 'location =/disk1 MANDATORY MAX_FAILURE = 1 ALTERNATE = LOG_ARCHIVE_DEST_2 'Log _ blank = LOCATION =/disk2 MANDATORY 'Log _ blank = ALTERNATE shows when the network service name fails time, start the standby network name to point to the same standby database LOG_ARCHIVE_DEST_1 = 'location =/disk1 MANDATORY MAX_FAILURE = 1' LOG _ timeout = affinity = 'service = stby1_path1 alterate = LOG_ARCHIVE_DEST_3 'Log _ AR CHIVE_DEST_STATE_2 = region = 'service = stby1_path2 'Log _ ARCHIVE_DEST_STATE_3 = ALTERNATECOMPRESSION this parameter specifies whether to compress the redo data before it is transmitted to a target address. For example, LOG_ARCHIVE_DEST_3 = 'service = denver sync compression = ENABLE 'Log _ ARCHIVE_DEST_STATE_3 = ENABLE DB_UNIQUE_NAME specifies the unique identifier of the database in this destination. DB_UNIQUE_NAME = bostonLOG_ARCHIVE_CONFIG = 'dg _ CONFIG = (chicago, boston, denver) 'Log _ ARCHIVE_DEST_1 = 'location =/arch1/VALID_FOR = (ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME = boston 'Log _ ARCHIVE_DEST_2 = 'service = Sales_DR VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME = chicago 'delay specifies a minimum time DELAY, this delay refers to the time when the redo data is archived to the standby site and the archive log files are applied to the standby database (no delay is required by default ). For a physical standby database: SQL> alter database recover managed standby database nodelay; For a logical standby database: SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY; LOG_ARCHIVE_DEST_1 = 'location =/arch/dest MANDATORY 'Log _ ARCHIVE_DEST_STATE_1 = region = 'service = stbyB SYNC affir' LOG _ region = 'service = stbyC DELAY = 120 'LOG _ ARCHIVE_DEST _ STATE_3 = enable location and SERVICE. When the redo transmission SERVICE can transmit redo data, a LOCATION or SERVICE attribute must be specified for each target to define a local disk or remote database target. Example 1 Specifying the LOCATION partition = 'location =/disk1/oracle/oradata/payroll/arch/'Log _ ARCHIVE_DEST_STATE_2 = ENABLEExample 2 Specifying the SERVICE partition = 'service = stby1' LOG _ ARCHIVE_DEST_STATE_3 = ENABLEMANDATORY specifies that online redo log files must be archived to the destination before being reused. LOG_ARCHIVE_DEST_1 = 'location =/arch/dest MANDATORY 'LOG _ ARCHIVE_DEST_STATE_1 = region = 'service = denver MANDATORY 'Log _ partition = ENABLE MAX_CONNECTIONS when an archive LOG file is applied to a transmission destination, make multiple network connections available. Multiple network connections can improve the redo Transmission Performance in High-latency network connections. If MAX_CONNECTIONS is not specified, the default value is 1. The redo transmission service transmits the redo data to the remote destination using an ARCn process. If this parameter is set to greater than 1, redo transmission uses multiple arcs to archive and redo log files in the parallel zone of your process to remotely. Each ARCn process uses an isolated network connection. LOG_ARCHIVE_DEST_1 = 'location =/arch/dest 'Log _ ARCHIVE_DEST_STATE_1 = region = 'service = denver MAX_CONNECTIONS = 3' LOG _ failure = ENABLE MAX_FAILURE before the master database waives the target LOCATION, control the number of consecutive failed attempts after connecting to a failed redo transfer log. LOG_ARCHIVE_DEST_1 = 'location =/arc_dest REOPEN = 5 MAX_FAILURE = 3' LOG _ Events = ENABLE NOREGISTERIndicates that the LOCATION of the archived redo log file shocould not be recorded at the corresponding destination. LOG_ARCHIVE_DEST_5 = 'noregister 'REOPEN specifies a minimum interval of seconds when the redo transmission service attempts to enable a failed destination. LOG_ARCHIVE_DEST_3 = 'service = stby1 mandatory reopen = 60' LOG _ ARCHIVE_DEST_STATE_3 = enable sync and ASYNC specify synchronous or asynchronous transmission mode. TEMPLATE defines a file format TEMPLATE as an archive redo log. The template name is different from the file name format specified by the LOG_ARCHIVE_FORMAT initialization parameter. It is optional. If it is not specified, the initialization parameter of LOG_ARCHIVE_FORMAT will be used. It is only available for remote targets. The specified TEMPLATE file name must contain % s, % t, and % r indicating that the description can be 15-1 ctictives for the TEMPLATE AttributeDirectiveDescription % tSubstitute the instance thread number. % TSubstitute the instance thread number, zero filled. % sSubstitute the log file sequence number. % SSubstitute the log file sequence number, zero filled. % rSubstitute the resetlogs ID. % RSubstitute the resetlogs ID, zero filled. VALID_FOR specifies whether the database runs in the master or slave database role. Whether online redo log files, standby redo log files, or they will all be archived to The destination the redo_log_type keyword identifies the destination as valid for archiving one of The following: ONLINE_LOGFILE-This destination is valid only when archiving online redo log files. STANDBY_LOGFILE-This destination is valid only when archiving standby redo log files. ALL_LOGFILES-This destination is valid when archiving either online redo l Og files or standby redo log files. the database_role keyword identifies the role in which this destination is valid for archiving: PRIMARY_ROLE-This destination is valid only when the database is running in the primary role. STANDBY_ROLE-This destination is valid only when the database is running in the standby role. ALL_ROLES-This destination is valid when the database is running in either the prima Ry or the standby role. LOG_ARCHIVE_DEST_1 = 'location =/disk1/oracle/oradata VALID_FOR = (ALL_LOGFILES, ALL_ROLES) 'other related parameters: 1. DB_NAME: database name. It must be the same for all databases in the same Data Guard. 2. LOG_ARCHIVE_CONFIG. This parameter lists all DB_UNIQUE_NAME (including primary db and standby db) in the same Data Guard using the DG_CONFIG attribute and is separated by commas. CONTROL_FILES: Specifies the location of the control file. Be sure to change it to the location of the control file. LOG_ARCHIVE_DEST_STATE_n. Specify the parameter value as ENABLE. Activate the defined archive log directory and allow the redo transmission service to transmit redo data to the specified path. REMOT E_LOGIN_PASSWORDFILE. We recommend that you set the parameter value to EXCLUSIVE or SHARED. Ensure that the sys password of all db servers in the same Data Guard configuration is the same. 6. LOG_ARCHIVE_FORMAT: Specifies the format of the archive file, which must be the same on the master and backup ends. LOG_ARCHIVE_MAX_PROCESSES: specifies the number of archiving processes (1-30). The default value is usually 4 8. COMPATIBLE, the oracle version of the primary database and the standby database must be consistent. This parameter specifies the oracle version number 9. FAL_SERVER, a parameter on the slave database, which provides the Oracle network service name. Generally, it is a connection string pointing to the master database. 10. FAL_CLIENT, the parameter of the standby database, which provides the Oracle network service name, usually the connection string 11 pointing to the standby database. DB_FILE_NAME_CONVERT: the data file conversion directory of the primary database and the standby database is mapped (if the directory structure of the two databases is different). If multiple mappings exist Specifying the ing Relationship 12. LOG_FILE_NAME_CONVERT indicates that the log files of the master database and the backup database are replaced by directories 13. STANDBY_FILE_MANAGEMENT. If the data file of the primary database is modified (such as new database creation or renaming), modify it in standby according to the settings of this parameter. AUTO indicates automatic management. Set MANUAL to manually manage 14. STANDBY_ARCHIVE_DEST, the archive directory of the backup database