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-Takeover on a System That Uses Oracle GoldenGate Replication

Use this procedure to restart an application on the original primary cluster and use the current data on the original primary cluster. Any updates that occurred on the secondary cluster while it was acting as primary are discarded.


Note -  This procedure asumes that the original primary cluster was down at the time of the takeover from the original secondary and that the original secondary cluster remains down.
  1. Check the status of the original primary cluster on a node of the current primary cluster to ensure that it is down.
    # geoadm status
  2. Before you boot the original primary cluster, stop the protection group on the current primary cluster.
    # geopg stop -e local protection-group
  3. Disable the database and the Oracle GoldenGate resource on the current primary cluster.
    # clresource disable GoldenGate-resource
    # clresource disable Database-resource
  4. Boot the original primary cluster.
  5. Disable the database and the Oracle GoldenGate resource on the original primary cluster.
    # clresource disable Goldengate-resource
    # clresource disable Database-resource
  6. Take an offline backup of the original primary and redeploy it on the current primary cluster.
  7. Enable the database and the Oracle GoldenGate resource on both the clusters.
    # clresource enable Goldengate-resource
    # clresource enable Database-resource
  8. Re-deploy the Oracle GoldenGate configuration.
    1. Delete the Oracle GoldenGate groups.
    2. Delete the remaining trail files.
    3. Redeploy the Oracle GoldenGate groups on both the clusters.

    Make sure that all relevant groups are up and running after you start them.

  9. Re-synchronize the protection group.

    Run the following command from the original primary cluster.

    # geopg update protection-group
  10. 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 .

  11. Check the status of the configuration on one node.
    # geoadm status
  12. Start the protection group globally.
    # geopg start -e global protection-group
  13. (Optional) Perform a switchover.
    # geopg switchover -e global protection-group