Fast Start Failover Disabled

Onur ARDAHANLI

2 years ago

We may request that Fast start Failover be disabled. We can do this disable process in 2 ways.

Without using the FORCE option

SYNTAX
DISABLE FAST_START FAILOVER;

1 2	SYNTAX DISABLE FAST_START FAILOVER;

This is how the system works when this command is run.

The broker disables Fast-start Failover first in Target Standby Database and then in Primary Database. Writes this information to the Broker configuration file. Then it sends this information to all databases in Environment.

Disable with FORCE option

SYNTAX 
DISABLE FAST_START FAILOVER FORCE;

1 2	SYNTAX DISABLE FAST_START FAILOVER FORCE;

In case the Primary Database does not communicate with the Fast-start Failover Target Standby Database, the operation of the system is as follows if this command is run on the Primary or other Standby Databases with the FORCE option.

In whichever database it was run, it is disabled only in that database for the moment.

It is only written to the Broker configuration file of the running database for the moment.

It then sends this change to all Broker configurations that communicate with the Primary in the Environment.

If the Primary Database does not communicate with the Fast-start Failover Target Standby Database, the operation of the system is as follows if this command is run on the Target Standby Database with the FORCE option.

Fast-start Failover is disabled only in Target Standby Database. When the Target Standby Database reconnects with the Primary, the Primary Database is also disabled.

In the light of this information, it would be best to run the Fast-start Failover disable command in either Primary or bystander Standby.

Disable steps are below.

1. Disable command is executed

DGMGRL> disable fast_start failover;
Disabled.

1 2	DGMGRL> disable fast_start failover; Disabled.

2. We check if it is disabled.

DGMGRL> show configuration verbose

Configuration - Broker_Configuration

  Protection Mode: MaxPerformance
  Databases:
    primary - Primary database
    standby - Physical standby database
    logical - Logical standby database

  Properties:
    FastStartFailoverThreshold      = '100'
    OperationTimeout                = '30'
    FastStartFailoverLagLimit       = '900'
    CommunicationTimeout            = '180'
    ObserverReconnect               = '15'
    FastStartFailoverAutoReinstate  = 'TRUE'
    FastStartFailoverPmyShutdown    = 'TRUE'
    BystandersFollowRoleChange      = 'ALL'
    ObserverOverride                = 'FALSE'
    ExternalDestination1            = ''
    ExternalDestination2            = ''
    PrimaryLostWriteAction          = 'CONTINUE'

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS

DGMGRL> show configuration verbose

Configuration - Broker_Configuration

Protection Mode: MaxPerformance

Databases:

primary - Primary database

standby - Physical standby database

logical - Logical standby database

Properties:

FastStartFailoverThreshold = '100'

OperationTimeout = '30'

FastStartFailoverLagLimit = '900'

CommunicationTimeout = '180'

ObserverReconnect = '15'

FastStartFailoverAutoReinstate = 'TRUE'

FastStartFailoverPmyShutdown = 'TRUE'

BystandersFollowRoleChange = 'ALL'

ObserverOverride = 'FALSE'

ExternalDestination1 = ''

ExternalDestination2 = ''

PrimaryLostWriteAction = 'CONTINUE'

Fast-Start Failover: DISABLED

Configuration Status:

SUCCESS

OperationTimeout: It is the maximum time that the broker will wait to receive and set parameters that can be monitored with health check.

CommunicationTimeout: Shows the broker’s waiting time before the network communication between databases in the broker configuration falls into timeout.

3. We check the status of the Observer.

Even if Fast-start Failover is disabled, the Observer will not be stopped automatically, it will remain idle until Fast-start Failover is enabled again.