Got some warnings from the alert log。
Tue Mar 8 13:45:26 2011
Starting control autobackup
Control autobackup written to DISK device
handle '/global/oracle3/ORADUMP/ARSPRD/backup/ARSPRD_rman_ctrl_c-909397006-20110308-01.bak'
Tue Mar 8 20:00:34 2011
Thread 1 advanced to log sequence 24677
Tue Mar 8 20:00:34 2011
ARC0: Evaluating archive log 1 thread 1 sequence 24676
Tue Mar 8 20:00:34 2011
Current log# 2 seq# 24677 mem# 0: /global/oracle/oradata1/ARSPRD/redo02.log
Tue Mar 8 20:00:34 2011
ARC0: Beginning to archive log 1 thread 1 sequence 24676
Creating archive destination LOG_ARCHIVE_DEST_1: '/global/oracle/oradump1/ARSPRD/archive/arch1_24676.dbf'
Tue Mar 8 20:00:36 2011
ARC1: Evaluating archive log 1 thread 1 sequence 24676
ARC1: Unable to archive log 1 thread 1 sequence 24676
Log actively being archived by another process
Tue Mar 8 20:00:43 2011
ARC0: Completed archiving log 1 thread 1 sequence 24676
Wed Mar 9 01:00:06 2011
Thread 1 advanced to log sequence 24678
Wed Mar 9 01:00:06 2011
Current log# 3 seq# 24678 mem# 0: /global/oracle/oradata1/ARSPRD/redo03.log
Wed Mar 9 01:00:06 2011
ARCH: Evaluating archive log 2 thread 1 sequence 24677
Wed Mar 9 01:00:06 2011
ARC0: Evaluating archive log 2 thread 1 sequence 24677
ARC0: Unable to archive log 2 thread 1 sequence 24677
Wed Mar 9 01:00:06 2011
ARCH: Beginning to archive log 2 thread 1 sequence 24677
Wed Mar 9 01:00:06 2011
Log actively being archived by another process
Wed Mar 9 01:00:06 2011
Creating archive destination LOG_ARCHIVE_DEST_1: '/global/oracle/oradump1/ARSPRD/archive/arch1_24677.dbf'
ARCH: Completed archiving log 2 thread 1 sequence 24677
Wed Mar 9 01:00:16 2011
Thread 1 advanced to log sequence 24679
Wed Mar 9 01:00:16 2011
ARCH: Evaluating archive log 3 thread 1 sequence 24678
Wed Mar 9 01:00:16 2011
Current log# 1 seq# 24679 mem# 0: /global/oracle/oradata1/ARSPRD/redo01.log
Wed Mar 9 01:00:16 2011
ARC1: Evaluating archive log 3 thread 1 sequence 24678
Wed Mar 9 01:00:16 2011
ARC1: Unable to archive log 3 thread 1 sequence 24678
Wed Mar 9 01:00:16 2011
ARCH: Beginning to archive log 3 thread 1 sequence 24678
Seems that there are two arch processes want to archive one archive logs.
The ARC0 has done it then ARC1 is unable to archive it again.
So we should cut off one if there are really two processes to archive logs.
Check it:
$ ps -ef|grep ora_arc
oracle 3463 1 0 May 26 ? 73:39 ora_arc0_ARSPRD
oracle 3465 1 0 May 26 ? 0:11 ora_arc1_ARSPRD
oracle 21125 20978 0 01:43:08 pts/1 0:00 grep ora_arc
SQL> show parameter log_archive_max_processes
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_max_processes integer 2
SQL>
Read the Note:
Purpose
When archiving locally and remotely using the ARCH process where the
remote destination is across a saturated or slow network you can receive
the following errors in the alert log:
ARC0: Evaluating archive log 2 thread 1 sequence 100
ARC0: Unable to archive log 2 thread 1 sequence 100
Log actively being archived by another process
If the ARCH process is unable to archive at the rate at which online
logs are switched then it is possible for the primary database to
suspend while waiting for archiving to complete.The following
discussion describes how this can occur.
Default Behavior for 9iR2 and Below
The ARCH process sits in a very tight loop waiting for an update to the
controlfile that states an online log needs to be archived.Once the
update occurs the ARCH process builds a list of archive destinations
that need to be serviced.Once this list is complete, the ARCH process
will read a one megabyte chunk of data from the online log that is to be
archived.This one megabyte chunk is then sent to the first
destination in the list.When the write has completed, the same one
megabyte chunk is written to the second destination.This continues
until all of the data from the online log being archived has been
written to all destinations.So it can be said that archiving is only
as fast as the slowest destination.
A common misconception is that if the LOG_ARCHIVE_DEST_n parameter for a
particular destination has the OPTIONAL attribute set, then that
destination will not impede local archiving. This is true during error
situations while archiving to that destination - e.g. a network
disconnect error, but not during an archival over a slow network, which
is not an error situation. In error situations, whether the destination
is marked OPTIONAL or MANDATORY, Data Guard will close that destination
and continue transmitting to all other valid destinations. Transmitting
to the closed destination will be attempted again only after the time
specified in the REOPEN attribute has expired and a log switch has
occurred.This process will continue for the number of times specified
by the MAX_FAILURE attribute. During this time, it is possible that the
log writer process recycles through the available online redo log groups
and tries to use the online redo log file which has not yet been
transmitted successfully to the remote destination. If the destination
is marked OPTIONAL, log writer will reuse the online redo log file for
the next set of redo. If the destination is marked MANDATORY,log
writer will not be able to reuse that online redo log file, and the
primary database will delay processing until that online redo log file
has been successfully transmitted to the remote destination.
However, the situation is very different if the transmission is being
done over a slow network. In this case, no error is encountered and the
destination is not closed. Transmission continues, but is very slow.
Ultimately, with the unavailability of any more online redo log groups,
Log writer may suspend because the archive process is taking a long time
to complete its archival, including local archival.
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.
From Metalink: 260040.1
分享到:
相关推荐
.arch!)清理残留.bat
This document will guide you through the process of installing Arch Linux using the Arch Install Scripts (https://github.com/falconindy/arch-install-scripts) . Before installing, you are advised to ...
Construction of the Hoover dam arch bridge.
Unknown error: Unable to build: the file dx.jar was not loaded from the SDK folder! 问题的缺失文件 eclipse.buildId=M20100211-1343 java.version=1.6.0_10-rc2 java.vendor=Sun Microsystems Inc. ...
What’s Inside the CloudAn Architectural Map of the Cloud Landscape
股票波动率预测ar-arch模型.#拟合均值方程和方差方程 #拟合AR(4)-GARCH(3,0)模型[AR(4)- ARCH(3)模型]
.arch录制教程★★★★★必看!!!.mp4
arch arch提供了Univariate volatility模型,Bootstrapping和Multiple comparison procedures
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. 网上的方法都是在CentOS下进行的,而我用的是Deepin系统,也就是基于Ubuntu/Debian的发行版...
A superb arch pic!!!
1、添加blackarch软件源 sudo gedit /etc/pacman.conf 如果没有gedit命令,运行 sudo pacman -S gedit 也可以用vim 添加以下内容: [blackarch] SigLevel = TrustAll Server = https://mirrors.tuna.tsinghua.e
变系数ARCH-M模型的ARCH效应检验,熊强, 李元,本文考虑变系数ARCH-M模型, 构造了非参数部分和参数部分的截面似然估计. 基于估计的渐近性质, 构造了Wald检验统计量来检验模型是否具�
arch4 ins
dirs3arch 是一个命令行工具,设计的目标是暴力破解网站的文件与目录。
arch wiki 离线版本,可以直接察看index.html然后搜索需要的关键词来查询内容.更多介绍可以访问奶牛博客
Arch Linux - 桌面环境 安装完基本系统后已经成功了一半,现在开始安装桌面环境以应用日常。
Lwip之Arch目录.pdf
Archway
BlackArch Linux 简体中文手册 202103 版本
本文档将指导您安装 Arch Linux:一个简单、轻量级、适合计算机水平较高用户使用的发行版。本向导写给 Arch 新用户,但是会尽量做到成为所有用户的参考和信息库。