oracle 12c data guard如何使用 sqlplus 主备切换

小编给大家分享一下oracle 12c data guard如何使用 sqlplus 主备切换，相信大部分人都还不怎么了解，因此分享这篇文章给大家参考一下，希望大家阅读完这篇文章后大有收获，下面让我们一起去了解一下吧！确认备库与主库是同步的并且日志切换正常。SQL>alter database switchover to verify;以上命令会验证如下信息：a. 验证数据库的版本至少为 12.1。b. 主库 REDO 传输正常。c. 备库 MRP 进程正常运行并且与主库同步，否则会在 SQLPROMPT 和 alert 中都报如下错误：列如：SQL>alter database switchover to chicago verify;ORA-16470: Redo Apply is not running on switchover target——Primary alert log—— SQL>alter database switchover to chicago verify; ORA-16470 signaled during: alter database switchover to chicago verify…如果是脏的那么会报出如下信息：SQL> alter database switchover to chicago verify;ERROR at line 1:ORA-16475: succeeded with warnings, check alert log for more details—–Primary Alert log———–SWITCHOVER VERIFY WARNING: switchover target has dirty online redo logfiles that require clearing.It takes time to clear online redo logfiles. This may slow down switchover process.确认 log_file_name_convert 参数在目标备库被正确设置：SQL>show parameter log_file_name_convert;注意：如果没有设置，请设置。例如，如果路径结构只有 db_uniquq_name 发生了改变：主库的日志在：/oradata/boston/备库的日志在： /oradata/chicago/logfiles>这样设置参数：alter system set LOG_FILE_NAME_CONVERT=’boston’,’chicago’ scope=spfile;注意：重启备库并且启动 MRP。当重启备库并且启动 MRP，将清除所有备库的 log_file_name_convert 参数设置的日志。如果备库是与主库同步的，将得到如下的信息：SQL> alter database switchover to chicago verify;Database altered.——— Primary Alert log ——-SWITCHOVER VERIFY: Send VERIFY request to switchover target CHICAGOSWITCHOVER VERIFY COMPLETECompleted: alter database switchover to chicago verify临时数据文件在创建备库之后，不会同时创建临时数据文件，用如下的命令查询临时数据文件，并且在备库进行创建。SQL> col name for a45SQL> select ts#,name,ts#,status from v$tempfile;SWITCHOVER VERIFY command returns ORA-16475 when log_archive_dest_n is not set on Standby as follows.SQL> ALTER DATABASE SWITCHOVER TO S1202 VERIFY;
ALTER DATABASE SWITCHOVER TO S1202 VERIFY
*
ERROR at line 1:
ORA-16475: succeeded with warnings, check alert log for more detailsIn alert.log, following messages appear.SWITCHOVER VERIFY: Send VERIFY request to switchover target S1202
SWITCHOVER VERIFY COMPLETE
SWITCHOVER VERIFY WARNING: switchover target has no standby database definedin LOG_ARCHIVE_DEST_n parameter. If the switchover target is converted to
a primary database, the new primary database will not be protected.ORA-16475 signalled during: ALTER DATABASE SWITCHOVER TO S1202 VERIFY…What to do? set log_archive_dest_state_n on Standby.1. 检查是否有些关闭的线程存在并且 disableSQL>SELECT thread#, instance, status FROM v$thread;Disable 线程使用：SQL> ALTER DATABASE DISABLE THREAD ;2. 检查是否有 log_archive_destination 指向不合法的目录SQL> select status,DEST_ID,TYPE,ERROR,GAP_STATUS,SYNCHRONIZED,SYNCHRONIZATION_STATUS,RECOVERY_MODE from V$ARCHIVE_DEST_STATUS where STatus ‘INACTIVE’;
SQL>show parameter log_Archive_destSQL>alter system set log_archive_trace=8191 sid=’*’;@primary and standby,SQL>show parameter background_dump_dest$tail -600f background_dump_dest/alert** 注意: 在 RAC 环境不需要关闭其他的实例，执行 Switchover 的命令会关闭所有的实例。主库 – Boston,SQL>alter database switchover to chicago;Database altered.以下是主库（BOSTON）和备库（CHICAGO）的 alert 输出：————–Primary Alert log “alert_boston.log”————–Fri Aug 23 11:05:23 2013ALTER SYSTEM SET log_archive_trace=8191 SCOPE=BOTH;alter database switchover to chicagoFri Aug 23 11:05:43 2013Starting switchover [Process ID: 3340]Fri Aug 23 11:05:43 2013ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY [Process Id: 3340] (boston).Fri Aug 23 11:05:44 2013Active, synchronized Physical Standby switchover ta免费主机域名rget has been identifiedPreventing updates and queries at the PrimaryGenerating and shipping final logs to target standbySwitchover End-Of-Redo Log thread 1 sequence 11 has been fixed
Switchover: Primary highest seen SCN set to 0x0.0x229306ARCH: Noswitch archival of thread 1, sequence 11.Switchover: Primary controlfile converted to standby controlfile succesfully.Switchover: Complete – Database shutdown requiredSending request (convert to primary database) to switchover target CHICAGOOCISessionBegin with PasswordVerifier succeededSwitchover complete. Database shutdown requiredUSER (ospid: 3340): terminating the instanceFri Aug 23 11:05:51 2013Instance terminated by USER, pid = 3340Completed: alter database swit免费主机域名chover to chicago——————-alert log “alert_chicago.log”——————Fri Aug 23 11:05:47 2013SWITCHOVER: received request ‘ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY’ from primary database.Fri Aug 23 11:05:47 2013ALTER DATABASE SWITCHOVER TO PRIMARY (chicago)Maximum wait for role transition is 15 minutes..Standby became primary SCN: 2265860Switchover: Complete – Database mounted as primarySWITCHOVER: completed request from primary database.注意：备库一端只等待15分钟，实现备库与主库的同步。SQL>alter database open;SQL>shut abortSQL>startupSQL>alter database recover managed standby database disconnect;SQL> alter system set log_archive_trace=0;System altered.在主库侧执行SQL>alter system switch logfile;SQL>select dest_id,error,status from v$archive_dest where dest_id=>;SQL>select max(sequence#),thread# from v$log_history group by thread#;如果备库端对应 log_archive_dest_2SQL>select max(sequence#)from v$archived_log where applied='YES' and
dest_id=2;在备库侧：SQL>select thread#,sequence#,process,status from gv$managed_standby;SQL>select max(sequence#),thread# from v$archived_log group by thread#;注意：在 12.2 中使用 v$dataguard_process 替代 v$managed_standbySQL> select name,role,instance,thread#,sequence#,action from gv$dataguard_process;以上是“oracle 12c data guard如何使用 sqlplus 主备切换”这篇文章的所有内容，感谢各位的阅读！相信大家都有了一定的了解，希望分享的内容对大家有所帮助，如果还想学习更多知识，欢迎关注云技术行业资讯频道！

相关推荐: DG归档日志断档时间过长怎么处理

这篇文章主要为大家展示了“DG归档日志断档时间过长怎么处理”，内容简而易懂，条理清晰，希望能够帮助大家解决疑惑，下面让小编带领大家一起研究并学习一下“DG归档日志断档时间过长怎么处理”这篇文章吧。 1、备库操作（1）取消日志的应用ALTER DATABASE …