How the Data Replication Subsystem Verifies the Oracle Data Guard Broker Configuration

When you add an Oracle Data Guard Broker configuration to a protection group, the data replication layer verifies that the Oracle Data Guard Broker configuration exists.

When you run the geopg add-replication-component command, if they do not already exist, an Oracle shadow RAC server proxy resource group and a replication resource group for the Oracle Data Guard Broker configuration are created. In addition, the configuration is successfully validated.

The Oracle shadow RAC server proxy resource group contains a Sun Cluster resource. This resource is based on the generic data service SUNW.gds resource type. The Oracle shadow RAC server proxy resource shadows the real Oracle RAC server proxy resource that manages and monitors the Oracle RAC database in the Oracle Data Guard Broker configuration.

For more information about the shadow RAC server proxy resource group, see Oracle Data Guard Shadow Resource Groups.

The replication resource group contains a Sun Cluster resource that is based on the generic data service SUNW.gds resource type. The replication resource monitors the state of the database replication as reported by Oracle Data Guard Broker.

For more information about replication resources, see Oracle Data Guard Replication Resource Groups.

For the validation to be successful, ensure that the following conditions are met:

• The resource group that is named in the local_rac_proxy_svr_rg_name property contains a resource of type SUNW.scalable_rac_server_proxy. This resource is used to determine the values for ${ORACLE_HOME} and the local Oracle RAC SID values.

• The Oracle dgmgrl command shows a SUCCESS status for the Oracle Data Guard Broker configuration. The presence of Oracle ORA- messages in the output from the dgmgrl command might indicate that the sysdba_username password is incorrect or that the cluster has been disabled. Oracle errors are returned as part of the messages that are generated by the validate command.

• The sysdba_username password is valid for the standby cluster to ensure that switchovers are possible.

• The Oracle Data Guard Broker configuration details match those held by Sun Cluster Geographic Edition. The details to check include which cluster is primary, the configuration name, the database mode (for both the primary and standby cluster), the replication mode, and the standby type.

Do not use Sun Cluster commands to change, remove, or bring offline these resources or resource groups. Use only Sun Cluster Geographic Edition commands to administer shadow RAC server proxy resource groups, replication resource groups, and resources that are internal entities that are managed by Sun Cluster Geographic Edition software. Altering the configuration or state of these entities directly with Sun Cluster commands could result in an unrecoverable failure.