RMAN Is Not Reporting Old Archive Log Files As Obsolete
(Doc ID 1936141.1)
Last updated on OCTOBER 18, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 and laterInformation in this document applies to any platform.
Symptoms
Archive logs are backed up using this RMAN command:
backup as copy format '/mnt/oralogs2/$ORACLE_SID/%U' archivelog like '+LOG%' delete input;
.....
delete force noprompt obsolete;
This is the retention policy:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
The database and archivelogs are backed up every three days. Backups are only run on the primary database.
Archivelog copies that are almost two months old are not being recognized as obsolete.
This is a primary, standby environment with an archivelog destination directing log_archive_dest_2 to archive to the standby database.
Changes
The standby database has been down for quite some time.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |