Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition Data Replication Guide for Oracle Data Guard Oracle Solaris Cluster Geographic Edition

Search Scope:

- This Document
- Entire Library

## Administering Oracle Data Guard Broker Configurations

The following procedures describe how to administer Oracle Data Guard Broker data replication configurations in an Oracle Data Guard protection group.

- How to Add an Oracle Data Guard Broker Configuration to an Oracle Data Guard Protection Group

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

- How to Modify an Oracle Data Guard Broker Configuration

- How to Delete an Oracle Data Guard Broker Configuration From an Oracle Data Guard Protection Group

For details about configuring an Oracle Data Guard protection group, see How to Create and Configure an Oracle Data Guard Protection Group.

## How to Add an Oracle Data Guard Broker Configuration to an Oracle Data Guard Protection Group

A protection group is the container for the replication component and the application resource groups, which contain data for services that are protected from disaster. Geographic Edition software protects the data by replicating it from the primary cluster to the standby cluster. By adding an Oracle Data Guard Broker configuration to a protection group, Geographic Edition software monitors the status of the data replication that corresponds to the database in the Oracle Data Guard Broker configuration.

Geographic Edition software also controls the role and state of the Oracle Data Guard Broker configuration during protection group operations, such as start, stop, switchover, and takeover.

Before You Begin

Before you add an Oracle Data Guard Broker configuration to a protection group, ensure that all of the following conditions are met:

- The protection group is defined on the local cluster.

- If the partner cluster can be reached, the protection group is offline on the local cluster and the partner cluster.

- The Oracle Data Guard Broker configuration exists on both the local cluster and the partner cluster.

- The Oracle database-server resource group and Oracle database-server resources that manage the Oracle database that is replicated by Oracle Data Guard exists on both the local and the partner cluster.

- Each partner cluster has the `Standby_type` data-replication property set to match the current standby mode of the Oracle Data Guard Broker database.

1. Ensure that the Oracle Data Guard Broker properties `BystandersFollowRuleChange` and `FAST_START FAILOVER` are set properly.
   1. Set `BystandersFollowRuleChange` to `NONE`.

          DGMGRL> edit configuration set property BystandersFollowRuleChange=NONE;

   2. Ensure that `FAST_START FAILLOVER` is disable.
2. Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.

   For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   Note - If you use a role with Geo Management RBAC rights, ensure that the `/var/cluster/geo` ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.

       # chmod A+user:username:rwx:allow /var/cluster/geo

   The `/var/cluster/geo` directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.

3. For HA for Oracle, ensure that the `Standby_mode` extension property of the `SUNW.oracle_server` resource matches the current standby mode of the Oracle Data Guard Broker database.

   Perform this step on one node of each partner cluster that runs HA for Oracle.

       phys-newyork-n# clresource set -p Standby_mode=mode ora-db-rs
       phys-paris-n# clresource set -p Standby_mode=mode ora-db-rs

4. Add an Oracle Data Guard Broker configuration to the protection group.

   This command adds a configuration to a protection group on the local cluster and propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.

       phys-node-n# geopg add-replication-component \
       -p property [-p...] ODGConfigurationName protectiongroupname

   `-p` property

     Specifies the properties of either the Oracle Data Guard Broker configuration, the Oracle database-server resource group, or the Oracle database user name and the associated password.

     You can specify the following properties:

     - `local_database_name` – Name of the local database in the Oracle Data Guard Broker configuration.

     - `local_db_service_name` – Oracle net service name for the local database.

     - `local_oracle_svr_rg_name` – Name of the local Oracle database-server resource group that manages the local database in the Oracle Data Guard Broker configuration.

     - `remote_database_name` – Name of the remote database in the Oracle Data Guard Broker configuration.

     - `remote_db_service_name` – Oracle net service name for the remote database.

     - `remote_oracle_svr_rg_name` – Name of the Oracle database-server resource group on the partner cluster that manages the remote database in the Oracle Data Guard Broker configuration.

     - `replication_mode` – Replication mode for the database in the Oracle Data Guard Broker configuration.

     - `standby_type` – Standby type for the database in the Oracle Data Guard Broker configuration.

     - `sysdba_password` – Password for the Oracle `SYSDBA` privileged database user. Do not specify the actual password on the command line. If you specify only `-p sysdba_password=`, the `geopg` command prompts you to type an actual password, which is not displayed as you type it.

       If you use an Oracle wallet, you do not need to specify this password.

     - `sysdba_username` – Name of an Oracle `SYSDBA` privileged database user who can perform the Oracle Data Guard Broker switchover and takeover operations.

       If you use an Oracle wallet, you do not need to specify this username.

     For more information about the properties that you can set, see Appendix A, Standard Geographic Edition Properties, in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   ODGConfigurationName

     Specifies the name of the new Oracle Data Guard Broker configuration.

   protectiongroupname

     Specifies the name of the protection group that contains the new Oracle Data Guard Broker configuration.

   For information about the names and values that are supported by Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities, in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   For more information about the `geopg` command, refer to the `geopg`(1M) man page.

Example 2-7 Adding an Oracle Data Guard Broker Configuration to an Oracle Data Guard Protection Group

This example shows how to add an Oracle Data Guard Broker configuration to the `sales-pg` protection group.

To run the following command successfully, you must already be able to connect to both a local and a remote database service.

    phys-paris-1# geopg add-replication-component  \
                   -p local_database_name=sales \
                   -p remote_database_name=salesdr \
                   -p local_db_service_name=sales-svc \
                   -p remote_db_service_name=salesdr-svc \
                   -p standby_type=physical \
                   -p replication_mode=MaxPerformance \
                   -p sysdba_username=sys \
                   -p sysdba_password= \
                   -p local_rac_proxy_svr_rg_name=sales-rac-proxy-svr-rg \
                   -p remote_rac_proxy_svr_rg_name=salesdr-rac-proxy-svr-rg \
                   mysales.com sales-pg

### 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, a shadow Oracle database-server resource group and a replication resource group for the Oracle Data Guard Broker configuration are created. In addition, the configuration is successfully validated on the local cluster. However, the configuration might not be valid on the remote cluster. You can use the `geopg validate protectiongroup` command on the remote cluster to troubleshoot an invalid configuration.

Note - To avoid possible configuration errors, do not create these resource groups separately, before running the `geopg add-replication-component` command.

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

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

The replication resource group contains an Oracle Solaris 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_oracle_svr_rg_name` property contains a resource of the appropriate resource type:

  - For a scalable resource group, the property specifies a resource group that contains a resource of the `SUNW.scalable_rac_server_proxy` resource type.

  - For a failover resource group, the property specifies a resource group that contains a resource of the `SUNW.oracle_server` resource type.

  This resource is used to determine the values for `${ORACLE_HOME}` and the local Oracle database `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. Or, the Oracle wallet connection mechanism, `dgmgrl /@service_name`, can successfully connect to the broker.

- The Oracle Data Guard Broker configuration details match those held by 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 standby type, that `FAST_START FAILOVER` is disabled, and that `BystandersFollowRoleChange` is set to `NONE`.

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

## How to Modify an Oracle Data Guard Broker Configuration

1. Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.

   For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   Note - If you use a role with Geo Management RBAC rights, ensure that the `/var/cluster/geo` ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.

       # chmod A+user:username:rwx:allow /var/cluster/geo

   The `/var/cluster/geo` directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.

2. Modify the Oracle Data Guard Broker configuration.

   This command modifies the properties of an Oracle Data Guard Broker configuration in a protection group on the local cluster. The command then propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.

       phys-node-n# geopg modify-replication-component -p property [-p…] \
       ODGConfigurationName protectiongroupname

   `-p` property

     Specifies the properties of the data replication Oracle Data Guard Broker configuration.

     For more information about the properties that you can set, see Appendix A, Standard Geographic Edition Properties, in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   ODGConfigurationName

     Specifies the name of the Oracle Data Guard Broker configuration.

   protectiongroupname

     Specifies the name of the protection group that contains the Oracle Data Guard Broker configuration.

## How to Delete an Oracle Data Guard Broker Configuration From an Oracle Data Guard Protection Group

Before You Begin

Before you remove an Oracle Data Guard Broker configuration from a protection group, ensure that the following conditions are met:

- The protection group is defined on the local cluster.

- If the partner cluster can be reached, the protection group is offline on the local cluster and the partner cluster.

- The Oracle Data Guard Broker configuration is managed by the protection group.

For information about deleting protection groups, refer to How to Delete an Oracle Data Guard Protection Group.

1. Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.

   For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   Note - If you use a role with Geo Management RBAC rights, ensure that the `/var/cluster/geo` ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.

       # chmod A+user:username:rwx:allow /var/cluster/geo

   The `/var/cluster/geo` directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.

2. Remove the Oracle Data Guard Broker configuration.

   This command removes an Oracle Data Guard Broker configuration from a protection group on the local cluster. The command then propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.

   This command removes the Oracle Data Guard Broker configuration from the protection group. This command also deletes the shadow Oracle database-server resource group and replication resource group for this Oracle Data Guard Broker configuration.

       phys-node-n# geopg remove-replication-component ODGConfigurationName protectiongroupname

   ODGConfigurationName

     Specifies the name of the Oracle Data Guard Broker configuration.

   protectiongroupname

     Specifies the name of the protection group.

Example 2-8 Deleting an Oracle Data Guard Broker Configuration From an Oracle Data Guard Protection Group

This example shows how to delete an Oracle Data Guard Broker configuration from an Oracle Data Guard protection group.

    phys-paris-1# geopg remove-replication-component mysales.com sales-pg

Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |