This paper provides an example of Oracle GoldenGate parameter files that can be used to configure Oracle GoldenGate replication that complies with recommended best practices. The example is generic and can serve as a starting point for a more customized Oracle GoldenGate implementation.
Most Oracle GoldenGate functionality is controlled by means of parameters specified in parameter files. A parameter file is an ASCII file that is read by an associated process. Oracle GoldenGate uses two types of parameter files: a GLOBALS file and runtime parameter files.
Overview of the GLOBALS file
The GLOBALS file stores parameters that relate to the Oracle GoldenGate instance as a whole. This is in contrast to runtime parameters, which are coupled with a specific process such as Extract. The parameters in the GLOBALS file apply to all processes in the Oracle GoldenGate instance, but can be overridden by specific process parameters. Once set, GLOBALS parameters are rarely changed and there are far fewer of them than runtime parameters.A GLOBALS parameter file is required only in certain circumstances and, when used, must be created from the command shell before starting any Oracle GoldenGate processes, including GGSCI. The GGSCI program reads the GLOBALS file and passes the parameters to processes that need them.
Overview of runtime parameter file
Runtime parameters give you control over the various aspects of Oracle GoldenGate synchronization, such as:
● Data selection, mapping, transformation, and replication
● DDL and sequence selection, mapping, and replication (where supported)
● Error resolution
● Status and error reporting
● System resource usage
● Startup and runtime behavior
There can be only one active parameter file for the Manager process or an Extract or Replicat group; however, you can use parameters in other files by using the OBEY parameter.
The complete document can be found on the Oracle Support site under the document ID:1321696.1