oracle dataguard protection level

最新推荐文章于 2022-07-10 23:21:52 发布
最新推荐文章于 2022-07-10 23:21:52 发布
阅读量743 收藏
点赞数
分类专栏： Oracle Oracle EBS 文章标签： oracle thread archive performance database sql
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/aicon/article/details/5410218
版权

物理dataguard：

 

主库：

 

SQL> SELECT DATABASE_ROLE, DB_UNIQUE_NAME INSTANCE, OPEN_MODE,
  2  PROTECTION_MODE, PROTECTION_LEVEL, SWITCHOVER_STATUS
  3  FROM V$DATABASE;

DATABASE_ROLE    INSTANCE                       OPEN_MODE  PROTECTION_MODE      PROTECTION_LEVEL     SWITCHOVER_STATUS
---------------- ------------------------------ ---------- -------------------- -------------------- --------------------
PRIMARY          10gpri                         READ WRITE MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  SESSIONS ACTIVE

SQL>

 

 

备库：

 

SQL> SELECT DATABASE_ROLE, DB_UNIQUE_NAME INSTANCE, OPEN_MODE,
  2  PROTECTION_MODE, PROTECTION_LEVEL, SWITCHOVER_STATUS
  3  FROM V$DATABASE;

DATABASE_ROLE    INSTANCE                       OPEN_MODE  PROTECTION_MODE      PROTECTION_LEVEL     SWITCHOVER_STATUS
---------------- ------------------------------ ---------- -------------------- -------------------- --------------------
PHYSICAL STANDBY 10gstandby                     MOUNTED    MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  NOT ALLOWED

SQL>

 

 

 

 

主库：

 

SQL> SELECT FS_FAILOVER_STATUS FSFO_STATUS,
  2  FS_FAILOVER_CURRENT_TARGET TARGET_STANDBY,
  3  FS_FAILOVER_THRESHOLD THRESHOLD,
  4  FS_FAILOVER_OBSERVER_PRESENT OBS_PRES
  5  FROM V$DATABASE;

FSFO_STATUS           TARGET_STANDBY                  THRESHOLD OBS_PRE
--------------------- ------------------------------ ---------- -------
DISABLED                                                      0

SQL>

 

 

 

 

从库：

 

SQL> SELECT FS_FAILOVER_STATUS FSFO_STATUS,
  2  FS_FAILOVER_CURRENT_TARGET TARGET_STANDBY,
  3  FS_FAILOVER_THRESHOLD THRESHOLD,
  4  FS_FAILOVER_OBSERVER_PRESENT OBS_PRES
  5  FROM V$DATABASE;

FSFO_STATUS           TARGET_STANDBY                  THRESHOLD OBS_PRE
--------------------- ------------------------------ ---------- -------
DISABLED                                                      0

SQL>

 

 

 

主库：

 

 

 SQL> SELECT MESSAGE FROM V$DATAGUARD_STATUS;

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ARC0: Archival started
ARC1: Archival started
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC2: Archival started
ARC1: Becoming the heartbeat ARCH
ARCH shutting down
ARC2: Archival stopped
ARC1: Standby redo logfile selected for thread 1 sequence 36 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 37 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 38 for destination LOG_ARCHIVE_DEST_2

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ARC1: Standby redo logfile selected for thread 1 sequence 39 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 40 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 41 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 42 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 43 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 44 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 45 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 46 for destination LOG_ARCHIVE_DEST_2
ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
PING[ARC1]: Error 3113 when pinging standby 10gstandby.

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ARC1: Standby redo logfile selected for thread 1 sequence 49 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 50 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 51 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 52 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 53 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 54 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 55 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 56 for destination LOG_ARCHIVE_DEST_2
ARC1: Standby redo logfile selected for thread 1 sequence 57 for destination LOG_ARCHIVE_DEST_2

31 rows selected.

SQL>

 

 

 

 

 

从库：

 

 

SQL> SELECT MESSAGE FROM V$DATAGUARD_STATUS;

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ARC0: Archival started
ARC1: Archival started
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Clearing online redo logfile 1 /u01/oradata/demo/redo01.log
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 47

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 14822
RFS[1]: Identified database type as 'physical standby'
Media Recovery Log /u01/oradata/log/1_47_714156559.dbf
Media Recovery Log /u01/oradata/log/1_48_714156559.dbf
Media Recovery Waiting for thread 1 sequence 49
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'
Media Recovery Log /u01/oradata/log/1_49_714156559.dbf
Media Recovery Waiting for thread 1 sequence 50
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Media Recovery Log /u01/oradata/log/1_50_714156559.dbf
Media Recovery Waiting for thread 1 sequence 51
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'
Media Recovery Log /u01/oradata/log/1_51_714156559.dbf
Media Recovery Waiting for thread 1 sequence 52
MRP0: Background Media Recovery cancelled with status 16037
MRP0: Background Media Recovery process shutdown
Managed Standby Recovery Canceled
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Clearing online redo logfile 1 /u01/oradata/demo/redo01.log
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 52
MRP0: Background Media Recovery cancelled with status 16037
MRP0: Background Media Recovery process shutdown
Managed Standby Recovery Canceled
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Clearing online redo logfile 1 /u01/oradata/demo/redo01.log

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Clearing online redo logfile 1 complete
Media Recovery Log /u01/oradata/log/1_52_714156559.dbf
Media Recovery Waiting for thread 1 sequence 53
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'
Media Recovery Log /u01/oradata/log/1_53_714156559.dbf
Media Recovery Waiting for thread 1 sequence 54
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'
Media Recovery Log /u01/oradata/log/1_54_714156559.dbf
Media Recovery Waiting for thread 1 sequence 55
MRP0: Background Media Recovery cancelled with status 16037
MRP0: Background Media Recovery process shutdown

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Managed Standby Recovery Canceled
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Clearing online redo logfile 1 /u01/oradata/demo/redo01.log
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 55
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'
Media Recovery Log /u01/oradata/log/1_55_714156559.dbf
Media Recovery Waiting for thread 1 sequence 56
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'

MESSAGE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Media Recovery Log /u01/oradata/log/1_56_714156559.dbf
Media Recovery Waiting for thread 1 sequence 57
RFS[1]: Successfully opened standby log 4: '/u01/oradata/demo/redo04.log'
Media Recovery Log /u01/oradata/log/1_57_714156559.dbf
Media Recovery Waiting for thread 1 sequence 58

71 rows selected.

SQL>

 

 

 

aicon
关注
专栏目录
Oracle DataGuard介绍
a743044559的专栏
09-04 8891
DataGuard 概述 DataGuard工作流程 主库把日志传输到备库，主库记录所有的操作信息，通过两种方式传输： 1：通过LNS（监听网络服务）传输到远程，通过service定义远程数据库，传输无延迟，延迟1~2秒。 2：把内存中得日志通过lgwr进程写到在线重做日志中，一段时间，通过arco进程写到归档日志中，这里是传输归档日志到远程服务器，这样的方式会造成延迟，延迟时间
ORACLE DataGuard环境搭建详细步骤（新方法）
DoubleJing的博客
12-03 3067
一：实验环境介绍 ***鉴于生产环境均采用64位系统和数据库软件，本实验也将采用这个标准*** 采用vmware workstation 10（版本随意，我用的10）虚拟机软件作为安装平台 对于真机的要求：CPU：INTEL：CORE I3级别或以上（推荐） AMD ：4核心CPU或以上（推荐） 内存：建议4G以上 系统：WIN7 /8 64位/WINDOWS SERVER 2003/2008 64位 硬盘：虚拟机所在分区剩余空间50G以上，固态硬盘最好 虚拟机系
oracle 11g dataguard同步异常，PROTECTION_LEVEL为RESYNCHRONIZATION
★ 分享、传播、open source
07-22 4064
起因：闪存区空间不足，导致DG出现异常，
ORACLE 11G DATAGUARD保护模式设置详解
justinhai的专栏
10-29 4354
先说说DG的三种保护模式 Maximum Protection: 最大保护模式，不允许数据丢失，所有事务必须完成主备库的日志写后才能提交，如果主备库之间网络异常，将会严重影响主库性能。 Maximum Performance： 此为DG的默认模式，此模式保证主库以最大性能运行，允许事务在完成本地日志写成功后主库立即提交，而不需等待redo数据写到备库，事务产生的redo 数据异步的传输到备库，此模
oracle dg 最大可用,10g DG保护模式的切换：从最大性能到最大可用
weixin_39715652的博客
04-03 390
这篇文章主要讨论DG环境下如何切换保护级别。数据库环境是linux as4 +10gr2。一、最大性能到最大可用1、检查当前主备库的保护模式--主库SQL> SELECT PROTECTION_MODE,PROTECTION_LEVEL FROM V$DATABASE;PROTECTION_MODE PROTECTION_LEVEL-------------------- ----...
Oracle-DataGuard保护模式(SYNC/ASYNC)测试
sinat_36757755的博客
07-10 3009
前言：本文主要测试Oracle DataGuard三种保护模式最大保护，最大可用以及最大性能的配置以及事务同步场景。
网络故障造成备库standby logfile的损坏
07-06 624
某生产库exadata,oracle 11.2.0.4,客户说物理备库与主库不能进行同步，如是要客户把生产库与备库的alert_sid.log文件打包传给我。查看了一个主库的alert.log日志文件发现从15号开始网络就...
Oracle Dataguard部署
lt53130640688的博客
11-26 534
这是我搭建的一个生产项目 部署环境Data Guard 环境： 操作系统： redhat 6.5Primary数据库： IP地址：172.16.212.135 数据库SID：orcl DB_UNIQUE_NAME：orcl_pdStandby数据库： IP地址：172.16.212.136 数据库SID：orcl DB_UNIQUE_NAME：orcl_st一、Primary 端的配置1.主库设置
在windows server 2016下实现单对单实例的oracle dataguard
cd4836的博客
09-24 470
目录 序言 实验部署环境 一、主库配置 二、备库配置 三、在主库操作，使用rman恢复到备库 四、备库操作，开启实时日志应用 五、测试 六、主备库switchover切换 一些日常管理 创建删除表空间 归档日志过多怎么办？ 介绍Dataguard三种保护模式 序言 本文详细描述了oracle数据库其中一项高可用性，叫做dataguard。这个功能实现了一个数据库的...
Oracle11g DataGuard不停机部署
DoubleJing的博客
12-05 856
Oracle DG部署（RMAN方式） 1.环境介绍 2.DG部署 2.1.建立主库orcl 2.2.主库开启归档 主库开启归档并设置强制日志 force logging --关闭数据库 SQL> shutdown immediate --以mount模式启动 SQL> startup mount --切换到归档模式 SQL> alter database archivelog; --开启强制日志 SQL> alter databas
ADG备库wait_for_log
喝醉酒的小白
11-28 4057
查看进程状态 归档目录确实没有406归档日志，而且观察发现实例1的归档都是每隔6个小时生成的，实例2是正常的。 测试实例1和备库的连通性 查看实例1的406归档，发现存在 检查standby logfile是否正常 ...
PROTECTION_MODE和PROTECTION_LEVEL的区别
loryliu的专栏
05-24 4286
版本：10.2.0.5 on windows 2008 64 bit 查看v$database
探索Oracle11gR2 之 DataGuard_03 三种保护模式
热门推荐
PrudentWoo 的个人空间
08-15 1万+
探索Oracle11gR2 之  DataGuard_03   三种保护模式 作者：吴伟龙 Oracle的DataGuard技术有三种实现模式，分别是max performance、max availability、maxprotection这三种模式。 以下是来自Oracle文档的摘要信息： In some situations, a business cannot affo
DataGuard 日常维护
12-11 162
第一部分 日常维护 一 正确打开主库和备库1 主库: SQL> STARTUP MOUNT;SQL> ALTER DATABASE ARCHIVELOG;SQL> ALTER DATABASE OPEN; ...
一个备库中ORA错误信息的分析
congbao6525的博客
09-25 157
最近也在处理一些遗留的问题，所以对于使用orabbix的报警还是心怀敬畏之心，一方面是我们让它能够做全方位的监控，另一方面也让我发现我们还是存在不少的小问题，小问题虽小，但是放大了，就是大麻烦，甚至数据库事故。 自从上次在社群...
DataGuard(一主一备一级联之failover)
cuimiwan3140的博客
06-13 376
fail over 1 failover介绍 failover转换，主要考虑的是如何减少数据量的丢失，如果可以允许数据丢失，可以直接切换备库为主库，不必在进行下面的讨论！ ...
PROTECTION_MODE is UNPROTECTED at standby database 分析
11-30 658
PROTECTION_MODE is UNPROTECTED at standby database 分析   数据库版本 SQL> select * from v$version;   BANNER ---------------------------------------------------------------------------------------------
oracle rfs进程过多,Oracle物理备库RFS进程消失，不能启动--解决
weixin_39722692的博客
04-03 1460
今天在测试Oracle环境上做热备，发现RFS进程不存在，做了如下操作后，还是不行：1、拷贝主库的密码文件到备库2、重启备库，也重启了主库，并alter system switch logfile;切换日志3、未发现主库与备库的gap，监听也正常备库似乎一切正常，但是就是RFS进程不存在，主库的归档日志没有传输到备库倒是在备库里有个错误提示：Sun May 25 21:24:09 2014Erro...
dg修改归档目录 oracle_OracleDG主库丢失归档增量同步
weixin_29666489的博客
01-17 321
1.1 问题在主库archivelog丢失后，数据无法同步到备库时，可以利用增量scn的方式，来避免全库还原备库或重建standby以下在Oracle10g下操作1.2 当前正常主备确认当前主库与备库是同步的：1.2.1 主库SQL> SELECT database_role FROM v$database;DATABASE_ROLE----------------PRIM...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值