Enable and Disable Fast-Start-Failover Data Guard Broker

 

Enable Fast-Start-Failover Data Guard Broker



Can be enabled automatic failover using Fast-Start-Failover Observer with Data Guard broker.

Configure FSFO

The StaticConnectIdentifier parameter must be set both in primary and standby

On primary(tansid_p1):

dgmgrl sys/sys@tansid_p1

DGMGRL> show database tansid_p1 StaticConnectIdentifier;
DGMGRL> show database tansid_p2 StaticConnectIdentifier;

SQL> ALTER SYSTEM SET LOCAL_LISTENER='(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.71)(PORT=1521))';


FastStartFailoverTarget: we need to pair physical standby with primary to let Fast Start Failover 

On primary (tansid_p1):
====================
dgmgrl sys/****@tansid_p1
DGMGRL> SHOW FAST_START FAILOVER
DGMGRL> EDIT DATABASE tansid_p1 SET PROPERTY FastStartFailoverTarget = 'tansid_p1';
DGMGRL> EDIT DATABASE proddb_p2 SET PROPERTY FastStartFailoverTarget = 'tansid_p2';
DGMGRL> show database verbose tansid_p1;
DGMGRL> show database verbose tansid_p2;

FastStartFailoverThreshold: Next we need to let broker know when to initiate automatic failover.
FSFO will wait before initiating failover

DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverThreshold=30;
DGMGRL> show fast_start failover

Define FastStartFailoverLagLimit: data we are ready to lose in case the Data Guard is in Max Performance Mode

DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverLagLimit = 30;

Enable FSFO: Now we can enable FSFO. Please keep in mind never start observer on production database

On Standby Server:


dgmgrl sys/****@tansid_p2

DGMGRL> ENABLE FAST_START FAILOVER;
DGMGRL> show configuration;
DGMGRL> start observer;


FSFO Configuration Test

Simulate failure: On tansid_p1, the current primary, shut abort the instance

On primary (tansid_p1):
===================
sqlplus / as sysdb
SQL> shut abort;

FSFO must perform automatic failover and tansid_p2 , check log files.

On new primary (tansid_p2):
===========================
sqlplus / as sysdba

SQL> select name, open_mode, db_unique_name from v$database;


Reinstate Failed Primary

Mount the failed primary (proddb) and it will auto reinstate. 

Do not open the database as it will be switched to physical standby

On failed primary (tansid_p1):
===========================
sqlplus / as sysdba
SQL> startup mount;

dgmgrl sys/***@tansid_p1
DGMGRL> show configuration;

Perform switchover to get back the original configuration

On current primary (proddb_st):
===============================
dgmgrl sys/sys@tansid_p2

DGMGRL> show configuration;
DGMGRL> switchover to tansid_p1


to Disable FSFO

dgmgrl sys/****@tansid_p2

DGMGRL> DISABLE FAST_START FAILOVER;

Stop observer:
==============

dgmgrl sys/****@tansid_p2

DGMGRL> stop observer;

Disabling FAST_START failover with FORCE option :

DGMGRL> show configuration;

Configuration - tansid_dgcnfg

Protection Mode: MaxAvailability
Databases:
tansid_p1- Primary database
Error: ORA-16820: fast-start failover observer is no longer observing this database

tansid_p2 - (*) Physical standby database (disabled)
ORA-16661: the standby database needs to be reinstated

Fast-Start Failover: ENABLED

Configuration Status:
ERROR


Checking Fast_start failover :
===============================

DGMGRL> show fast_start failover;

Fast-Start Failover: ENABLED

Threshold: 50 seconds
Target: testdb
Observer: shsebs121db01.appsol.com
Lag Limit: 50 seconds (not in use)
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Observer Reconnect: (none)
Observer Override: FALSE

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

Oracle Error Conditions:
(none)


DGMGRL> disable fast_start failover;
Error: ORA-16652: fast-start failover target standby database is disabled

Failed.
We can see here it returns the error.

Stopping it with FORCE option.
===============================

DGMGRL> disable fast_start failover force;
Disabled.
DGMGRL>








Comments

Post a Comment

Popular posts from this blog

How to fix Oracle SQL Developer connection issue "Got minus one from a read call"

Image
 During connection from SQL Developer to EBS database got below error message: Status : Failure - Test failed: IO Error: Got minus one from a read call Following solution can be done : 1. Go to directory $ORACLE_HOME / network / admin 2. Modify sqlnet.ora file with following parameter : tcp.validnode_checking = no 3. If you don 't want to disable this, you can put the machine names as follows: tcp.invited_nodes=(machine1, machine2) 3. Bounce the listener. Due to security enhancements it is not good to put tcp.validnode_checking = no or comment out will through error when we start listener like below: Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=shsebs7idb1.appsolworld.com)(PORT=1522))) TNS-00584: Valid node checking configuration error TNS-12560: TNS:protocol adapter error Better plan is to add localhost or IP address of client (Local Computer) in the sqlnet.ora file That will solve the problem NAMES.DIRECTORY_PATH=(TNSNAMES, ONAMES, HOSTNAME) SQLNET.EXPI
Read more

How to troubleshoot Long Running Concurrent Request in EBS 12.2

 The following points need to answer before jumping into troubleshooting: Are there any recent code changes done in the concurrent program?           Check long_running_sid and verify the recent code change of last_ddl_timestamp after a             discussion with the developer. Was this running long in the last few run as well, or was this time only?            ==> Check the program history. How much time does it take to complete?           Once again program history can give us some idea. Are these jobs fetching higher data compared to the last run           ===> Confirm on data change . Query Plan change will indicate this issue. Does this job runs at any specific time or it can be run anytime           ===> The nature of the job can help to understand the job's nature. Does this job fetch data using DB Link          ====> Check whether the DB link is involved or not. The below-given approach would help to conclude the gray areas. Check the load of the server using t
Read more

Few Important steps of Oracle Database Clone

 Make Sure oraInst.loc location is correct and accessble. [demantra@dsiddem ~]$ cat /etc/oraInst.loc inventory_loc=/orastage/oraInventory inst_group=dba [demantra@dsiddem ~]$ cd /orastage/oraInventory [demantra@dsiddem oraInventory]$ ls -ltr total 16 drwxrwx---. 5 demantra dba 4096 Jul 22 19:37 backup drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 ContentsXML drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 locks drwxrwx---. 3 demantra dba 4096 Jul 23 10:08 logs Remove Oracle Home from Inventory [demantra@dsiddem oraInventory]$ cd $ORACLE_HOME/oui/bin [demantra@dsiddem bin]$ ./runInstaller -detachHome ORACLE_HOME=$ORACLE_HOME Starting Oracle Universal Installer... Checking swap space: must be greater than 500 MB.   Actual 3039 MB    Passed The inventory pointer is located at /etc/oraInst.loc Run Clone.pl [demantra@dsiddem bin]$ echo $ORACLE_HOME /dnbsid/demantra/oracle/19.0.0 [demantra@dsiddem bin]$ echo $ORACLE_BASE /dnbsid/demantra [demantra@dsiddem bin]$ E01=ORACLE_HOME=$ORACLE_HOME [dema
Read more