1.问题描述dg环境扩展表空间新增数据文件没有转移到备库，报ORA-16136:ManagedStandbyRecoverynotactive。2.分析处理过程：2.1在备库上查看v$managed_standbySQL>selectprocess,status,sequence#fromv$managed_standby;PROCESSSTATUSSEQUENCE#ARCHCLOSING114516ARCHCLOSING114517ARCHCONNECTED0ARCHCLOSING114518RFSIDLE0RFSWRITING114519RFSIDLE0.rowsselected。2.2确认报错信息SQL>alterdatabaserecovermanagedstandbydatabase;alterdatabaserecovermanagedstandbydatabase*ERRORatline1:ORA-00283:recoverysessioncanceledduetoerrorsORA-01111:namefordatafile14isunknown-renametocorrectfileORA-01110:datafile14:'/data/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00014'ORA-01157:cannotidentify/lockdatafile14-seeDBWRtracefileORA-01111:namefordatafile14isunknown-renametocorrectfileORA-01110:datafile14:'/data/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00014'从上面的输出可以看出是14号文件问题2.3备库在表空间扩容时重新创建14号文件新增的数据文件。altersystemsetstandby_file_management=manual;alterdatabasecreatedatafile'/data/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00014'as'/data/app/oracle/newdata/dataqiye_data9.dbf'altersystemsetstandby_file_management=auto;2.4查看警告日志文件againstartedlogmergerprocessTueJan3013:31:352018ManagedStandbyRecoverynotusingRealTimeApplyParallelMediaRecoverystartedwith8slavesWaitingforallnon-currentORLstobearchived...Allnon-currentORLshavebeenarchived.MediaRecoveryWaitingforthread1sequence114456Fetchinggapsequenceinthread1,gapsequence114456-114459Completed:alterdatabaserecovermanagedstandbydatabasedisconnectfromsessionTueJan3013:33:262018FAL[client]:FailedtorequestgapsequenceGAP-thread1sequence114456-114459DBID1477707379branch949967087FAL[client]:AlldefinedFALservershavebeenattempted.CheckthattheCONTROL_FILE_RECORD_KEEP_TIMEinitializationparameterisdefinedtoavaluethat'ssufficientlylargeenoughtomaintainadequatelogswitchinformationtoresolvearchiveloggaps.日志出现断档，从主天秤座的存档备份赖恢复序号为sequence114456-114459的归档日志2.5主库上操作从主库归档备份中恢复所需的归档日志序列(114456-114459)rmantarget/restorearchivelogfromsequence114456untilsequence114459;2.6备库上观察警告日志输出RFS[3]:Openedlogforthread1sequence114456dbid1477707379branch949967087TueJan3013:42:442018ArchivedLogentry114633addedforthread1sequence114457rlc949967087ID0x0dest2:TueJan3013:42:442018ArchivedLogentry114634addedforthread1sequence114456rlc949967087ID0x0dest2:TueJan3013:42:442018RFS[4]:AssignedtoRFSprocess5977RFS[4]:Openedlogforthread1sequence114504dbid1477707379branch949967087RFS[2]:Openedlogforthread1sequence114503dbid1477707379branch949967087RFS[3]:Openedlogforthread1sequence114502dbid1477707379branch949967087TueJan3013:42:472018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114456.arcMediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114457.arcMediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114458.arcTueJan3013:43:082018ArchivedLogentry114635addedforthread1sequence114506blc94996d57081ID:n3013:43:082018ArchivedLogentry114636addedforthread1sequence114503rlc949967087ID0x58146bd8dest2:TueJan3013:43:082018ArchivedLogentry114637addedforthread1sequence114504rlc949967087ID0x58146bd8dest2:TueJan3013:43:172018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114459.arcMediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114460.arcMediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114461.arc[oracle@iZwz9h66josrg1nhghd32dZtrace]$tail-falert_orcl.logTueJan3013:43:082018ArchivedLogentry114636addedforthread1sequence114503rlc949967087ID0x58146bd8dest2:TueJan3013:43:082018ArchivedLogentry114637addedforthread1sequence114504rlc949967087ID0x58146bd8dest2:TueJan3013:43:172018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114459.arcMediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114460.arcMediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114461.arcTueJan3013:43:432018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114462.arcTueJan3013:43:552018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114463.arcTueJan3013:44:112018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114464.arcTueJan3013:44:232018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114465.arcTueJan3013:44:372018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114466.arcTueJan3013:44:512018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114467.arcTueJan3013:45:052018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114468.arcTueJan3013:45:172018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114469.arcTueJan3013:45:312018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114470.arcTueJan3013:45:452018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114471.arcTueJan3013:46:012018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114472.arcTueJan3013:46:142018MediaRecoveryLog/data/app/oracle/arch/arch_949967087_1_114473.arc..............从日志的输出可以看出，备库正在申请归档三、验证3.1备库验证SQL>selectprocess,status,sequence#fromv$managed_standby;PROCESSSTATUSSEQUENCE#ARCHCLOSING114534ARCHCLOSING114535ARCHCONNECTED0ARCHCLOSING114533RFSIDLE0RFSIDLE114536RFSIDLE0MRP0WAIT_FOR_LOG114536RFSIDLE09rowsselected.SQL>selectdatabase_role,switchover_status,open_modefromv$database;DATABASE_ROLESWITCHOVER_STATUSOPEN_MODEPHYSICALSTANDBYNOTALLOWEDMOUNTEDSQL>selectdistinctthread#,max(sequence#)over(partitionbythread#)afromv$archived_log;THREAD#A1114537SQL>3.2主数据库验证SQL>selectdistinctthread#,max(sequence#)over(partitionbythread#)afromv$archived_log;THREAD#A1114537SQL>4.dgrestartshutdown命令总结4.1关闭备库SQL>alterdatabaserecovermanagedstandbydatabasecancel;SQL>shutdownimmediate;4.2启动备库SQL>startupnomount;SQL>alterdatabasemountstandbydatabase;SQL>alterdatabaserecovermanagedstandbydatabasedisconnectfromsession;4.3启用备库实时应用SQL>startupnomount;SQL>alterdatabasemountstandbydatabase;SQL>ALTERDATABASERECOVERMANAGEDSTANDBYDATABASEUSINGCURRENTLOGFILEDISCONNECTFROMSESSION;4.4启用备库实时应用+只读模式面试官问HTTPS是怎么转过来的。我有点困惑。2022年及以后全球IT行业的十大预测。苹果系统版本将再次更新，从iOS14.6升级到iOS15.2。您想要的Windows：精简+CPU使用率暴跌！立即杀死LTSC
