RMAN Not Considering Backups of Dropped Tablespaces as Obsolete
(Doc ID 2742310.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.9.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
The Database was upgraded from a lower release to 19.9.0.0 version.
The backups of dropped tablespace(s) are not being considered as obsolete although they are beyond the configured retention.
For example, consider:
a. the following retention:
RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
b. a tablespace was dropped after the first level 0 backup.
After the fourth LEVEL=0 backup, RMAN is not listing (or deleting) backup pieces created during the first level 0 backup of the the dropped tablespaces as obsolete.
Changes
The database was upgraded to 19.9 with October RU Patch 31771877 "Database Release Update : 19.9.0.0.201020 (31771877)"
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 |