设为首页 加入收藏

TOP

关于DataGuard的三种保护模式实验(五)
2015-11-13 01:24:13 来源: 作者: 【 】 浏览:21
Tags:关于 DataGuard 保护 模式 实验
e发现传输状态不是同步情况。于是自动加快进行日志传输和同步动作。在Standby端,也可以看到后续追赶动作。


SQL> select name, open_mode, database_role, protection_mode from v$database;


NAME? ? ? OPEN_MODE? ? ? ? ? ? DATABASE_ROLE? ? PROTECTION_MODE


--------- -------------------- ---------------- --------------------


VLIFE? ? READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM AVAILABILITY


Standby端上的日志追赶动作。


Wed Oct 21 08:27:05 2015


Primary database is in MAXIMUM PERFORMANCE mode


Re-archiving standby log 4 thread 1 sequence 80


Wed Oct 21 08:27:05 2015


Media Recovery Waiting for thread 1 sequence 81


RFS[14]: Assigned to RFS process 31500


RFS[14]: Selected log 5 for thread 1 sequence 81 dbid -87496857 branch 892734889


Wed Oct 21 08:27:05 2015


Archived Log entry 76 added for thread 1 sequence 80 ID 0xfad4f44b dest 1:


Recovery of Online Redo Log: Thread 1 Group 5 Seq 81 Reading mem 0


? Mem# 0: /u01/app/oracle/oradata/VLIFESB/onlinelog/o1_mf_5_c265gqd8_.log


? Mem# 1: /u01/app/oracle/fast_recovery_area/VLIFESB/onlinelog/o1_mf_5_c265gqj0_.log


Wed Oct 21 15:13:52 2015


Primary database is in MAXIMUM AVAILABILITY mode


Changing standby controlfile to MAXIMUM AVAILABILITY mode


Changing standby controlfile to RESYNCHRONIZATION level


Standby controlfile consistent with primary


RFS[15]: Assigned to RFS process 969


RFS[15]: Selected log 4 for thread 1 sequence 82 dbid -87496857 branch 892734889


Wed Oct 21 15:13:53 2015


Archived Log entry 77 added for thread 1 sequence 81 ID 0xfad4f44b dest 1:


Wed Oct 21 15:13:53 2015


Media Recovery Waiting for thread 1 sequence 82 (in transit)


Recovery of Online Redo Log: Thread 1 Group 4 Seq 82 Reading mem 0


? Mem# 0: /u01/app/oracle/oradata/VLIFESB/onlinelog/o1_mf_4_c265gc9q_.log


? Mem# 1: /u01/app/oracle/fast_recovery_area/VLIFESB/onlinelog/o1_mf_4_c265gcfk_.log


Wed Oct 21 15:14:41 2015


Archived Log entry 78 added for thread 1 sequence 82 ID 0xfad4f44b dest 1:


Wed Oct 21 15:14:41 2015


Media Recovery Waiting for thread 1 sequence 83


Wed Oct 21 15:14:42 2015


Primary database is in MAXIMUM AVAILABILITY mode


Changing standby controlfile to MAXIMUM AVAILABILITY level


Standby controlfile consistent with primary


RFS[16]: Assigned to RFS process 976


RFS[16]: Selected log 4 for thread 1 sequence 83 dbid -87496857 branch 892734889


Recovery of Online Redo Log: Thread 1 Group 4 Seq 83 Reading mem 0


? Mem# 0: /u01/app/oracle/oradata/VLIFESB/onlinelog/o1_mf_4_c265gc9q_.log


? Mem# 1: /u01/app/oracle/fast_recovery_area/VLIFESB/onlinelog/o1_mf_4_c265gcfk_.log


此时,两个库由于网络通畅,同步状态正常,同步测试正常。


(Maximium Availiablity模式下使用)


--主库下


SQL> create table t_m as select * from dba_objects where rownum<10;


Table created


--Standby下


SQL> select count(*) from t_m;


? COUNT(*)


----------


? ? ? ? 9


如果此时中断应用日志,Standby情况如下:


SQL> alter database recover managed standby database cancel;


Database altered


SQL> select name, open_mode, database_role, protection_mode from v$database;


NAME? ? ? OPEN_MODE? ? ? ? ? ? DATABASE_ROLE? ? PROTECTION_MODE


--------- -------------------- ---------------- --------------------


VLIFE? ? READ ONLY? ? ? ? ? ? PHYSICAL STANDBY MAXIMUM AVAILABILITY


日志情况如下:


Wed Oct 21 15:20:49 2015


alter database recover managed standby database cancel


Wed Oct 21 15:20:49 2015


MRP0: Background Media Recovery cancelled with status 16037


Errors in file /u01/app/oracle/diag/rdbms/vlifesb/vlifesb/trace/vlifesb_pr00_17539.trc:


ORA-16037: user requested cancel of managed recovery operation


Managed Standby Recovery not using Real Time Apply


Recovery interrupted!


Recovered data files t

首页 上一页 2 3 4 5 6 下一页 尾页 5/6/6
】【打印繁体】【投稿】【收藏】 【推荐】【举报】【评论】 【关闭】 【返回顶部
分享到: 
上一篇Oracle 12c In-Memory in Tablesp.. 下一篇MySQL中order by 结果不准确的问..

评论

帐  号: 密码: (新用户注册)
验 证 码:
表  情:
内  容: