Failover of the logical standby database (logicalstandbyfailover)

In Oracle10glogicalstandby mode, if the master database fails, the slave database can be quickly switched to the master database. See 7.3.2Fa in oracle official documentation

In Oracle 10g logical standby mode, if the master database fails, the slave database can be quickly switched to the master database. See 7.3.2 Fa in oracle official documentation

In Oracle 10g logical standby mode, if the master database fails, the slave database can be quickly switched to the master database.

Refer to chapter 7.3.2 Failovers Involving a Logical Standby Database in the oracle official document. The switchover process is described in detail.

The following three steps are summarized based on the actual project requirements.

Step 1: Disable the application mode of the logical standby database, and close all archived log files, minimizing data loss.

Use this SQL statement to check the log application.

SELECT APPLIED_SCN, LATEST_SCN from v $ LOGSTDBY_PROGRESS;

Select to_char (applied_scn), to_char (latest_scn) from v $ logstdby_progress;

If the two values are equal, proceed to the next step.

If the SQL application mode is not active, you can enable it.

SQL> ALTER DATABASE START LOGICAL STANDBY APPLY FINISH;

Database altered.

After the SQL application is completed, disable the SQL application mode. Here I restarted the database directly.

SQL> alter database open;

Database altered.

Step 2: Convert the logical standby database to the master database

SQL> ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY;

Database altered.

This statement stops the RFS process, applies the redo logs in all standby redo log files, stops the SQL application, and switches the slave database to the master database.

If finish apply is not specified, the redo log information in the standby redo log file will not be applied.