Support Globalization Functions

Oracle GoldenGate provides globalization support, which you should consider when using this support.

Replicating From a Source that Contains Both ASCII and EBCDIC

When replicating to or from a Db2 source system to a target with a different character set, some consideration should be given to the encoding of the character data on the Db2 source if it contains a mix of ASCII and EBCDIC data. Character set conversion by any given Replicat requires source data to be in a single character set.

The source character set gets specified in the trail header. Thus, the Oracle GoldenGate trail can contain either ASCII or EBCDIC data, but not both. Unicode tables are processed without particular configuration and are exempt from the one-character set requirement.

For a source that contains both character encoding types, you have the following options:

To output the correct character set in either of those scenarios, use the TRAILCHARSETASCII and TRAILCHARSETEBCDIC parameters. The default is TRAILCHARSETEBCDIC. Without these parameters, ASCII and EBCDIC data are written to the trail as-is. When using these parameters, note the following:

Specifying Multi-Byte Characters in Object Names

If the name of a schema, table, column, or stored procedure in a parameter file contains a multi-byte character, use double quotes on the name.

For more information about specifying object names, see Specifying Object Names in Oracle GoldenGate Input.