ARC1: Error 19809 - ORA-19809 or ORA-00257

Following error message appears in alert log file:

   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************
ARC1: Error 19809 Creating archive log file to '+DATA'
or in ohs1.log for fusion middle tier

How to solve ORA-00257 archiver error. Connect internal only, until freed.

Root cause: flash recovery area is full.

solution: you need delete files from flash recovery area through rman. If you delete them through os, you need run rman crosscheck and delete expired.

Concern: good thing is flash recovery will prevent database from using up all disk space when something wrong happens. So os or other applcation will not be affected by database issue. Bad thing is flash recovery area is always less than availabe disk in server. it will generate more database freeze because of the small buffer size.

check flash recovery area usage:

set lines 100
col name format a60
select name
, floor(space_limit / 1024 / 1024) "Size MB"
, ceil(space_used  / 1024 / 1024) "Used MB"
from v$recovery_file_dest
order by name
/

delete archive log through rman:

rman> delete archivelog until time 'trunc(sysdate -1)'

reference:

http://www.shutdownabort.com/errors/ORA-19809.php

http://www.oraclefaq.net/2007/04/16/how-to-solve-ora-00257-archiver-error-connect-internal-only-until-freed/