Re: Automation: DG Broker

From: Neil Chandler <>
Date: Thu, 22 Aug 2019 16:40:29 +0000
Message-ID: <DB7PR10MB2090EEFD97C6C0959DD8EE2985A50_at_DB7PR10MB2090.EURPRD10.PROD.OUTLOOK.COM>

Automated failover is a bad idea only if your app can't handle it, or if you have too much instability in your network, but I have implemented it successfully with a couple of clients (and argued against with a couple of others due to the first 2 issues.) It works very well. I do know of other clients (not mine) who have removed RAC and implemented DG/FSFO instead, too.

You can reinstantiate the (former) primary as a standby if you have flashback enabled. There is no need to fully recreate: it's basically flashback the primary to the SCN of failover, start recovering. There's plenty of blogs out there describing how to do this.

Oracle recommend having flashback on for all Primary and Standby databases, otherwise you will potentially need to rebuild both the primary and any tertiary standbys [DB's not the Failover Target] if you failover.



From: <> on behalf of Mladen Gogala <> Sent: 22 August 2019 16:12
To: <> Subject: Re: Automation: DG Broker

Of course, using automated fail-over is a terrible ide. Any power outage will trigger a fail-over. And contrary to what people are told, minor power outages do happen. After a fail-over you have to rebuild because fail-over does resetlogs.


On 8/22/19 8:53 AM, Dba DBA wrote:
If you dont want to use oracle services or a trigger to handle this, you will need a shell script on primary/standby to poll the db to see if its primary/standby and use that to notify the server.

On Mon, Aug 19, 2019 at 4:41 AM Sourav Biswas <<>> wrote: Hi Everybody,

This is a client requirement related to Oracle Dataguard.

DG Broker is configured to perform "Failover". Which works fine and fails over to Physical Standby when the conditions are met. Now, the client wants, that once DG Broker performs "Failover" its should also notify the Application DNS Server to redirect its traffic to new Primary Database.

This is part of automation workflow, where client wants to ensure there is no manual intervention with Database Failover as well as Application switch to new Primary Database.

Please suggest.

Thanks and Regards,
Sourav Biswas

Received on Thu Aug 22 2019 - 18:40:29 CEST

Original text of this message