Oracle® Solaris Cluster Data Service for Oracle GoldenGate Guide

Exit Print View

Updated: July 2014, E48593-01
 
 

How to Verify the Operation of the Fault Monitor for the GoldenGate Process

Perform this procedure on each set of two nodes where the Oracle GoldenGate process can run.

  1. Assume the root role on a cluster node.
  2. Ensure that the resource group hosting the Oracle GoldenGate resource is offline on all nodes.
  3. Bring online the resource group to which the Oracle GoldenGate belongs.
    # clresourcegroup online -n node db-rg
    -n node

    Specifies the name of the node on which the resource group is to be brought online. This node is the node that you have just logged in to.

    db-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the Oracle GoldenGate resource belongs.

  4. Terminate the Oracle GoldenGate process.
    # su - ggowner -c "echo 'stop er *' | basepath/ggsci"
    # su - ggowner -c "echo 'stop mgr \!' | basepath/ggsci"
  5. Kill all remaining Oracle GoldenGate processes.
  6. Confirm that the Oracle GoldenGate process gets restarted.

    Run the clresource status command to confirm that the Oracle GoldenGate resource is online on the first node or zone.

  7. Failover the resource group hosting the Oracle GoldenGate instance to another node if the resource group is configured as a failover resource group. If the resource group is configured as a multiple master resource group, skip this step.
    # clresourcegroup switch -n node db-rg
    -n node

    Specifies the name of the node or the zone on which the resource group is to be brought online.

    db-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the Oracle GoldenGate resource belongs.