test

Sun Cluster Geographic Edition Data Replication Guide for Oracle Data Guard

ProcedureHow to Deactivate an Oracle Data Guard Protection Group

You can deactivate a protection group in the following ways:

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.

  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. 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
    -e scope

    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.

    If the Configuration status is set to Error, revalidate the protection group by using the procedures described in How to Validate an Oracle Data Guard Protection Group.

Example 2–12 Deactivating an Oracle Data Guard Protection Group on All Clusters

This example shows how to deactivate a protection group on all clusters.


phys-paris-1# geopg stop -e global sales-pg
Example 2–13 Deactivating an Oracle Data Guard Protection Group on a Local Cluster

This example shows how to deactivate a protection group on the local cluster.


phys-paris-1# geopg stop -e local sales-pg
Example 2–14 Stopping Oracle Data Guard Data Replication While Leaving the Protection Group Online

This example shows how to stop only data replication on a local cluster.


phys-paris-1 geopg stop -e local -D sales-pg

If you decide later to deactivate both the protection group and its underlying data replication subsystem, you can rerun the command without the -D option.


phys-paris-1# geopg stop -e local sales-pg
Example 2–15 Deactivating an Oracle Data Guard Protection Group While Keeping Application Resource Groups Online

This example shows how to keep online two application resource groups, apprg1 and apprg2, while deactivating their protection group, sales-pg.

  1. Remove the application resource groups from the protection group.


    phys-paris-1# geopg remove-resource-group apprg1,apprg2 sales-pg

  2. Deactivate the protection group.


    phys-paris-1# geopg stop -e global sales-pg