Planning an Oracle GoldenGate Protection Group
An Oracle GoldenGate resource group can belong to only one protection group.
The Oracle GoldenGate geographic replication was developed with the script-based plug-in module
of Geographic Edition, so it must comply with all rules of the script-based plug-in. For each
protection group, you must provide a script-based plug-in configuration file on each
node. In addition, the Oracle GoldenGate geographic replication brings in its own configuration
file, which is needed only at registration.
The Oracle GoldenGate geographic replication creation is an automated process that takes the
Oracle GoldenGate geographic configuration file as input and performs the necessary actions. The
essential content of this file consists of the following
key=value pairs.
Key
|
Explanation of Value
|
PS
|
Name of the partnership.
|
PG
|
Name of the protection group to create.
|
REPCOMP
|
Name of the replication component to create in this protection
group.
|
REPRS
|
Name of the replication resource.
|
REPRG
|
Name of the replication resource group.
|
DESC
|
Description for the protection group.
|
CONFIGFILE
|
Absolute path for the script-based plug-in configuration
file.
|
APPRG
|
Name of the application resource group.
|
REALGGRG
|
Resource group names that contain the Oracle GoldenGate resource on the
clusters. If the resource group names on the clusters differ,
provide a comma-separated list.
|
REALGGRS
|
Resource names configured as the Oracle GoldenGate resources. If the
resource names on the clusters differ, provide a comma-separated
list.
|
GGGROUPS
|
List of Oracle GoldenGate extracts or replicats forming the
replication between the databases. The format for one group is
clustername:group
name. For multiple groups, provide a
comma-separated list.
|
PINGTIME
|
Timeout for the extensive ping test. The
default is 60 seconds if this variable is unset. This timeout is
used at check_takeover where it must be verified
if the remote site is unavailable.
|
|
Note -
You must use the any keyword in the script-based plug-in
configuration file for Oracle GoldenGate.
Note -
The script-based plug-in configuration file must be in the same location on all
cluster nodes on the primary and the secondary cluster.