The Data Guard broker logically groups these primary and standby databases into a broker configuration that allows the broker to manage and monitor them together as an integrated unit. You can manage a broker configuration using either the Oracle Enterprise Manager graphical user interface or the Data Guard command-line interface.

To know more about it Oracle Dataguard

The Oracle Data Guard broker is a distributed management framework that automates and centralizes the creation, maintenance, and monitoring of Data Guard configurations. The following list describes some of the operations the broker automates and simplifies:

  • Creating Data Guard configurations that incorporate a primary database, a new or existing (physical, logical, or snapshot) standby database, redo transport services, and log applies services, where any of the databases could be Oracle Real Application Clusters (RAC) databases.
  • Adding additional new or existing (physical, snapshot, logical, RAC or non-RAC) standby databases to an existing Data Guard configuration, for a total of one primary database, and from 1 to 9 standby databases in the same configuration.
  • Managing an entire Data Guard configuration, including all databases, redo transport services, and log applies services, through a client connection to any database in the configuration.
  • Managing the protection mode for the broker configuration.
  • Invoking switchover or failover with a single command to initiate and control complex role changes across all databases in the configuration.
  • Configuring failover to occur automatically upon loss of the primary database, increasing availability without manual intervention.
  • Monitoring the status of the entire configuration, capturing diagnostic information, reporting statistics such as the redo apply rate and the redo generation rate and detecting problems quickly with centralized monitoring, testing, and performance tools.

Before configuring data guard broker , let us see configuration and log files of data guard :

Broker configuration files are created and named when we start dg broker for first time.

The DMON process maintains persistent configuration data about all the databases in the broker configuration in a broker configuration file.Each database that is part of  dg broker either primary or standby will have 2 configuration files which are maintained and synchronized for every database.

One of the files is in use and the other acts as a backup. The configuration files are binary files and cannot be edited.

Default naming convention is dr1<db_unique_name>.dat .

We can check this files from parameter.

We can change name of this files using alter system statement. But to change this we need to disable broker and stop DMON process.

Log file in Data Guard Broker :

As we know each background process is associated with one trace file ,DMON process is also having one trace file.

It is located in same directory as alert log file with following name :


How to use Data Guard broker

Configuration details cannot be determined by DGMGRL

Add Standby Database

Now, enable and check the configuration

Stay tuned for More articles on Oracle DataGuard

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel:

Skant Gupta’s LinkedIn:

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.