Sun Cluster Geographic Edition Data Replication Guide for Oracle Data Guard

ProcedureHow to Add an Oracle Data Guard Broker Configuration to an Oracle Data Guard Protection Group

Before You Begin

A protection group is the container for the application resource groups, which contain data for services that are protected from disaster. Sun Cluster 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, Sun Cluster Geographic Edition software monitors the replication status of the Oracle RAC database that belongs to that Oracle Data Guard Broker configuration.

Sun Cluster 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 add an Oracle Data Guard Broker configuration to a protection group, ensure that the following conditions are met:

  1. Log in to a cluster node.

    To complete this step, you need to be assigned the Geo Management RBAC rights profile. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.

  2. 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 RAC server proxy 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_rac_proxy_svr_rg_name – Name of the local Oracle RAC server proxy 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_rac_proxy_svr_rg_name – Name of the Oracle RAC server proxy 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.

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

    For more information about the properties that you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties, in Sun 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 Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities, in Sun 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