_log_archive_callout
First of all the problem with the destination being stuck at the OS level should
be resolved.
Secondly you can change the above outlined archiver behavior, to make sure the local destination is archived first, causing the OPTIONAL destination to behave really optional. If the following 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.
For 9iR2 (9.2.0.5 and above):
_log_archive_callout='LOCAL_FIRST=TRUE'
--OR--
alter system set "_LOG_ARCHIVE_CALLOUT"='LOCAL_FIRST=TRUE' scope=both;
In Oracle 10g this parameter is replaced by 'log_archive_local_first', which defaults to TRUE[@more@]_log_archive_callout
Secondly you can change the above outlined archiver behavior, to make sure the local destination is archived first, causing the OPTIONAL destination to behave really optional. If the following 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.
For 9iR2 (9.2.0.5 and above):
_log_archive_callout='LOCAL_FIRST=TRUE'
--OR--
alter system set "_LOG_ARCHIVE_CALLOUT"='LOCAL_FIRST=TRUE' scope=both;
In Oracle 10g this parameter is replaced by 'log_archive_local_first', which defaults to TRUE[@more@]_log_archive_callout
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/48010/viewspace-1030367/ ，如需转载，请注明出处，否则将追究法律责任。
请登录后发表评论
登录
全部评论
