Re: Rman purging issue

Posted by ErmanArslansOracleBlog on Jun 27, 2016; 8:22am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Rman-purging-issue-tp1089p1090.html

Hi Sumair,

Why don't you use Recovery window rather than redundancy?

Anyways;

Go through the following list below and update me accordingly . If the issue not resolved, send me the rman backup scripts(you didnt mention the backup types -level0,level1 or full) along with the rman outputs (list of backups, report obsolete and so on) ->

1)Did you do any recent changes in the database configuration?
2)Check this document: RMAN not Reporting any Backups as Obsolete (Doc ID 1949622.1)
3)Also , consider this:
Relationship Between Retention Policy and Flash Recovery Area Rules

Ref: Rman backup retention policy (Doc ID 462978.1)
 
The RMAN status OBSOLETE is always determined in reference to a retention policy. For example, if a database backup is OBSOLETE in the RMAN repository, it is because it is either not needed for recovery to a point within the recovery window, or it is redundant.

If you configure a flash recovery area, then the database uses an internal algorithm to select files in the flash recovery area that are no longer needed to meet the configured retention policy. These backups have status OBSOLETE, and are eligible for deletion to satisfy the disk quota rules.

There is one important difference between the flash recovery area criteria for OBSOLETE status and the disk quota rules for deletion eligibility. Assume that archived logs 1000 through 2000, which are on disk, are needed for the currently enabled recovery window and so are not obsolete. If you back up these logs to tape, then the retention policy still considers the disk logs as required, that is, not obsolete. Nevertheless, the flash recovery area disk quota algorithm considers the logs on disk as eligible for deletion because they have already been backed up to tape. The logs on disk do not have OBSOLETE status in the repository, but they are eligible for deletion by the flash recovery area. Note, though, that the retention policy is never violated when determining which files to delete from the flash recovery area to satisfy the disk quota rules.