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.
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.
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?