Go to main content

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

Exit Print View

Updated: September 2015
 
 

How to Create and Configure an Oracle GoldenGate Protection Group

Before You Begin

Ensure that the following conditions are met:

  • The local cluster is a member of a partnership.

  • The protection group you are creating does not already exist.

  • All extracts and replicats that form the active-active topology have the status RUNNING on both clusters. Using the ggsci utility and as an Oracle GoldenGate user, do the following:

    $ ggsci 
    GGSCI (nodename) > info all 
    GGSCI (nodename) > start er * 

    Note -  The start er * command might not be appropriate for all configurations.
  • Oracle GoldenGate resources and resource groups must exist on the primary and the secondary cluster.

  • The application resource groups must exist on the primary and the secondary 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 .

  1. Log in to a cluster node of the primary cluster.
  2. Copy the goldengate_geo_config file to a different location.

    For example:

    phys-paris-1# cp /opt/ORCLscGoldenGate/geocontrol/util/goldengate_geo_config /var/tmp/geo
  3. Specify the following variables in /var/tmp/geo/goldengate_geo_config.

    This list uses sample values.

    PS=goldengate-ps
    PG=goldengate-pg
    REPCOMP=goldengate.sbp
    REPRS=goldengate-rep-rs
    REPRG=goldengate-rep-rg
    DESC="goldengate replication pg"
    CONFIGFILE=/geo-config/geo-gg-config
    REALGGRG=paris-rg,newyork-rg
    REALGGRS=paris-gg-rs,newyork-gg-rs
    GGGROUPS=paris:mysqlex1,paris:mysqlre2,newyork:mysqlex2,newyork:mysqlre1
    APPRG=usa-rg
    PINGTIME=
    
  4. Create the script-based plug-in configuration file on all nodes of all clusters.

    Assuming that the nodes of the primary cluster, cluster-paris, are phys-paris-1 and phys-paris-2, on each node of cluster-paris, you would issue the following commands:

    phys-paris-1# mkdir /geo-config
    phys-paris-1# echo "goldengate.sbp|any|phys-paris-1,phys-paris-2" \
    > /geo-config/geo-gg-config

    Assuming that the nodes of the secondary cluster, cluster-newyork, are phys-newyork-1 and phys-newyork-2, on each node of cluster-newyork, you would issue the following commands:

    phys-newyork-1# mkdir /geo-config
    phys-newyork-1# echo "goldengate.sbp|any|phys-newyork-1,phys-newyork-2" \
    > /geo-config/geo-gg-config
  5. Execute the goldengate_geo_register script on the primary cluster.

    For example:

    phys-paris-1# ksh /opt/ORCLscGoldenGate/geocontrol/util/goldengate_geo_register \
    -f /var/tmp/geo/goldengate_geo_config
  6. Replicate the protection group to the partner cluster.

    Note -  You can also accomplish this step by using the Oracle Solaris Cluster Manager GUI. Click Partnerships, click the partnership name, highlight the protection group name, and click Get Protection Groups. 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 .

    The final messages of the registration script outline the required geopg get command. You must log in to one node of the partner cluster and execute that exact command. For example:

    phys-newyork-1# geopg get -s goldengate-ps goldengate-pg