Chapter 2 Administering Oracle Data Guard Protection Groups

This chapter describes how to administer data replication with Oracle Data Guard software.

This chapter covers the following topics:

• Working With Oracle Data Guard Protection Groups

• Creating, Modifying, Validating, and Deleting an Oracle Data Guard Protection Group

• Administering Oracle Data Guard Application Resource Groups

• Administering Oracle Data Guard Broker Configurations

• Replicating the Oracle Data Guard Protection Group Configuration to a Partner Cluster

• Activating and Deactivating a Protection Group

• Resynchronizing an Oracle Data Guard Protection Group

• Checking the Runtime Status of Oracle Data Guard Data Replication

Working With Oracle Data Guard Protection Groups

Unlike other data replication mechanisms, such as Sun StorageTek Availability Suite, Hitachi TrueCopy, and EMC SRDF, Oracle Data Guard is an integral part of Oracle RAC software. Consequently, you do not place Oracle RAC server proxy resource groups under Sun Cluster Geographic Edition control as you do when you are using one of these host or storage-based data replication mechanisms. You can add Oracle Data Guard Broker configurations for databases that are being replicated by Oracle Data Guard to Sun Cluster Geographic Edition without stopping the databases or the replication.

Overview of Administering Protection Groups

To add an existing Oracle Data Guard Broker configuration that contains an Oracle Data Guard replicated database to a new protection group, you will complete the following general procedures.

1. On a node in either cluster, create the protection group.

   This procedure is covered in How to Create and Configure an Oracle Data Guard Protection Group.

2. On the same node, add the Oracle Data Guard Broker configuration to the protection group.

   This procedure is covered in How to Add an Oracle Data Guard Broker Configuration to an Oracle Data Guard Protection Group.

3. On a node in the other cluster, retrieve the protection group configuration.

   This procedure is covered in How to Replicate the Oracle Data Guard Protection Group Configuration to a Partner Cluster.

4. On the same node, add the Oracle shadow RAC server proxy resource group and application resource group to the protection group.

   This procedure is covered in How to Add an Application Resource Group to an Oracle Data Guard Protection Group.

5. Activate the protection group, either globally from either cluster or locally from the primary.

   This procedure is covered in How to Activate an Oracle Data Guard Protection Group.

How to Administer an Oracle Data Guard Protection Group (Example)

The following example shows all the steps that are involved in administering Oracle Data Guard protection groups, as described in more detail in procedures that are included later in this chapter.

1. Create the protection group on the cluster-paris cluster.

   phys-paris-1# geopg create -d odg -o primary -s paris-newyork-ps sales-pg Protection group "sales-pg" has been successfully created

   The cluster-paris cluster is the primary cluster. You do not need to set any additional Oracle Data Guard protection group properties.

2. Add the Oracle Data Guard Broker configuration, mysales.com, to the protection group.

   ---

   Caution –

   To ensure security, do not supply a password when you specify the sysdba_password property. 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. You can pipe the password to the command if you want to drive the geopg command from another shell script.

   Also, 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 Oracle Data Guard configuration "mysales.com" successfully added to the protection group "sales-pg"

3. Confirm that the shadow Oracle RAC and replication resource groups and resources that you added to the protection group in the preceding step were added.

   phys-paris-1# clresourcegroup status === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ rac-framework-rg phys-paris-1 No Online phys-paris-2 No Online scal-oradata-dg-rg phys-paris-1 No Online phys-paris-2 No Online qfs-oradata-mds-rg phys-paris-1 No Online phys-paris-2 No Offline scal-oradata-mp-rg phys-paris-1 No Online phys-paris-2 No Online rac_server_proxy-rg phys-paris-1 No Online phys-paris-2 No Online geo-clusterstate phys-paris-1 No Online phys-paris-2 No Online geo-infrastructure phys-paris-1 No Offline phys-paris-2 No Online sales-pg-odg-rep-rg phys-paris-1 No Online phys-paris-2 No Offline mysales_com-rac-proxy-svr-shadow-rg phys-paris-1 No Unmanaged phys-paris-2 No Unmanaged phys-paris-1# clresource status Resource Name Node Name State Status Message ------------- --------- ----- -------------- rac-framework-rs phys-paris-1 Online Online phys-paris-2 Online Online rac-udlm-rs phys-paris-1 Online Online phys-paris-2 Online Online rac-svm-rs phys-paris-1 Online Online phys-paris-2 Online Online crs_framework-rs phys-paris-1 Online Online phys-paris-2 Online Online scal-oradata-dg-rs phys-paris-1 Online Online - Diskgroup online phys-paris-2 Online Online - Diskgroup online qfs-oradata-mds-rs phys-paris-1 Online Online - Service is online. phys-paris-2 Offline Offline scal-oradata-mp-rs phys-paris-1 Online Online phys-paris-2 Online Online rac_server_proxy-rs phys-paris-1 Online Online - Oracle instance UP phys-paris-2 Online Online - Oracle instance UP geo-servicetag phys-paris-1 Online but not monitored Online phys-paris-2 Online but not monitored Online geo-clustername phys-paris-1 Offline Offline phys-paris-2 Online Online - LogicalHostname online. geo-hbmonitor phys-paris-1 Offline Offline phys-paris-2 Online Online - Daemon OK geo-failovercontrol phys-paris-1 Offline Offline phys-paris-2 Online Online - Service is online. mysales_com-odg-rep-rs phys-paris-1 Offline Offline phys-paris-2 Offline Offline mysales_com-rac-proxy-svr-shadow-rs phys-paris-1 Offline Offline phys-paris-2 Offline Offline

4. Locally activate the protection group.

   phys-paris-1# geopg start -e local sales-pg Processing operation... The timeout period for this operation on each cluster is 3600 seconds (3600000 milliseconds)... Protection group "sales-pg" successfully started.

   If your mysales.com Oracle Data Guard Broker configuration is not already enabled, this process might take a few minutes or more. The actual time that the process takes depends on the configuration of your primary and standby databases as well as the distance between the clusters.

5. Verify that the data replication is successfully started.

   phys-paris-1# geoadm status Cluster: cluster-paris Partnership "paris-newyork-ps" : OK Partner clusters : cluster-newyork Synchronization : OK ICRM Connection : OK Heartbeat "hb_cluster-paris~cluster-newyork" monitoring \ "paris-newyork-ps" OK Plug-in "ping-plugin" : Inactive Plug-in "tcp_udp_plugin" : OK Protection group "sales-pg" : Error Partnership : paris-newyork-ps Synchronization : Error Cluster cluster-paris : OK Role : Primary Activation State : Activated Configuration : OK Data replication : OK Resource groups : None Cluster cluster-newyork : Unknown Role : Unknown Activation State : Unknown Configuration : Unknown Data Replication : Unknown Resource Groups : Unknown

6. On one node of the partner cluster, retrieve the protection group.

   phys-newyork-1# geopg get -s paris-newyork-ps sales-pg Protection group "sales-pg" has been successfully created.

7. Confirm that the shadow Oracle RAC and replication resource groups and resources for the protection group that you retrieved in the preceding step were retrieved.

   phys-newyork-1# clresourcegroup status === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ rac-framework-rg phys-newyork-1 No Online phys-newyork-2 No Online scal-oradata-dg-rg phys-newyork-1 No Online phys-newyork-2 No Online qfs-oradata-mds-rg phys-newyork-1 No Online phys-newyork-2 No Offline scal-oradata-mp-rg phys-newyork-1 No Online phys-newyork-2 No Online rac_server_proxy-rg phys-newyork-1 No Online phys-newyork-2 No Online geo-clusterstate phys-newyork-1 No Online phys-newyork-2 No Online geo-infrastructure phys-newyork-1 No Offline phys-newyork-2 No Online sales-pg-odg-rep-rg phys-newyork-1 No Online phys-newyork-2 No Offline mysales_com-rac-proxy-svr-shadow-rg phys-newyork-1 No Unmanaged phys-newyork-2 No Unmanaged phys-newyork-1# clresource status === Cluster Resources === Resource Name Node Name State Status Message ------------- --------- ----- -------------- rac-framework-rs phys-newyork-1 Online Online phys-newyork-2 Online Online rac-udlm-rs phys-newyork-1 Online Online phys-newyork-2 Online Online rac-svm-rs phys-newyork-1 Online Online phys-newyork-2 Online Online crs_framework-rs phys-newyork-1 Online Online phys-newyork-2 Online Online scal-oradata-dg-rs phys-newyork-1 Online Online - Diskgroup online phys-newyork-2 Online Online - Diskgroup online qfs-oradata-mds-rs phys-newyork-1 Online Online - Service is online. phys-newyork-2 Offline Offline scal-oradata-mp-rs phys-newyork-1 Online Online phys-newyork-2 Online Online rac_server_proxy-rs phys-newyork-1 Online Online - Oracle instance UP phys-newyork-2 Online Online - Oracle instance UP geo-servicetag phys-newyork-1 Online but Online not monitored phys-newyork-2 Online but Online not monitored geo-clustername phys-newyork-1 Offline Offline phys-newyork-2 Online Online - LogicalHostname online. geo-hbmonitor phys-newyork-1 Offline Offline phys-newyork-2 Online Online - Daemon OK geo-failovercontrol phys-newyork-1 Offline Offline phys-newyork-2 Online Online - Service is online. mysales_com-odg-rep-rs phys-newyork-1 Offline Offline phys-newyork-2 Offline Offline mysales_com-rac-proxy-svr-shadow-rs phys-newyork-1 Offline Offline phys-newyork-2 Offline Offline

8. From any node in a partner cluster, add the shadow RAC server proxy resource group to the protection group.

   # geopg add-resource-group mysales_com-rac-proxy-svr-shadow-rg sales-pg Following resource groups were successfully added: "mysales_com-rac-proxy-svr-shadow-rg"

   Adding the shadow RAC server proxy resource group to the protection group is not critical to the operation of the replication. The resource contained within it simply reflects the status of the real RAC server proxy resource group and highlights whether the cluster is the Oracle Data Guard primary cluster.

9. From any node in a partner cluster, globally activate the protection group on both clusters.

   # geopg start -e global sales-pg Processing operation... The timeout period for this operation on each cluster is 3600 seconds (3600000 milliseconds)... Protection group "sales-pg" successfully started.

10. Verify that the protection group is successfully created and activated.

    phys-newyork-1# geoadm status Cluster: cluster-newyork Partnership "paris-newyork-ps": OK Partner clusters : cluster-newyork Synchronization : OK ICRM Connection : OK Heartbeat "hb_cluster-newyork~cluster-paris" monitoring "cluster-paris": OK Heartbeat plug-in "ping_plugin" : Inactive Heartbeat plug-in "tcp_udp_plugin": OK Protection group "sales-pg" : OK Partnership : "paris-newyork-ps" Synchronization : OK Cluster cluster-newyork : OK Role : Primary PG activation state : Activated Configuration : OK Data replication : OK Resource groups : OK Cluster cluster-paris : OK Role : Secondary PG activation state : Activated Configuration : OK Data replication : OK Resource groups : OK

Creating, Modifying, Validating, and Deleting an Oracle Data Guard Protection Group

This section covers the following topics:

You can create protection groups that are not configured to use data replication. To create a protection group that does not use a data replication subsystem, omit the -d datareplicationtype option when you use the geopg command. If you omit this option, the geoadm status command shows that the state of data replication is NONE.

How to Create and Configure an Oracle Data Guard Protection Group

The following example builds on the example configuration that was described in Chapter 1, Replicating Data With Oracle Data Guard Software.

In this example, the sales database is online on the cluster-paris cluster and is protected by Oracle Data Guard.

Ensure that the mysales.com Oracle Data Guard Broker configuration exists before you proceed, as Sun Cluster Geographic Edition does not create the configuration for you.

Before You Begin

Ensure that the following conditions are met:

• Your clusters are members of a partnership.

• The protection group that you are creating does not already exist.

Protection group names are unique in the global Sun Cluster Geographic Edition namespace. You cannot use the same protection group name in two partnerships on the same system.

You can also replicate the existing configuration of a protection group from a remote cluster to the local cluster. For more information, see Replicating the Oracle Data Guard Protection Group Configuration to a Partner Cluster.

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. On all nodes of the local cluster, create a new protection group.

   phys-node-n# geopg create -s partnershipname -d odg \ -o localrole [-p property [-p...]] protectiongroupname

   -s partnershipname

   Specifies the name of the partnership.

   -d odg

   Specifies that the protection group data is replicated by Oracle Data Guard software.

   -o localrole

   Specifies the role of this protection group on the local cluster as either primary or secondary.

   -p propertysetting

   Specifies the properties of the protection group.

   You can specify the following properties:

   • Description – Describes the protection group.

   • Timeout – Specifies the timeout period for the protection group, in seconds.

   protectiongroupname

   Specifies the name of the protection group.

   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.

   Before creating the protection group, the data replication layer validates that the configuration is correct.

   • If the validation is successful, the local Configuration status is set to OK and the Synchronization status is set to Error.

   • If the validation is unsuccessful, the protection group is not created.

How to Modify an Oracle Data Guard Protection Group

Before You Begin

Ensure that the protection group that you want to modify exists locally.

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. Modify the configuration of the protection group.

   phys-node-n# geopg set-prop -p property[-p…] protectiongroupname

   -p property

   Specifies the properties of the protection group.

   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.

   protectiongroupname

   Specifies the name of the protection group.

   If the partner cluster contains a protection group of the same name, the geopg set-prop command also propagates the new configuration information to the partner cluster.

   The geopg set-prop command revalidates the protection group with the new configuration information. If the validation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration is modified and its status is set to OK on the local cluster.

   If the Configuration status is set to OK on the local cluster, but the validation is unsuccessful on the partner cluster, the Configuration is modified on the partner cluster and the configuration status is set to Error on the partner cluster.

   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–1 Modifying the Configuration of a Protection Group

This example shows how to modify the timeout property of a protection group.

phys-paris-1# geopg set-prop -p Timeout=300 sales-pg

How to Validate an Oracle Data Guard Protection Group

Before You Begin

When the Configuration status of a protection group is displayed as Error in the output of the geoadm status command, you can validate the configuration by using the geopg validate command. This command checks the current state of the protection group and its entities.

If the protection group and its entities are valid, the Configuration status of the protection groups is set to OK. If the geopg validate command finds an error in the configuration files, the command displays a message about the error and the configuration remains in the error state. In such a case, you can fix the error in the configuration and run the geopg validate command again.

This command validates the configuration of the protection group on the local cluster only. To validate the protection group configuration on the partner cluster, run the command again on the partner cluster.

Before validating the configuration of a protection group, ensure that the protection group you want to validate exists locally and that the common agent container is online on all nodes of both clusters in the partnership.

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. Validate the configuration of the protection group.

   This command validates the configuration of a single protection group on the local cluster only.

   phys-node-n# geopg validate protectiongroupname

Example 2–2 Validating the Configuration of a Protection Group

This example shows how to validate a protection group.

phys-node-n# geopg validate sales-pg

How the Data Replication Layer Validates the Application Resource Groups and Data Replication Entities

During protection group validation, the Oracle Data Guard data replication layer validates the application resource groups and the data replication entities. The Oracle Data Guard data replication layer verifies the following conditions:

• That the resource group in the protection group that is being validated does not contain an Oracle RAC server proxy resource group that contains an Oracle RAC server proxy resource

  You cannot add these resource groups to an Oracle Data Guard protection group because the Oracle RAC database that is managed by the Oracle RAC server proxy resource is shut down on the standby cluster when the protection group is started globally, thus disabling the Oracle Data Guard data replication.

• That the Auto_start_on_new_cluster property in an application resource group in the protection group is set to False

  When you bring a protection group online on the primary cluster, the data replication layer brings the application resources groups that are participating in that protection group online only on the same primary cluster. Setting the Auto_start_on_new_cluster property to False prevents the Sun Cluster resource group manager from automatically starting the application resource groups. In this case, the startup of resource groups is reserved for the Sun Cluster Geographic Edition software.

  When the protection group is activated, application resource groups need to be online only on the primary cluster. Ensure that the following conditions are met:

• That the Oracle dgmgrl command is showing a SUCCESS status for the each of the Oracle Data Guard Broker configurations

  The presence of Oracle ORA- messages in the output from the dgmgrl command might indicate that the sysdba_username password is incorrect or that the cluster has been disabled. This information is reflected in the status of the replication resource for the Oracle Data Guard Broker configuration.

• That the Oracle Data Guard Broker configuration details match those 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 cluster), the replication mode, and the standby type.

• That the sysdba_username password is valid for the standby cluster, to ensure that switchovers are possible

When validation is complete, the Sun Cluster Geographic Edition software creates the shadow RAC server proxy resource group and resource, the replication resource group, and the resources for this replication resource group, if they do not exist, and brings them online. If a resource group or a resource with the same name already exists, the Sun Cluster Geographic Edition operations might modify their properties. Sun Cluster Geographic Edition software cannot create a new resource group or resource of the same name if one already exists.

The Configuration status is set to OK after successful validation. If validation is not successful, the Configuration status is set to Error.

How to Delete an Oracle Data Guard Protection Group

Before You Begin

To delete a protection group on all clusters, run the geopg delete command on each cluster where the protection group exists.

Before deleting a protection group, ensure that the following conditions are met:

• The protection group exists locally

• The protection group is offline on the local cluster

To keep the application resource groups online while deleting a protection group, remove the application resource groups from the protection group before deleting the protection group. You do not need to do anything to shadow RAC server proxy resource groups, as deleting the protection group removes these resource groups without affecting the RAC server proxy resource groups that they shadow.

1. Log in to a node in the cluster where you want to delete the protection group, for example, cluster-paris.

   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.

   cluster-paris is the primary cluster. See Example Sun Cluster Geographic Edition Cluster Configuration in Sun Cluster Geographic Edition System Administration Guide for a sample cluster configuration.

2. Delete the protection group.

   phys-node-n# geopg delete protectiongroupname

   This command deletes the configuration of the protection group from the local cluster. The command also removes the Oracle RAC server proxy resource groups and the replication resource group for the Oracle Data Guard Broker configuration in the protection group.

   If the protection group is not deleted, the Configuration status is set to Error. Resolve the error and rerun the geopg delete command.

Example 2–3 Deleting a Protection Group

This example shows how to delete a protection group from both partner clusters.

# rlogin cluster-paris -l root
phys-paris-1# geopg delete sales-pg
# rlogin cluster-newyork -l root
phys-newyork-1# geopg delete sales-pg

Example 2–4 Deleting a Protection Group While Keeping Application Resource Groups Online

This example shows how to keep two application resource groups, apprg1 and apprg2, online, while deleting the protection group that they share, sales-pg.

Remove the application resource groups from the protection group and delete the protection group.

phys-paris-1# geopg remove-resource-group apprg1,apprg2 sales-pg
phys-paris-1# geopg stop -e global sales-pg
phys-paris-1# geopg delete sales-pg

Unlike other data replication modules, the Oracle RAC server proxy resource group is not added to the protection group. Instead, a shadow RAC server proxy resource group is added to represent this resource group. You can add and remove the shadow RAC server proxy resource group to and from the protection group at any time without affecting the Oracle Data Guard data replication.

Consequently, the application resource groups that are shown in this example can have no data to replicate, as only Oracle Data Guard data replication is supported in this particular protection group. Application resource groups that might meet this criteria can be scalable web servers, where their data is static or held on some remote storage that is not controlled by this cluster.

Administering Oracle Data Guard Application Resource Groups

To make an application highly available, you must ensure that the application is managed as a resource in an application resource group. Unlike other data replication modules, the Oracle RAC server proxy resource group is not added to the protection group. Instead, a shadow RAC server proxy resource group is added to represent this resource group.

You can add and remove the Oracle shadow RAC server proxy resource group to and from the protection group at any time without affecting the Oracle Data Guard data replication. This fact does not prevent you from adding other, non-RAC server proxy resource groups to the protection group if necessary. However, these applications cannot use any data that requires replication to the standby cluster as only Oracle Data Guard is supported in this type of protection group.

You need to replicate, on the standby cluster, all entities that you configure for the primary cluster's application resource group. Examples of entities that you need to replicate are application data resources, configuration files, and resource groups. Resource group names must also match on both clusters. In addition, the data that the application resource uses needs to be replicated on the standby cluster.

This section shows you how to perform the following procedures:

• How to Add an Application Resource Group to an Oracle Data Guard Protection Group

• How to Delete an Application Resource Group From an Oracle Data Guard Protection Group

How to Add an Application Resource Group to an Oracle Data Guard Protection Group

Before You Begin

You can add an existing resource group, other than an Oracle RAC server proxy resource group containing an Oracle RAC server proxy resource, to the list of application resource groups for a protection group. If you do try to add an Oracle RAC server proxy resource group, the geopg command returns an error.

Before you add an application resource group (of any other type) to a protection group, ensure that the following conditions are met:

• The protection group is defined.

• The application resource group does not need any data replicating. You are not prevented from adding such resource groups, but the Oracle Data Guard module does not coordinate the switchover of other types of data replication.

• The resource group to add already exists on both clusters and is in an appropriate state.

• The Auto_start_on_new_cluster property of the resource group is set to False. You can determine the setting of this property by using the clresourcegroup show command.

  phys-node-n# clresourcegroup show -p auto_start_on_new_cluster apprg

  Set the Auto_start_on_new_cluster property to False as follows:

  phys-node-n# clresourcegroup set -p Auto_start_on_new_cluster=False apprg1

  Setting the Auto_start_on_new_cluster property to False prevents the Sun Cluster resource group manager from automatically starting the resource groups in the protection group.

  When the protection group is activated, application resource groups need to be online only on the primary cluster.

  The application resource group does not have dependencies on resource groups and resources outside of this protection group unless the External_Dependency_Allowed protection group property is set to TRUE. To add several application resource groups that share dependencies while the External_Dependency_Allowed protection group property is set to FALSE, you need to add all the application resource groups that share dependencies to the protection group in a single operation. If you add the application resource groups separately, the operation fails.

The protection group can be activated or deactivated, and the resource group can be either Online or Unmanaged.

If the resource group is Unmanaged and the protection group is activated after the configuration of the protection group has changed, the local state of the protection group becomes Error.

If the resource group to add is Online and the protection group is deactivated, the request is rejected. Before you add an online resource group, you need to activate the protection group.

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 application resource group to the protection group.

   phys-node-n# geopg add-resource-group resourcegrouplist protectiongroup

   resourcegrouplist

   Specifies the name of the application resource group. You can specify more than one resource group in a comma-separated list.

   protectiongroup

   Specifies the name of the protection group.

   This command adds an application resource group to a protection group on the local cluster. If the partner cluster contains a protection group of the same name, the command then propagates the new configuration information to the partner cluster.

   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.

   If the add operation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration is added and its status is set to OK on the local cluster.

   If the Configuration status is set to OK on the local cluster, but the add operation is unsuccessful on the partner cluster, the Configuration is added on the partner cluster and the configuration status is set to Error on the partner cluster.

   After the application resource group is added to the protection group, the application resource group is managed as an entity of the protection group. Then, the application resource group is affected by protection group operations such as start, stop, switchover, and takeover.

Example 2–5 Adding an Application Resource Group to an Oracle Data Guard Protection Group

This example shows how to add two application resource groups, apprg1 and apprg2, to sales-pg.

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

How to Delete an Application Resource Group From an Oracle Data Guard Protection Group

You can remove an application resource group from a protection group without altering the state or contents of the application resource group. You can remove Oracle shadow RAC server proxy resource groups at any time, without affecting the Oracle RAC server proxy resource groups or Oracle RAC databases that they represent. You can remove these resource groups because the shadow RAC server proxy resource groups simply reflect the status of the real Oracle RAC server proxy resource groups and do not control the Oracle RAC databases.

Before You Begin

Ensure that the following conditions are met:

• The protection group is defined on the local cluster.

• The resource group to remove is part of the application resource groups of the protection group. For example, you cannot remove a resource group that belongs to the data replication management entity.

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, seeSun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.

2. Remove the application resource group from the protection group.

   phys-node-n# geopg remove-resource-group resourcegrouplist protectiongroup

   resourcegrouplist

   Specifies the name of the application resource group.

   You can specify more than one resource group in a comma-separated list.

   protectiongroup

   Specifies the name of the protection group.

   This command removes an application resource group from a protection group on the local cluster. If the partner cluster contains a protection group of the same name, the application resource group is also removed from the protection group of the partner cluster.

   If the resource group that is being removed shares dependencies with other resource groups in the protection group and the External_Dependency_Allowed protection group property is set to FALSE, you also need to remove all other resource groups that share dependencies with the resource group that is being removed.

   If the remove operation fails on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration is removed and its status is set to OK on the local cluster.

   If the Configuration status is set to OK on the local cluster, but the remove operation is unsuccessful on the partner cluster, the Configuration is removed from the partner cluster and the configuration status is set to Error on the partner cluster.

Example 2–6 Deleting an Application Resource Group From a Protection Group

This example shows how to remove two application resource groups, apprg1 and apprg2, from sales-pg.

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

Administering Oracle Data Guard Broker Configurations

The following procedures describe how to administer Oracle Data Guard Broker data replication configurations in an Oracle Data Guard protection group.

• How to Add an Oracle Data Guard Broker Configuration to an Oracle Data Guard Protection Group

• How the Data Replication Subsystem Verifies the Oracle Data Guard Broker Configuration

• How to Modify an Oracle Data Guard Broker Configuration

• How to Delete an Oracle Data Guard Broker Configuration From an Oracle Data Guard Protection Group

For details about configuring an Oracle Data Guard protection group, see How to Create and Configure an Oracle Data Guard Protection Group.

How 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:

• 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 local cluster and the partner cluster.

• The Oracle RAC server proxy resource group and Oracle RAC server proxy resources that manage the Oracle RAC databases that are replicated by Oracle Data Guard exist on both the local and the partner cluster.

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

How the Data Replication Subsystem Verifies the Oracle Data Guard Broker Configuration

When you add an Oracle Data Guard Broker configuration to a protection group, the data replication layer verifies that the Oracle Data Guard Broker configuration exists.

When you run the geopg add-replication-component command, if they do not already exist, an Oracle shadow RAC server proxy resource group and a replication resource group for the Oracle Data Guard Broker configuration are created. In addition, the configuration is successfully validated.

The Oracle shadow RAC server proxy resource group contains a Sun Cluster resource. This resource is based on the generic data service SUNW.gds resource type. The Oracle shadow RAC server proxy resource shadows the real Oracle RAC server proxy resource that manages and monitors the Oracle RAC database in the Oracle Data Guard Broker configuration.

For more information about the shadow RAC server proxy resource group, see Oracle Data Guard Shadow Resource Groups.

The replication resource group contains a Sun Cluster resource that is based on the generic data service SUNW.gds resource type. The replication resource monitors the state of the database replication as reported by Oracle Data Guard Broker.

For more information about replication resources, see Oracle Data Guard Replication Resource Groups.

For the validation to be successful, ensure that the following conditions are met:

• 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. This resource is used to determine the values for ${ORACLE_HOME} and the local Oracle RAC SID values.

• The Oracle dgmgrl command shows a SUCCESS status for the Oracle Data Guard Broker configuration. The presence of Oracle ORA- messages in the output from the dgmgrl command might indicate that the sysdba_username password is incorrect or that the cluster has been disabled. Oracle errors are returned as part of the messages that are generated by the validate command.

• The sysdba_username password is valid for the standby cluster to ensure that switchovers are possible.

• The Oracle Data Guard Broker configuration details match those 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 cluster), the replication mode, and the standby type.

Do not use Sun Cluster commands to change, remove, or bring offline these resources or resource groups. Use only Sun Cluster Geographic Edition commands to administer shadow RAC server proxy resource groups, replication resource groups, and resources that are internal entities that are managed by Sun Cluster Geographic Edition software. Altering the configuration or state of these entities directly with Sun Cluster commands could result in an unrecoverable failure.

How to Modify an Oracle Data Guard Broker Configuration

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. Modify the Oracle Data Guard Broker configuration.

   This command modifies the properties of an Oracle Data Guard Broker configuration in a protection group on the local cluster. The command then propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.

   phys-node-n# geopg modify-replication-component -p property \ [-p…] ODGConfigurationName protectiongroupname

   -p property

   Specifies the properties of the data replication Oracle Data Guard Broker configuration.

   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 Oracle Data Guard Broker configuration.

   protectiongroupname

   Specifies the name of the protection group that contains the Oracle Data Guard Broker configuration.

How to Delete an Oracle Data Guard Broker Configuration From an Oracle Data Guard Protection Group

Before You Begin

Before you remove an Oracle Data Guard Broker configuration from 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 is managed by the protection group.

For information about deleting protection groups, refer to How to Delete an Oracle Data Guard Protection Group.

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. Remove the Oracle Data Guard Broker configuration.

   This command removes an Oracle Data Guard Broker configuration from a protection group on the local cluster. The command then propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.

   This command removes the Oracle Data Guard Broker configuration from the protection group. This command also deletes the Oracle shadow RAC server proxy resource group and replication resource group for this Oracle Data Guard Broker configuration.

   phys-node-n# geopg remove-replication-component ODGConfigurationName protectiongroupname

   ODGConfigurationName

   Specifies the name of the Oracle Data Guard Broker configuration.

   protectiongroupname

   Specifies the name of the protection group.

Example 2–8 Deleting an Oracle Data Guard Broker Configuration From an Oracle Data Guard Protection Group

This example shows how to delete an Oracle Data Guard Broker configuration from an Oracle Data Guard protection group.

phys-paris-1# geopg remove-replication-component mysales.com sales-pg

Replicating the Oracle Data Guard Protection Group Configuration to a Partner Cluster

You can replicate the configuration of a protection group to the partner cluster either before or after you configure data replication, resource groups, and resources on both clusters.

How to Replicate the Oracle Data Guard Protection Group Configuration to a Partner Cluster

Before You Begin

Before you replicate the configuration of an Oracle Data Guard protection group to a partner cluster, ensure that the following conditions are met:

• The protection group is defined on the remote cluster, not on the local cluster.

• The Oracle Data Guard Broker configuration in the protection group on the remote cluster exists on the local cluster.

• The application resource groups in the protection group on the remote cluster exist on the local cluster.

• The Auto_start_on_new_cluster property of the resource groups is set to False. You can view this property by using the clresourcegroup show command.

  phys-node-n# clresourcegroup show -p Auto_start_on_new_cluster apprg

  Set the Auto_start_on_new_cluster property to False as follows:

  phys-node-n# clresourcegroup set -y Auto_start_on_new_cluster=False apprg1

  Setting the Auto_start_on_new_cluster property to False prevents the Sun Cluster resource group manager from automatically starting the resource groups in the protection group. The Sun Cluster Geographic Edition software restarts and communicates with the remote cluster to ensure that it is running and that it is the standby cluster for that resource group. The Sun Cluster Geographic Edition software does not automatically start the resource group on the primary cluster.

  When the protection group is activated, application resource groups need to be online only on the primary cluster.

• You have not added the shadow RAC server proxy resource group for an Oracle Data Guard Broker configuration to a protection group application resource group list before that resource group exists on all clusters.

  ---

  Note –

  You must replicate the protection group configuration to a partner cluster before you can add a shadow RAC server proxy resource group to a protection group.

  ---

  When you successfully add the Oracle Data Guard configuration to the protection group on the clusters on which the protection group exists, Oracle Data Guard creates the shadow RAC server proxy resource group on the clusters. The means by which you can successfully add a shadow RAC server proxy resource group to a protection group include the following:

  If an Oracle Data Guard protection group does not contain an Oracle Data Guard Broker configuration, once you replicate the protection group on the partner cluster and add the Oracle Data Guard Broker configuration to it, Oracle Data Guard adds the shadow RAC server proxy resource group on both clusters.

  If an Oracle Data Guard protection group contains an Oracle Data Guard Broker configuration, does not contain a shadow RAC server proxy resource group on one cluster, and is not replicated on the partner cluster, when you replicate the protection group to the partner cluster, Oracle Data Guard creates the shadow RAC server proxy resource group on the partner cluster.

  Once a shadow RAC server proxy resource group exists on both clusters, you can add that resource group to the protection group.

1. Log in to phys-newyork-1.

   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. Replicate the protection group configuration to the partner cluster.

   phys-newyork-1# geopg get -s partnershipname ODGprotectiongroup

   -s partnershipname

   Specifies the name of the partnership from which the protection group configuration information is gathered.

   ODGprotectiongroup

   Specifies the name of the protection group.

   The geopg get command retrieves the configuration information of the protection group from the remote cluster and creates the protection group on the local cluster.

   ---

   Note –

   The geopg get command replicates Sun Cluster Geographic Edition related entities. For information about how to replicate Sun Cluster entities, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

   ---

Example 2–9 Replicating the Oracle Data Guard Protection Group Configuration to a Partner Cluster

This example shows how to replicate the configuration of sales-pg to cluster-newyork.

# rlogin phys-newyork-1 -l root
phys-newyork-1# geopg get -s paris-newyork-ps sales-pg

The configuration of the protection group is retrieved from the remote cluster, in this example cluster-paris, and then validated by the data replication subsystem on the local cluster cluster-newyork.

• If the validation is successful, the Configuration status is set to OK and the protection group is created on the local cluster.

• If the validation fails, the protection group is not created on the local cluster. Resolve the error and replicate the protection group again.

Activating and Deactivating a Protection Group

This section describes how to perform the following procedures:

• How to Activate an Oracle Data Guard Protection Group

• How to Deactivate an Oracle Data Guard Protection Group

When you activate a protection group, it assumes the role that you assigned to it during configuration.

For more information about configuring protection groups, see How to Create and Configure an Oracle Data Guard Protection Group.

How to Activate an Oracle Data Guard Protection Group

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.

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

   -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 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_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.

   ODGprotectiongroup

   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.

Example 2–10 Globally Activating 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

Example 2–11 Activating an Oracle Data Guard Protection Group Locally

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.

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

Resynchronizing an Oracle Data Guard Protection Group

You can resynchronize the configuration information of the local protection group with the configuration information that you retrieve from the partner cluster. The cluster on which you run the command to resynchronize forfeits its own protection group configuration of the partner cluster. To determine if you need to resynchronize a protection group, you use the geoadm status command. If the value of the Synchronization parameter for a protection group is listed as Error, you need to resynchronize the protection group.

For example, you might need to resynchronize protection groups after booting the cluster. For more information, see Booting a Cluster in Sun Cluster Geographic Edition System Administration Guide.

Resynchronizing a protection group updates only entities that are related to Sun Cluster Geographic Edition. For information about how to update Sun Cluster entities, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

How to Resynchronize an Oracle Data Guard Protection Group

Before You Begin

You need to deactivate the protection group on the cluster where you run the geopg update command.

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. Resynchronize the protection group.

   phys-node-n# geopg update protectiongroupname

Example 2–16 Resynchronizing an Oracle Data Guard Protection Group

This example shows how to resynchronize a protection group.

phys-paris-1# geopg update sales-pg

Checking the Runtime Status of Oracle Data Guard Data Replication

You can obtain an overall view of the status of replication, as well as a more detailed runtime status of the Oracle Data Guard software from the status of the replication resource groups. The following sections describe how to check the runtime status of replication:

• Displaying an Oracle Data Guard Runtime Status Overview

• Displaying a Detailed Oracle Data Guard Runtime Status

Displaying an Oracle Data Guard Runtime Status Overview

The status of each Oracle Data Guard data replication resource indicates the status of replication on a particular Oracle Data Guard Broker configuration. The status of all the resources under a protection group are aggregated in the replication status.

To view the overall status of replication, look at the protection group state, as described in the following procedure.

How to Check the Overall Runtime Status of Replication

1. Log in to a node of a cluster where the protection group is defined.

   To complete this step, you need to be assigned the Basic Solaris User 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. Check the runtime status of replication.

   phys-paris-1# geoadm status

   Refer to the Protection Group section of the output for replication information. The output of this command includes the following information:

   • Whether the local cluster is enabled for partnership participation

   • Whether the local cluster is involved in a partnership

   • Status of the heartbeat configuration

   • Status of the defined protection groups

   • Status of current transactions

3. Check the runtime status of data replication for each Oracle Data Guard protection group.

   phys-paris-1 clresource status -v ODGConfigurationName-odg-rep-rs

   Refer to the Status and StatusMessage fields that are presented for the Oracle Data Guard Broker configuration data replications that you want to check. For more information about these fields, see Table 2–1.

Displaying a Detailed Oracle Data Guard Runtime Status

One replication resource group exists for each protection group. The name of the replication resource group conforms to the following format:

ODGprotectiongroupname-odg-rep-rg

If you add an Oracle Data Guard Broker configuration to a protection group, the Sun Cluster Geographic Edition software creates a resource for that configuration. This resource monitors and displays the status of replication for the Oracle Data Guard Broker configuration. The name of each resource conforms to the following format:

ODGConfigurationName-odg-rep-rs

You can monitor the state of the replication resource to give you the overall status of replication. Use the clresource status command as follows to obtain the State and Status Message values for the replication status of the Oracle Data Guard Broker configuration:

phys-node-n# clresource status -v ODGConfigurationName-odg-rep-rs

The State is Online while the resource is online.

The following table describes the Status and Status Message values that are returned by the clresource status command when the State of the Oracle Data Guard replication resource group is Online.

For more information about the clresource command, see the clresource(1CL) man page.