Valid For
Extract
Description
Use the EXTTRAIL parameter to specify a trail on the local system that was created with the ADD EXTTRAIL command. The trail is read by a data pump Extract group or by a Replicat group on the local system.
EXTTRAIL must precede all associated TABLE statements. Multiple EXTTRAIL statements can be used to define different trails.
Do not use EXTTRAIL for an Extract that is configured in PASSIVE mode. See Administering Oracle GoldenGate for more information about PASSIVE mode, an Oracle GoldenGate security feature.
EXTTRAIL parameter is deprecated and ignored for Data Pump.
You can encrypt the data in this trail by using the ENCRYPTTRAIL parameter. See "ENCRYPTTRAIL | NOENCRYPTTRAIL" for more information.
Default
None
Syntax
EXTTRAIL file_name [, FORMAT RELEASE major.minor] [, OBJECTDEFS | NO_OBJECTDEFS] [, TRAILBYTEORDER {BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}]
file_nameThe relative or fully qualified name of the trail. Use a maximum of two characters for the name. As trail files are aged, a nine-character sequence number will be added to this name, for example /ogg/dirdat/rt000000001.
FORMAT RELEASE major.minorSpecifies the metadata format of the data that is sent by Extract to a trail, a file, or (if a remote task) to another process. The metadata tells the reader process whether the data records are of a version that it supports. The metadata format depends on the version of the Oracle GoldenGate process. Older Oracle GoldenGate versions contain different metadata than newer ones.
FORMAT is a required keyword.
RELEASE specifies an Oracle GoldenGate release version. major is the major version number, and minor is the minor version number. The X.x must reflect a current or earlier, generally available (GA) release of Oracle GoldenGate. Valid values are 9.0 through the current Oracle GoldenGate X.x version number, for example 12.2.. If you use an Oracle GoldenGate version that is earlier than 9.0, specify either 9.0 or 9.5.
The release version is programmatically mapped back to an appropriate internal compatibility level. The default is the current version of the process that writes to this trail.
Note:
RELEASE versions earlier than 12.1 do not support three-part object names.There is a dependency between FORMAT and the RECOVERYOPTIONS parameter. See "RECOVERYOPTIONS" for more information.
See the Administering Oracle GoldenGate for additional information about Oracle GoldenGate trail file versioning and recovery modes.
For Oracle Database 12.2 non-CDB with compatibility set to 12.1, FORMAT RELEASE 12.2 or above is supported.
For Oracle Database 12.2 non-CDB with compatibility set to 12.2, FORMAT RELEASE 12.2 or above is supported.
For Oracle Database 12.2 CDB/PDB with compatibility set to 12.2, FORMAT RELEASE values 12.3 is supported. This is due to the use of local undo for PDBs, which requires augmenting the transaction ID with the PDB number to ensure uniqueness of trx IDs.
OBJECTDEFS | NO_OBJECTDEFSUse the OBJECTDEFS and NO_OBJECTDEFS options to control whether or not to include the object definitions in the trail. These two options are applicable only when the output trail is formatted in Oracle GoldenGate canonical format and the trail format release is greater than 12.1. Otherwise, both options are ignored because no metadata record will be added to the trail.
When replicating from an Open Systems database to NonStop, specify format version below 12.2 to avoid including the object definitions in the trail since NonStop does not support processing object definitions from the trail.
TRAILBYTEORDER {BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}Sets the byte format of the metadata in the trail records. This parameter does not affect the column data. Valid only for trails that have a FORMAT RELEASE version of at least 12.1. Valid values are BIGENDIAN (big endian), LITTLEENDIAN (little endian), and NATIVEENDIAN (default of the local system). The default is BIGENDIAN. See the GLOBALS version of TRAILBYTEORDER for additional usage instructions.