dataguard 由於主庫引數未配置歸檔刪除策略導致庫歸檔丟失ORA-16016
dataguard 由於主庫引數未配置歸檔刪除策略導致庫歸檔丟失
今天巡檢庫時候發現備庫未啟動，監控agent也被人關閉了，手動啟動
按照日誌慣例開啟備庫(read_only)，但是在open的過程中顯示以下錯誤
但是手動應用歸檔顯示已經應用完成，後臺查日誌備庫應用到sequence 173而主庫已經應用到214，檢視歸檔目錄下，發現歸檔已經丟失了，由於備機關機未啟動導致歸檔未傳送過來．
我們在主庫中恢復歸檔
將恢復出來的日誌複製到備庫
手動註冊丟失的歸檔,這裡我用指令碼批次處理的;
173-214為丟失歸檔的範圍
注：如果歸檔量比較多可以指定並行度
資料庫可正常open
最後設定一下主庫歸檔刪除策略
主庫操作
如果出現以下錯誤
需要修改修改資料庫引數，重啟庫，然後重新 設定歸檔刪除策略
今天巡檢庫時候發現備庫未啟動，監控agent也被人關閉了，手動啟動
按照日誌慣例開啟備庫(read_only)，但是在open的過程中顯示以下錯誤
點選(此處)摺疊或開啟
- Standby crash recovery failed to bring standby database to a consistent
- point because needed redo hasn't arrived yet.
- MRP: Wait timeout: thread 1 sequence# 173
- Standby Crash Recovery aborted due to error 16016.
- Errors in file /u01/app/oracle/diag/rdbms/orcl_st1/orcl/trace/orcl_ora_29639.trc:
- ORA-16016: archived log for thread 1 sequence# 173 unavailable
- Recovery interrupted!
- Some recovered datafiles maybe left media fuzzy
- Media recovery may continue but open resetlogs may fail
- Completed Standby Crash Recovery.
- Errors in file /u01/app/oracle/diag/rdbms/orcl_st1/orcl/trace/orcl_ora_29639.trc:
- ORA-10458: standby database requires recovery
- ORA-01196: file 1 is inconsistent due to a failed media recovery session
- ORA-01110: data file 1: '/u01/app/oracle/oradata/orcl/system01.dbf'
- ORA-10458 signalled during: alter database open...
但是手動應用歸檔顯示已經應用完成，後臺查日誌備庫應用到sequence 173而主庫已經應用到214，檢視歸檔目錄下，發現歸檔已經丟失了，由於備機關機未啟動導致歸檔未傳送過來．
我們在主庫中恢復歸檔
點選(此處)摺疊或開啟
- rman target /
- restore archivelog from sequence 173
將恢復出來的日誌複製到備庫
手動註冊丟失的歸檔,這裡我用指令碼批次處理的;
點選(此處)摺疊或開啟
- for i in `seq 173 214`;do echo "ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_"$i"_956999399.dbf;'";done
點選(此處)摺疊或開啟
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_173_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_174_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_175_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_176_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_177_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_178_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_179_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_180_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_181_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_182_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_183_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_184_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_185_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_186_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_187_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_188_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_189_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_190_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_191_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_192_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_193_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_194_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_195_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_196_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_197_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_198_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_199_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_200_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_201_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_202_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_203_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_204_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_205_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_206_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_207_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_208_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_209_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_210_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_211_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_212_956999399.dbf';
-
ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_213_956999399.dbf';
- ALTER DATABASE REGISTER LOGFILE '/u01/archive/1_214_956999399.dbf';
點選(此處)摺疊或開啟
- SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
注：如果歸檔量比較多可以指定並行度
點選(此處)摺疊或開啟
-
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE PARALLEL 2 DISCONNECT FROM SESSION;
- ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
點選(此處)摺疊或開啟
-
SQL> ALTER DATABASE OPEN;
- SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
主庫操作
點選(此處)摺疊或開啟
- rman target /
- CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
點選(此處)摺疊或開啟
- CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
- new RMAN configuration parameters:
- CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
- new RMAN configuration parameters are successfully stored
- RMAN-08591: WARNING: invalid archivelog deletion policy
點選(此處)摺疊或開啟
- SQL>alter system set "_log_deletion_policy"=ALL scope=spfile sid='*';
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/24486203/viewspace-2147645/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- DG 主庫丟失歸檔
- [Dataguard]主庫歸檔丟失，備庫不需重建實驗
- Oracle Data Guard 主庫歸檔檔案刪除策略Oracle
- Oracle Data Guard 主庫 歸檔檔案 刪除策略Oracle
- dataguard 歸檔丟失,備庫基於SCN恢復
- Oracle Data Guard 主庫 歸檔檔案 刪除策略--續Oracle
- 【轉載】Oracle Data Guard 主庫 歸檔檔案 刪除策略Oracle
- dg 主庫丟失歸檔 解決方案
- 誤刪歸檔日誌除導致備份歸檔日誌失敗
- Oracle 10g DG 主庫丟失歸檔Oracle 10g
- dg中備庫歸檔目錄滿了，導致不能接收主庫歸檔檔案
- 【DATAGUARD】物理dg在主庫丟失歸檔檔案的情況下的恢復(七)
- 備庫歸檔刪除策略失效的問題分析
- Oracle歸檔檔案丟失導致OGG不用啟動Oracle
- 歸檔日誌無法歸檔導致資料庫hang住資料庫
- 【DB2學習】由於TSM損壞導致歸檔失敗DB2
- 邏輯dg刪除主庫過期歸檔日誌
- Oracle DataGuard歸檔日誌丟失處理方法Oracle
- oracle dataguard 自動刪除歸檔日誌Oracle
- oracle adg主庫通過rman無法刪除歸檔Oracle
- redo log 丟失（非歸檔模式,資料庫正常關閉，redo log 被誤刪除！）模式資料庫
- 由於網路卡故障導致DATAGUARD傳輸檔案失敗
- 丟失已歸檔日誌檔案下恢復資料庫資料庫
- 【DataGuard】由於備庫引數設定不當導致資料檔案無法新增的故障分析
- ORACLE刪除歸檔Oracle
- Oralce資料庫關閉歸檔日誌並且刪除歸檔日誌資料庫
- TSM備份時因歸檔日誌丟失而導致備份失敗
- 【DataGuard】由於備庫引數設定不當導致資料檔案無法新增的故障分析(轉）
- 11g主庫歸檔自動刪除的小問題分析
- DATAGUARD_standby刪除歸檔日誌的指令碼指令碼
- DataGuard已應用歸檔日誌刪除指令碼指令碼
- Oracle 10G RAC歸檔引數格式問題導致歸檔至ASM時出錯Oracle 10gASM
- 利用sqlplus指令碼刪除備庫歸檔SQL指令碼
- oracle歸檔日誌丟失後的資料庫恢復Oracle資料庫
- 強制刪除歸檔檔案
- 刪除歸檔日誌檔案
- 【轉載】Oracle Data Guard 備庫 歸檔檔案 刪除指令碼Oracle指令碼
- 【故障處理】DG環境主庫丟失歸檔情況下資料檔案的恢復