How to Activate an Oracle Data Guard Protection Group

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.

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

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.

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

-escope

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.

Note - The property values, such as global and local, are not case sensitive.

-n

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_oracle_svr_rg_name property contains a resource of type SUNW.scalable_rac_server_proxy for a scalable resource group or a resource of type SUNW.oracle_server for a failover resource group.

Verifies that the Oracle Data Guard dgmgrl command can connect using the values that are given for sysdba_username, sysdba_password, and local_db_service_name. Or if the sysdba_username and sysdba_password properties are null, verifies that the dgmgrl command can connect using the Oracle wallet connection format, dgmgrl /@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 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, the standby type, that FAST_START FAILOVER is disabled, and that BystandersFollowRoleChange is equal to NONE.

ODGprotectiongroup

Specifies the name of the protection group.

The geopg start command uses the clresource enable resources and clresroucegroup online resourcegroups command to bring resource groups
and resources online. For more information about these commands, 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 Oracle database-server 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.

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

How to Deactivate an Oracle Data Guard Protection Group

You can deactivate a protection group in the following ways:

Globally, meaning you deactivate a protection group on both the primary and the standby cluster where the protection group is configured

On the primary cluster only

On the standby cluster only

The result of deactivating a protection group on the primary or standby cluster
depends on the type of data replication that you are using. If
you are using Oracle Data Guard software, you can stop the Oracle Data
Guard configuration from the primary or the standby cluster when the configuration is
enabled because the Oracle Data Guard command-line interface (dgmgrl) on both clusters still accepts
commands.

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

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.

Deactivate the protection group on all nodes of the local cluster.

When you deactivate a protection group, its application resource groups are also unmanaged.

phys-node-n# geopg stop -e scope [-D] protectiongroupname

-escope

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 where the protection group is located.

Note - The property values, such as global and local, are not case sensitive.

-D

Specifies that only data replication be stopped and the protection group be put online.

If you omit this option, the data replication subsystem and the protection group are both stopped. If the role of the protection group on the local cluster is set to primary and you omit the -D option, the application resource groups are taken offline and put in an Unmanaged state.

protectiongroupname

Specifies the name of the protection group.

If the role of the protection group is primary on the local
cluster, the geopg stop command disables the Oracle Data Guard Broker configuration.

If the geopg stop command fails, run the geoadm status command to see the
status of each component. For example, the Configuration status might be set to
Error depending on the cause of the failure. The protection group might remain
activated even though some resource groups might be unmanaged. The protection group might be
deactivated with data replication running.