Using Fast Recovery Area to let Oracle automatically manage the backup/flashback/recovery related files is very useful, but avoiding problems related with FRA free space shortage requires careful planning. There are several factors that have to be taken into account, apart from the most obvious like DB_RECOVERY_FILE_DEST_SIZE parameter, there are some additional ones depending on the type of files stored. For example DB_FLASHBACK_RETENTION_TARGET (and _MINIMUM_DB_FLASHBACK_RETENTION) affecting flashback logs or archived logs deletion policy which is also taken into account while reclaimable files purging is done.
Tag: FRA
How to verify if archived log deletion policy is correctly applied?
Originally posted on “Databases at CERN” blog
What is the best way to handle archived logs deletion in environments with standby and downstream capture databases? One could use own scripts, to delete for example all backed up archived logs, older than n days. But better way, will be to set RMAN archived log deletion policy, because then, additional options could be specified, to delete archived logs which are not only BACKED UP N TIMES, but also APPLIED or SHIPPED to other databases in the environment. Then, with proper settings, we should not end up with standby database which needs already deleted archived log… Of course unless there are some bugs causing problems with correct handling of archived logs deletion, so it’s good idea to double-check your configuration, before real deletion occurs, which usually happens when there is space pressure in FRA.
Continue reading “How to verify if archived log deletion policy is correctly applied?”
Change is the only constant... 