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 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 primary and standby database systems.
The Oracle database-server resource group and Oracle database-server resources that manage the Oracle database that is replicated by Oracle Data Guard exist on both the local and the partner cluster.
If the cluster will remotely manage an Oracle database, each cluster node is installed and configured with HA for Oracle External Proxy.
If you are using HA for Oracle External Proxy to manage replication of a remote Oracle database, all cluster nodes where HA for Oracle External Proxy is installed are also installed with the Oracle Database software client administrative kit. This software installs $ORACLE_HOME/bin/sqlplus and $ORACLE_HOME/bin/dgmgrl.
If you are using HA for Oracle External Proxy, ensure that one of the following is true on all cluster nodes:
The TNS_ADMIN property of the HA for Oracle External Proxy resource is set to $ORACLE_HOME/network/admin.
The /var/cluster/geo/odg/odg_configuration_name_config file contains the entry ORACLE_HOME=$ORACLE_HOME.
If you are using HA for Oracle External Proxy, ensure that you have granted the sysdba privilege to the user that the agent utilizes to monitor the database. The following SQL command grants this privilege:
$ sqlplus '/ as sysdba' SQL> grant sysdba to hauser; Grant succeeded.
The hauser is the name you set in the dbuser property of the corresponding SUNW.oracle_external_proxy resource. For more information, see Remote Database User in Oracle Solaris Cluster Data Service for Oracle External Proxy Guide.
DGMGRL> edit configuration set property BystandersFollowRoleChange=NONE;
For more information, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.
# 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 rights profile and Oracle Data Guard.
Perform this step on one node of each partner cluster that runs HA for Oracle Database.
phys-newyork-n# clresource set -p Standby_mode=mode \ -p Dataguard_role=role ora-db-rs phys-paris-n# clresource set -p Standby_mode=mode \ -p Dataguard_role=role ora-db-rs
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…] ODG-configuration-name protection-group
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. This resource group can be configured for Oracle RAC, HA for Oracle Database, or HA for Oracle External Proxy.
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. This resource group can be configured for Oracle RAC, HA for Oracle Database, or HA for Oracle External Proxy.
replication_mode – Replication mode for the database in the Oracle Data Guard broker configuration.
edit configuration set protection mode as $replication_mode
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 password.
For more information about the properties that you can set, see Appendix A, Standard Geographic Edition Properties, in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
Specifies the name of the new Oracle Data Guard broker configuration.
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 Legal Names and Values of Geographic Edition Entities in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
For more information about the geopg command, refer to the geopg(1M) man page.
The resource group that is defined in the local_rac_proxy_svr_rn_name or remote_rac_proxy_svr_rg_name property has an affinity with, or a dependency on, the rac-framework-rg.
The corresponding cluster has other resource groups that have an affinity with, or a dependency on, the rac-framework-rg.
# geopg show protection-group | grep -i external_dependency_allowed
If necessary, change the property value to True.
# geopg set-prop -p External_Dependency_Allowed=True 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