Oracle Data Guard Broker Configurations (Sun Cluster Geographic Edition Data Replication Guide for Oracle Data Guard)

Sun Cluster Geographic Edition Data Replication Guide for Oracle Data Guard

Oracle Data Guard Broker Configurations

To define Oracle Data Guard Broker configurations, you need to determine the following information:

The name of the Oracle Data Guard Broker configuration, such as mysales.com, being replicated between the cluster-paris and cluster-newyork clusters.
The unique database names that are taking part in the replication, such as sales on the cluster-paris cluster, and salesdr on the cluster-newyork cluster.
The Oracle service names for these databases, such as sales -svc on the cluster-paris cluster and salesdr-svc on the tcluster-newyork cluster. These names are held in the tnsnames.ora files in the ${ORACLE_HOME}/network/admin directory of the nodes that are hosting the Oracle database that is being replicated, or in the Oracle naming service directory.
The database standby type for the Oracle Data Guard Broker configuration, which you set to either physical or logical.
The replication mode for the Oracle Data Guard Broker configuration, which you set to MaxPerformance, MaxAvailability, or MaxProtection.

After you configure Oracle Data Guard between a pair of primary and standby databases, you create an Oracle Data Guard Broker configuration by using the ${ORACLE_HOME}/bin/dgmgrl command to define the properties of the named replication. You can use this command to set and to retrieve the previously listed Oracle Data Guard Broker properties.

You also need to determine the names of the RAC server proxy resource groups that manage the Oracle RAC databases on each cluster. You configure these names by using the Data Service configuration wizard through the clsetup command, or by following the instructions in Appendix D, Command-Line Alternatives, in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS.

Of the Oracle Data Guard Broker configuration properties that are listed in the following table, you can change only the Protection Mode property with the Sun Cluster Geographic Edition software. You cannot use the Sun Cluster Geographic Edition software to modify other Oracle Data Guard Broker properties in the configuration, such as the DelayMins, MaxFailure, MaxConnections, and NetTimeout properties. You need to adjust these properties manually by using the Oracle Data Guard Broker command, or by modifying the appropriate database parameters that are held in the spfile server parameter file or the init${SID}.ora file through SQL*Plus.

Property	Allowed Values	Description
`Protection Mode`	`MaxPerformance`, `MaxAvailability` or `MaxProtection`	The data replication mode that is being used by Oracle, ranging from asynchronous (`MaxPerformance`) to synchronous (`MaxProtection`)
`Standby type`	`physical` or `logical`	The type of replication that is being performed, either Redo Apply (`physical`) or SQL Apply (`logical`) held as part of the primary database definition
`Configuration name`		The name for the Oracle Data Guard Broker configuration, which consists of a primary and a standby database
`Primary database`		The name of the primary database, its net service name, and its standby type
`Secondary database`		The name of the standby database and its net service name

The Sun Cluster Geographic Edition software modifies the Oracle Data Guard Broker configuration role changes during switchover and takeover operations.

For more information about the Oracle Data Guard Broker configuration, refer to the Oracle Data Guard Broker documentation.