Shulou(Shulou.com)06/01 Report--

This article will explain in detail how the archived logs in RMAN-08137 are not deleted and need to be used for backup or upstream capture. The content of the article is of high quality, so the editor will share it for you as a reference. I hope you will have some understanding of the relevant knowledge after reading this article.

This is 11g bug, and you need to add the force keyword after delete, as follows:

When RMAN-08137 deletes an archive file, even if the stream capture does not require the archive file [ID 1079953.1]

For: 11gR1-11gR2

RMAN cannot delete archived logs from the database, even if they are no longer needed during the capture process.

Reason

In 11g, RMAN looks at the minimum required change capture in the v$ database instead of DBA capture. By default, this value is updated every 6 hours. Therefore, by default, the value in the v$ database will be six hours later than the current value.

Solution

Because you cannot control the change to change the update frequency to the minimum required in the v$ database to capture the change, you can use the following workaround:

You can delete archive logs that are not needed during the capture process by using the following methods:

Delete all unprompted files completed before "sysdate-10/1440"

On the RMAN-08137 archive log is not deleted need to be used for backup or upstream capture process is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

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.