<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>V$backup_piece on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/vbackup_piece/</link><description>Recent content in V$backup_piece on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Thu, 12 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/vbackup_piece/index.xml" rel="self" type="application/rss+xml"/><item><title>Oracle RMAN Delete Obsolete - Remove Unneeded Backups</title><link>https://www.oraclescripts.com/post/oracle-rman-delete-obsolete-remove-unneeded-backups/</link><pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/oracle-rman-delete-obsolete-remove-unneeded-backups/</guid><description>
&lt;h2 id="oracle-rman-delete-obsolete---remove-unneeded-backups"&gt;Oracle RMAN Delete Obsolete - Remove Unneeded Backups&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;A backup disk fills up slowly. Every night adds another set of backup files, and nobody removes the old ones. One morning the nightly backup fails because there is no space left. RMAN already knows which backups are no longer needed, but it does not remove them on its own. The &lt;code&gt;DELETE OBSOLETE&lt;/code&gt; command does that job.&lt;/p&gt;
&lt;p&gt;RMAN decides what is obsolete by applying the retention policy. The policy is either a redundancy count (how many full backups to keep) or a recovery window (how many days back you must be able to recover). A backup that the policy no longer needs is obsolete. It uses space and gives you no extra recovery options.&lt;/p&gt;</description></item></channel></rss>