The LOG_ARCHIVE_
DEST_2 parameter gives the service name of the physical standby database as its location. For
each of these destinations, the corresponding LOG_ARCHIVE_DEST_STATE_n parameter should
have a value of ???ENABLE??™.
The standby role??“related parameters include the FAL (Fetch Archive Log) parameters used
prior to Oracle Database 10g to resolve gaps in the range of archive logs copied to the standby
databases:
TIP
FAL_SERVER and FAL_CLIENT should both be defined on each node
so they are ready to switch back to their original roles after a role
switch.
FAL_SERVER Specify the service name of the FAL server (typically the
primary database).
FAL_CLIENT Specify the service name of the FAL client (the standby
database fetching the logs).
DB_FILE_NAME_CONVERT If the primary and standby databases use differing directory
structures, specify the pathname and filename location of the
primary database datafiles, followed by the standby location.
LOG_FILE_NAME_CONVERT If the primary and standby databases use differing directory
structures, specify the pathname and filename location of the
primary database log files, followed by the standby location.
STANDBY_FILE_MANAGEMENT Set to AUTO.
Sample settings for these parameters are shown in the following listing:
FAL_SERVER=headqtr
FAL_CLIENT=salesofc
LOG_FILE_NAME_CONVERT=
'/arch/headqtr/','/arch/salesofc/','/arch1/headqtr/','/arch1/salesofc/'
STANDBY_FILE_MANAGEMENT=AUTO
482 Oracle Database 11g DBA Handbook
If the primary database is not already in ARCHIVELOG mode, enable archiving by issuing
the alter database archivelog command while the database is mounted but not open.
Pages:
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730