RMAN Deletes Archivelog Files Not Yet Applied To Standby Database
(Doc ID 1987102.1)
Last updated on MARCH 10, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 12.1.0.1 [Release 11.1 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
RMAN may delete un-shipped/un-applied archive logs to the standby DB under the following conditions.
- Deletion policy of RMAN on the primary DB is "APPLIED ON [ALL] STANDBY"
- Log_archive_dest_state_x for the mandatory standby DB is set to DEFER or RESET
NOTE: "APPLIED on [ALL] STANDBY" is used to allow archive log deletion only when it has been applied to the mandatory standby DB.
NOTE: Abount BUG:16082541, it occurs under the following situation.
- Deletion policy of RMAN on the primary DB is "SHIPPED TO [ALL] STANDBY"
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 |
| Cause |
| Solution |
| References |