Oracle goldengate high availability using oracle.
Oracle golden gate configuration file.
Oracle goldengate creates parameter files in the default character set of the local operating system.
For more information see the reference for oracle goldengate and optional parameters for integrated modes for additional configuration considerations.
Oracle goldengate basic configuration.
Ensuring the availability of the checkpoint files is essential to ensure that after a failure occurs the extract process can continue.
Once the basic configuration has been tested new features can be added incrementally simplifying any troubleshooting.
If the network or the target system becomes unavailable extract could run out of memory and abend.
Using a clustered file system is fundamental to the continuing availability of oracle goldengate checkpoint and trail files in the event of a node failure.
Protection against network and target failures.
Oracle goldengate configuration best practices.
To avoid issues caused by character set incompatibilities.
The following procedure describes a minimal oracle golden gate configuration.
In the event that the local platform does not support a required character set as the default in the operating system you can use the charset parameter either globally or per process to specify a character set for parameter files.
If you are using an oracle goldengate data pump process release v11 1 1 or earlier to transfer the trail files from a source host on the database machine using dbfs this applies to the exadata database machine and to non exadata configurations see oracle goldengate best practices.
It is intended for research and or training purposes and is not intended to be a production configuration.