RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream
客戶資料庫備份日誌報錯:RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process,
DB版本為11.2.0.1,根據備策略,每天備份歸檔,並且自動刪除檔,保留兩個星期的歸檔,手功執如下命令:
delete noprompt archivelog until time 'sysdate-14';
依然報錯,資訊如下:
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218319_0796336681.0001 thread=1 sequence=218319
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218320_0796336681.0001 thread=1 sequence=218320
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218321_0796336681.0001 thread=1 sequence=218321
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218322_0796336681.0001 thread=1 sequence=218322
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218323_0796336681.0001 thread=1 sequence=218323
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218324_0796336681.0001 thread=1 sequence=218324
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218325_0796336681.0001 thread=1 sequence=218325
搜尋MOS,發現這是11g中的一個bug,需要在delete 後面加上force,mos描述如下:
—————————————————————————————————————————————————————————————————————————
Symptoms
Applies To: 11gR1-11gR2
RMAN is unable to delete archive logs from database even though they are not needed by CAPTURE process anymore.
Changes
Cause
In 11g, RMAN looks at MIN_REQUIRED_CAPTURE_CHANGE# in v$database and not at DBA_CAPTURE. By default this value is updated every 6 hours. So by default the value in v$database will be six hours behind the current value.
Solution
Since changing frequency of update to MIN_REQUIRED_CAPTURE_CHANGE# in v$database can not be controlled, following workaround can be used:
Archive log which are not needed by capture process can be deleted using:
delete noprompt force archivelog all completed before 'sysdate-10/1440';
_________________________________________________________________________________________________________________________________________
最後加上force關鍵字,手動執行delete noprompt force archivelog until time 'sysdate-14'; 成功將歸檔刪除!
DB版本為11.2.0.1,根據備策略,每天備份歸檔,並且自動刪除檔,保留兩個星期的歸檔,手功執如下命令:
delete noprompt archivelog until time 'sysdate-14';
依然報錯,資訊如下:
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218319_0796336681.0001 thread=1 sequence=218319
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218320_0796336681.0001 thread=1 sequence=218320
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218321_0796336681.0001 thread=1 sequence=218321
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218322_0796336681.0001 thread=1 sequence=218322
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218323_0796336681.0001 thread=1 sequence=218323
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218324_0796336681.0001 thread=1 sequence=218324
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=E:\ORAARCH\JZH\ARC0000218325_0796336681.0001 thread=1 sequence=218325
搜尋MOS,發現這是11g中的一個bug,需要在delete 後面加上force,mos描述如下:
—————————————————————————————————————————————————————————————————————————
Symptoms
Applies To: 11gR1-11gR2
RMAN is unable to delete archive logs from database even though they are not needed by CAPTURE process anymore.
Changes
Cause
In 11g, RMAN looks at MIN_REQUIRED_CAPTURE_CHANGE# in v$database and not at DBA_CAPTURE. By default this value is updated every 6 hours. So by default the value in v$database will be six hours behind the current value.
Solution
Since changing frequency of update to MIN_REQUIRED_CAPTURE_CHANGE# in v$database can not be controlled, following workaround can be used:
Archive log which are not needed by capture process can be deleted using:
delete noprompt force archivelog all completed before 'sysdate-10/1440';
_________________________________________________________________________________________________________________________________________
最後加上force關鍵字,手動執行delete noprompt force archivelog until time 'sysdate-14'; 成功將歸檔刪除!
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10271187/viewspace-1358036/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- RMAN-08137: WARNING: Archived Log Not DeletedHivedelete
- 【RMAN】Archive Log Not Deleted As It Is Still Needed Rman-08137Hivedelete
- 關於RMAN-08137: WARNING: archive log not deleted as it is still needed問題的分析Hivedelete
- oracle 9i physical standby database 上的v$archived_logOracleDatabaseHive
- Archived redolog is (significant) smaller than the redologfileHiveNifi
- 【REDO】Archived redolog is (significant) smaller than the redologfileHiveNifi
- Archived redolog is (significant) smaller than the redologfile_1356604.1HiveNifi
- RMAN-06207: WARNING: 286 objects could not be deleted for DISK channel(s)Objectdelete
- RMAN-05541: no archived logs found in target databaseHiveDatabase
- OGG-00446 ERROR: Could not find archived logErrorHive
- ogg GGS ERROR 500 Could not find archived logErrorHive
- [Rman]RMAN-06207 WARNING:2 objects could not be deleted for DISK channel(s) dueObjectdelete
- Log actively being archived by another process問題解決Hive
- Nobody is needed
- standby redo log的理解
- 建立 Logical Standby DatabaseDatabase
- manage logical standby databaseDatabase
- DataGuard:Logical Standby Switchover
- 物理Standby資料庫及邏輯Standby資料庫(Physical Standby & Logical Standby)資料庫
- 【oracle】ORA-16038: log 2 sequence# 98 cannot be archivedOracleHive
- Bug 5483067: UNSHIPPED LOGS DELETED DELETION POLICY TO APPLIEDdeleteAPP
- Scripts to resize standby redolog files
- DataGuard:Logical Standby FailoverAI
- 監控Logical standby databaseDatabase
- Oracle DG建立Logical Standby DatabaseOracleDatabase
- Archived Redo Logs歸檔重做日誌介紹及其優點Hive
- 清除Oracle控制檔案中的歸檔資訊v$archived_logOracleHive
- Dataguard環境修改主庫和standby庫online redo log&standby redo log大小
- RMAN-06054: media recovery requesting unknown archived log for thread...Hivethread
- RMAN 中V$ARCHIVED_LOG 中STATUS 為"X" 的檔案處理Hive
- 建立Oracle 11g logical standbyOracle
- Logical Standby Database的配置步驟.Database
- Oracle10g logical standby 建立Oracle
- Create Logical Standby For Oracle 10GOracle 10g
- Logical Standby的維護操作_SKIP
- Oracle Standby Redo Log實驗兩則Oracle
- Logical Standby中Job的處理
- Nginx upstream 配置Nginx