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 Oracle Solaris Cluster Geographic Edition System Administration Guide.

How to Resynchronize an Oracle Data Guard Protection Group

Before You Begin

Ensure that you have deactivated the protection group on the cluster where you run the geopg update command.

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

   For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   ---

   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.

   ---

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