RMAN-08120 Since Upgrade To 12.1.0.2 Archive Logs Are Not Being Removed By Rman
(Doc ID 2022958.1)
Last updated on APRIL 09, 2024
Applies to:
Oracle Database Backup Service - Version N/A and laterOracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
One of the log_archive_dest_state_n has destinations that are marked DEFERED
You can run
SELECT * from v$archive_dest where (valid_now = 'UNKNOWN' AND status = 'DEFERRED') ;
o Since upgrade to 12.1.0.2 archive logs are not being removed by rman
- Archived redo logs are backing up in the primary.
- Archived redo logs are not being removed from the primary.
- It says they are not applied to the standby, but they have been.
RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
Actions done:
-------------
o Due to this error the
STANDBY DATABASE WAS REBUILD (from rman backup of production - duplicate for standby.)
all went well, the standby applied the logs but still will not delete at Primary with rman backup.
Verified all logs are APPLIED at STANDBY:
o RMAN Backup of Archivelogs running at PRIMARY reports:
RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
archived log file name=/<path>/<archivelogname_<sequence#>_<thread#>_<dbid>.arc thread=1 sequence=<sequence#> <<<-- *)1
Changes
Upgraded from 11.2.0.3 to 12.1.0.2
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 |
| References |