Oracle goldengate creates parameter files in the default character set of the local operating system.
Oracle golden gate configuration file.
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.
To avoid issues caused by character set incompatibilities.
You can edit this file at any point before starting processing by using the edit params command in ggsci.
The following procedure describes a minimal oracle golden gate configuration.
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.
Once the basic configuration has been tested new features can be added incrementally simplifying any troubleshooting.
Protection against network and target failures.
Oracle goldengate configuration best practices.
Oracle goldengate basic 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.
It is intended for research and or training purposes and is not intended to be a production configuration.