Databases Reference
In-Depth Information
Solution 1: Delete Unneeded Files
When the FRA does not have enough space for the newer files, Oracle deletes the unneeded files to make room; but not
everything at the same time. Therefore, there may be a time when Oracle does actually delete some redundant files but
not enough to free up sufficient space. You can manually clean up a lot of files yourself by using this command in RMAN:
RMAN> delete obsolete;
This causes RMAN to clean up unneeded files immediately. Files needed for recovery are not touched.
Solution 2: Increase Space
You can increase the size of the flashback area dynamically. To increase it to, say, 10GB, you would issue the following:
SQL> alter system set db_recovery_file_dest_size = 10G;
By the way, the converse is also possible; you can reduce the FRA size using this command, although that will not
solve the problem addressed in this recipe.
Solution 3: Remove Restore Points
The alternative to increasing the size of the flashback area is to remove some of the older restore points that you no
longer need. The following is a query to list the restore points you currently have:
SQL> col name format a15
SQL> select name, storage_size
2 from v$restore_point;
NAME STORAGE_SIZE
--------------- ------------
GRP1 0
GRP2 52428800
GRP3 52428800
RP1 0
RP2 0
4 rows selected.
These results show that restore points GRP2 and RP2 have storage associated with them. This is because they are
guaranteed restore points (see “How It Works” for an explanation of what that means). You should remove them to
make some room in the fast recovery area. To remove a restore point, issue a
drop restore point
command:
SQL> drop restore point grp2;
Restore point dropped.
SQL> drop restore point grp2;
Restore point dropped.
Dropping restore point should clear up space inside FRA, and you may be able to start the database.
