🧩 ORA-19809: Limit Exceeded for Recovery Files

🧩 Introduction

The ORA-19809 error is a common issue in Oracle environments that use the Fast Recovery Area (FRA). It usually appears when the FRA reaches its maximum allocated size and cannot store new archived logs or backups.

Typical error message:

ORA-19809: limit exceeded for recovery files

ORA-19804: cannot reclaim space for 123456 bytes disk space limit 2147483648 bytes

This issue can stop archiving, backups, and even database operations if not resolved quickly.

Root Cause

The FRA (Fast Recovery Area) is a designated location where Oracle stores archived redo logs, backups, and flashback logs. When it fills up, Oracle cannot write new data, resulting in the ORA-19809 error.

Common causes include:

The FRA size is too small.

Old archive logs or backups are not deleted automatically.

The backup retention policy is not configured correctly.

Flashback Database or guaranteed restore points are consuming excessive space.

How to Diagnose

To check your current FRA configuration and usage:

SHOW PARAMETER db_recovery_file_dest;

SHOW PARAMETER db_recovery_file_dest_size;

Check how much space is used:

SELECT * FROM v$recovery_file_dest;

List archive logs and their sizes:

ARCHIVE LOG LIST;

SELECT NAME, SPACE_LIMIT, SPACE_USED FROM v$recovery_file_dest;

To check which files are consuming the most space:

SELECT file_type, percent_space_used, percent_space_reclaimable 

FROM v$recovery_area_usage;

Possible Solutions

1️⃣ Increase the FRA Size If you have enough disk space, increase the FRA limit:

ALTER SYSTEM SET db_recovery_file_dest_size = 20G;

(Adjust the size according to your storage capacity.)

2️⃣ Delete Unnecessary Archive Logs If old archive logs have already been backed up, you can safely delete them using RMAN:

RMAN> DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-2';

This deletes archive logs older than two days.

3️⃣ Crosscheck and Remove Expired Backups Sometimes old backups are marked as expired but not deleted:

RMAN> CROSSCHECK BACKUP;

RMAN> DELETE EXPIRED BACKUP;

4️⃣ Disable or Drop Unused Restore Points Guaranteed restore points can prevent space reclamation:

SELECT NAME, GUARANTEE_FLASHBACK_DATABASE FROM v$restore_point;

Drop the ones you no longer need:

DROP RESTORE POINT <name>;

5️⃣ Turn Off Flashback if Not Needed If flashback logs are consuming space and the feature is not in use:

ALTER DATABASE FLASHBACK OFF;

6️⃣ Move FRA to a Larger Disk If disk capacity is permanently insufficient:

ALTER SYSTEM SET db_recovery_file_dest='/u02/fast_recovery_area' SCOPE=BOTH;

Example Scenario

You receive the following error during archiving:

ORA-19809: limit exceeded for recovery files

ORA-16038: log 3 sequence 125 cannot be archived

Diagnosis shows that db_recovery_file_dest_size is only 10 GB and is full.

Solution:

Delete old archive logs via RMAN.

Increase FRA size to 20 GB.

Re-archive or rerun backup.

Best Practices

Monitor FRA usage regularly:

SELECT SPACE_LIMIT/1024/1024 "Allocated_MB", SPACE_USED/1024/1024 "Used_MB" FROM v$recovery_file_dest;

Schedule automatic cleanup jobs using RMAN.

Ensure regular backups are running so old logs can be purged.

Avoid unnecessarily large flashback retention or restore points.

Conclusion

The ORA-19809 error is a space management issue within the Fast Recovery Area. Proactive monitoring, appropriate sizing, and periodic cleanup can prevent the FRA from filling up and disrupting critical database operations.