Ensuring the availability of the checkpoint files is essential to ensure that after a failure occurs the extract process can continue.
Oracle golden gate configuration file.
Protection against network and target failures.
The following procedure describes a minimal oracle golden gate configuration.
Oracle goldengate creates parameter files in the default character set of the local operating system.
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.
For more information see the reference for oracle goldengate and optional parameters for integrated modes for additional configuration considerations.
If the network or the target system becomes unavailable extract could run out of memory and abend.
In a basic oracle goldengate configuration with only a trail on the target system there is nowhere on the source system to store the data operations that extract continuously extracts into memory.
Enter any optional replicat parameters that are recommended for your configuration.
Oracle goldengate high availability using oracle.
Oracle goldengate basic configuration.
You can edit this file at any point before starting processing by using the edit params command in ggsci.
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.
To avoid issues caused by character set incompatibilities.
Oracle goldengate configuration best practices.