CHARSET
Valid For
Extract, Replicat, DEFGEN, Manager, and GLOBALS
Description
Use the CHARSET parameter to specify the character set of the parameter files in the local Oracle GoldenGate instance. By default, the parameter file is created in the default character set of the local operating system. CHARSET specifies an alternative character set to use in the event that the local platform does not support a required character or characters.
CHARSET cannot be used with query parameters.
CHARSET allows operating-system incompatible characters, including multi byte characters, to be used in the parameter file without the need for an escape sequence (\uXXXX) when the local platform does not support multibyte characters as the default character set of the operating system.
CHARSET can also be used when the parameter file is being created on one system but will be used on a different system with a different character set. To avoid possible incompatibilities between different character sets, you should create parameter files on the same system where they will be used by Oracle GoldenGate.
Note:
Use of CHARSET in the mgr.prm file is not supported in 12.1.2.x or earlier releases.
Placement in the Parameter File
CHARSET must be placed on the first line of the parameter file.
Usage in the GLOBALS File
CHARSET in a GLOBALS file sets a default character set for the parameter files of all local processes. CHARSET in an individual parameter file overrides the default that is set in GLOBALS.
Usage in Nested Parameter Files
You can use CHARSET in a parameter file that includes an OBEY or INCLUDE parameter, but the referenced parameter file does not inherit the CHARSET character set. The CHARSET character set is used to read wildcarded object names in the referenced file, but you must use an escape sequence (\uXXXX) to specify all other incompatible characters in the referenced file.
Default
None
Example
CHARSET UTF-8