Go to main content

Oracle® Solaris Cluster Geographic Edition Data Replication Guide for Oracle GoldenGate

Exit Print View

Updated: September 2015
 
 

How to Perform a Failback-Switchover on a System That Uses Oracle GoldenGate Replication

Use this procedure to restart an application on the original primary cluster, paris, after the data on this cluster has been resynchronized with the data on the current primary cluster, newyork.


Note -  You can also accomplish Step 6 and Step 8 by using the browser interface. Click Partnerships, click the partnership name, and highlight the protection group name. Click Update Protection Group and when the update is completed click Start Protection Group. For more information about Oracle Solaris Cluster Manager, see Chapter 13, Using the Oracle Solaris Cluster Manager Browser Interface, in Oracle Solaris Cluster 4.3 System Administration Guide .
  1. Log in to a node on the original primary cluster.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide .

  2. Check the status of the original primary cluster to ensure that it is running and has the status Deactivated.
    # geoadm status
  3. Ensure that the Oracle GoldenGate resource and the underlying database have the status online on the original primary cluster.
    # clresource status
  4. Start the extracts and replicats.
    GGSCI (node)> start extract name
    GGSCI (node)> start replicat name
  5. Verify that the extracts and replicats are running.
    GGSCI (node)> info all

    If the extract or the replicats are not running, fix the root cause, and retry the operation. As a last resort, you can take a backup from the current primary cluster and perform a fresh Oracle GoldenGate setup.

    Connect to a node of the original primary cluster and update the protection group to change the role from a deactivated primary cluster to a secondary cluster.

  6. Resynchronize the protection group.
    # geopg update protection-group
  7. From one node in each cluster, validate the configuration locally for each protection group.

    Note -  Ensure that the protection group is not in an Error state. You cannot start a protection group when it is in an Error state.
    # geopg validate protection-group

    For more information, see How to Validate an Oracle Data Guard Protection Group in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Oracle Data Guard .

  8. From one node of either cluster, start the protection group globally.
    # geopg start -e global protection-group
  9. (Optional) From one node of either cluster, perform a protection group switchover to make the original primary the current primary.
    # geopg switchover -m cluster-paris protection-group