Oracle - 11GR2 - RAC - to - RAC - DATAGUARD - 配置方案(4)

1.5.9 备库RAC配置

--配置初始化参数文件 vi $ORACLE_HOME/dbs/initorcl1.ora spfile='+DATA/orclstd/parameterfile/spfileorcl.ora' vi $ORACLE_HOME/dbs/initorcl2.ora spfile='+DATA/orclstd/parameterfile/spfileorcl.ora' --备库注册到ocr oracle用户执行： srvctl add database -d orclstd -n orcl -o /oracle/app/oracle/product/11.2.0/db_1 -p +DATA/orclstd/parameterfile/spfileorcl.ora -r physical_standby srvctl add instance -d orclstd -i orcl1 -n orclstd1 srvctl add instance -d orclstd -i orcl2 -n orclstd2 srvctl config database -d orclstd alter database recover managed standby database cancel; shutdown immediate; srvctl start database -d orclstd select name, database_role, open_mode from gv$database; --database_role 为PHYSICAL STANDBY， open_mode 为read only 1.6 Dataguard 日常管理 1.6.1 DG数据库检查

--检查主备库的状态 set line 1000 col db_unique_name format a10 col open_mode format a15 col database_role format a20 col STANDBY_BECAME_PRIMARY_SCN format '999999999999999' select name, db_unique_name, open_mode, protection_mode, database_role, switchover_status, standby_became_primary_scn from gv$database; --主库database_role 为PRIMARY， open_mode 为READ WRITE --备库database_role 为PHYSICAL STANDBY， open_mode 为READ ONLY --检查是否有gap日志 select inst_id,thread#,low_sequence#,high_sequence# from gv$archive_gap; --检查远程归档日志的状态 set pagesize 999 set line 1000 col dest_name format a30 col error format a30 col DESTINATION format a30 select inst_id, status, type, recovery_mode, SYNCHRONIZATION_STATUS, SYNCHRONIZED, GAP_STATUS, error, ARCHIVED_THREAD#, APPLIED_THREAD#, ARCHIVED_SEQ#, APPLIED_SEQ# from gv$archive_dest_status where DEST_NAME='LOG_ARCHIVE_DEST_2'; --查询主库有哪些日志没有被传输到备库 SELECT LOCAL.THREAD#, LOCAL.SEQUENCE# FROM (SELECT THREAD#, SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=1) LOCAL WHERE LOCAL.SEQUENCE# NOT IN (SELECT SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND THREAD# = LOCAL.THREAD#); --检查dg 日志传输情况 col MESSAGE format a50 SELECT * FROM V$DATAGUARD_STATUS; --检查归档日志目标和进程 select target,archiver,process from v$archive_dest where dest_id=2; --检查dg 相关进程状态 select process, client_process, sequence#, status from v$managed_standby; --检查主备库日志是否同步 --检查主备库日志序列 Select max(sequence#) from v$log; --检查归档日志序列 select sequence#, first_time, next_time, applied from v$archived_log; --检查redo日志历史记录 select thread#, max (sequence#) from v$log_history group by thread#; --检查归档日志信息 select thread#, max (sequence#) from v$archived_log where APPLIED='YES' group by thread#;

1.6.2 DG数据库启动关闭

--启动 先起备库，后起主库 srvctl start database –d dbname 备库启动日志应用服务 sql> alter database recover managed standby database using current logfile disconnect; --关闭 先关主库，后关备库 srvctl stop database –d dbname 备库关闭日志应用服务 sql> alter database recover managed standby database cancel; srvctl stop database –d dbname 1.6.3 主备库切换

在RAC状态下，主从数据库的切换时主备库只能有一个实例在运行状态。在切换前需关掉其他节点，在切换完成后再启动其他节点。

--查询主备库状态 sql> select database_role,switchover_status from v$database; --将主库切换到备库状态 sql> alter database commit to switchover to physical standby [with session shutdown]; --如果主库状态为 “sessions active”， 则需要在命令后加上 with session shutdown 语句。 --重起原数据库到mount 状态。 srvctl stop database -d dbname srvctl start database -d dbname --在原备库上执行切换命令 sql> alter database commit to switchover to primary with session shutdown; --shutdown 并startup 新主数据库。 srvctl stop database -d dbname srvctl start database -d dbname --在新的备库启动 redo apply. sql>alter database recover managed standby database using current logfile disconnect; 1.6.4 故障转移

在某些情况下，不能执行正常的切换操作。如源端主数据库停掉，不能在短时间内恢复或数据库无法恢复甚至需要重建，需要启用备库。值得注意的是，这