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 database-server resource group is not added to the protection group. Instead, a shadow Oracle database-server resource group is added to represent this resource group.
You can add and remove the shadow Oracle database-server 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-Oracle database-server 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.
Before You Begin
You can add an existing resource group, other than an Oracle database-server resource group containing an Oracle database-server resource, to the list of application resource groups for a protection group. If you do try to add an Oracle database-server 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.
For more information about RBAC, see Securing Geographic Edition Software in Oracle Solaris Cluster 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 RBAC rights profile and Oracle Data Guard.
# clresourcegroup show -p Auto_start_on_new_cluster resource-group
If necessary, change the property value to False.
# clresourcegroup set -p Auto_start_on_new_cluster=False resource-group
# geopg list protection-group | grep -i external_dependencies_allowed
If necessary, change the property value to True.
# geopg set-prop -p External_dependencies_allowed=TRUE protection-group
If the protection group is offline, the application resource group must also be offline before it can successfully be added to the protection group.
# clresourcegroup offline resource-group
phys-node-n# geopg add-resource-group resource-group-list protection-group
Specifies the name of the application resource group. You can specify more than one resource group in a comma-separated list.
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 Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities, in Oracle Solaris 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.
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