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. 高可用Mysql架构_Mysql主从复制、Mysql双主热备、Mysql双主双从、Mysql读写分离(Mycat中间件)、Mysql分库分表架构(Mycat中间件)的演变

    [Mysql主从复制]解决的问题数据分布:比如一共150台机器,分别往电信.网通.移动各放50台,这样无论在哪个网络访问都很快.其次按照地域,比如国内国外,北方南方,这样地域性访问解决了.负载均衡:M ...

  2. django session 使用案例

    django session 使用案例 HTTP被设计为”无状态”,每次请求都处于相同的空间中. 在一次请求和下一次请求之间没有任何状态保持,我们无法根据请求的任何方面(IP地址,用户代理等)来识别来 ...

  3. noip2016普及组题解和心得

    前言 感觉稍微有些滑稽吧,毕竟每次练的题都是提高组难度的,结果最后的主要任务是普及组抱一个一等奖回来.至于我的分数嘛..还是在你看完题解后写在[后记]里面.废话不多说,开始题解. (其实这篇博客只有题 ...

  4. cmd命令分类

    1.系统功能类 AT:计划在计算机上运行的命令和程序.ATTRIB:显示或更改文件属性.BREAK:设置或清除扩展式 CTRL+C 检查.CACLS:显示或修改文件的访问控制列表(ACLs).CALL ...

  5. python中的迭代器和生成器学习笔记总结

    生成器就是一个在行为上和迭代器非常类似的对象.   是个对象! 迭代,顾名思意就是不停的代换的意思,迭代是重复反馈过程的活动,其目的通常是为了逼近所需目标或结果.每一次对过程的重复称为一次“迭代”,而 ...

  6. Python3基础 list reversed 列表逆转并输出

             Python : 3.7.0          OS : Ubuntu 18.04.1 LTS         IDE : PyCharm 2018.2.4       Conda ...

  7. Where is HttpContent.ReadAsAsync?

    It looks like it is an extension method (in System.Net.Http.Formatting): HttpContentExtensions Class ...

  8. C#面试题集锦

    1.貌似最常用的是  值类型和引用类型,还有 装箱和 http://www.cnblogs.com/Autumoon/archive/2008/08/18/1270685.html http://ww ...

  9. css布局一屏幕的自适应高度

    css ;;list-style: none;} .top{height: 100px;background-color:orange;} .max{;background-color:skyblue ...

  10. junit中test注解测试使用案列解析二

    本文原创,转载请注明出处 在上文中,已经简单的解析了junit中test注解的使用方法,今天在进行test测试时,遇到了一个异常,于是想深 入的研究一下. 还原一下今天的异常代码: @Service ...