Steps to Enable fast_start failover (automatic) in Data Guard(DG) Broker

advertisements

_____________________________________________________________________________________________________________________

Assumption: 

You have setup the data guard and broker successfully and the apply is working properly. 

Steps to Setup Data Guard

Steps To Setup DG Broker

Steps 

1. Enable the flashback on both primary and standby database using following commands.

SQL> Select flashback_on from gv$database;

FLASHBACK_ON
------------------
NO
NO

SQL> show parameter flashb

NAME                                 TYPE        VALUE
------------------------------------ ----------- -----------
db_flashback_retention_target        integer     1440

SQL>  ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=2880 scope=both sid='*';

System altered.

SQL> alter database recover managed standby database cancel;

Database altered.

SQL> alter database flashback ON;

Database altered.

SQL> Select flashback_on from gv$database;

FLASHBACK_ON
------------------
YES
YES

2. Connect dgmgrl and enable the conditions as per the requirement using following commands.

DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverThreshold = '90';
Property "faststartfailoverthreshold" updated

For primary database set the standby database as failover target.
DGMGRL> EDIT DATABASE 'CRMPROD' SET PROPERTY FastStartFailoverTarget = 'CRMPRODSTBY';
Property "faststartfailovertarget" updated

For Standby database set the primary database as failover target.
DGMGRL> EDIT DATABASE 'CRMPRODSTBY' SET PROPERTY FastStartFailoverTarget = 'CRMPROD';
Property "faststartfailovertarget" updated
DGMGRL> ENABLE FAST_START FAILOVER CONDITION 'Inaccessible Logfile';
Succeeded.

Other conditions:

      Corrupted Controlfile

      Corrupted Dictionary
      Inaccessible Logfile
      Stuck Archiver
      Datafile Offline

3. Check the fast_start failover status using following command. Currently disabled but the settings are done.

DGMGRL> show fast_start failover

Fast-Start Failover: DISABLED

  Threshold:          180 seconds
  Target:             (none)
  Observer:           (none)
  Lag Limit:          30 seconds
  Shutdown Primary:   TRUE
  Auto-reinstate:     TRUE
  Observer Reconnect: (none)
  Observer Override:  FALSE

Configurable Failover Conditions
  Health Conditions:
    Corrupted Controlfile          YES
    Corrupted Dictionary           YES
    Inaccessible Logfile           YES
    Stuck Archiver                  NO
    Datafile Offline               YES

  Oracle Error Conditions:
    (none)

4. Enable fast_start failover

 

DGMGRL> enable fast_start failover
Enabled.
DGMGRL> show fast_start failover

Fast-Start Failover: ENABLED

  Threshold:          180 seconds
  Target:             ADMPRODSTBY
  Observer:           (none)
  Lag Limit:          30 seconds (not in use)
  Shutdown Primary:   TRUE
  Auto-reinstate:     TRUE
  Observer Reconnect: (none)
  Observer Override:  FALSE

Configurable Failover Conditions
  Health Conditions:
    Corrupted Controlfile          YES
    Corrupted Dictionary           YES
    Inaccessible Logfile            NO
    Stuck Archiver                  NO
    Datafile Offline               YES

  Oracle Error Conditions:
    (none)s

5. If you find a warning(ORA-16819) in DG broker; you will have to start observer process using following command.

 

a.  Foreground mode: Connect to dgmgrl using sys user credentials and run
DGMGRL> start observer
b.  Background Mode: run the following command after login as oracle.
dgmgrl -logfile $HOME/observer.log sys/paygate1 "start observer" &

DGMGRL> show configuration;

Configuration - DG_Conf

  Protection Mode: MaxAvailability
  Members:
  ADMPROD       - Primary database

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

Steps to Setup Data Guard

Steps To Setup DG Broker

_____________________________________________________________________________________________________________________

Website Stats