Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Oracle Dataguard Fast Start Failover Tips -->>Edit The Listener In Wrongly And Restart The Listner

Enable fast_start failover you must have a working set of primary / standby databases.
Both databases must be in flashback mode.
Verify your Data Guard configuration with OEM.  You will need to review your Data Guard property.

p1 my primary, S1 my standby
edit database p1 set LogXptMode='SYNC';

edit database p1 set FastStartFailoverTarget= 'S1'

edit database S1set LogXptMode='SYNC';

edit database S1set FastStartFailoverTarget= 'p1'

Edit Configuration Set Protection Mode As Maxavailability;
Next, you need to start the fast_start failover observer  (using the Data Guard dgmgrl -silent "start observer" command.  You submit this dgmgrl command in the background with the nohup command so it is always running as a daemon process.:
nohup dgmgrl -silent sys/*** "start observer" &

note: it does not work if you connect with /. You will get DGM-16979 if you use / or if you use different passwords in standby and primary.
Now that we have the fast_start failover prerequisites, enable fast_start failover in dgmgrl:
DGMGRL> enable fast_start failover
Before you switch, check the listener.ora is correctly configured :



          (ADDRESS = (PROTOCOL = TCP)(HOST = precision.example.com)(PORT = 1521))

The GLOBAL_DBNAME is mandatory to enable a painless switchover. Otherwise the standby startup will fail with ORA-12514.


Popular posts from this blog

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

7 Steps to configure BDR replication in postgresql

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

PostgreSQL Monitoring Tools

PostgreSQL pgBadger