Using a larger or smaller recovery
window or adjusting the redundancy policy will require an adjustment in the size of the flash
recovery area. If the flash recovery area is limited in size due to disk space constraints, at a minimum
there should be enough room to hold the archived log files that have not yet been copied to tape.
The dynamic performance view V$RECOVERY_FILE_DEST displays information about the number
of files in the flash recovery area, how much space is currently being used, and the total amount
of space available in the flash recovery area.
The flash recovery area automatically uses OMF. As part of Oracle 11g??™s simplified
management structure, you do not need to explicitly set any of the LOG_ARCHIVE_DEST_n
initialization parameters if you only need one location for archived redo log files; if the database
is in ARCHIVELOG mode, and a flash recovery area is defined, then the initialization parameter
LOG_ARCHIVE_DEST_10 is implicitly defined as the flash recovery area.
As you have seen in many previous examples, RMAN uses the flash recovery area in a very
organized fashion??”with separate directories for archived logs, backupsets, image copies, block
change tracking files, and automatic backups of the control file and SPFILE. In addition, each
subdirectory is further subdivided by a datestamp, making it easy to find a backupset or image
copy when the need arises.
Multiple databases can share the same flash recovery area, even a primary and a standby
database.
Pages:
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696