Shulou(Shulou.com)05/31 Report--

This article mainly explains the "database RMAN delete archive log RMAN-0813 error handling method is what", the article explains the content is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in-depth, together to study and learn "database RMAN delete archive log RMAN-0813 error processing method is what" it!

Database backup log error: RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process,DB version 11.2.0.4. According to the backup policy, back up the archive every day, delete the file automatically, and keep the archive for one week. Execute the following command:

Delete noprompt archivelog until time 'sysdate-7'

Still reported an error, the message is as follows:

Archived log file name=+CWDATA/sjjhdg/archivelog/2019_12_24/thread_1_seq_2328.1241.1027887401 thread=1 sequence=2328RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_24/thread_1_seq_2329.1242.1027887719 thread=1 sequence=2329RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_24/thread_1_seq_2330.1243.1027887813 thread=1 sequence=2330RMAN-08137: WARNING: archived log not deleted Needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_24/thread_1_seq_2331.1244.1027887873 thread=1 sequence=2331RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2332.1245.1027902623 thread=1 sequence=2332RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2333.1246.1027902719 thread=1 sequence=2333RMAN-08137: WARNING: archived log not deleted Needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2334.1247.1027908493 thread=1 sequence=2334RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2335.1248.1027911721 thread=1 sequence=2335RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_26/thread_1_seq_2336.1249.1027989005 thread=1 sequence=2336RMAN-08137: WARNING: archived log not deleted Needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_26/thread_1_seq_2337.1250.1027989067 thread=1 sequence=2337RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_26/thread_1_seq_2338.1251.1027990617 thread=1 sequence=2338RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_26/thread_1_seq_2339.1252.1028041713 thread=1 sequence=2339RMAN-08137: WARNING: archived log not deleted Needed for standby or upstream capture processarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_27/thread_1_seq_2340.1253.1028075413 thread=1 sequence=2340.

A MOS search found that this is a bug in 11g, describing the reason that in 11g, RMAN looks at the MIN_REQUIRED_CAPTURE_CHANGE#, in v$database instead of DBA_CAPTURE. By default, this value is updated every 6 hours. Therefore, by default, the value in v$database will be 6 hours later than the current value.

The solution given is to add force after delete.

Manual execution of delete noprompt force archivelog until time 'sysdate-7', successfully deleted the archive.

Deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_24/thread_1_seq_2330.1243.1027887813 RECID=18420 STAMP=1027887814deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_24/thread_1_seq_2331.1244.1027887873 RECID=18421 STAMP=1027887875deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2332.1245.1027902623 RECID=18422 STAMP=1027902628deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2333.1246.1027902719 RECID=18423 STAMP=1027902721deleted archived logarchived log File name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2334.1247.1027908493 RECID=18424 STAMP=1027908500deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_25/thread_1_seq_2335.1248.1027911721 RECID=18425 STAMP=1027911722deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_26/thread_1_seq_2336.1249.1027989005 RECID=18426 STAMP=1027989010deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_26/thread_1_seq_2337.1250.1027989067 RECID=18427 STAMP=1027989069deleted archived logarchived log file name=+CWDATA/sjjhdg / archivelog/2019_12_26/thread_1_seq_2338.1251.1027990617 RECID=18428 STAMP=1027990618deleted archived logarchived log file name=+CWDATA/sjjhdg/archivelog/2019_12_26/thread_1_seq_2339.1252.1028041713 RECID=18429 STAMP=1028041715.Deleted 800objects Thank you for your reading The above is the content of "what is the handling method of RMAN-0813 errors when RMAN deletes archive logs in the database". After the study of this article, I believe you have a deeper understanding of what is the handling method of RMAN-0813 errors when RMAN deletes archive logs in the database, and the specific usage still needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.