This note describes the wait events that monitor the performance of the log
transport modes that were specified on the primary database with the ARCH, LGWR,
SYNC, and ASYNC attributes on the LOG_ARCHIVE_DEST_n initialization parameter.
The wait events and associated timing information are displayed by the
V$SYSTEM_EVENT view, as follows: Wait events for standby destinations configured with the ARCH attribute:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "ARCH wait on ATTACH" This wait event monitors the amount of time spent by all archiver
processes to spawn an RFS connection. "ARCH wait on SENDREQ" This wait event monitors the amount of time spent by all archiver
processes to write the received redo to disk as well as open and close
the remote archived redo logs. "ARCH wait on DETACH" This wait event monitors the amount of time spent by all archiver
processes to delete an RFS connection. Wait events for standby destinations configured with the LGWR SYNC attributes:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "LGWR wait on ATTACH" This wait event monitors the amount of time spent by all log writer
processes to spawn an RFS connection. "LGWR wait on SENDREQ" This wait event monitors the amount of time spent by all log writer
processes to write the received redo to disk as well as open and close
the remote archived redo logs. "LGWR wait on DETACH" This wait event monitors the amount of time spent by all log writer
processes to delete an RFS connection. Wait events for standby destinations configured with the LGWR ASYNC attributes:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "LNS wait on ATTACH" This wait event monitors the amount of time spent by all network servers
to spawn an RFS connection. "LNS wait on SENDREQ" This wait event monitors the amount of time spent by all network servers
to write the received redo to disk as well as open and close the remote
archived redo logs. "LNS wait on DETACH" This wait event monitors the amount of time spent by all network servers
to delete an RFS connection. "LGWR wait on full LNS buffer" This wait event monitors the amount of time spent by the log writer
(LGWR) process waiting for the network server (LNS) to free up ASYNC
buffer space. If buffer space has not been freed in a reasonable amount
of time, availability of the primary database is not compromised by
allowing the archiver process (ARCn) to transmit the redo log data. This
wait event is not relevant for destinations configured with the LGWR
SYNC=PARALLEL attributes. Wait events for standby destinations configured with either the LGWR ASYNC or
LGWR SYNC=PARALLEL attributes:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "LGWR wait on LNS" This wait event monitors the amount of time spent by the log writer (LGWR)
process waiting to receive messages on KSR channels from the network
server. "LNS wait on LGWR" This wait event monitors the amount of time spent by the network server
waiting to receive messages on KSR channels from the log writer (LGWR)
process. "LGWR-LNS wait on channel" This wait event monitors the amount of time spent by the log writer (LGWR)
process or the network server processes waiting to receive messages on
KSR channels.Data Guard Wait Events

Data Guard Wait Events的更多相关文章

  1. Oracle Data Guard Protection Modes

    Maximum Availability This protection mode provides the highest level of data protection that is poss ...

  2. Oracle Data Guard的配置

    概述 Oracle Data Guard 是针对企业数据库的最有效和最全面的数据可用性.数据保护和灾难恢复解决方案.它提供管理.监视和自动化软件基础架构来创建和维护一个或多个同步备用数据库,从而保护数 ...

  3. 场景7 Data Guard

    场景7  Data Guard 官方文档 :Oracle Data Guard Concepts and Administration 用于数据容灾,通过主备库同步(主库将redo日志传送到备库,一个 ...

  4. 【原】Configuring Oracle Data Guard In Physical Standby Database

    作者:david_zhang@sh [转载时请以超链接形式标明文章] http://www.cnblogs.com/david-zhang-index/p/5042640.html参照文档:https ...

  5. DG - 开启Active Data Guard

    在配置active data guard之前,phycial standby必须处于以下两个状态之一: (1)standby处于mount状态,并且redo apply正在运行中 (2)standby ...

  6. DATA GUARD架构(一)

    Data Guard传输-应用架构.>图1-1 ------------------------------------------------------------ 重做传输架构>图1 ...

  7. ORACLE 11g 用Duplicate恢复Data Guard 备库详细过程

    1.先查找备库控制文件路径 先在备库上找出控制文件的路径,通过和主库一样,不过为了以防万一,还是check为好. SQL>  select name from v$controlfile; NA ...

  8. Oracle 11gR2 Database和Active Data Guard迁移案例

    客户一套核心系统由一台Oracle Database 11.2.0.3.4单机和一台Active Data Guard组成,分别运行在两台PC服务器上,Oracle Linux 5.8 x86_64b ...

  9. data guard折腾记一

    终于有空闲的机器腾出来了,生产环境上的一套Oracle环境终于可以鸟枪换炮了,生产环境有Data Guard,为了减少停机时间,而且避免重新构建Data Guard的麻烦(其实也不麻烦,就是浪费时间) ...

随机推荐

  1. Kali更新deb源

    vim /etc/apt/sources.list #中科大deb http://mirrors.ustc.edu.cn/kali kali-rolling main non-free contrib ...

  2. spring MVC @Resource不支持Lazy加载及解决方法

    今天迁一系统时发现有个bean使用@Resource注入了另外一个bean,这个被注入的bean是将被deprecated的类,而且只有一两个功能使用到,为了先调整进行测试,增加了@Lazy注解,启动 ...

  3. tomcat热启动没问题, 访问项目报500解决办法

    新建maven项目 添加热启动 启动访问项目报错 报错提示 解决办法 思路:包冲突 在pom.xml中添加servlet <dependency> <groupId>javax ...

  4. fhq treap抄袭笔记

    目录 碎碎念 点一下 注意!!! 模板 fhq treap 碎碎念 我咋感觉合并这么像左偏树呢 ps:难道你们的treap都是小头堆的吗 fhq真的是神人 现在看以前学的splay是有点恶心,尤其是压 ...

  5. 如何在一台主机上管理自己的多个git repository

    在使用git时,通常是直接ssh-keygen生成默认秘钥.然后将共钥添加到远程仓库,就可以访问了. 但是,当我们有多个repository时,这种方式就不适用了,因为一个秘钥只能关联一个远程仓库. ...

  6. Java之Elasticsearch 增删改查

    <!--ELK --> <dependency> <groupId>org.elasticsearch.client</groupId> <art ...

  7. Ubuntu上 配置Eclipse:安装CDT

    在最新的 Ubuntu Kylin 16.04 中安装了eclipse,在纠结了很久的网络问题之后,开始了eclipse的配置以便在上面运行ns3. 在官方网站上安装完 eclipse LUNA 之后 ...

  8. pyqt 调用颜色选择器

    # -*- coding: utf- -*- from PyQt5.QtWidgets import QApplication, QPushButton, QColorDialog , QWidget ...

  9. python pstats ,profile 性能分析

    #! /usr/bin/env python # encoding=utf8 import pstats import profile def func1(): for i in range(1000 ...

  10. kali删除软件

    kali中主要为2种卸载方法:1.apt2.dpkg 使用apt的方式有:apt-get remove [package]apt-get remove --purge # ------(package ...