Hello Everyone.
I would be grateful if someone could confirm if my understanding of the below is correct.
Let's say that we have an application that is storing it's data in Oracle 11gR2 database.
Here are RMAN settings:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
The application is triggering backups through RMAN script once a week which also purges obsolete backups and archivelogs. Let's say that at some point (for any reason) backups start to fail. Archivelogs will be growing and will not be purged as Oracle will not mark any of them as obsolete (all archivelogs will be needed to perform recovery since last successful backup).
Archivelogs continue to grow until DB_RECOVERY_FILE_ DEST_SIZE is reached and at some point DB will hung.
Please correct if I'm wrong until this point.
From below documentation:
Configuring the RMAN Environment
"Archived redo logs can be deleted automatically by the database or by user-initiated RMAN commands. Only logs in the fast recovery area can be deleted automatically by the database. For archived redo log files in the fast recovery area, the database retains them as long as possible and automatically deletes eligible logs when additional disk space is required."
Since in the above scenario archive logs are not eligible for deletion (they are needed for recovery since last backup) they will not be deleted automatically.
I'm looking for possible ways to prevent DB hung due to archive logs filling FRA.
My question is:
1. Is it possible to modify above RMAN settings so the archive logs are cleared automatically in above scenario? (Loosing ability to recover database is acceptable) or the only way is to create RMAN script that will for example forcefully remove archive logs older then a week.?
Thanks,
Greg