设为首页 收藏本站
查看: 835|回复: 0

[经验分享] oracle dataguard protection level

[复制链接]

尚未签到

发表于 2016-7-19 09:42:51 | 显示全部楼层 |阅读模式
  物理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>
  
  
  

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-246135-1-1.html 上篇帖子: Oracle 遍历游标循环更新 下篇帖子: oracle dataguard PROTECTION_MODE
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表