<<Back to Oracle Data Guard Broker Page
How Oracle Dataguard Broker Works
Oracle Dataguard Broker has server side and client side components. At client side it has OEM and DGMGRL. Both the utilities can be used to read and manipulate Broker Configuration data.At server Side it has got 2 components
1> Binary Configuration File
2> DMON process
DMON processes is responsible to monitor the health of the broker configuration and ensures that every database has a consistent description of the configuration. To Ensure this DMON process persistently maintains information about all members of the broker configuration in a binary configuration file. In Configuration file Broker stores various properties associated with each database to control the database's behavior. Whenever you add databases to a broker configuration, or make a change to an existing database's properties, each DMON process records the new information in its copy of the configuration file. The parameter values are updated in both database and configuration file itself. Parameters in database can only be updated if you are using server parameter file (SPFILE), therefore you must use servers parameter file.
To keep the locally stored configuration file synchronized and to propagate any modification from one member to another member DMON process of each member communicates (bi-directional) with each other. See Figure 2 below.
Starting from 12.2 there is a fixed view V$DATAGUARD_PROCESS to monitor the status of broker processes, as well as other Data Guard processes
Dataguard Broker Components
Bi-Directional DMON Process communication among each Broker Members
Oracle Data Guard broker configuration can have up to 253 members, including one primary database and a combination of standby databases, far sync instances, and Zero Data Loss Recovery Appliances
Comments
Post a Comment