In the standby database, you should first attempt to identify and resolve any gaps in the archived
redo log files (see the section ???Managing Gaps in Archive Log Sequences,??? earlier in this chapter).
You may need to manually copy and register log files for use by the standby database. Query the
DBA_LOGSTDBY_LOG view for details on the logs remaining to be applied. If the redo apply
process was not active on the logical standby database, start it using the following command:
alter database start logical standby apply nodelay finish;
Next, enable the remote locations for the redo log files that the logical standby database
generates. You may need to update the logical standby database??™s settings of the LOG_ARCHIVE_
DEST_STATE_n parameters so the other standby databases in the configuration will receive the
redo generated from the original logical standby database. You can then activate the original
logical standby database as the new primary database via the following command:
alter database activate logical standby database finish apply;
If there are other logical standby databases that are part of the Data Guard configuration, you
may need to re-create them or use database links to add them to the new configuration. First,
create a link in each of the databases that will act as a logical standby database to the new primary
Chapter 13: Oracle Data Guard 491
database. The alter session disable guard command allows you to bypass the Data Guard processes
within your session.
Pages:
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746