Oracle database - DBRECOVERYFILEDEST & DBRECOVERYFILEDESTSIZE parameters

Discussion

• Nirja Shah   -Posted on 01 Sep 15
  - Include the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE parameters in your initialization parameter file to identify the default location for the flash recovery area.
  
  - The flash recovery area contains:
  
  1. Redo log files or multiplexed copies of redo log files - The most crucial structure for recovery operations is the redo log, which consists of two or more preallocated files that store all changes made to the database as they occur. Every instance of an Oracle Database has an associated redo log to protect the database in case of an instance failure.
  
  2. Control files or multiplexed copies of control files - A control file is a small binary file that records the physical structure of the database and includes: The database name. Names and locations of associated datafiles and online redo log files. The timestamp of the database creation.
  
  3. RMAN backups (datafile copies, control file copies, backup pieces, control file autobackups) - RMAN (Recovery Manager) is a backup and recovery manager supplied for Oracle databases (from version 8) created by the Oracle Corporation. It provides database backup, restore, and recovery capabilities addressing high availability and disaster recovery concerns.
  
  4. Archived logs - Oracle Database lets you save filled groups of redo log files to one or more offline destinations, known collectively as the archived redo log, or more simply the archive log
  
  5. Flashback logs - A Flashback Database operation applies to the whole database.
  - You cannot flash back individual tablespaces.
  - A Flashback Database operation is similar to a database point-in-time recovery (DBPITR) performed with RECOVER , but RMAN uses flashback logs to undo changes to a point before the target time or SCN.

➨ Post your comment / Share knowledge