Re: RMAN delete obsolete

Posted by ErmanArslansOracleBlog on Nov 12, 2021; 5:20pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/RMAN-delete-obsolete-tp10415p10425.html

Ensure you have no offline datafiles /or Tablespaces.. Offline Tablespace and datafiles may prevent rman making old backups obsolete.

It seems some of your backups are on SBT / Tape, and some of them are on Disk.

Check this one, ensure it is not related with your case : OLD ARCHIVELOGS BACKUPS NOT RECOGNIZED AS OBSOLETE (Doc ID 2102055.1)

Run the following commands to diagnose;

list backup of archivelog all summary;
show retention policy;
list backup of database summary;
report obsolete;

İf still weird, enable debug on RMAN and re-issue report obsolete command and check the debug trace.

(Example : rman target / debug trace=/tmp/erm.log)

Do you run Streams processes in this database? -> Check -> Report/Delete obsolete not reporting/deleting obsolete backups of Archivelog Files (Doc ID 1553261.1)

Also check -> RMAN Does Not Delete The Obsolete Archivelog Due To Incomplete Full Backup (Doc ID 2448376.1)
RMAN Not Deleting Archive Log Backups due to READ ONLY Tablespace (Doc ID 2751210.1)
RMAN Retains Archivelog Backups Beyond Recovery Window for PDB(PDB$SEED) Recovery (Doc ID 2492130.1)

Also read this sentence ->

The retention policy is not responsible for deleting or rendering obsolete archived redo logs and incremental level 1 backups. Rather, these files become obsolete when no full backups exist that need them. Besides affecting full or level 0 data file and control file backups, the retention policy affects archived redo logs and level 1 incremental backups. First, RMAN decides which data file and control file backups are obsolete. Then, RMAN considers as obsolete all archived logs and incremental level 1 backups that are not needed to recover the oldest data file or control file backup that must be retained.