Before configuring Data Guard Broker, following prerequisites must be fulfilled.
To know about DG Broker Architecture
1. To configure Data Guard Broker , we need an enterprise edition of a database.
2. We can configure data guard broker on a single instance and RAC [multiple] instance.
3. DG_BROKER_START initialization parameter must be set to TRUE.
ALTER SYSTEM SET DG_BROKER_START=TRUE;
4. Net services must be created prior to to configuring data guard broker for the Primary and Existing standby database
Note : When we configure DG Broker with Enterprise Manager Grid Control it configures net services for any new standby database.
5. To do restart operation of any instance with dg broker , a service with a specific name must be registered with the local listener of each instance. Your DB global name should be set to : <db_unique_name>_DGMGRL.db_domain
Example : mydb.example.com
6. To configure data guard broker compatible parameter must be set 10.2.0.1.0 or higher on both primary and standby database.
Note: Set the COMPATIBLE initialization parameter to 11.2.0 to take advantage of new Oracle Database 11g Release 2 (11.2) features.
7. Database must be in archivelog mode.
8. To configure data guard broker database should be in mount or opened and not in a nomount stage.
9. DG_BROKER_CONFIG_FILEn: Configured for any RAC databases.
Now let us see the usage of SPFILE in Data Guard Broker.
To configure Data Guard Broker we must use SPFILE to set initialization parameters.
To ensure that the broker can update the values of parameters in both the database instance and the configuration file, you must use the persistent server parameter file (SPFILE) to control static and dynamic initialization parameters.
Use of the SPFILE gives the broker a mechanism that enables it to reconcile property values that you have selected when using the broker with any related initialization parameter values that are recorded in the SPFILE. In
addition, the SPFILE permits persistent Data Guard settings so that Data Guard continues to work even after the broker is disabled.
addition, the SPFILE permits persistent Data Guard settings so that Data Guard continues to work even after the broker is disabled.
When a broker is disabled we can still update database property using the broker . Broker will then update those property to SPFILE and in memory . Once the broker is started it will update configuration file from SPFILE and from memory parameters.
To see a configuration of data guard broker: Configure DG broker
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: https://t.me/helporacle
Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/
Joel Perez’s LinkedIn: Joel Perez’s Profile
LinkedIn Group: Oracle Cloud DBAAS
Facebook Page: OracleHelp
