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 cluster-newyork cluster. These names are held in one of the following locations:
The tnsnames.ora files in the ${ORACLE_HOME}/network/admin directory of the nodes that host the replicated Oracle database
The Oracle naming service directory
The database standby type for the Oracle Data Guard broker configuration, which you set to either logical, physical, or snapshot.
The replication mode for the Oracle Data Guard broker configuration, which you set to MaxPerformance, MaxAvailability, or MaxProtection.
The names of the Oracle database-server resource groups that manage the Oracle databases on each cluster. You configure these names by using the data service configuration wizard through the clsetup command. Alternatively, follow the instructions in Registering and Configuring HA for Oracle Database in Oracle Solaris Cluster Data Service for Oracle Database Guide or Appendix D, Command-Line Alternatives, in Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide.
If running the primary or secondary replicated Oracle database on a remote node, the name of the HA for Oracle External Proxy resource and resource group on that remote node. For configuration instructions, see Registering and Configuring HA for Oracle External Proxy in Oracle Solaris Cluster Data Service for Oracle External Proxy Guide.
The disaster recovery framework manages start, stop, and role changes between primary and standby databases during switchover and takeover operations. Your Oracle Data Guard configuration may include Far Sync instances. Usage of Far Sync instances is transparent to the disaster recovery framework since the framework manages the primary and standby states and role changes between primary and standby and corresponding commands do not change in the existence of Far Sync instances.
For more information about the Oracle Data Guard broker configuration, refer to the Oracle Data Guard broker documentation.