Re: DataGuard Broker opinions please.

You can neatly follow the progress and see everything it's doing. If anything goes wrong, you'll see exactly why and what fails. On top of that, the DRC logs are also highly detailed.

All in all, it's a great tool and should be part of every standby environment.

Stefan

On Tue, Oct 31, 2017 at 12:49 AM, Nassyam Basha <nassyambasha_at_gmail.com<mailto:nassyambasha_at_gmail.com>> wrote: Forget the customer systems, even in my test machines, i manage only with Broker. Even I suggest using Data Guard broker to all the customer whomever I work.

DG Broker considered as a lousy product but in fact, it is a very beautiful utility and simple to manage. Even the troubleshooting is also simplified with broker.

The main challenge is when managing with Broker then we should not use SQL*Plus to manage Data Guard. for example, we have to change the parameter standby_file_management from AUTO to MANUAL, then being lazy DBA the command issued from SQL*Plus. Then it creates inconsistency and also we can see the warnings in the broker configuration.

I hardly remember the commands, again we have the beautiful "help" like for other utilities GDSCTL, srvctl etc and everytime I use the syntax by help only. if we manage broker smoothly then it is definitely your best mate. :)

DGMGRL> help edit database
Edits a configuration, database, or instance Syntax:
  EDIT CONFIGURATION SET PROTECTION MODE AS     {MaxProtection|MaxAvailability|MaxPerformance};