Refining the Default Behavior
The following underscore parameter was introduced as of 9.2.0.5 to allow the DBA to change this default behavior.:
_LOG_ARCHIVE_CALLOUT='LOCAL_FIRST=TRUE'
If the above parameter is set then the ARCH process will begin archiving to the local destination first. Once the redo log has been
completely and successfully archived to at least one local destination, it will then be transmitted to the remote destination. This is the
default behavior. beginning with Oracle Database 10g Release 1.
Starting in 9.2.0.7 patchsets, one ARCH process will begin acting as a 'dedicated' archiver, handling only local archival duties. It will not perform. remote log shipping or service FAL requests. This is a backport of behavior. from 10gR1 to 9iR2.
一般,对最大性能standby , 9i 下都是从 online redo log 中轮流读1m 到prrimary db本地归档目录,然后再1m到standby归档目录,这样直到读取完一个redo log 为止 ,出现网络极其慢的情况下,tnsping standby不会有返回任何结果(不正常但是又没有error返回), 可能会导致不能读写到 standby , 从而priamry db 不能归档挂起 。
10g没有这种情况,因为它都是在本地归档之后,传输归档到standby , 而不是同时轮替读online redo log到primary 本地与standby 归档目录 。
所以针对9i , oracle给出了参数 _LOG_ARCHIVE_CALLOUT='LOCAL_FIRST=TRUE' 来达到 10g 这个效果 。不是读online redo log 到
standby , 而是优先归档到本地, 然后 " then be transmitted to the remote destination " .
这里的 transmitted to the remote destination , 是否指的是直接类似拷贝本地归档文件到远端standby , 还是读取primary db上的online redo log (只是没有和primary db 一起, 读1m到primary 归档目录, 然后读1m 到standby归档目录,轮流...) ?
[ 本帖最后由 tolywang 于 2009-3-5 11:09 编辑 ]
The following underscore parameter was introduced as of 9.2.0.5 to allow the DBA to change this default behavior.:
_LOG_ARCHIVE_CALLOUT='LOCAL_FIRST=TRUE'
If the above parameter is set then the ARCH process will begin archiving to the local destination first. Once the redo log has been
completely and successfully archived to at least one local destination, it will then be transmitted to the remote destination. This is the
default behavior. beginning with Oracle Database 10g Release 1.
Starting in 9.2.0.7 patchsets, one ARCH process will begin acting as a 'dedicated' archiver, handling only local archival duties. It will not perform. remote log shipping or service FAL requests. This is a backport of behavior. from 10gR1 to 9iR2.
一般,对最大性能standby , 9i 下都是从 online redo log 中轮流读1m 到prrimary db本地归档目录,然后再1m到standby归档目录,这样直到读取完一个redo log 为止 ,出现网络极其慢的情况下,tnsping standby不会有返回任何结果(不正常但是又没有error返回), 可能会导致不能读写到 standby , 从而priamry db 不能归档挂起 。
10g没有这种情况,因为它都是在本地归档之后,传输归档到standby , 而不是同时轮替读online redo log到primary 本地与standby 归档目录 。
所以针对9i , oracle给出了参数 _LOG_ARCHIVE_CALLOUT='LOCAL_FIRST=TRUE' 来达到 10g 这个效果 。不是读online redo log 到
standby , 而是优先归档到本地, 然后 " then be transmitted to the remote destination " .
这里的 transmitted to the remote destination , 是否指的是直接类似拷贝本地归档文件到远端standby , 还是读取primary db上的online redo log (只是没有和primary db 一起, 读1m到primary 归档目录, 然后读1m 到standby归档目录,轮流...) ?
[ 本帖最后由 tolywang 于 2009-3-5 11:09 编辑 ]
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/35489/viewspace-561465/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/35489/viewspace-561465/