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.
Within the standby database, you must then finish the recovery process. If you have configured
the standby database to have standby redo log files, the command to execute is
alter database recover managed standby database finish;
If there are no standby redo log files, execute the following command:
alter database recover managed standby database finish
skip standby logfile;
Once the standby recovery operation has completed, you can perform the switchover using
the following command:
alter database commit to switchover to primary;
Shut down and restart the new primary database to complete the transition. The old primary
database is no longer a part of the Data Guard configuration. If you want to re-create the old
primary database and use it as a standby database, you must create it as a standby database
following the steps provided earlier in this chapter.
Failovers to Logical Standby Databases
Failovers occur when the primary database can no longer be part of the primary database
configuration. In this section, you will see the steps required to fail over a logical standby
database to the role of the primary database in a Data Guard configuration.
Pages:
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745