I configured fast_recovery_area for my instance,months ago, the old archivelog in fast_recovery_area will be auto deleted when the space in fast_recovery_area been used up,
but this suddenly stop working, I have to manually delete the archivelog to free up some space in fast_recovery_area.
The archivelogs in fast_recovery_area was backed up daily.
Anyone know what others factor will cause this?
You need to delete archives manually or you may use DELETE INPUT clause in RMAN backup archivelog command which will delete archives once backed up on disk or tape.
If FRA used for backup then BACKUP RECOVERY AREA ( 11g ) using RMAN & then delete expired backups to clean it up
Use v$flash_recovery_area_usage to monitor usage of FRA or increase db_recovery_file_dest_size
Can you please confirm on below rman config value , which is responsible for auto deletion
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF xx DAYS;
CONFIGURE ARCHIVELOG DELETION POLICY TO xx;
Thanks for the reply.
Both instances have the same setting
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
but one instance delete archivelog automatically, but another don't, it's weird...
Can you confirm below
show parameter db_recovery_file_dest_size
select * from v$flash_recovery_area_usage;
select space_used/(1024*1024*1024),space_limit/(1024*1024*1024) from v$recovery_file_dest;
select max(sequence#),max(FIRST_TIME),thread# from v$backup_redolog group by thread#;
Is it RAC ? how many nodes ? As OMF Archives getting deleted from other instance does if includes other thread archives also ?
Could something else on the device be using up space that Oracle doesn't know about? Are different instances sharing space? In addition to what Ajay asked for, also show us what the OS thinks is going on.
Query V$RECOVERY_AREA_USAGE to see what the Oracle database instance thinks is the current usage of FRA. If the current usage is much higher (because of files that Oracle isn't aware of) you will see the actual free space much lesser than what Oracle expects. The database instance is aware only of files that it maintains in the FRA (control files, online redo logs, archivelogs, backuppieces) and monitors space usage by these files. When space usage exceeds a threshold, it starts deleting older archivelogs that are not required for recovery. However, if space is consumed by some other files, the database instance will assume that there is free space and will not delete older archivelogs.
Hemant K Chitale
I am using ASM for the fast_recovery_area, in the RECO diskgroup
Below is the output from v$recovery_area_usage, it's shown only abot 56% of space been used.
But in the ASM EM page, it show 95.5% of the disk group been used.
Should these two values different for that much?
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROL FILE 0 0 0
REDO LOG 0 0 0
ARCHIVED LOG 55.25 55.25 336
BACKUP PIECE 1.71 1.71 1
IMAGE COPY 0 0 0
FLASHBACK LOG 0 0 0
FOREIGN ARCHIVED LOG 0 0 0