ITPub博客

首页 > 数据库 > Oracle > LOG_ARCHIVE_DEST_n参数选项简单小记

LOG_ARCHIVE_DEST_n参数选项简单小记

原创 Oracle 作者:流浪的野狼 时间:2014-02-08 10:50:03 0 删除 编辑

 

LOG_ARCHIVE_DEST_n

Property  Description

Parameter type  String

Syntax LOG_ARCHIVE_DEST_[1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10] =

 { null_string |

 { LOCATION=path_name | SERVICE=service_name }

 [ MANDATORY ]

 [ REOPEN[=seconds] ]

 [ DELAY[=minutes] ]

 [ NOREGISTER ]

 [ TEMPLATE=template ]

 [ ALTERNATE=destination ]

 [ DEPENDENCY=destination ]

 [ MAX_FAILURE=count ]

 [ SYNC | ASYNC ]

 [ AFFIRM | NOAFFIRM ]

 [ NET_TIMEOUT=seconds ]

 [ VALID_FOR=(redo_log_type,database_role) ]

 [ DB_UNIQUE_NAME ]

 [ MAX_CONNECTIONS=count ]

 [ COMPRESSION={ENABLE|DISABLE} ]

 }

Default value   There is no default value.

Modifiable   Most attributes are modifiable by ALTER SESSION and ALTER SYSTEM, but some are not. See Oracle Data Guard Concepts and Administration for further information.

Basic Yes

The LOG_ARCHIVE_DEST_n initialization parameter defines up to 10 (where n = 1, 2, 3, ... 10) destinations, each of which must specify either the LOCATION or the SERVICE attribute to specify where to archive the redo data. All other attributes are optional. Note that whether you are specifying the LOCATION attribute or the SERVICE attribute, it must be the first attribute supplied in the list of attributes.

If you choose not to enter any attributes, then you can specify a NULL string by entering the following:

LOG_ARCHIVE_DEST_n=' ';

You set the attributes for the LOG_ARCHIVE_DEST_n initialization parameter to control different aspects of how redo transport services transfer redo data from a production or primary database destination to another (standby) database destination. You can query the V$ARCHIVE_DEST view to see the current attribute settings for each destination (n).

注:虽然此处说明该参数的n值是从1----10,但是在查看数据库是你可能会看到达到了31,如下,真正在设置该参数时通常最多设置10个:

SQL> sho parameter log_archive_dest_state

NAME                                     TYPE        VALUE

-------------------------------     -----      -----------

log_archive_dest_state_1             string      enable

log_archive_dest_state_10            string      enable

log_archive_dest_state_11            string      enable

log_archive_dest_state_12            string      enable

log_archive_dest_state_13            string      enable

log_archive_dest_state_14            string      enable

log_archive_dest_state_15            string      enable

log_archive_dest_state_16            string      enable

log_archive_dest_state_17            string      enable

log_archive_dest_state_18            string      enable

log_archive_dest_state_19            string      enable

log_archive_dest_state_2             string      enable

log_archive_dest_state_20            string      enable

log_archive_dest_state_21            string      enable

log_archive_dest_state_22            string      enable

log_archive_dest_state_23            string      enable

log_archive_dest_state_24            string      enable

log_archive_dest_state_25            string      enable

log_archive_dest_state_26            string      enable

log_archive_dest_state_27            string      enable

log_archive_dest_state_28            string      enable

log_archive_dest_state_29            string      enable

log_archive_dest_state_3             string      enable

log_archive_dest_state_30            string      enable

log_archive_dest_state_31            string      enable

log_archive_dest_state_4             string      enable

log_archive_dest_state_5             string      enable

log_archive_dest_state_6             string      enable

log_archive_dest_state_7             string      enable

log_archive_dest_state_8             string      enable

log_archive_dest_state_9             string      enable

Note:

Some of the attributes for this parameter are deprecated, but are being retained for backward compatibility. See "Deprecated Attributes for LOG_ARCHIVE_DEST_n".

For every LOG_ARCHIVE_DEST_n initialization parameter that you define, you must specify a corresponding LOG_ARCHIVE_DEST_STATE_n parameter. The LOG_ARCHIVE_DEST_STATE_n (where n is an integer from 1 to 10) initialization parameter specifies whether the corresponding destination is currently enabled or disabled.

See Also:

"LOG_ARCHIVE_DEST_STATE_n"--------该参数控制归档位置的状态。如:deferenable…..

Values:

See Also:

Oracle Data Guard Concepts and Administration for detailed descriptions of all the values listed in this section

AFFIRM and NOAFFIRM

Control whether or not redo transport services use synchronous or asynchronous disk I/O to write redo data to the archived redo log files. The default is NOAFFIRM.

ALTERNATE=LOG_ARCHIVE_DEST_n------一看英文意思就知道是两个中二选一的意思,不过此处略有不同,是在原先的归档位置不可用的情况下使用第二个归档目录。

Specifies an alternate archiving destination to be used when the original destination fails. There is no default value; if an alternate destination is not specified, then archiving does not automatically change to another destination if the original destination fails.

ASYNC---------指定异步归档,与SYNC反向对应。

The redo data generated by a transaction need not have been received at a destination which has this attribute before that transaction can commit. This is the default behavior if neither SYNC nor ASYNC is specified.

COMPRESSION----------指定归档之前是否先压缩redo数据。

Indicates whether network compression is enabled or disabled.

DB_UNIQUE_NAME=name

Specifies a unique name for the database at this destination. You must specify a name; there is no default value.

DELAY[=minutes]------指定standby 端接受完数据后redo数据应用的时间,仅用于物理standby,默认30分钟。

Specifies a time lag between when redo data is archived on a physical standby site and when the archived redo log file is applied to the physical standby database. You cannot set the DELAY attribute for a logical standby database destination. If you specify the DELAY attribute without a time interval, the default is 30 minutes.

DEPENDENCY=LOG_ARCHIVE_DEST_n-------指定归档日志在多个standby上的共享。

Defines one archival destination to receive redo data on behalf of several destinations. Redo transport services transmit redo data to the destination that then shares its archived redo log files with multiple standby databases.

LOCATION=local_disk_directory or USE_DB_RECOVERY_FILE_DEST-----指定本地归档位置,如设置为USE_DB_RECOVERY_FILE_DEST,则使用闪回区,并采用OMF格式。

Specifies either a local file system destination or the directory, file system, or Automatic Storage Manager disk group that will serve as the flash recovery area. You must specify this attribute for at least one destination. You can specify either a local disk directory or flash recovery area with the LOCATION attribute. You must include either the LOCATION or the SERVICE attribute for each destination to specify where to archive the redo data.

MANDATORY--------强制在该位置归档成功与optional对应。

Specifies that the transmission of redo data to the destination must succeed before the local online redo log file can be made available for reuse. If the MANDATORY attribute is not specified, then the destination is optional.

MAX_CONNECTIONS-----归档位置的网络最大连接数。

Specifies the maximum number of network connections that can be used to transmit redo data to this destination. The default is 1.

MAX_FAILURE--------在失败的归档位置的最大尝试连接次数。

Controls the consecutive number of times redo transport services attempt to reestablish communication and transmit redo data to a failed destination before the primary database permanently gives up on the standby database.

NET_TIMEOUT=seconds-----网络超时。

Specifies the number of seconds the log writer process on the primary system waits for status from the network server (LNSn) process before terminating the network connection. The default is 30 seconds.

NOREGISTER-----------归档日志登记。

Indicates that the location of the archived redo log file is not to be recorded at the corresponding destination.

REOPEN[=seconds]---------失败归档位置再次尝试时的等待时间。

Specifies the minimum number of seconds before the archiver processes (ARCn) or the log writer process (LGWR) should try again to access a previously failed destination. The default is 300 seconds.

SERVICE=net_service_name----------目标位置上的网络服务名

Specifies a valid Oracle Net service name (SERVICE=net_service_name) that identifies the remote Oracle database instance to which redo data will be sent. Each destination must specify either the LOCATION or the SERVICE attribute. There is no default net service name.

SYNC------------同步归档。

The redo data generated by a transaction must have been received by every enabled destination which has this attribute before that transaction can commit.

TEMPLATE=filename_template_%t_%s_%r

Specifies a pathname and a filename template for archived redo log files created at a redo transport destination that contain redo data from the database where this attribute is specified. This attribute overrides the value of the LOG_ARCHIVE_FORMAT initialization parameter at a redo transport destination. This attribute does not have a default value.

VALID_FOR=(redo_log_type, database_role)-------归档日志类型及使用该位置的数据库角色。

Identifies when redo transport services can transmit redo data to destinations based on the following factors:

redo_log_type—whether online redo log files, standby redo log files, or both are currently being archived on the database at this destination

database_role—whether the database is currently running in the primary or the standby role

Deprecated Attributes for LOG_ARCHIVE_DEST_n

The following attributes are deprecated for the LOG_ARCHIVE_DEST_n parameter. They are retained for backward compatibility only.

Table 1-2 Deprecated Attributes on the LOG_ARCHIVE_DEST_n Initialization Parameter

Deprecated Attribute  Alternative

ARCH------------默认的日志传输方式:归档后传输归档日志。

Specify SYNC or ASYNC. ASYNC is the default if neither attribute is specified.

LGWR-----------通过LGWR进程传输redo日志信息,分为同步于异步。

Specify SYNC or ASYNC. ASYNC is the default if neither attribute is specified.

OPTIONAL-------归档位置可选。

Destinations are optional by default.

VERIFY

None. This attribute is only used with the deprecated ARCH attribute.

In addition, note the following changes to the ASYNC and SYNC attributes:

The BLOCKS keyword on the ASYNC attribute is no longer needed.

It is no longer necessary to set this keyword because Data Guard dynamically adjusts the block count up or down to an appropriate number of blocks, as necessary.

The PARALLEL and NOPARALLEL keywords on the SYNC attribute are no longer needed.

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/28612416/viewspace-1077931/,如需转载,请注明出处,否则将追究法律责任。

下一篇: rman备份类型
请登录后发表评论 登录
全部评论

注册时间:2013-04-10

  • 博文量
    151
  • 访问量
    1511528