Oracle 11g DG Broker open fast-start failover automatic failover

A. First, to ensure that owners are open from Flashback Database feature, and forced the archive database, following assurances are yes

SQL> select flashback_on,force_logging from v$database;

FLASHBACK_ON      FOR

------------------ ---

NO NO

1.1 open Flashback Database

SQL> ALTER SYSTEM SET db_recovery_file_dest_size=3g SCOPE=BOTH;

System altered.

System altered.

SQL> alter database flashback on;

Database altered.

1.2 forced open archives

SQL>  alter database force logging;

Database altered.

SQL> select flashback_on,force_logging from v$database;

FLASHBACK_ON      FOR

------------------ ---

YES                YES

 


Two: open fast-start failover

2.1: Open the fast-start failover

DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production

Copyright (c) 2000, 2009, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.

Connected.

DGMGRL>  enable fast_start failover;

Enabled.

2.2. Check the configuration state, found that warning because the observer does not start and the alarm!

DGMGRL> show configuration

Configuration - dbha_c

Protection Mode: MaxPerformance

Databases:

db2 - Primary database

Warning: ORA-16819: fast-start failover observer not started

db1 - (*) Physical standby database

Warning: ORA-16819: fast-start failover observer not started

Fast-Start Failover: ENABLED

Configuration Status:

WARNING

2.3 Start Open observer (observer):

DGMGRL> show configuration

Configuration - dbha_c

Protection Mode: MaxPerformance

Databases:

db2 - Primary database

db1 - (*) Physical standby database

Fast-Start Failover: ENABLED

Configuration Status:

SUCCESS

Since the start of the observer will always occupy session window, it is recommended that written script to hang backstage

Here we create a script on the standby database, as follows

Create a script called observer.sql, the following command into them, and then execute the script.

nohup dgmgrl  sys/oracle@db2 "start observer">>observer.log 2>&1 &

III: Verify automatic switching:

db2 main library:

SQL> select  DATABASE_ROLE,OPEN_MODE from  v$database;

 


DATABASE_ROLE    OPEN_MODE

---------------- --------------------

PRIMARY          READ WRITE

db1 as standby

SQL> select  DATABASE_ROLE,OPEN_MODE from  v$database;

DATABASE_ROLE    OPEN_MODE

---------------- --------------------

PHYSICAL STANDBY READ ONLY WITH APPLY

db2 simulations of closed main library

SQL> shu abort

ORACLE instance shut down.

View the status of db1 again:

SQL> select  DATABASE_ROLE,OPEN_MODE from  v$database;

DATABASE_ROLE    OPEN_MODE

---------------- --------------------

PRIMARY          READ WRITE

Guess you like

Origin www.linuxidc.com/Linux/2019-08/160287.htm