How to configure FRA and Some useful details

FRA Configuration and Some useful details

FRA : Fast Recovery Area.

Configuring the FRA we can easily manage backup and recovery files. The fast recovery area is an Oracle-managed directory, file system, or Oracle Automatic Storage Management disk group that provides a centralized storage location for all backup and recovery files.

Generated archived logs and flashback logs in the fast recovery area. FRA also store details of RMAN backup sets and image copies in it, and it generally use when restoring files during media recovery. Importantly fast recovery area also acts as a disk cache for tape. 



 Oracle Database automatically manages this storage, deleting files that are no longer needed. Periodically copying backups to tape frees space in the fast recovery area for other files.
When you issue the RMAN BACKUP command without specifying a backup destination, RMAN automatically backs up to the fast recovery area if it is configured. Oracle recommends that you configure a fast recovery area to simplify backup management. 

To Configure FRA , we have to set below two important parameters.

DB_RECOVERY_FILE_DEST -- As per set value for this parameter archivelog, flashbacklog, backup set etc are generated on particular location. Location should be local file system or ASM but not raw disk. If it is not set then Oracle base directory will be used as default location.

DB_RECOVERY_FILE_DEST_SIZE -- This parameter define how much space will be occupy by generated logs.


To set these parameters we not need shut down or restart the database. In RAC database, need to set both parameters same values for all the nodes. 

--- TOTAL FRA USAGE DETAIL:

  

SELECT   ROUND((A.SPACE_LIMIT / 1024 / 1024 / 1024), 2) AS FLASHSIZE_IN_GB,

  ROUND((A.SPACE_USED / 1024 / 1024 / 1024), 2) AS FLASHSIZE_USED_IN_GB,

  ROUND((A.SPACE_RECLAIMABLE / 1024 / 1024 / 1024), 2) AS    FLASHSIZE_RECLAIMABLE_GB,

  SUM(B.PERCENT_SPACE_USED)  AS PERCENT_OF_SPACE_USED

FROM

  V$RECOVERY_FILE_DEST A,

  V$FLASH_RECOVERY_AREA_USAGE B

GROUP BY

  SPACE_LIMIT,

  SPACE_USED ,

  SPACE_RECLAIMABLE ;

--- FRA SIZE USAGE  WITH FILE TYPE :

  SELECT

  ROUND((A.SPACE_LIMIT / 1024 / 1024 / 1024), 2) AS FLASH_IN_GB,

  ROUND((A.SPACE_USED / 1024 / 1024 / 1024), 2) AS FLASH_USED_IN_GB,

  ROUND((A.SPACE_RECLAIMABLE / 1024 / 1024 / 1024), 2) AS FLASH_RECLAIMABLE_GB,

  SUM(B.PERCENT_SPACE_USED)  AS PERCENT_OF_SPACE_USED, B.FILE_TYPE

FROM

  V$RECOVERY_FILE_DEST A,

  V$FLASH_RECOVERY_AREA_USAGE B

GROUP BY

  SPACE_LIMIT,

  SPACE_USED ,

  SPACE_RECLAIMABLE, B.FILE_TYPE  ;

So, whenever the FRA getting full or reached to threshold value, we have to check it's usage and we can deleted already backed up archivelog through RMAN. For same case we need to increase DB_RECOVERY_FILE_DEST_SIZE as well. 

Sometimes Archivelog not getting deleted which already backed up, because of RMAN ARCHIVELOG Deletion policy is not proper set.  So, we have to check it and set it proper.

 CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE';     ----- need to set archivelog backup done on tape rather than local file system. 

 CONFIGURE ARCHIVELOG DELETION POLICY TO NONE ;  --- Need to set as if no achivelog backup going on.

Delete archivelog through RMAN   :

RMAN > DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-7';