Where to find db recovery file dest size

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. All rights reserved by Burleson. Reader comment by Dmitry : I've also noticed, that manual manipulation backupsets, using asmcmd can lead to the same problem. All rights reserved.

Disabling a Flash Recovery Area. 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. This depends on several factors:. If the FRA is large, you can have more; because these are OMF files, flashback files are only removed if the database needs the storage for other things.

If the FRA is too small, you may not have enough to reach the target. In this case, the target is minutes 1 day , but we have storage in use for a possible flashback of minutes. We have GB in use, but only need about to reach the target. So, some of the space is reclaimable:. If you want to be sure you can flashback your database, you need to make a guaranteed restore point aka a snapshot.

Definition of your retention policy should be done in RMAN. Your policy can be a recovery window or the number of backups you want to save. If you keep the defaults, the backup files will be stored in the FRA with retention policy redundancy 1. Meaning that if I make two backups, 1 will be reclaimable. The first backup is removed, and the reclaimable space is back to 0. Be aware that the most common problem with an undersized FRA is a database hang, because the database cannot create an archivelog file at time of a logswitch.

The most common solution is to create a backup of the archivelogs, which will also delete these archivelogs. This doesn't make much sense if both the archivelogs and the backups are stored in the FRA. So, always investigate if you can locate backups outside the FRA. If you are licensed to use the advanced compression option, you can compress RMAN backups while they are created.

Automatic compression of archivelog files is still not implemented by Oracle; see Oracle support Doc ID You should not write your own scripts to compress archivelogs in the FRA. If you want to save space using your own scripts, you should create an archive location outside the FRA. A full FRA can cause a hanging database, so a system down. When monitoring the FRA, focus on the space that is unreclaimable and not just on the actual usage.