RMAN Archivelog Deletion Policy 'Backed up N Times' is Ignored
(Doc ID 1487508.1)
Last updated on FEBRUARY 14, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 18.1.0.0.0 [Release 11.2 to 18]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 delete input syntax ignores ARCHIVELOG DELETION POLICY BACKED UP N TIMES TO 'SBT_TAPE':
RMAN> backup archivelog sequence 260 delete input;
Starting backup at 25-may-11 18:12:40
using channel ORA_DISK_1
skipping archived log file
<path>\USE_RECOVERY_FILE_DEST1_260_744745422.DBF; already backed up 1 time(s)
channel ORA_DISK_1: deleting archived log(s)
archived log file name=<path>\USE_RECOVERY_FILE_DEST1_260_744745422.DBF RECID=369 STAMP=752067783
Finished backup at 25-may-11 18:12:40
This archived log should not have been deleted given that it has never been
backed up to tape.
Changes
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 |