Oracle® Solaris Cluster Data Service for Oracle GoldenGate Guide

Exit Print View

Updated: July 2014, E48593-01
 
 

How to Enable the Oracle GoldenGate Instance to Run in a Cluster

The following resource group is created in this procedure.

  • Storage Resource group to contain the following resource:

    • Storage resource (required in the case of failover resource groups, but optional for multiple master resource groups)

  • Database resource group, to contain the following resources:

    • Database resource

    • GoldenGate resource

    • Logical hostname for the resources (required in the case of failover resource groups)


Note -  Depending on whether the file system that is managed by the storage resource is a global file system or a failover file system, you might need to add affinities between the database resource group and the storage resource group. You do have an option to combine the storage resource group and the database resource group into one resource group.

Before You Begin

Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.

  1. Assume the root role on a cluster node.
  2. Create the resource group for your storage topology.

    In failover topologies, Oracle GoldenGate requires shared storage, so you must make your storage highly available. For example, you can create a resource group containing the HAStoragePlus resource managing the global file systems.


    Note -  If you plan to create a failover file system, place the storage resource in the same resource group as the Oracle GoldenGate resource.
    # clresourcegroup create storage-rg
    storage-rg

    Specifies the name of the resource group to be created. Choose a unique name for each resource group within the cluster.

  3. Register the SUNW.HAStoragePlus resource type.
    # clresourcetype register SUNW.HAStoragePlus
  4. Create your storage resource.
    # clresource create -g storage-rg \
    -t SUNW.HAStoragePlus \
    -p filesystemmountpoints=mountpoint-list \
    hsp-rs
    	
    -g storage-rg

    Specifies that the resource is to be added to the Oracle GoldenGate storage resource group.

    -t SUNW.HAStoragePlus

    Specifies that the resource is an instance of the SUNW.HAStoragePlus resource type.

    -p filesystemmountpoints=mountpoint-list

    Specifies a list of valid mount points for the file system. For more information, see the SUNW.HAStoragePlus(5) man page.

    hsp-rs

    Specifies the name of the resource that you are creating.

    The resource is created in the enabled state.

  5. Bring online the storage resource group.
    # clresourcegroup online -M storage-rg
    -M

    Specifies that the resource group is to be brought into the managed state.

    storage-rg

    Specifies the name of the resource group to be brought online.

  6. Create a resource group for the database and the Oracle GoldenGate resource.

    The Oracle GoldenGate instance resource group can be configured as a failover or multiple master resource group to contain the resource for the database and the Oracle GoldenGate resource. If the Oracle GoldenGate instance is configured as a failover resource, the logical hostname for this resource is also contained in the Oracle GoldenGate resource group.

    • To create a failover resource group, run the following command:

      # clresourcegroup create db-rg
    • To create a multiple master resource group, run the following command:

      # clresourcegroup create \
      -p Maximum_primaries=value \
      -p Desired_primaries=value \
      db-rg
    -p Maximum_primaries=value

    Specifies the maximum number of primary nodes for this multiple master resource group.

    -p Desired_primaries=value

    Specifies the desired number of primary nodes for this multiple master resource group.

    db-rg

    Specifies the name of the resource group to be added. This name can be your choice but must be unique for the resource groups within the cluster.

  7. If the resource group that you created in Step 6 is configured as a failover resource group, add a logical hostname resource to the resource group.

    If the resource group that you created in Step 6 is configured as a multiple master resource group, skip this step.

    # clreslogicalhostname create -g db-rg db-logical-hostname
    -g db-rg

    Specifies the name of the resource group.

    db-logical-hostname

    Specifies the logical hostname db-logical-hostname of the Oracle GoldenGate resource. By default, the name of the logical host resource is set to the same name as this. If you wish to specify a separate name, then place the name of the resource at the end of the command listing.


    Note - If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.
  8. Bring online the Oracle GoldenGate resource group.
    # clresourcegroup online -M db-rg
    -M

    Specifies that the resource group is to be brought into the managed state.

    db-rg

    Specifies the name of the resource group that needs to be brought online.

  9. Install the database software.

    Install your database software and make the database highly available using an Oracle Solaris Cluster resource.


    Tip  -  One option is to place the database resource in the same resource group where you plan on creating the Oracle GoldenGate resource.

    The following is a list of several databases and a link to the corresponding documentation.

    If you have a specific agent associated with your database, then use the configuration procedure for the data service in your database.

  10. Install the Oracle GoldenGate software.

    Follow the instructions in the Oracle GoldenGate installation manual to install the Oracle GoldenGate software. You will also need to configure the replication between the different Oracle GoldenGate instances.


    Note -  For failover configurations, ensure that you replicate every user and group to all the servers on which you plan to run Oracle GoldenGate.