物理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>
分享到:
相关推荐
### Oracle DataGuard 运维:正确停机启动步骤详解 #### 一、Oracle RAC DataGuard 基础概述 Oracle RAC (Real Application Clusters) 和 Oracle DataGuard 是两个非常重要的技术,前者用于实现数据库的高可用性和...
oracle dataguard 原理与功能,优点,如何自动同步,培训
Oracle DataGuard是Oracle数据库系统中一个强大的高可用性和灾难恢复解决方案。在11g版本中,它提供了多种保护模式,增强了数据库的容错能力和性能,同时确保了数据的安全性和完整性。以下是对Oracle DataGuard 11g...
### Oracle DataGuard 知识点总结 #### 一、Oracle DataGuard 概念与作用 - **Oracle DataGuard**:是Oracle提供的一项用于提高数据库高可用性和灾难恢复能力的技术。它通过在生产环境(Primary Database)之外...
Oracle DataGuard 是Oracle数据库系统中的一种高可用性和灾难恢复解决方案,它通过创建和维护一个或多个备用数据库(Standby Databases)来确保数据的安全性和业务连续性。在DataGuard环境中,主数据库(Primary ...
### Oracle DataGuard完全手册 #### 一、概述 Oracle DataGuard是一种高级的容灾解决方案,它利用Redo日志文件的复制技术实现主数据库(primary database)与备用数据库(standby database)之间的数据同步,从而确保...
Oracle DataGuard是Oracle数据库系统提供的一种高可用性和灾难恢复解决方案,它通过创建并维护一个或多个数据库副本(称为物理 standby数据库或逻辑 standby数据库),在主数据库出现故障时,能够快速接管业务,确保...
### ORACLE DATAGUARD维护手册关键知识点解析 #### 一、ORACLE DATAGUARD简介 Oracle Data Guard是Oracle数据库提供的一种高级数据保护技术,主要用于实现数据的高度可用性和灾难恢复能力。它通过构建主数据库...
### SAP系统Oracle DataGuard配置操作手册 #### Oracle DataGuard 原理介绍 Oracle DataGuard 是 Oracle 数据库提供的一种高级解决方案,旨在实现高可用性、数据保护和灾难恢复功能。它通过实现在多个数据库间复制...
- **选择保护模式**:Oracle DataGuard提供了三种保护模式:最大保护(Maximum Protection)、最大性能(Maximum Performance)和最大可用性(Maximum Availability)。每种模式都有其特定的重做日志传输和应用策略...
Oracle DataGuard配置说明。一步一步配置DataGuard。 Oracle DataGuard配置说明。一步一步配置DataGuard。
"Oracle Dataguard 的 3 种创建方法" Oracle Dataguard 是 Oracle 数据库中的一种灾难恢复解决方案,它可以将主数据库的数据实时同步到备用数据库中,确保数据的安全和高可用性。本文将详细介绍 Oracle Dataguard ...
Oracle DataGuard 容灾解决方案 一、需求分析 在用户现有的两台服务器上运行 Oracle 11g R2 和用友 NC 6.3,为了保证数据安全,每天进行备份。但是,用户希望在另一个机房中搭建容灾平台,以便在主数据库遇到极端...
Oracle Dataguard 实施步骤详解 Oracle Dataguard 是 Oracle 数据库的一种高可用性解决方案,通过在备库(Standby)上维护一份主库(Primary)的副本,实现数据的实时同步和灾难恢复。本文将详细介绍 Oracle ...
Oracle DataGuard是一种强大的高可用性和灾难恢复解决方案,用于保护Oracle数据库。它通过创建一个或多个备用数据库来确保数据的安全性,这些备用数据库可以是物理的(Physical Standby)或者逻辑的(Logical ...
oracle dataguard 切换,分为正常切换和非正常切换。可以参考
### Oracle DataGuard 数据保护模式切换详解 #### 一、引言 Oracle DataGuard 是一种用于保护数据的关键技术,它能够确保在出现故障时,主数据库(Primary Database)的数据能够被实时复制到备用数据库(Standby ...
### Oracle DataGuard 数据备份方案详解 #### 一、Oracle DataGuard 概述 Oracle DataGuard 是一种高级的数据保护技术,它能够确保业务连续性,并在出现灾难时提供数据恢复的能力。通过创建一个或多个实时物理副本...