You can activate a protection group in the following ways:
Globally, which activates a protection group on both clusters where the protection group has been configured
On the primary cluster only
On a standby cluster only
When you activate a protection group, the data replication product that you are using determines the clusters on which data replication can start. For example, the Oracle Data Guard software allows data replication to start only if you activate a protection group in one of the following ways:
Locally from the primary cluster.
Globally from either the primary or the standby cluster.
So, if you attempt to activate a protection group locally from the standby cluster, data replication does not start. However, if you activate a protection group globally from the standby cluster, data replication starts.
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.
Activate the protection group on the local cluster.
When you activate a protection group on the primary cluster, its application resource groups are also brought online.
phys-node-n# geopg start -e scope [-n] ODGprotectiongroup
Specifies the scope of the command.
If the scope is local, the command operates on the local cluster only. If the scope is global, the command operates on both clusters that deploy the protection group.
The property values, such as global and local, are not case sensitive.
Prevents the start of data replication when the protection group starts.
If you omit this option, the data replication subsystem starts at the same time as the protection group, and the command performs the following operations on each Oracle Data Guard Broker configuration in the protection group:
Verifies that 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.
Verifies that the Oracle dgmgrl command can connect using the values that are given for sysdba_username, sysdba_password, and local_db_service_name.
Verifies that the role configured for the replication resource is the same as the role of the protection group on the local cluster.
Verifies that the Oracle Data Guard Broker configuration details match those that are 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 clusters), the replication mode, and the standby type.
Specifies the name of the protection group.
The geopg start command uses the clrs enable resources and clrg online resourcegroups command to bring resource groups and resources online. For more information about using this command, see the clresource(1CL) and clresourcegroup(1CL) man pages.
If the role of the protection group is primary on the local cluster, the geopg start command performs the following operations:
Runs a script that is defined by the RoleChange_ActionCmd property
Brings the application resource groups, including the shadow RAC server proxy resource groups, in the protection group online on the local cluster
If the command fails, the Configuration status might be set to Error, depending on the cause of the failure. The protection group remains deactivated, but data replication might be started and some resource groups might be brought online.
Run the geoadm status command to obtain the status of your system.
If the Configuration status is set to Error, revalidate the protection group by using the procedures that are described in How to Validate an Oracle Data Guard Protection Group.
This example shows how to activate a protection group globally.
phys-paris-1# geopg start -e global sales-pg
This example shows how to activate a protection group on a local cluster only. This local cluster might be a primary cluster or a standby cluster, depending on the role of the cluster.
phys-paris-1 geopg start -e local sales-pg