Sunday, July 12, 2015

Fast Start Failover



Setup the Data Guardbroker  configuration
dgmgrl
DGMGRL> connect sys/oracle
create configuration drs as    primary database is rmanp    connect identifier is rmanp;
add database rmans as   connect identifier is rmans   maintained as physical;
enable configuration;

DGMGRL> show configuration;

Configuration - drs

  Protection Mode: MaxAvailability
  Databases:
    rmanp - Primary database
    rmans - (*) Physical standby database

Fast-Start Failover: ENABLED

Configuration Status:
SUCCESS


Setup Fast failover:

Enable flashback on both databases

alter system set db_recovery_file_dest_size=2G;
alter system set db_recovery_file_dest='/u01/app/oracle/oradata';

set fast failover target

DGMGRL> EDIT DATABASE rmanp SET PROPERTY FastStartFailoverTarget = rmans;
DGMGRL> EDIT DATABASE rmans SET PROPERTY FastStartFailoverTarget = rmanp;

set log mode and protection mode
DGMGRL> EDIT DATABASE 'rmans' SET PROPERTY LogXptMode=SYNC;
DGMGRL> EDIT DATABASE 'rmanp' SET PROPERTY LogXptMode=SYNC;
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MaxAvailability;
DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverThreshold = 10;

FastStartFailoverThreshold Used to specify the number of seconds to delay failover after the detection of a primary database failure. This parameter defaults to 30 seconds.
FastStartFailoverPmyShutdown In its default setting of true, this parameter causes the primary database to shut down when FastStartFailoverThreshold has been reached for a particular database. This parameter setting is ignored in the case of a user-configurable condition failover.
FastStartFailoverLagLimit Allows for definition of the number of seconds the standby database is able to fall behind. When this threshold is exceeded, automatic failover will not be allowed.
FastStartFailoverAutoReinstate When set to its default of true, this parameter enables the automatic reinstatement of a failed primary database as a standby. Automatic reinstatement is not possible for user-configurable failover conditions regardless of this parameter setting.

DGMGRL> edit database 'cosp' set property  ' FastStartFailoverLagLimit '='60';
DGMGRL> ENABLE FAST_START FAILOVER CONDITION 'Inaccessible Logfile';

enable fash failover
DGMGRL> enable fast_start failover

DGMGRL>  show fast_start failover

Fast-Start Failover: ENABLED

  Threshold:        10 seconds
  Target:           rmans
  Observer:         Yusuf-PC
  Lag Limit:        30 seconds (not in use)
  Shutdown Primary: TRUE
  Auto-reinstate:   TRUE

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

  Oracle Error Conditions:
    (none)

DGMGRL> show configuration;

Configuration - drs

  Protection Mode: MaxAvailability
  Databases:
    rmanp - Primary database
    rmans - (*) Physical standby database

Fast-Start Failover: ENABLED

Configuration Status:
SUCCESS