Before starting the database in ARCHIVELOG mode, make sure you are using one of the
following configurations, listed from most to least recommended:
Enable archiving to the flash recovery area only; use disk mirroring on the disks containing
the flash recovery area. The DB_RECOVERY_FILE_DEST parameter specifies the file system
location or ASM disk group containing the flash recovery area. If you configured your
Oracle Database 11g using the same options as the installation in the appendix to this
book, you created the flash recovery area on a mirrored ASM disk group.
Enable archiving to the flash recovery area and set at least one LOG_ARCHIVE_DEST_n
parameter to another location outside of the flash recovery area.
Set at least two LOG_ARCHIVE_DEST_n parameters to archive to non-flash recovery area
destinations.
NOTE
If the initialization parameter DB_RECOVERY_FILE DEST is specified
and no LOG_ARCHIVE_DEST_n parameter is specified, then LOG_
ARCHIVE_DEST_10 is implicitly set to the flash recovery area.
In the following examples, I assume that the best configuration, a single mirrored flash
recovery area, has been selected. The following listing shows the steps needed to place a
database in ARCHIVELOG mode; first, shut down the database, and then issue these commands:
SQL> startup mount;
SQL> alter database archivelog;
SQL> alter database open;
NOTE
To see the currently active online redo log and its sequence number,
query the V$LOG dynamic view.
Pages:
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642