Go to main content

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

Exit Print View

Updated: September 2015
 
 

Overview of Oracle GoldenGate Replication

This section provides an overview of the Oracle GoldenGate replication resource groups. A protection group that secures Oracle GoldenGate with Oracle GoldenGate replication consists of the following two resource groups securing a third resource group that is not part of the protection group on each cluster:

The Oracle GoldenGate resource group holding Oracle GoldenGate is the foundation underneath the protection group. Hence, strong positive affinities with failover delegation must exist from the Oracle GoldenGate replication resource groups in the protection group and the Oracle GoldenGate resource group.

Using Oracle GoldenGate for replication allows the databases to be writable on both sides.

Oracle GoldenGate Resource Groups

The Oracle GoldenGate resource group typically contains the following resources:

  • Storage resource, which makes the storage for the database and Oracle GoldenGate highly available

  • Logical host resource, which provides the address to connect with the Oracle GoldenGate replication

  • HA for Oracle GoldenGate resource, requires the logical host resource and the storage resource to make Oracle GoldenGate highly available locally

  • Database resource, which protects the database to be replicated with Oracle GoldenGate

The resource group hosting the Oracle GoldenGate resource must contain a logical host resource which provides the address to connect to a replication target. The logical host in the database or in the Oracle GoldenGate resource group is the replication target for Oracle GoldenGate to replicate between the clusters. Hence, if you want to replicate between two clusters, you need to have a logical host to make the Oracle GoldenGate daemons accessible in case of a failover of the resource group containing Oracle GoldenGate and the database. The logical host can be used for communication between the application and the database as well.

On single-node clusters, the storage resource can be omitted, if for instance you use the root file system for storage. The creation of the database resource group and its resources is the topic of Oracle Solaris Cluster Data Service for Oracle GoldenGate Guide .

The database resource group and its objects can have different names across the clusters.

Oracle GoldenGate Replication Resource Groups

The Oracle GoldenGate replication resource group contains the Oracle GoldenGate replication resource. This resource does not start or stop any process. Its only purpose is to monitor the status of the Oracle GoldenGate replication.

Application Resource Groups

Depending on the application configuration and the underlying database, the application resource group can contain a logical host, with or without the application resources.

Since the application resource group and the database or the Oracle GoldenGate resource group need not be co-located, you will need two logical hosts - one in the application resource group and the other in the database or the Oracle GoldenGate resource group.

If you do not plan to include a real application in the application resource group, but plan to leave it with the logical host only for accessing the database, then there must be a strong positive affinity between the application resource group and the database resource group. The database connectivity features determine whether you need the logical host to connect to the database or not.

If the application resides on a replicated storage, you must configure a separate protection group containing this storage replication and the application.


Note -  The application resource cannot be in the Oracle GoldenGate resource group.