To increase Oracle Fast Recovery Area (FRA) capacity, first determine whether the constraint is Oracle’s FRA quota, DB_RECOVERY_FILE_DEST_SIZE, or the actual filesystem or ASM storage beneath it. Raise the quota only when the underlying storage can support it; if that storage is full, expand it or choose an appropriate archive destination. A larger quota does not create physical capacity.
Identify what is full
The FRA is Oracle-managed storage for recovery-related files. DB_RECOVERY_FILE_DEST_SIZE sets the quota for those files; it is separate from the capacity of the filesystem or ASM disk group where the FRA resides. Oracle calls it a hard limit on space used by target database recovery files. See the Oracle AI Database Reference, release 23.
Before changing anything, inspect the current FRA location and quota, the configured archive destinations, and the actual remaining space in the backing filesystem or ASM disk group. Do not assume the FRA is the active archive target merely because one is configured: Oracle can use it automatically as a local archive destination when no local archive destination is specified. Check the applicable release’s guidance on automatic FRA archive destinations and your actual configuration.
- If the Oracle quota is the constraint and storage has sufficient headroom, increase the FRA quota.
- If the filesystem or ASM disk group is full, add or expand physical storage before increasing the quota.
- If archived logs go to a separate destination, assess that destination’s storage and configuration rather than changing the FRA quota.
Size the FRA for the recovery workload
Choose a quota based on what the installation is intended to retain in the FRA: archived redo logs, flashback logs, and any local database backups. Oracle’s Backup and Recovery User’s Guide describes the FRA location as a filesystem directory or ASM disk group, not a raw disk. If multiple databases share storage, account for their combined use and monitor the shared capacity, as discussed in Oracle Database Configuration Best Practices.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
The quota is not a one-for-one measure of physical disk needed. Oracle excludes block 0 and each file’s operating-system header from the quota calculation and advises allowing an additional 10% for this overhead. Mirroring and other storage-layer overhead can increase the physical capacity required further. For ASM, account for the disk group’s configuration rather than treating the FRA quota as raw disk consumption.
Increase the FRA quota
Oracle documents DB_RECOVERY_FILE_DEST_SIZE as dynamically modifiable with ALTER SYSTEM. Set the quota to a value supported by the actual storage and the intended recovery retention. Check the command syntax and persistence method for the database’s release and parameter-file configuration before applying a change.
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 200G SCOPE=BOTH;200G is an example value, not a sizing recommendation. Select a value appropriate to your deployment. Oracle’s release 23 parameter reference says the parameter is not modifiable in a PDB. In Oracle RAC, the value must be the same for all instances.
Oracle’s current recovery settings guidance says to set the FRA size before the FRA location. If you are establishing or changing both settings, follow the procedure for your database release and configuration.
Expand or redirect an archive destination
When the full destination is a separate archive location, increasing the FRA quota will not resolve the shortage. Provision more capacity for that filesystem or ASM disk group, or configure a suitable destination that aligns with the database’s recovery design. Oracle’s Database 19c Administrator’s Guide documents LOG_ARCHIVE_DEST_n destinations for local filesystem paths, ASM disk groups, the FRA via USE_DB_RECOVERY_FILE_DEST, and remote services.
Changing where archived logs are written can affect recovery and standby requirements. Confirm that the proposed destination is appropriate for the site before redirecting logs. Oracle’s Database 19c guide also says archive destination parameter changes take effect at the next automatic or manual log switch, so do not assume existing archive activity switches immediately.
Rank #4
Oracle’s Database 19c recovery settings tutorial recommends placing the FRA on a storage device separate from database files. Apply that recommendation in the context of your actual storage architecture.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the change
- Check the resulting values for
DB_RECOVERY_FILE_DESTandDB_RECOVERY_FILE_DEST_SIZE, including every RAC instance where applicable. - Check free capacity beneath the FRA or archive destination in the filesystem or ASM disk group; confirm it can support the quota and relevant physical overhead.
- Review archive destination status and confirm the intended destination is active.
- After the applicable log switch, verify that archived redo logs are being created at the intended destination and that recovery-related files continue to fit within the planned capacity.
These steps establish configuration and operating checks; a successful parameter change alone does not prove the underlying storage has enough capacity.
Recommended Free Tools
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
