Last updated on OCTOBER 31, 2016
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
***Checked for relevance on 02-Dec-2013***
***Checked for relevance on 06-Jul-2015***
By default Oracle 10g will use the Flash Recovery Area for archivedlogs and recovery related files; the parameter log_archive_dest_10 is reserved for the Flash Recovery Area and is set to 'LOCATION=USE_DB_RECOVERY_FILE_DEST' by default. RMAN disk backups for which no format is supplied will be created in the Flash Recovery Area.
It is possible to:
a. Archive to another file system location in addition to the Flash Recovery Area
b. Archive to another file system location instead of the Flash Recovery Area
c. Place disk backups in an alternate location
d. Avoid use of the Flash Recovery Area altogether
If a Flash Recovery Area is defined, space management of the FRA can only be automated via use of Recovery Manager - if recovery related files (eg archivelogs) are created in the FRA and RMAN is not used to backup and delete the archivelogs then the space usage metrics for the FRA will never be updated and it is possible to run out of space in the FRA even though archivelogs are removed (using OS commands such as rm or mv). Typical errors might be:
ORA-19804: cannot reclaim 46035968 bytes disk space from 536870912 limit
ARCH: Error 19809 Creating archive log file to '.../flash_recovery_area/../2011_01_2/o1_mf_1_995_%u_.arc'
Errors in file ...frsprd_ora_827560.trc:
ORA-16038: log 11 sequence# 995 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 11 thread 1: '../redo11_2.rdo'
ORA-00312: online log 11 thread 1: '../redo11_1.rdo'
USER (ospid: 827560): terminating the instance due to error 16038
Instance terminated by USER, pid = 827560
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms