Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







ORA-19809: limit exceeded for recovery files tips

Oracle Database Tips by Donald BurlesonOctober 22,  2015

Question:  I'm getting these errors upon instance startup:

Database mounted.
ORA-16038: log 1 sequence# 49 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:

. . .
ORA-01033: ORACLE initialization or shutdown in progress

How do I fix this ORA-19809 error?

Answer:  The ORA-19809 error involves adjusting a parameter and bouncing your instance.  The storage in db_recovery_file_dest is disk, not RAM.  The db_recovery_file_dest is located instance-wide, you it is not specified for a specific instance:

  • In Windows: c:\oracle\app\oracle\flash_recovery_area\

  • In UNIX/Linux /u01/app/oracle/flash_recovery_area

The docs note:

ORA-19809: limit exceeded for recovery files

Cause: The limit for recovery files specified by the db_recovery_file_dest_size was exceeded.

Action: The error is accompanied by 19804. See message 19804 for further details

ORA-19804: cannot reclaim string bytes disk space from string limit

Cause: Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.

Action: There are five possible solutions:
   1) Take frequent backup of recovery area using RMAN.
   2) Consider changing RMAN retention policy.
   3) Consider changing RMAN archivelog deletion policy.
   4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
   5) Delete files from recovery area using RMAN.

Also see ADRCI flash archiver error tips on Oracle Applications.

The solution to the ORA-19809 error is to increase the value of your db_recovery_file_dest_size parameter and bounce the instance:

SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16038: log 1 sequence# 230 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/opt/oracle/db/home/data/imapdb/redo01.log


SQL> shutdown abort

SQL> startup



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational