{"id":52011,"date":"2022-08-08T17:00:40","date_gmt":"2022-08-08T17:00:40","guid":{"rendered":"https:\/\/dbtut.com\/?p=52011"},"modified":"2022-08-08T17:07:11","modified_gmt":"2022-08-08T17:07:11","slug":"fast-start-failover-configuration","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/","title":{"rendered":"Fast-Start Failover Configuration"},"content":{"rendered":"

In today’s article, we will examine Fast-Start Failover Configuration.<\/p>\n

The configuration of Fast-Start Failover consists of the following 8 steps in summary.<\/p>\n

A. Identifying the Fast-start Failover Standby Database<\/p>\n

B. Setting Data Protection Mode<\/p>\n

C. Setting the threshold value at which Fast-start Failover will occur<\/p>\n

\u00c7. Setting additional Fast-start Failover features<\/p>\n

D. Setting the additional conditions we want to happen<\/p>\n

E. Activating Fast-start Failover<\/p>\n

F.Starting Observer<\/p>\n

G. Verifying the configuration<\/p>\n

Now let’s see how these operations are done.<\/p>\n

Commands run from DGMGRL will be run from Primary-1 unless specified separately.<\/p>\n

A. Identifying the Fast-start Failover Standby Database<\/h4>\n

The first step of Fast-start Failover configuration is to determine the Target Standby Database.<\/p>\n

1. We query the current status of the Fast-start Failover configuration.<\/p>\n

DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
2. We question the Fast-start Failover configuration in detail.<\/p>\n
DGMGRL> show fast_start failover\r\n\r\nFast-Start Failover: DISABLED\r\n\r\n  Threshold:          30 seconds\r\n  Target:             (none)\r\n  Observer:           (none)\r\n  Lag Limit:          30 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: (none)\r\n  Observer Override:  FALSE\r\n\r\nConfigurable Failover Conditions\r\n  Health Conditions:\r\n    Corrupted Controlfile          YES\r\n    Corrupted Dictionary           YES\r\n    Inaccessible Logfile            NO\r\n    Stuck Archiver                  NO\r\n    Datafile Offline               YES\r\n\r\n  Oracle Error Conditions:\r\n    (none)\r\n<\/pre>\n
3. Fast-start Failover Target Standby Database is determined.<\/p>\n
\tDGMGRL> edit database primary set property FastStartFailoverTarget=standby;\r\n\tProperty \"faststartfailovertarget\" updated\r\n<\/pre>\n
4. We query the Fast-start Failover configuration again.<\/p>\n
DGMGRL> show fast_start failover\r\n\r\nFast-Start Failover: DISABLED\r\n\r\n  Threshold:          30 seconds\r\n  Target:             (none)\r\n  Observer:           (none)\r\n  Lag Limit:          30 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: (none)\r\n  Observer Override:  FALSE\r\n\r\nConfigurable Failover Conditions\r\n  Health Conditions:\r\n    Corrupted Controlfile          YES\r\n    Corrupted Dictionary           YES\r\n    Inaccessible Logfile            NO\r\n    Stuck Archiver                  NO\r\n    Datafile Offline               YES\r\n\r\n  Oracle Error Conditions:\r\n    (none)\r\n<\/pre>\n
There is no change in the configuration. It is necessary to ENABLE Fast-start Failover for it to appear, or we can see it when queried as follows.<\/p>\n
DGMGRL> show database primary FastStartFailoverTarget;\r\n  FastStartFailoverTarget = 'standby'\r\nDGMGRL> show database standby FastStartFailoverTarget;\r\n  FastStartFailoverTarget = ''\r\n<\/pre>\n
B. Setting Data Protection Mode<\/h4>\n
To enable Fast-start Failover, Data Protection mode must be in either Maximum Availability or Maximum Performance mode.<\/p>\n
It is important to choose the right protection mode, as it has a direct effect on data loss in the event of a disaster.<\/p>\n
If it is decided to use Maximum Performance mode, the FastStartFailoverLagLimit parameter must be set.<\/p>\n
This parameter determines that Fast-start Failover will be activated when the maximum number of seconds of lag occurs.<\/p>\n
1. We check the current Data Protection Mode.<\/p>\n
DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
2. We question Redo-Transport Mods.<\/p>\n
DGMGRL> show database primary 'LogXptMode';\r\n  LogXptMode = 'ASYNC'\r\nDGMGRL> show database standby 'LogXptMode';\r\n  LogXptMode = 'ASYNC'\r\nDGMGRL> Show database logical 'LogXptMode';\r\n  LogXptMode = 'ASYNC'\r\n<\/pre>\n
3. If I want Redos to SYNC to Fast-start Failover Standby Database, I follow these steps.<\/p>\n
DGMGRL> edit database primary set property 'LogXptMode'=SYNC;\r\nProperty \"LogXptMode\" updated\r\nDGMGRL> edit database standby set property LogXptMode=SYNC;\r\nProperty \"logxptmode\" updated\r\nDGMGRL> edit configuration set protection mode as MaxAvailability;\r\nSucceeded.\r\n<\/pre>\n
DGMGRL> show configuration \r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxAvailability\r\n  Databases:\r\n    primary - Primary database\r\n      Warning: ORA-16629: database reports a different protection level from the protection mode\r\n\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nWARNING\r\n<\/pre>\n
The reason for this error is because I did not use the correct syntax when setting LogXptMode for Primary Database.<\/p>\n
The syntax is corrected and queried again.<\/p>\n
DGMGRL> edit database primary set property LogXptMode=SYNC;\r\nProperty \"logxptmode\" updated\r\nDGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxAvailability\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
4. To see how to set the FastStartFailoverLagLimit parameter when Maximum Performance mode is used, I change the Protection Mode again and set the parameter.<\/p>\n
The default value of this parameter is 30 seconds.<\/p>\n
DGMGRL> show configuration verbose\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\n  Properties:\r\n    FastStartFailoverThreshold      = '30'\r\n    OperationTimeout                = '30'\r\n    FastStartFailoverLagLimit       = '30'\r\n    CommunicationTimeout            = '180'\r\n    ObserverReconnect               = '0'\r\n    FastStartFailoverAutoReinstate  = 'TRUE'\r\n    FastStartFailoverPmyShutdown    = 'TRUE'\r\n    BystandersFollowRoleChange      = 'ALL'\r\n    ObserverOverride                = 'FALSE'\r\n    ExternalDestination1            = ''\r\n    ExternalDestination2            = ''\r\n    PrimaryLostWriteAction          = 'CONTINUE'\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
DGMGRL> edit database primary set property LogXptMode=ASYNC;\r\nError: ORA-16802: downgrading redo transport mode from SYNC disallowed\r\n\r\nFailed.\r\n<\/pre>\n
The reason for this error is that the Protection Mode needs to be changed first.<\/p>\n
DGMGRL> edit configuration set protection mode as MaxPerformance;\r\nSucceeded.\r\nDGMGRL> edit database primary set property LogXptMode=ASYNC;\r\nProperty \"logxptmode\" updated\r\nDGMGRL> edit database standby set property LogXptMode=ASYNC;\r\nProperty \"logxptmode\" updated\r\nDGMGRL> edit database logical set property LogXptMode=ASYNC;\r\nProperty \"logxptmode\" updated\r\n<\/pre>\n
DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
DGMGRL> show database primary LogXptMode;               \r\n  LogXptMode = 'async'\r\nDGMGRL> show database standby LogXptMode;\r\n  LogXptMode = 'async'\r\nDGMGRL> show database logical LogXptMode;\r\n  LogXptMode = 'async'\r\n<\/pre>\n
DGMGRL> edit configuration set property FastStartFailoverLagLimit=900;\r\nProperty \"faststartfailoverlaglimit\" updated\r\nDGMGRL> show configuration verbose\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\n  Properties:\r\n    FastStartFailoverThreshold      = '30'\r\n    OperationTimeout                = '30'\r\n    FastStartFailoverLagLimit       = '900'\r\n    CommunicationTimeout            = '180'\r\n    ObserverReconnect               = '0'\r\n    FastStartFailoverAutoReinstate  = 'TRUE'\r\n    FastStartFailoverPmyShutdown    = 'TRUE'\r\n    BystandersFollowRoleChange      = 'ALL'\r\n    ObserverOverride                = 'FALSE'\r\n    ExternalDestination1            = ''\r\n    ExternalDestination2            = ''\r\n    PrimaryLostWriteAction          = 'CONTINUE'\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
C. Setting the threshold value at which Fast-start Failover will occur<\/h4>\n
Fast-start Failover Standby Database and how long the Observer does not receive a response from the Primary Database, determines how Fast-start Failover will be triggered.<\/p>\n
This is done with the FastStartFailoverThreshold parameter.<\/p>\n
This parameter must be set very accurately to prevent an unnecessary failover.<\/p>\n
For example, if our network connection is constantly interrupted for a few seconds, setting this parameter value low will do more harm than good.<\/p>\n
Oracle recommends the optimum values to set this parameter based on.<\/p>\n
For a system with a single instace Primary with almost no network latency: 10-15 seconds<\/p>\n
For a network latency system with a single instace Primary: 30-45 seconds<\/p>\n
For a build with RAC Primary: CSS Miss Count + Reconfiguration Time + 24-40 seconds.<\/p>\n
The CSS Miss Count is found as follows.<\/p>\n
[grid@primary1 ~]$ cd $GRID_HOME\r\n[grid@primary1 grid]$ crsctl get css misscount;\r\nCRS-4678: Successful get misscount 30 for Cluster Synchronization Services.<\/pre>\n
1. In the light of the information above, I set this value to 100 since I use RAC structure and CSS MissCount value is 30 seconds.<\/p>\n
DGMGRL> show configuration verbose\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\n  Properties:\r\n    FastStartFailoverThreshold      = '30'\r\n    OperationTimeout                = '30'\r\n    FastStartFailoverLagLimit       = '900'\r\n    CommunicationTimeout            = '180'\r\n    ObserverReconnect               = '0'\r\n    FastStartFailoverAutoReinstate  = 'TRUE'\r\n    FastStartFailoverPmyShutdown    = 'TRUE'\r\n    BystandersFollowRoleChange      = 'ALL'\r\n    ObserverOverride                = 'FALSE'\r\n    ExternalDestination1            = ''\r\n    ExternalDestination2            = ''\r\n    PrimaryLostWriteAction          = 'CONTINUE'\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
DGMGRL> edit configuration set property FastStartFailoverThreshold=100;\r\nProperty \"faststartfailoverthreshold\" updated\r\n<\/pre>\n
DGMGRL> show configuration FastStartFailoverThreshold\r\n  FastStartFailoverThreshold = '100'\r\n<\/pre>\n
\u00c7. Setting additional Fast-start Failover features<\/h4>\n
In order to use Fast-start Failover most accurately, I need to set many additional parameters.<\/p>\n
a. FastStartFailoverLagLimit<\/h5>\n
We have given information in Protection mode, but there are some restrictions on the use of this parameter.<\/p>\n
A conscious use is essential as it is a parameter that directly affects data loss.<\/p>\n
Can be set while in Maximum Performance Mode.<\/p>\n
Maximum Availability is invalid in this mode because SYNC is already running.<\/p>\n
Real-Time Apply must be enabled on the standby side.<\/p>\n
The default value is 30 and the minimum value is 10.<\/p>\n
DGMGRL> edit configuration set property FastStartFailoverLagLimit=900;\r\nProperty \"faststartfailoverlaglimit\" updated\r\nDGMGRL> show configuration verbose\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\n  Properties:\r\n    FastStartFailoverThreshold      = '30'\r\n    OperationTimeout                = '30'\r\n    FastStartFailoverLagLimit       = '900'\r\n    CommunicationTimeout            = '180'\r\n    ObserverReconnect               = '0'\r\n    FastStartFailoverAutoReinstate  = 'TRUE'\r\n    FastStartFailoverPmyShutdown    = 'TRUE'\r\n    BystandersFollowRoleChange      = 'ALL'\r\n    ObserverOverride                = 'FALSE'\r\n    ExternalDestination1            = ''\r\n    ExternalDestination2            = ''\r\n    PrimaryLostWriteAction          = 'CONTINUE'\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
b. FastStartFailoverPmyShutdown<\/h5>\n
It determines whether the Primary Database will be closed after the Failover that will occur by disconnecting the Primary Database from the Observer and Target Standby Database.<\/p>\n
The default value is TRUE, that is, it is turned off.<\/p>\n
TRUE: After the Failover that occurs after the FastStartFailoverThreshold value, the Primary Database is shut down with Shutdown Abort.<\/p>\n
FALSE: Primary Database is not turned off to see what is causing the failover.<\/p>\n
This information is visible from the V$FS_FAILOVER_STATS view.<\/p>\n
If I don’t want it shut down.<\/p>\n
DGMGRL> edit configuration set property FastStartFailoverPmyShutdown=FALSE;\r\nProperty \"faststartfailoverpmyshutdown\" updated\r\nDGMGRL> show configuration FastStartFailoverPmyShutdown \r\n  FastStartFailoverPmyShutdown = 'FALSE'\r\n<\/pre>\n
I set it back to TRUE because I want it to be turned off.<\/p>\n
DGMGRL> edit configuration set property FastStartFailoverPmyShutdown=TRUE ;\r\nProperty \"faststartfailoverpmyshutdown\" updated\r\nDGMGRL> show configuration FastStartFailoverPmyShutdown\r\n  FastStartFailoverPmyShutdown = 'TRUE'\r\n<\/pre>\n
In case of user configuration or an application with SYSDBA authorization calls Failover with the DBMS_DG.INITIATE_FS_FAILOVER function, the Primary Database is shutdown even if this parameter is set to FALSE.<\/p>\n
c. FastStartFailoverAutoReinstate<\/h5>\n
It specifies whether the Primary Database, which will no longer work after failover, will be automatically made as a Physical Standby Database.<\/p>\n
We call this process REINSTATE. Its default value is TRUE. There are some prerequisites for this process.<\/p>\n
The FastStartFailoverAutoReinstate parameter is TRUE.<\/p>\n
Before failover and after the original Primary Database’s restart, the original and new primary databases must have the same Fast-start Failover configuration.<\/p>\n
The Observer that will perform the REINSTATE and the New Primary Database must be able to connect to the original Primary database.<\/p>\n
If automatic REINSTATE is not requested;<\/p>\n
DGMGRL> edit configuration set property FastStartFailoverAutoReinstate=FALSE;\r\nProperty \"faststartfailoverautoreinstate\" updated\r\nDGMGRL> show configuration FastStartFailoverAutoReinstate\r\n  FastStartFailoverAutoReinstate = 'FALSE'\r\n<\/pre>\n
I want automatic REINSTATE again I set the parameter to TRUE.<\/p>\n
DGMGRL> edit configuration set property FastStartFailoverAutoReinstate=TRUE;\r\nProperty \"faststartfailoverautoreinstate\" updated\r\nDGMGRL> show configuration FastStartFailoverAutoReinstate\r\n  FastStartFailoverAutoReinstate = 'TRUE'\r\n<\/pre>\n
\u00e7. ObserverConnectIdentifier<\/h5>\n
It is the parameter that determines how the Observer will be connected to the Primary and Standby Database.<\/p>\n
By default, this value takes the “DGConnectIdentifier” parameter. If a different value is not used, there is no need to set it.<\/p>\n
We set it as follows.<\/p>\n
1. We query the current value of the parameter.<\/p>\n
DGMGRL> show database primary ObserverConnectIdentifier\r\n  ObserverConnectIdentifier = ''\r\nDGMGRL> show database standby ObserverConnectIdentifier\r\n  ObserverConnectIdentifier = ''\r\nDGMGRL> show database logical ObserverConnectIdentifier\r\n  ObserverConnectIdentifier = ''<\/pre>\n
2. We set the parameter to its new value.<\/p>\n
DGMGRL> edit database primary set property ObserverConnectIdentifier=PRIMARY;\r\nProperty \"observerconnectidentifier\" updated\r\nDGMGRL> edit database logical set property ObserverConnectIdentifier=LOGICAL;\r\nProperty \"observerconnectidentifier\" updated\r\nDGMGRL> edit database standby set property ObserverConnectIdentifier=STANDBY;\r\nProperty \"observerconnectidentifier\" updated\r\n<\/pre>\n
3. We check if the new value is set.<\/p>\n
DGMGRL> show database primary ObserverConnectIdentifier\r\n  ObserverConnectIdentifier = 'primary'\r\nDGMGRL> show database standby ObserverConnectIdentifier\r\n  ObserverConnectIdentifier = 'standby'\r\nDGMGRL> show database logical ObserverConnectIdentifier\r\n  ObserverConnectIdentifier = 'logical'\r\n<\/pre>\n
4. We said that if the parameter was not set, we would use DGConnectIdentifier.<\/p>\n
The DGConnectIdentifier is queried to see its value.<\/p>\n
DGMGRL> show database logical DGConnectIdentifier\r\n  DGConnectIdentifier = 'logical'\r\nDGMGRL> show database primary DGConnectIdentifier\r\n  DGConnectIdentifier = 'primary'\r\nDGMGRL> show database standby DGConnectIdentifier\r\n  DGConnectIdentifier = 'standby'<\/pre>\n
d. ObserverOverride<\/h5>\n
Even if the Standby Database has communication with the Primary, it indicates whether the Failover operation will be performed in case the Observer’s communication with the Primary is lost. Default is FALSE.<\/p>\n
DGMGRL> edit configuration set property ObserverOverride=FALSE;\r\nProperty \"observeroverride\" updated\r\nDGMGRL> show configuration ObserverOverride\r\n  ObserverOverride = 'FALSE'\r\n<\/pre>\n
e. ObserverReconnect<\/h5>\n
It determines how often the Observer will establish a connection with the Primary Database. Default value is 0.<\/p>\n
In other words, a connection will be established initially, and then there will be no request to establish a connection again.<\/p>\n
The advantage of this is that it does not burden the system with new connections, and the disadvantage is that it is not possible to understand whether the Primary will go or not without new connection requests.<\/p>\n
Oracle recommends that this value be set so that neither too often a connection load nor too rare a disconnection of communication is detected too late.<\/p>\n
DGMGRL> edit configuration set property ObserverReconnect=15;\r\nProperty \"observerreconnect\" updated\r\nDGMGRL> show configuration ObserverReconnect\r\n  ObserverReconnect = '15'\r\n<\/pre>\n
D. Setting the additional conditions we want to happen<\/h4>\n
When the following conditions occur apart from the parameters, it may request the Failover to be triggered without waiting for the FastStartFailoverThreshold value.<\/p>\n
When Datafile goes offline,<\/p>\n
When Dictionary Corruption occurs in a critical database object,<\/p>\n
If the Control File is damaged due to a problem with the disk,<\/p>\n
In case LGWR process cannot write to Online Redo Logs,<\/p>\n
If the archive process cannot create an archive due to lack of space in the relevant path, FAST START FAILOVER operation takes place.<\/p>\n
When a specific ORA error is received\u2026<\/p>\n
1. What these features are can be seen as follows.<\/p>\n
DGMGRL> show fast_start failover\r\n\r\nFast-Start Failover: DISABLED\r\n\r\n  Threshold:          100 seconds\r\n  Target:             (none)\r\n  Observer:           (none)\r\n  Lag Limit:          900 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: 15 seconds\r\n  Observer Override:  FALSE\r\n\r\nConfigurable Failover Conditions\r\n  Health Conditions:\r\n    Corrupted Controlfile          YES\r\n    Corrupted Dictionary           YES\r\n    Inaccessible Logfile            NO\r\n    Stuck Archiver                  NO\r\n    Datafile Offline               YES\r\n\r\n  Oracle Error Conditions:\r\n    (none)\r\n<\/pre>\n
2. We can enable a condition that is NO in the default as follows.<\/p>\n
DGMGRL> enable fast_start failover condition \"Inaccessible Logfile\";\r\nSucceeded.\r\nDGMGRL> show fast_start failover\r\n\r\nFast-Start Failover: DISABLED\r\n\r\n  Threshold:          100 seconds\r\n  Target:             (none)\r\n  Observer:           (none)\r\n  Lag Limit:          900 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: 15 seconds\r\n  Observer Override:  FALSE\r\n\r\nConfigurable Failover Conditions\r\n  Health Conditions:\r\n    Corrupted Controlfile          YES\r\n    Corrupted Dictionary           YES\r\n    Inaccessible Logfile           YES\r\n    Stuck Archiver                  NO\r\n    Datafile Offline               YES\r\n\r\n  Oracle Error Conditions:\r\n    (none)\r\n<\/pre>\n
3. We can enable specific ORA errors as follows.<\/p>\n
DGMGRL> enable fast_start failover condition '1578';\r\nSucceeded.\r\nDGMGRL> show fast_start failover;\r\n\r\nFast-Start Failover: DISABLED\r\n\r\n  Threshold:          100 seconds\r\n  Target:             (none)\r\n  Observer:           (none)\r\n  Lag Limit:          900 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: 15 seconds\r\n  Observer Override:  FALSE\r\n\r\nConfigurable Failover Conditions\r\n  Health Conditions:\r\n    Corrupted Controlfile          YES\r\n    Corrupted Dictionary           YES\r\n    Inaccessible Logfile           YES\r\n    Stuck Archiver                  NO\r\n    Datafile Offline               YES\r\n\r\n  Oracle Error Conditions:\r\n    ORA-01578: ORACLE data block corrupted (file # %s, block # %s)\r\n<\/pre>\n
E. Activating Fast-start Failover<\/h4>\n
I can now enable Fast-start Failover after I have made both parameter and all condition’ settings.<\/p>\n
There is no Observer at this stage yet. Primary Database and Fast-start Failover Standby Database are communicating.<\/p>\n
We will get this warning when we enable Fast-start Failover anyway.<\/p>\n
\"\"<\/p>\n
DGMGRL> enable fast_start failover;\r\nEnabled.\r\nDGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n      Warning: ORA-16819: fast-start failover observer not started\r\n\r\n    standby - (*) Physical standby database\r\n      Warning: ORA-16819: fast-start failover observer not started\r\n\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: ENABLED\r\n\r\nConfiguration Status:\r\nWARNING\r\n<\/pre>\n
The information falling to the logs during activation is as follows.<\/p>\n[Primary-1]—–>ALERT_LOG<\/p>\n
Fri Jan 27 13:33:54 2017\r\nFast-Start Failover (FSFO) has been enabled between:\r\n  Primary = \"primary\"\r\n  Standby = \"standby\"\r\nFri Jan 27 13:33:54 2017\r\nFSFP started with pid=27, OS id=21775 \r\n<\/pre>\n[Primary-2]—–>ALERT_LOG<\/p>\n
Fri Jan 27 13:34:12 2017\r\nFSFP started with pid=49, OS id=31147 \r\n<\/pre>\n
The process is controlled by the operating system.<\/p>\n
[root@primary1 ~]# ps -ef |grep fsfp |grep -v grep\r\noracle   21775     1  0 13:33 ?        00:00:00 ora_fsfp_primary1\r\n<\/pre>\n
[root@primary2 ~]# ps -ef |grep fsfp |grep -v grep\r\noracle   31147     1  0 13:34 ?        00:00:00 ora_fsfp_primary2\r\n<\/pre>\n
F.Starting Observer<\/h4>\n
Observer must first be run on a separate server, if available, or run on Fast-start Failover Standby Database.<\/p>\n
When the Observer is run, it tells the Broker to manage the monitoring job of the Data Guard Environment via DGMGRL.<\/p>\n
There is only 1 Observer in the Data Guard Environment.<\/p>\n
It does all the management with a small configuration file containing information and connection definitions of Observer, Primary and Standby Databases.<\/p>\n
Observer is a foreground process. Therefore, it keeps the command prompt busy all the time.<\/p>\n
Once stopped, something can be done at the command prompt again.<\/p>\n
Therefore, it should be at a point where it will work continuously.<\/p>\n
For example, on Terminal servers.<\/p>\n
1. The Observer is started.<\/p>\n
DGMGRL> start observer;\r\nObserver Started.\r\n<\/pre>\n
2. We are querying the status of the configuration.<\/p>\n
DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - (*) Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: ENABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
3. The Terminal window where the Observer is started is closed with a cross and the status of the Configuration is questioned.<\/p>\n
DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - (*) Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: ENABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
Although the Observer was not running, it did not give an error warning in the configuration.<\/p>\n
The reason is that the ObserverReconnect parameter is set to 15 seconds.<\/p>\n
We wait for a while and question again.<\/p>\n
DGMGRL> show configuration verbose\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n      Error: ORA-16820: fast-start failover observer is no longer observing this database\r\n\r\n    standby - (*) Physical standby database\r\n      Error: ORA-16820: fast-start failover observer is no longer observing this database\r\n\r\n    logical - Logical standby database\r\n\r\n  (*) Fast-Start Failover target\r\n\r\n  Properties:\r\n    FastStartFailoverThreshold      = '100'\r\n    OperationTimeout                = '30'\r\n    FastStartFailoverLagLimit       = '900'\r\n    CommunicationTimeout            = '180'\r\n    ObserverReconnect               = '15'\r\n    FastStartFailoverAutoReinstate  = 'TRUE'\r\n    FastStartFailoverPmyShutdown    = 'TRUE'\r\n    BystandersFollowRoleChange      = 'ALL'\r\n    ObserverOverride                = 'FALSE'\r\n    ExternalDestination1            = ''\r\n    ExternalDestination2            = ''\r\n    PrimaryLostWriteAction          = 'CONTINUE'\r\n\r\nFast-Start Failover: ENABLED\r\n\r\n  Threshold:          100 seconds\r\n  Target:             standby\r\n  Observer:           standby1.tivibulab.local\r\n  Lag Limit:          900 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: 15 seconds\r\n  Observer Override:  FALSE\r\n\r\nConfiguration Status:\r\nERROR\r\n<\/pre>\n
G. Verifying the configuration<\/h4>\n
After all operations, it is checked whether there is an error in the configuration.<\/p>\n
There are 3 ways.<\/p>\n
1. The broker configuration is queried.<\/p>\n
DGMGRL> show configuration verbose\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - (*) Physical standby database\r\n    logical - Logical standby database\r\n\r\n  (*) Fast-Start Failover target\r\n\r\n  Properties:\r\n    FastStartFailoverThreshold      = '100'\r\n    OperationTimeout                = '30'\r\n    FastStartFailoverLagLimit       = '900'\r\n    CommunicationTimeout            = '180'\r\n    ObserverReconnect               = '15'\r\n    FastStartFailoverAutoReinstate  = 'TRUE'\r\n    FastStartFailoverPmyShutdown    = 'TRUE'\r\n    BystandersFollowRoleChange      = 'ALL'\r\n    ObserverOverride                = 'FALSE'\r\n    ExternalDestination1            = ''\r\n    ExternalDestination2            = ''\r\n    PrimaryLostWriteAction          = 'CONTINUE'\r\n\r\nFast-Start Failover: ENABLED\r\n\r\n  Threshold:          100 seconds\r\n  Target:             standby\r\n  Observer:           standby1.tivibulab.local\r\n  Lag Limit:          900 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: 15 seconds\r\n  Observer Override:  FALSE\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
2. The Fast_start Failover configuration is queried.<\/p>\n
DGMGRL> show fast_start failover\r\n\r\nFast-Start Failover: ENABLED\r\n\r\n  Threshold:          100 seconds\r\n  Target:             standby\r\n  Observer:           standby1.tivibulab.local\r\n  Lag Limit:          900 seconds\r\n  Shutdown Primary:   TRUE\r\n  Auto-reinstate:     TRUE\r\n  Observer Reconnect: 15 seconds\r\n  Observer Override:  FALSE\r\n\r\nConfigurable Failover Conditions\r\n  Health Conditions:\r\n    Corrupted Controlfile          YES\r\n    Corrupted Dictionary           YES\r\n    Inaccessible Logfile           YES\r\n    Stuck Archiver                  NO\r\n    Datafile Offline               YES\r\n\r\n  Oracle Error Conditions:\r\n    ORA-01578: ORACLE data block corrupted (file # %s, block # %s)\r\n<\/pre>\n
3. We query from the v$DATABASE view.<\/p>\n
[Primary-1] SQL> set linesize 9000\r\n[Primary-1] SQL> column FS_FAILOVER_OBSERVER_HOST format a24\r\n[Primary-1] SQL> select FS_FAILOVER_STATUS, FS_FAILOVER_CURRENT_TARGET, FS_FAILOVER_THRESHOLD, FS_FAILOVER_OBSERVER_PRESENT, FS_FAILOVER_OBSERVER_HOST from v$database;\r\n\r\nFS_FAILOVER_STATUS     FS_FAILOVER_CURRENT_TARGET     FS_FAILOVER_THRESHOLD FS_FAILOVER_OBSERVER_PRESENT FS_FAILOVER_OBSERVER_HOST\r\n---------------------- ------------------------------ --------------------- ------- ------------------------\r\nTARGET UNDER LAG LIMIT standby                                          100 YES     standby1.tivibulab.local\r\n<\/pre>\n
The values and meanings of the FS_FAILOVER_STATUS column<\/p>\n
\"\"<\/p>\n
 <\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"
In today’s article, we will examine Fast-Start Failover Configuration. The configuration of Fast-Start Failover consists of the following 8 steps in summary. A. Identifying the Fast-start Failover Standby Database B. Setting Data Protection Mode C. Setting the threshold value at which Fast-start Failover will occur \u00c7. Setting additional Fast-start Failover features D. Setting the additional …<\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"author":484,"featured_media":52017,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[4],"tags":[],"class_list":["post-52011","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-oracle"],"aioseo_notices":[],"yoast_head":"\nFast-Start Failover Configuration - Database Tutorials<\/title>\n<meta name=\"description\" content=\"In today's article, we will examine Fast-Start Failover Configuration. The configuration of Fast-Start Failover consists of the following 8 steps in summary.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fast-Start Failover Configuration - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"In today's article, we will examine Fast-Start Failover Configuration. The configuration of Fast-Start Failover consists of the following 8 steps in summary.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2022-08-08T17:00:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-08-08T17:07:11+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png\" \/>\n\t<meta property=\"og:image:width\" content=\"795\" \/>\n\t<meta property=\"og:image:height\" content=\"351\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Onur ARDAHANLI\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Onur ARDAHANLI\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"15 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/\"},\"author\":{\"name\":\"Onur ARDAHANLI\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\"},\"headline\":\"Fast-Start Failover Configuration\",\"datePublished\":\"2022-08-08T17:00:40+00:00\",\"dateModified\":\"2022-08-08T17:07:11+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/\"},\"wordCount\":1518,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png\",\"articleSection\":[\"ORACLE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/\",\"name\":\"Fast-Start Failover Configuration - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png\",\"datePublished\":\"2022-08-08T17:00:40+00:00\",\"dateModified\":\"2022-08-08T17:07:11+00:00\",\"description\":\"In today's article, we will examine Fast-Start Failover Configuration. The configuration of Fast-Start Failover consists of the following 8 steps in summary.\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png\",\"width\":795,\"height\":351},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Fast-Start Failover Configuration\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\",\"name\":\"Onur ARDAHANLI\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"caption\":\"Onur ARDAHANLI\"},\"url\":\"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Fast-Start Failover Configuration - Database Tutorials","description":"In today's article, we will examine Fast-Start Failover Configuration. The configuration of Fast-Start Failover consists of the following 8 steps in summary.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/","og_locale":"en_US","og_type":"article","og_title":"Fast-Start Failover Configuration - Database Tutorials","og_description":"In today's article, we will examine Fast-Start Failover Configuration. The configuration of Fast-Start Failover consists of the following 8 steps in summary.","og_url":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/","og_site_name":"Database Tutorials","article_published_time":"2022-08-08T17:00:40+00:00","article_modified_time":"2022-08-08T17:07:11+00:00","og_image":[{"width":795,"height":351,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png","type":"image\/png"}],"author":"Onur ARDAHANLI","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onur ARDAHANLI","Est. reading time":"15 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/"},"author":{"name":"Onur ARDAHANLI","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6"},"headline":"Fast-Start Failover Configuration","datePublished":"2022-08-08T17:00:40+00:00","dateModified":"2022-08-08T17:07:11+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/"},"wordCount":1518,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png","articleSection":["ORACLE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/","url":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/","name":"Fast-Start Failover Configuration - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png","datePublished":"2022-08-08T17:00:40+00:00","dateModified":"2022-08-08T17:07:11+00:00","description":"In today's article, we will examine Fast-Start Failover Configuration. The configuration of Fast-Start Failover consists of the following 8 steps in summary.","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/Ekran-goruntusu-2022-08-08-195911.png","width":795,"height":351},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2022\/08\/08\/fast-start-failover-configuration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"Fast-Start Failover Configuration"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6","name":"Onur ARDAHANLI","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","caption":"Onur ARDAHANLI"},"url":"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/52011","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/484"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=52011"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/52011\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/52017"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=52011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=52011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=52011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}