{"id":52327,"date":"2022-09-15T10:05:38","date_gmt":"2022-09-15T10:05:38","guid":{"rendered":"https:\/\/dbtut.com\/?p=52327"},"modified":"2022-09-15T10:07:05","modified_gmt":"2022-09-15T10:07:05","slug":"fast-start-failover-single-node","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/","title":{"rendered":"Fast Start Failover -SINGLE NODE"},"content":{"rendered":"

Today I will give you information about Fast Start Failover -SINGLE NODE.<\/p>\n

1. We check the broker’s configuration to see if everything is normal.<\/p>\n

\tDGMGRL> show configuration\r\n\t\r\n\tConfiguration - DG_Solution\r\n\t\r\n\t  Protection Mode: MaxPerformance\r\n\t  Members:\r\n\t  primary  - Primary database\r\n\t    prmyFS   - Far sync instance \r\n\t      physical - Physical standby database \r\n\t      logical  - Logical standby database \r\n\t\r\n\t  Members Not Receiving Redo:\r\n\t  physclFS - Far sync instance \r\n\t\r\n\tFast-Start Failover: DISABLED\r\n\t\r\n\tConfiguration Status:\r\n\tSUCCESS   (status updated 42 seconds ago)\r\n<\/pre>\n
2. We check whether Flashback is enabled in Primary and Standby Databases.<\/p>\n
\t[Primary] SQL> select flashback_on from v$database;\r\n\t\r\n\tFLASHBACK_ON\r\n\t------------------\r\n\tNO\r\n\t\r\n\t\r\n\t[Physical] SQL> select flashback_on from v$database;\r\n\t\r\n\tFLASHBACK_ON\r\n\t------------------\r\n\tNO\r\n\t\r\n\t\r\n\t[Logical] SQL> select flashback_on from v$database;\r\n\t\r\n\tFLASHBACK_ON\r\n\t------------------\r\n\tNO\r\n<\/pre>\n
3. We control the duration that Flashback Logs will be stored.<\/p>\n
\t[Primary] SQL> show parameter db_flashback_retention\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tdb_flashback_retention_target        integer     1440\r\n\t\r\n\t\r\n\t[Physical] SQL> show parameter db_flashback_retention\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tdb_flashback_retention_target        integer     1440\r\n\t\r\n\t\r\n\t[Logical] SQL> show parameter db_flashback_retention\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tdb_flashback_retention_target        integer     1440\r\n<\/pre>\n
4. We check whether there is enough space in the location where Flashback Logs will be stored.<\/p>\n
\t[Primary] SQL> show parameter db_recovery\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tdb_recovery_file_dest                string      \/u01\/app\/oracle\/recovery_area\r\n\tdb_recovery_file_dest_size           big integer 10G\r\n\t\r\n\t\r\n\t[Physical] SQL> show parameter db_recovery\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tdb_recovery_file_dest                string      \/u01\/app\/oracle\/recovery_area\r\n\tdb_recovery_file_dest_size           big integer 10G\r\n\t\r\n\t\r\n\t[Logical] SQL> show parameter db_recovery\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tdb_recovery_file_dest                string      \/u01\/app\/oracle\/recovery_area\r\n\tdb_recovery_file_dest_size           big integer 10G\r\n<\/pre>\n
5. Before activating Flashback, we stop Log Apply operations on Standby Databases.<\/p>\n
\t[oracle@primary ~]$ dgmgrl\r\n\tDGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production\r\n\t\r\n\tCopyright (c) 2000, 2013, Oracle. All rights reserved.\r\n\t\r\n\tWelcome to DGMGRL, type \"help\" for information.\r\n\tDGMGRL> connect sysdg\r\n\tPassword:\r\n\tConnected as SYSDG.\r\n\tDGMGRL> edit database physical set state='APPLY-OFF';\r\n\tSucceeded.\r\n\tDGMGRL> edit database logical set state='APPLY-OFF';\r\n\tSucceeded.\r\n<\/pre>\n
If I did it with SQL, I would use the following commands.<\/p>\n
\t[Physical] SQL> alter database recover managed standby database cancel;\r\n\t[Logical] SQL> alter database stop logical standby apply;\r\n<\/pre>\n
6. We enable Flashback feature in Primary and Standby Databases.<\/p>\n
\tDGMGRL> sql \"alter database flashback on\";\r\n\tSucceeded.\r\n\tDGMGRL> connect sysdg\/Passw0rd4@physical\r\n\tConnected as SYSDG.\r\n\tDGMGRL> sql \"alter database flashback on\";\r\n\tSucceeded.\r\n\tDGMGRL> connect sysdg\/Passw0rd4@logical\r\n\tConnected as SYSDG.\r\n\tDGMGRL> sql \"alter database flashback on\";\r\n\tSucceeded.\r\n\tDGMGRL> \r\n<\/pre>\n
The reason we put this feature into use is that the databases other than the Primary Database, which will be Disabled after Failover, and the Fast-Start Failover Target Standby database, can successfully perform the necessary roles again with Flashback Logs.<\/p>\n
Otherwise I would have to create these databases again.<\/p>\n
I could also do this with SQL from SQLPLUS, but after the Broker configuration, I will need to manage the Data Guard Environment from the Broker, so I do it from the Broker for the sake of hand.<\/p>\n
7. We check whether the flashback feature is enabled in the databases.<\/p>\n
\t[Primary] SQL> select flashback_on from v$database;\r\n\t\r\n\tFLASHBACK_ON\r\n\t------------------\r\n\tYES\r\n\t\r\n\t[Physical] SQL> select flashback_on from v$database;\r\n\t\r\n\tFLASHBACK_ON\r\n\t------------------\r\n\tYES\r\n\t\r\n\t[Logical] SQL> select flashback_on from v$database;\r\n\t\r\n\tFLASHBACK_ON\r\n\t------------------\r\n\tYES\r\n<\/pre>\n
8. It is checked whether Flashback Logs have started to occur.<\/p>\n
\t[Primary] SQL> select file_type,number_of_files,percent_space_used from v$recovery_area_usage;\r\n\t\r\n\tFILE_TYPE               NUMBER_OF_FILES PERCENT_SPACE_USED\r\n\t----------------------- --------------- ------------------\r\n\tCONTROL FILE                          0                  0\r\n\tREDO LOG                              0                  0\r\n\tARCHIVED LOG                         95               6.33\r\n\tBACKUP PIECE                          0                  0\r\n\tIMAGE COPY                            0                  0\r\n\tFLASHBACK LOG                         2                .98\r\n\tFOREIGN ARCHIVED LOG                  0                  0\r\n\tAUXILIARY DATAFILE COPY               0                  0\r\n\t\r\n\t8 rows selected.\r\n\t\r\n\t\r\n\t[Physical] SQL> select file_type,number_of_files,percent_space_used from v$recovery_area_usage;\r\n\t\r\n\tFILE_TYPE               NUMBER_OF_FILES PERCENT_SPACE_USED\r\n\t----------------------- --------------- ------------------\r\n\tCONTROL FILE                          0                  0\r\n\tREDO LOG                              0                  0\r\n\tARCHIVED LOG                         95               6.33\r\n\tBACKUP PIECE                          0                  0\r\n\tIMAGE COPY                            0                  0\r\n\tFLASHBACK LOG                         2                .98\r\n\tFOREIGN ARCHIVED LOG                  0                  0\r\n\tAUXILIARY DATAFILE COPY               0                  0\r\n\t\r\n\t8 rows selected.\r\n\t\r\n\t\r\n\t[Logical] SQL> select file_type,number_of_files,percent_space_used from v$recovery_area_usage;\r\n\t\r\n\tFILE_TYPE               NUMBER_OF_FILES PERCENT_SPACE_USED\r\n\t----------------------- --------------- ------------------\r\n\tCONTROL FILE                          0                  0\r\n\tREDO LOG                              0                  0\r\n\tARCHIVED LOG                         59              18.66\r\n\tBACKUP PIECE                          0                  0\r\n\tIMAGE COPY                            0                  0\r\n\tFLASHBACK LOG                         2                .98\r\n\tFOREIGN ARCHIVED LOG                 67               3.54\r\n\tAUXILIARY DATAFILE COPY               0                  0\r\n\t\r\n\t8 rows selected.\r\n<\/pre>\n
9. Current Flashback Size is also checked.<\/p>\n
\t[Primary] SQL> select flashback_size from v$flashback_database_log;\r\n\t\r\n\tFLASHBACK_SIZE\r\n\t--------------\r\n\t     104857600\r\n\t\r\n\t\t \r\n\t[Physical] SQL> select flashback_size from v$flashback_database_log;\r\n\t\r\n\tFLASHBACK_SIZE\r\n\t--------------\r\n\t     104857600\r\n\t\t \r\n\t\t\r\n\t[Logical] SQL> select flashback_size from v$flashback_database_log;\r\n\t\r\n\tFLASHBACK_SIZE\r\n\t--------------\r\n\t     104857600\r\n<\/pre>\n
That’s equivalent to 100MB. This is allocate to you when it is created in Default. It increases according to Flaschback_Retention time.<\/p>\n
10. We start Log Apply operations on Standby Databases.<\/p>\n
\tDGMGRL> edit database physical set state='APPLY-ON';\r\n\tSucceeded.\r\n\tDGMGRL> edit database logical set state='APPLY-ON';\r\nSucceeded.<\/pre>\n
11. We check if the Log Apply processes have started.<\/p>\n
\tDGMGRL> show database physical\r\n\t\r\n\tDatabase - physical\r\n\t\r\n\t  Role:               PHYSICAL STANDBY\r\n\t  Intended State:     APPLY-ON\r\n\t  Transport Lag:      0 seconds (computed 1 second ago)\r\n\t  Apply Lag:          0 seconds (computed 1 second ago)\r\n\t  Average Apply Rate: 10.00 KByte\/s\r\n\t  Real Time Query:    ON\r\n\t  Instance(s):\r\n\t    physical\r\n\t\r\n\tDatabase Status:\r\n\tSUCCESS\r\n\t\r\n\tDGMGRL> show database logical\r\n\t\r\n\tDatabase - logical\r\n\t\r\n\t  Role:               LOGICAL STANDBY\r\n\t  Intended State:     APPLY-ON\r\n\t  Transport Lag:      0 seconds (computed 0 seconds ago)\r\n\t  Apply Lag:          0 seconds (computed 0 seconds ago)\r\n\t  Active Apply Rate:  0 Byte\/s\r\n\t  Instance(s):\r\n\t    logical\r\n\t\r\n\tDatabase Status:\r\n\tSUCCESS\r\n<\/pre>\n
12. A new table is created under the TEST user to check whether the Log Apply processes have started.<\/p>\n
\t[Primary] SQL> create table test.regions_yedek as select * from hr.regions;\r\n\t\r\n\tTable created.\r\n\t\r\n\t[Primary] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\r\n\tTABLE_NAME\r\n\t--------------------------------------------------------------------------------\r\n\tDEPARTMENTS_YEDEK\r\n\tREGIONS_YEDEK\r\n\tJOBS_YEDEK\r\n\tEMPLOYEES_YEDEK\r\n\t\r\n\t[Physical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\r\n\tTABLE_NAME\r\n\t--------------------------------------------------------------------------------\r\n\tDEPARTMENTS_YEDEK\r\n\tREGIONS_YEDEK\r\n\tJOBS_YEDEK\r\n\tEMPLOYEES_YEDEK\r\n\t\r\n\t[Logical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\r\n\tTABLE_NAME\r\n\t--------------------------------------------------------------------------------\r\n\tJOBS_YEDEK\r\n\tEMPLOYEES_YEDEK\r\n\tDEPARTMENTS_YEDEK\r\n\tREGIONS_YEDEK\r\n<\/pre>\n
13. Finally, we check the RedoRoutes parameters to see if the logs will go according to the desired architecture.<\/p>\n
\tDGMGRL> show database primary 'RedoRoutes';\r\n\t  RedoRoutes = '(primary:prmyFS SYNC)'\r\n\tDGMGRL> show database physical 'RedoRoutes';\r\n\t  RedoRoutes = '(physical:physclFS SYNC)'\r\n\tDGMGRL> show database logical 'RedoRoutes';\r\n\t  RedoRoutes = ''\r\n\tDGMGRL> show far_sync 'prmyFS' 'RedoRoutes';\r\n\t  RedoRoutes = '(primary:physical,logical ASYNC)'\r\n\tDGMGRL> show far_sync 'physclFS' 'RedoRoutes';\r\n  RedoRoutes = '(physical:primary,logical ASYNC)'<\/pre>\n
14. Now we start the parameter adjustments for Fast-Start Failover operations.<\/p>\n
a. Target Standby Database is determined for Fast-start Failover.<\/p>\n
DGMGRL> edit database primary set property 'FastStartFailoverTarget'='physical';\r\nProperty \"FastStartFailoverTarget\" updated\r\n\r\nDGMGRL> show database primary FastStartFailoverTarget\r\nFastStartFailoverTarget = 'physical'<\/pre>\n
b. After the role change, Fast-start Failover Target Standby Database is determined.<\/p>\n
DGMGRL> edit database physical set property 'FastStartFailoverTarget'='primary';\r\nProperty \"FastStartFailoverTarget\" updated\r\n\r\nDGMGRL> show database physical 'FastStartFailoverTarget';\r\nFastStartFailoverTarget = 'primary'<\/pre>\n
c. It is determined how often the Observer will establish a connection with the Primary Database.<\/p>\n
DGMGRL> edit configuration set property ObserverReconnect=120;\r\nProperty \"observerreconnect\" updated<\/pre>\n
I don’t think so much parameter changes are necessary for now and I don’t make any other changes.<\/p>\n
15. Before enabling Fast-start Failover, we check the status of the parameters one last time.<\/p>\n
DGMGRL> show fast_start failover\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nThreshold: 30 seconds\r\nTarget: (none)\r\nObserver: (none)\r\nLag Limit: 30 seconds\r\nShutdown Primary: TRUE\r\nAuto-reinstate: TRUE\r\nObserver Reconnect: 120 seconds\r\nObserver Override: FALSE\r\n\r\nConfigurable Failover Conditions\r\nHealth Conditions:\r\nCorrupted Controlfile YES\r\nCorrupted Dictionary YES\r\nInaccessible Logfile NO\r\nStuck Archiver NO\r\nDatafile Offline YES\r\n\r\nOracle Error Conditions:\r\n(none)<\/pre>\n
Observer is not START yet, so it cannot be seen on which HOST it is running. Also, Target parameter will be seen after Fast-start Failover ENABLE.<\/p>\n
16. We ENABLE the broker.<\/p>\n
DGMGRL> enable fast_start failover;\r\nError: ORA-16693: requirements not met for enabling fast-start failover\r\n\r\nFailed.<\/pre>\n
The reason for this error is that although we use Far SYNC in the Data Guard Environment, the current Protection Mode is Max Performance. Protection Mode must be Maximum Availability.<\/p>\n
17. We make Protection Mode Maximum Availability.<\/p>\n
DGMGRL> edit configuration set protection mode as maxavailability;\r\nSucceded.<\/pre>\n
18. The broker is requested to be ENABLEd again.<\/p>\n
DGMGRL> enable fast_start failover\r\nEnabled.<\/pre>\n
19. We are questioning the status of Fast-start Failover.<\/p>\n
DGMGRL> show fast_start failover\r\n\r\nFast-Start Failover: ENABLED\r\n\r\nThreshold: 30 seconds\r\ntarget: physical\r\nObserver: (none)\r\nLag Limit: 30 seconds (not in use)\r\nShutdown Primary: TRUE\r\nAuto-reinstate: TRUE\r\nObserver Reconnect: 120 seconds\r\nObserver Override: FALSE\r\n\r\nConfigurable Failover Conditions\r\nHealth Conditions:\r\nCorrupted Controlfile YES\r\nCorrupted Dictionary YES\r\nInaccessible Logfile NO\r\nStuck Archiver NO\r\nDatafile Offline YES\r\n\r\nOracle Error Conditions:\r\n(none)<\/pre>\n
The reason why it says “not in use” in the Lag Limit parameter is that this parameter is used while in Maximum Performance mode.<\/p>\n
20. We query the status of the broker configuration.<\/p>\n
\tDGMGRL> show configuration\r\n\t\r\n\tConfiguration - DG_Solution\r\n\t\r\n\t  Protection Mode: MaxAvailability\r\n\t  Members:\r\n\t  primary  - Primary database\r\n\t    Warning: ORA-16819: fast-start failover observer not started\r\n\t\r\n\t    prmyFS   - Far sync instance \r\n\t      physical - (*) Physical standby database \r\n\t        Warning: ORA-16819: fast-start failover observer not started\r\n\t\r\n\t      logical  - Logical standby database \r\n\t\r\n\t  Members Not Receiving Redo:\r\n\t  physclFS - Far sync instance \r\n\t\r\n\tFast-Start Failover: ENABLED\r\n\t\r\n\tConfiguration Status:\r\n\tWARNING   (status updated 11 seconds ago)\r\n<\/pre>\n
The reason for these warnings is that the Observer has not been started yet.<\/p>\n
21. The Observer is started.<\/p>\n
\"\"<\/p>\n
Since the Observer is a foreground process, it constantly occupies the DGMGRL prompt it is running, and we can see all the processes it captures and the jobs it does from this prompt.<\/p>\n
For this reason, it is useful to connect from a different computer. In addition, since it will follow the Primary and Standby Databases, it should not be run in these databases. That’s why I run it in Primary Far_SYNC.<\/p>\n
22. We are questioning the status of Fast-start Failover again.<\/p>\n
\tDGMGRL> show fast_start failover\r\n\t\r\n\tFast-Start Failover: ENABLED\r\n\t\r\n\t  Threshold:          30 seconds\r\n\t  Target:             physical\r\n\t  Observer:           broker.tivibulab.local\r\n\t  Lag Limit:          30 seconds (not in use)\r\n\t  Shutdown Primary:   TRUE\r\n\t  Auto-reinstate:     TRUE\r\n\t  Observer Reconnect: 120 seconds\r\n\t  Observer Override:  FALSE\r\n\t\r\n\tConfigurable Failover Conditions\r\n\t  Health Conditions:\r\n\t    Corrupted Controlfile          YES\r\n\t    Corrupted Dictionary           YES\r\n\t    Inaccessible Logfile            NO\r\n\t    Stuck Archiver                  NO\r\n\t    Datafile Offline               YES\r\n\t\r\n\t  Oracle Error Conditions:\r\n\t    (none)\r\n<\/pre>\n
I ran Observer from a completely separate instance. This is not mandatory. As I mentioned before, it can also be run from Far SYNC instances.<\/p>\n
23. The broker configuration is also queried again.<\/p>\n
\tDGMGRL> show configuration\r\n\t\r\n\tConfiguration - DG_Solution\r\n\t\r\n\t  Protection Mode: MaxAvailability\r\n\t  Members:\r\n\t  primary  - Primary database\r\n\t    prmyFS   - Far sync instance \r\n\t      physical - (*) Physical standby database \r\n\t      logical  - Logical standby database \r\n\t\r\n\t  Members Not Receiving Redo:\r\n\t  physclFS - Far sync instance \r\n\t\r\n\tFast-Start Failover: ENABLED\r\n\t\r\n\tConfiguration Status:\r\n\tSUCCESS   (status updated 46 seconds ago)\r\n<\/pre>\n
(*) Indicates Fast-start Failover Target Standby Database.<\/p>\n
24. Fast-start Failover is triggered by closing Primary Database with Shutdown Abort.<\/p>\n
\t[Primary] SQL> shu abort;\r\n\t\r\n\tOracle instance shutdown\r\n<\/pre>\n
25. Follow the steps during the Failover process from the computer where the Observer is started.<\/p>\n
\tDGMGRL> start observer\r\n\tObserver started\r\n\t\r\n\t13:57:24.56  Saturday, February 11, 2017\r\n\tInitiating Fast-Start Failover to database \"physical\"...\r\n\tPerforming failover NOW, please wait...\r\n\tFailover succeeded, new primary is \"physical\"\r\n\t13:58:43.37  Saturday, February 11, 2017\r\n\t\r\n\t13:58:44.41  Saturday, February 11, 2017\r\n\tInitiating reinstatement for database \"logical\"...\r\n\tReinstating database \"logical\", please wait...\r\n\tOperation requires shut down of instance \"logical\" on database \"logical\"\r\n\tShutting down instance \"logical\"...\r\n\tDatabase closed.\r\n\tDatabase dismounted.\r\n\tORACLE instance shut down.\r\n\tOperation requires start up of instance \"logical\" on database \"logical\"\r\n\tStarting instance \"logical\"...\r\n\tORACLE instance started.\r\n\tDatabase mounted.\r\n\tContinuing to reinstate database \"logical\" ...\r\n\tOperation requires shut down of instance \"logical\" on database \"logical\"\r\n\tShutting down instance \"logical\"...\r\n\tORA-01109: database not open\r\n\t\r\n\tDatabase dismounted.\r\n\tORACLE instance shut down.\r\n\tOperation requires start up of instance \"logical\" on database \"logical\"\r\n\tStarting instance \"logical\"...\r\n\tORACLE instance started.\r\n\tDatabase mounted.\r\n\tContinuing to reinstate database \"logical\" ...\r\n\tReinstatement of database \"logical\" succeeded\r\n\t14:00:25.56  Saturday, February 11, 2017\r\n<\/pre>\n
26. Failover operation completed successfully. We pass to the controls.<\/p>\n
a. The broker configuration is queried to see if there is an error.<\/p>\n
\t\tDGMGRL> show configuration\r\n\t\t\r\n\t\tConfiguration - DG_Solution\r\n\t\t\r\n\t\t  Protection Mode: MaxAvailability\r\n\t\t  Members:\r\n\t\t  physical - Primary database\r\n\t\t    Warning: ORA-16817: unsynchronized fast-start failover configuration\r\n\t\t\r\n\t\t    physclFS - Far sync instance \r\n\t\t      primary  - (*) Physical standby database (disabled)\r\n\t\t        ORA-16661: the standby database needs to be reinstated\r\n\t\t\r\n\t\t      logical  - Logical standby database \r\n\t\t\r\n\t\t  Members Not Receiving Redo:\r\n\t\t  prmyFS   - Far sync instance \r\n\t\t\r\n\t\tFast-Start Failover: ENABLED\r\n\t\t\r\n\t\tConfiguration Status:\r\n\t\tWARNING   (status updated 27 seconds ago)\r\n<\/pre>\n
The reason for this warning is that the Original Primary Database is disabled and is not synchronized with the New Primary.<\/p>\n
The reason for the error is that the Original Primary needs the Reinstate operation.<\/p>\n
b. The statuses of the databases are queried.<\/p>\n
\t\t[oracle@primary ~]$ sqlplus \/ as sysdba\r\n\t\t\r\n\t\tSQL*Plus: Release 12.1.0.2.0 Production on Sat Feb 11 14:01:16 2017\r\n\t\t\r\n\t\tCopyright (c) 1982, 2014, Oracle.  All rights reserved.\r\n\t\t\r\n\t\tConnected to an idle instance.\r\n\t\t\r\n\t\t[Physical] SQL> select status from v$instance;\r\n\t\t\r\n\t\tSTATUS\r\n\t\t------------\r\n\t\tOPEN\r\n\t\t\r\n\t\t[PhysicalFS] SQL> select status from v$instance;\r\n\t\t\r\n\t\tSTATUS\r\n\t\t------------\r\n\t\tMOUNTED\r\n\t\t\r\n\t\t[Logical] SQL> select status from v$instance;\r\n\t\t\r\n\t\tSTATUS\r\n\t\t------------\r\n\t\tOPEN\r\n\t\t\r\n\t\t[PrimaryFS] SQL> select status from v$instance;\r\n\t\t\r\n\t\tSTATUS\r\n\t\t------------\r\n\t\tMOUNTED\r\n<\/pre>\n
c. Databases’ open_mode, roles and protection modes are queried.<\/p>\n
\t\t[Physical] SQL> select open_mode, database_role, protection_mode from v$database;\r\n\t\t\r\n\t\tOPEN_MODE            DATABASE_ROLE    PROTECTION_MODE\r\n\t\t-------------------- ---------------- --------------------\r\n\t\tREAD WRITE           PRIMARY          MAXIMUM AVAILABILITY\r\n\t\t\r\n\t\t[Logical] SQL> select open_mode, database_role, protection_mode from v$database;\r\n\t\t\r\n\t\tOPEN_MODE            DATABASE_ROLE    PROTECTION_MODE\r\n\t\t-------------------- ---------------- --------------------\r\n\t\tREAD WRITE           LOGICAL STANDBY  MAXIMUM AVAILABILITY\r\n\t\t\r\n\t\t[PhysicalFS] SQL> select open_mode, database_role, protection_mode from v$database;\r\n\t\t\r\n\t\tOPEN_MODE            DATABASE_ROLE    PROTECTION_MODE\r\n\t\t-------------------- ---------------- --------------------\r\n\t\tMOUNTED              FAR SYNC         MAXIMUM AVAILABILITY\r\n\t\t\r\n\t\t[PrimaryFS] SQL> select open_mode, database_role, protection_mode from v$database;\r\n\t\t\r\n\t\tOPEN_MODE            DATABASE_ROLE    PROTECTION_MODE\r\n\t\t-------------------- ---------------- --------------------\r\n\t\tMOUNTED              FAR SYNC         MAXIMUM AVAILABILITY\r\n<\/pre>\n
d. It is questioned whether the Log Switch operation has been carried out successfully. For this, first RESETLOGS_TIME is learned. This is because databases eat OPEN RESETLOGS and the log sequence numbers change.<\/p>\n
\t\t[Physical] SQL> select RESETLOGS_TIME from v$database;\r\n\t\t\r\n\t\tRESETLOGS\r\n\t\t---------\r\n\t\t11-FEB-17\r\n\t\t\r\n\t\t[Physical] SQL> alter session set nls_date_format='dd-mm-yyyy hh24:mi:ss';\r\n\t\t\r\n\t\tSession altered.\r\n\t\t\r\n\t\t\r\n\t\t[Physical] SQL> select RESETLOGS_TIME from v$database;\r\n\t\t\r\n\t\tRESETLOGS_TIME\r\n\t\t-------------------\r\n\t\t11-02-2017 13:58:39\r\n\t\t \r\n<\/pre>\n
e. Existing log sequence numbers are queried.<\/p>\n
\t\t[Physical] SQL> select max(sequence#),thread# from v$archived_log where first_time  > to_date('11\/02\/2017 13:58:39', 'DD-MM-YYYY HH24:MI:SS') group by thread#;\r\n\t\t\r\n\t\tMAX(SEQUENCE#)    THREAD#\r\n\t\t-------------- ----------\r\n\t\t            28          1\r\n\t\t\t\t\t\r\n\t\t[Logical] SQL> select max(sequence#),thread# from dba_logstdby_log where first_time  > to_date('11\/02\/2017 13:58:39', 'DD-MM-YYYY HH24:MI:SS') group by thread#;\r\n\t\t\r\n\t\tMAX(SEQUENCE#)    THREAD#\r\n\t\t-------------- ----------\r\n\t\t            28          1\r\n\t\t\t\t\t\r\n\t\t[PhysicalFS] SQL> select max(sequence#),thread# from v$archived_log where first_time  > to_date('11\/02\/2017 13:58:39', 'DD-MM-YYYY HH24:MI:SS') group by thread#;\r\n\t\t\r\n\t\tMAX(SEQUENCE#)    THREAD#\r\n\t\t-------------- ----------\r\n\t\t            28          1\r\n<\/pre>\n
f. Log Switch operation is performed and log sequence numbers are checked.<\/p>\n
\t\t[Physical] SQL> alter system switch logfile;\r\n\t\t\r\n\t\tSystem altered.\r\n\t\t\r\n\t\t[Physical] SQL> select max(sequence#),thread# from v$archived_log where first_time  > to_date('11\/02\/2017 13:58:39', 'DD-MM-YYYY HH24:MI:SS') group by thread#;\r\n\t\t\r\n\t\tMAX(SEQUENCE#)    THREAD#\r\n\t\t-------------- ----------\r\n\t\t            30          1\r\n\t\t\t\t\t\r\n\t\t[Logical] SQL> select max(sequence#),thread# from dba_logstdby_log where first_time  > to_date('11\/02\/2017 13:58:39', 'DD-MM-YYYY HH24:MI:SS') group by thread#;\r\n\t\t\r\n\t\tMAX(SEQUENCE#)    THREAD#\r\n\t\t-------------- ----------\r\n\t\t            30          1\r\n\t\t\t\t\t\r\n\t\t[PhysicalFS] SQL> select max(sequence#),thread# from v$archived_log where first_time  > to_date('11\/02\/2017 13:58:39', 'DD-MM-YYYY HH24:MI:SS') group by thread#;\r\n\t\t\r\n\t\tMAX(SEQUENCE#)    THREAD#\r\n\t\t-------------- ----------\r\n\t\t            30          1\r\n\t\t\r\n<\/pre>\n
The reason for the difference in 2 sequences is that there is 1 more log switch operation until I do my operations.<\/p>\n
g. A table belonging to the TEST user is DROPed to see if the DDL and DML operations are running smoothly.<\/p>\n
i. Existing tables are queried.<\/p>\n
\t\t\t[Physical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\t\r\n\t\t\tTABLE_NAME\r\n\t\t\t--------------------------------------------------------------------------------\r\n\t\t\tDEPARTMENTS_YEDEK\r\n\t\t\tREGIONS_YEDEK\r\n\t\t\tJOBS_YEDEK\r\n\t\t\tEMPLOYEES_YEDEK\r\n\t\t\t\r\n\t\t\t[Logical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\t\r\n\t\t\tTABLE_NAME\r\n\t\t\t--------------------------------------------------------------------------------\r\n\t\t\tREGIONS_YEDEK\r\n\t\t\tDEPARTMENTS_YEDEK\r\n\t\t\tEMPLOYEES_YEDEK\r\n\t\t\tJOBS_YEDEK\r\n<\/pre>\n
ii. A table is DROP.<\/p>\n
\t\t\t[Physical] SQL> drop table test.DEPARTMENTS_YEDEK;\r\n\t\t\t\r\n\t\t\tTable dropped.\r\n\t\t\t\r\n\t\t\t[Physical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\t\r\n\t\t\tTABLE_NAME\r\n\t\t\t--------------------------------------------------------------------------------\r\n\t\t\tREGIONS_YEDEK\r\n\t\t\tJOBS_YEDEK\r\n\t\t\tEMPLOYEES_YEDEK\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t[Logical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\t\r\n\t\t\tTABLE_NAME\r\n\t\t\t--------------------------------------------------------------------------------\r\n\t\t\tREGIONS_YEDEK\r\n\t\t\tEMPLOYEES_YEDEK\r\n\t\t\tJOBS_YEDEK\r\n<\/pre>\n
27. Assuming that the problem in the original Primary database has been resolved, let’s re-enable it and ask it to assume the role of Physical Standby. For this, the database is mounted.<\/p>\n
\t[Primary] SQL> startup mount;\r\n\tORACLE instance started.\r\n\t\r\n\tTotal System Global Area 3472883712 bytes\r\n\tFixed Size                  2930272 bytes\r\n\tVariable Size             822086048 bytes\r\n\tDatabase Buffers         2634022912 bytes\r\n\tRedo Buffers               13844480 bytes\r\n\tDatabase mounted.\r\n\t\r\n<\/pre>\n
28. The logs in the Observer are followed.<\/p>\n
\t14:24:05.01  Saturday, February 11, 2017\r\n\tInitiating reinstatement for database \"primary\"...\r\n\tReinstating database \"primary\", please wait...\r\n\tReinstatement of database \"primary\" succeeded\r\n\t14:24:20.64  Saturday, February 11, 2017\r\n<\/pre>\n
29. The status of the original Primary database is queried.<\/p>\n
\t[Primary] SQL> select status from v$instance;\r\n\t\r\n\tSTATUS\r\n\t------------\r\n\tOPEN\r\n\t\r\n<\/pre>\n
30. The Recovery Modes of the databases are queried.<\/p>\n
\t[Primary] SQL> select open_mode, database_role, protection_mode from v$database;\r\n\t\r\n\tOPEN_MODE            DATABASE_ROLE    PROTECTION_MODE\r\n\t-------------------- ---------------- --------------------\r\n\tREAD ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM AVAILABILITY\r\n\t\r\n\t\r\n\t[Primary] SQL> select recovery_mode from v$archive_dest_status where dest_id <4;\r\n\t\r\n\tRECOVERY_MODE\r\n\t-----------------------\r\n\tMANAGED REAL TIME APPLY\r\n\t\r\n\t[Logical] SQL> select recovery_mode from v$archive_dest_status where dest_id <4;\r\n\t\r\n\tRECOVERY_MODE\r\n\t-----------------------\r\nLOGICAL REAL TIME APPLY<\/pre>\n
31. It is questioned whether there is an error in the broker configuration.<\/p>\n
\tDGMGRL> show configuration\r\n\t\r\n\tConfiguration - DG_Solution\r\n\t\r\n\t  Protection Mode: MaxAvailability\r\n\t  Members:\r\n\t  physical - Primary database\r\n\t    physclFS - Far sync instance \r\n\t      primary  - (*) Physical standby database \r\n\t      logical  - Logical standby database \r\n\t\r\n\t  Members Not Receiving Redo:\r\n\t  prmyFS   - Far sync instance \r\n\t\r\n\tFast-Start Failover: ENABLED\r\n\t\r\n\tConfiguration Status:\r\n\tSUCCESS   (status updated 30 seconds ago)\r\n<\/pre>\n
32. A table belonging to the TEST user is DROPed to see if the DDL and DML operations are running smoothly.<\/p>\n
a. We are querying the existing tables.<\/p>\n
\t\t[Physical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\r\n\t\tTABLE_NAME\r\n\t\t--------------------------------------------------------------------------------\r\n\t\tREGIONS_YEDEK\r\n\t\tJOBS_YEDEK\r\n\t\tEMPLOYEES_YEDEK\r\n\t\t\r\n\t\t[Primary] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\r\n\t\tTABLE_NAME\r\n\t\t--------------------------------------------------------------------------------\r\n\t\tREGIONS_YEDEK\r\n\t\tJOBS_YEDEK\r\n\t\tEMPLOYEES_YEDEK\r\n\t\t\r\n\t\t[Logical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\r\n\t\tTABLE_NAME\r\n\t\t--------------------------------------------------------------------------------\r\n\t\tREGIONS_YEDEK\r\n\t\tEMPLOYEES_YEDEK\r\n\t\tJOBS_YEDEK\r\n<\/pre>\n
b. A table is DROP.<\/p>\n
\t\t[Physical] SQL> drop table test.REGIONS_YEDEK;\r\n\t\t\r\n\t\tTable dropped.\r\n\t\t\r\n\t\t[Physical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\r\n\t\tTABLE_NAME\r\n\t\t--------------------------------------------------------------------------------\r\n\t\tJOBS_YEDEK\r\n\t\tEMPLOYEES_YEDEK\r\n\t\t\r\n\t\t[Primary] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\r\n\t\tTABLE_NAME\r\n\t\t--------------------------------------------------------------------------------\r\n\t\tJOBS_YEDEK\r\n\t\tEMPLOYEES_YEDEK\r\n\t\t\r\n\t\t[Logical] SQL> select table_name from dba_tables where owner='TEST';\r\n\t\t\r\n\t\tTABLE_NAME\r\n\t\t--------------------------------------------------------------------------------\r\n\t\tEMPLOYEES_YEDEK\r\n\t\tJOBS_YEDEK\r\n\t\r\n<\/pre>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"
Today I will give you information about Fast Start Failover -SINGLE NODE. 1. We check the broker’s configuration to see if everything is normal. DGMGRL> show configuration Configuration – DG_Solution Protection Mode: MaxPerformance Members: primary – Primary database prmyFS – Far sync instance physical – Physical standby database logical – Logical standby database Members Not …<\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"author":484,"featured_media":52329,"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-52327","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-oracle"],"aioseo_notices":[],"yoast_head":"\nFast Start Failover -SINGLE NODE - Database Tutorials<\/title>\n<meta name=\"description\" content=\"Today I will give you information about Fast Start Failover -SINGLE NODE. 1. We check the broker's configuration to see if everything is normal\" \/>\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\/09\/15\/fast-start-failover-single-node\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fast Start Failover -SINGLE NODE - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"Today I will give you information about Fast Start Failover -SINGLE NODE. 1. We check the broker's configuration to see if everything is normal\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2022-09-15T10:05:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-09-15T10:07:05+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png\" \/>\n\t<meta property=\"og:image:width\" content=\"746\" \/>\n\t<meta property=\"og:image:height\" content=\"377\" \/>\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=\"12 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\/09\/15\/fast-start-failover-single-node\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/\"},\"author\":{\"name\":\"Onur ARDAHANLI\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\"},\"headline\":\"Fast Start Failover -SINGLE NODE\",\"datePublished\":\"2022-09-15T10:05:38+00:00\",\"dateModified\":\"2022-09-15T10:07:05+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/\"},\"wordCount\":921,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png\",\"articleSection\":[\"ORACLE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/\",\"name\":\"Fast Start Failover -SINGLE NODE - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png\",\"datePublished\":\"2022-09-15T10:05:38+00:00\",\"dateModified\":\"2022-09-15T10:07:05+00:00\",\"description\":\"Today I will give you information about Fast Start Failover -SINGLE NODE. 1. We check the broker's configuration to see if everything is normal\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png\",\"width\":746,\"height\":377},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Fast Start Failover -SINGLE NODE\"}]},{\"@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 -SINGLE NODE - Database Tutorials","description":"Today I will give you information about Fast Start Failover -SINGLE NODE. 1. We check the broker's configuration to see if everything is normal","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\/09\/15\/fast-start-failover-single-node\/","og_locale":"en_US","og_type":"article","og_title":"Fast Start Failover -SINGLE NODE - Database Tutorials","og_description":"Today I will give you information about Fast Start Failover -SINGLE NODE. 1. We check the broker's configuration to see if everything is normal","og_url":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/","og_site_name":"Database Tutorials","article_published_time":"2022-09-15T10:05:38+00:00","article_modified_time":"2022-09-15T10:07:05+00:00","og_image":[{"width":746,"height":377,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png","type":"image\/png"}],"author":"Onur ARDAHANLI","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onur ARDAHANLI","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/"},"author":{"name":"Onur ARDAHANLI","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6"},"headline":"Fast Start Failover -SINGLE NODE","datePublished":"2022-09-15T10:05:38+00:00","dateModified":"2022-09-15T10:07:05+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/"},"wordCount":921,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png","articleSection":["ORACLE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/","url":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/","name":"Fast Start Failover -SINGLE NODE - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png","datePublished":"2022-09-15T10:05:38+00:00","dateModified":"2022-09-15T10:07:05+00:00","description":"Today I will give you information about Fast Start Failover -SINGLE NODE. 1. We check the broker's configuration to see if everything is normal","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-15-130449.png","width":746,"height":377},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/15\/fast-start-failover-single-node\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"Fast Start Failover -SINGLE NODE"}]},{"@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\/52327","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=52327"}],"version-history":[{"count":1,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/52327\/revisions"}],"predecessor-version":[{"id":52330,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/52327\/revisions\/52330"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/52329"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=52327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=52327"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=52327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}