Ask Me

Data guard Broker Configuration

: Data Guard Broker :

       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  describes  some of the operations the broker automates and simplifies 

I.) 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 30 standby databases(in Oracle 11g) in the same configuration.

II.) Managing  an entire Data Guard configuration, including  all databases, redo transport services, and log apply services, through a client connection to any database in the configuration.
III.) Managing the protection mode for the broker configuration.
IV.) Invoking switchover or failover with a single command to initiate and control complex role changes across all databases in the configuration.
V.) Configuring failover to occur automatically upon loss of the primary database, increasing availability without manual intervention.
VI.) 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.









  •  Step by Step How to Create Dataguard Broker Configuration

1. Set the parameter dg_broker_config_file1 and dg_broker_config_file2 on all instances
of primary and standby. 
Default location of broker configuration file is $ORACLE_HOME/dbs or $ORACLE_HOME/database. 
In case if you want broker configuration files in non default location, set these parameters. 
In case of RAC database, set broker configuration file location to shared location
and same value on all the instances. 
ALTER SYSTEM SET dg_broker_config_file1 = '\U01\oradata\dr1mfg.dat' scope=both sid='*'; 
ALTER SYSTEM SET dg_broker_config_file2 = '\U01\oradata\dr2mfg.dat' scope=both sid='*'; 
OR in case of ASM file system use: 
ALTER SYSTEM SET dg_broker_config_file1 = '+DATA/mfg/dr1mfg.dat' scope=both sid='*'; 
ALTER SYSTEM SET dg_broker_config_file2 = '+DATA/mfg/dr2mfg.dat' scope=both sid='*';
If you want the broker configuration files in default location,
then you can ignore this step- 1
2. Enable broker on both primary and standby: 
SQL>ALTER SYSTEM SET DG_BROKER_START=TRUE scope=both sid='*'; 
3. Connect to DGMGRL on primary: (from instance one in case of RAC) 
$dgmgrl 
DGMGRL for Linux: Version 10.2.0.3.0 - Production 
Copyright (c) 2000, 2005, Oracle. All rights reserved. 
Welcome to DGMGRL, type "help" for information. 
DGMGRL> CONNECT sys/<password>; 
Connected. 
4. Create configuration on primary: 
DGMGRL> CREATE CONFIGURATION 'COLDB_CONF' AS PRIMARY DATABASE IS
'colldb_pm' CONNECT IDENTIFIER IS colldb_pm;
Configuration "COLDB_CONF" created with primary database "COLLDB_PM"
5. Add standby in the configuration: 
DGMGRL> ADD DATABASE 'colldb_st' AS CONNECT IDENTIFIER IS colldb_st MAINTAINED
AS PHYSICAL;
Database "COLLDB_ST" added
6. Enable Configuration: 
DGMGRL> ENABLE CONFIGURATION; 
Enabled.
Use the SHOW command to verify that the configuration and databases were successfully
enabled and brought online: 
DGMGRL> SHOW CONFIGURATION; 
Configuration 
Name: PRODCONF 
Enabled: YES 
Protection Mode: MaxPerformance 
Fast-Start Failover: DISABLED 
Databases: 
PROD10G - Primary database 
STDBY10G - Physical standby database 
Current status for "PRODCONF" 
SUCCESS
IF ANYONE WANT TO RECONFIGURE AGAIN THE USE BELOW STEPS.
1. DGMGRL> CONNECT SYS/MANAGER
2. DGMGRL> DISABLE CONFIGURATION;
Disabled.
3. DGMGRL> remove CONFIGURATION;
Removed configuration
4. Continue Step 3 

Popular Posts