Planning the HA for Oracle GoldenGate Installation and Configuration
This section contains the information that you need to plan your HA for Oracle GoldenGate installation and configuration.
Note - Before you begin, consult your Oracle GoldenGate documentation for configuration restrictions and requirements that are not stated in the Oracle Solaris Cluster documentation or imposed by the Oracle Solaris Cluster software.
Note - HA for Oracle GoldenGate can be configured to run in either a global zone or a zone cluster.
Configuration Restrictions
 | Caution - Your data service configuration might not be supported if you do not observe these restrictions. |
For restrictions that apply to all data services, see the release notes for your release of Oracle Solaris Cluster. The following configuration restriction applies only to HA for Oracle GoldenGate.
The Oracle GoldenGate resource must be co-located with the database resource. To achieve this in a failover configuration, you can always place them in the same resource group. If you do not want the resources in the same resource group, define strong positive affinities or strong positive affinities with failover delegation between the resource groups.
Ensure that the Oracle GoldenGate user login process is not interactive. For example, the su - gg-user command must not require any additional inputs from the user.
Configuration Requirements
| Caution - Configuration requirements represent actions that you must perform. If your data service configuration does not satisfy these requirements, the data service configuration might not be supported. |
For requirements that apply to all data services, see Configuration Guidelines for Oracle Solaris Cluster Data Services in Planning and Administering Data Services for Oracle Solaris Cluster 4.4.
The following configuration requirements apply only to HA for Oracle GoldenGate.
The Oracle GoldenGate manager must be configured to restart abended extract and replicat processes.
Replications between clusters or within a cluster must be started by the HA for Oracle GoldenGate.
The PATH variable that is set in the Oracle GoldenGate user environment must not contain paths from the NFS servers. If the NFS servers hang for some reason, then it can cause availability issues for HA for Oracle GoldenGate.
The resource default failover mode implies that an Oracle GoldenGate resource can trigger a failover of the resource group. This default mode will disrupt the client access to the underlying database. If this behavior is not acceptable, configure the Failover_mode property to restart_only or log_only.
Note - The criteria to pick a desired behavior depends on the importance of the underlying database. If undisrupted client access to the underlying database is more important than undisrupted replication, change the Failover_mode of the Oracle GoldenGate resource.
Supported Data Service Configurations
HA for Oracle GoldenGate supports configurations that conform to the requirements that are specified in the previous section.
All configurations of HA for Oracle GoldenGate have the following requirements:
The Oracle GoldenGate instance is configured as a failover resource.
The Oracle GoldenGate instance is configured as a multiple master resource.
Since Oracle GoldenGate does not have any other client access besides the administrative one, it is not practical to have a scalable configuration.
Configuration Considerations
The following configuration considerations affect the installation and configuration of HA for Oracle GoldenGate.
In failover configurations, the binaries of the Oracle GoldenGate software can reside on local storage. The configuration data and the trail files must reside on shared storage.
See Configuration Guidelines for Oracle Solaris Cluster Data Services in Planning and Administering Data Services for Oracle Solaris Cluster 4.4. This section details the advantages and disadvantages of placing the Oracle GoldenGate binaries on the local file system or on the cluster file system.
In failover configurations, you need at least one corresponding Oracle GoldenGate instance. The second instance can be configured outside of a cluster, although it is highly recommended to make it highly available as well. If you plan to make the other instance highly available also, you will need to repeat the instructions in this guide.
In multiple master configurations, the complete Oracle GoldenGate software including the configuration data and the trail files can reside in the local storage.
Configuration Planning Questions
Use the questions in this section to plan the installation and configuration of HA for Oracle GoldenGate.
Will you run the Oracle GoldenGate instance as a failover resource or as a multiple master resource?
What is the logical hostname in a failover configuration for the corresponding Oracle GoldenGate instances that will access the data service?
Where will the Oracle GoldenGate configuration files reside?
See Configuration Guidelines for Oracle Solaris Cluster Data Services in Planning and Administering Data Services for Oracle Solaris Cluster 4.4 for the advantages and disadvantages of placing the Oracle GoldenGate binaries on the local file system or on the cluster file system.