Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Recovery area errors

user2907418Apr 27 2012 — edited Apr 27 2012
We are now seeing errors like this:

*** 2012-04-26 16:53:12.146
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 50864128 bytes disk space from 106300440576 limit
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 50896896 bytes disk space from 106300440576 limit
*** 2012-04-26 17:53:07.862
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 50364416 bytes disk space from 106300440576 limit
*** 2012-04-27 08:52:50.182
ORA-19815: WARNING: db_recovery_file_dest_size of 106300440576 bytes is 97.01% used, and has 3177718784 remaining bytes available.
*** 2012-04-27 08:52:50.192
************************************************************************
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************


Actually archivelogs is taking very little space up and this is all useless flb flashback files which are older than the requested flashback retention period.

SQL> SELECT * FROM V$FLASH_RECOVERY_AREA_USAGE;

FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                11.35                         0             252
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG               88.5                     88.41            1761

6 rows selected.
It seems to me that there is nothing whatsoever I can do about this. The space IS there so I just have to ignore errors and wait for oracle to remove flashback reclaimable files?

Personally this seems to me to be a reason not to use flashback. We simply can't have flb files using all that space beyond our required flashback retention period. It's a waste of shared NAS disk and also makes it h arder to monitor actual growth issues.

Can I have old flb files removed perhaps by setting an RMAN retention policy?

This is linked to my more general question here 10294656 which is about not being able to delete flashback logs.

Thanks.

Edited by: user2907418 on 27-Apr-2012 04:18

Edited by: user2907418 on 27-Apr-2012 04:18
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 25 2012
Added on Apr 27 2012
6 comments
2,224 views