TRAILBYTEORDER

Valid For

GLOBALS

Description

Note:

TRAILBYTEORDER is automatically handled by Oracle GoldenGate, and should only be used if the default settings are not working or when you want a required conversion to take place on the source machine and not the target to manage overhead.

Use the TRAILBYTEORDER parameter in the GLOBALS file to set the byte format of the trails or files created by Extract. By default, Extract always writes the trail metadata in the native byte order of the source machine..

When used in the GLOBALS file, TRAILBYTEORDER affects all of the files or trails in the same Oracle GoldenGate instance. To specify the byte order of a specific trail or file, use the TRAILBYTEORDER option of the associated EXTFILE, RMTFILE, or EXTTRAIL parameters in the Extract parameter file. In cases where Extract writes to multiple trails or files on different platforms, TRAILBYTEORDER in the Extract parameter file enables the correct byte ordering of each one. When TRAILBYTEORDER is used as an Extract parameter, it overrides any TRAILBYTEORDER specification in the GLOBALS file.

In the case where the source byte order is different than the target and where some conversion is required, you can decide whether the conversion takes place at the source or at the target. To perform the conversion on the source, set TRAILBYTEORDER to the endianness of the target. To perform the conversion on the target, do not use this parameter.

If nothing is specified with TRAILBYTEORDER, a data pump writes the trail using the same byte order as the input trail, which may not be the desired format and cannot be altered in a data pump.

TRAILBYTEORDER is valid for files that have a FORMAT RELEASE version of at least 12.1. For older versions, this parameter is ignored.

You must use TRAILBYTEORDER when replicating data to a NonStop system. On the NonStop platform, Oracle GoldenGate only supports BIGENDIAN, generally not the default of the source.

To identify the byte order of the metadata in a trail, use the ENV command of the Logdump utility.

Default

NATIVEENDIAN

Syntax

TRAILBYTEORDER {BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}

BIGENDIAN

Formats the trail metadata in big endian.

LITTLEENDIAN

Formats the trail metadata in little endian.

NATIVEENDIAN

Formats the trail metadata in the default byte order of the local system. Enables you to make certain the output trail is converted to the native format of the source machine.

Example

TRAILBYTEORDER BIGENDIAN