RMTTRAIL

Valid For

Extract

Description

Use the RMTTRAIL parameter to specify a remote trail that was created with the ADD RMTTRAIL command. A trail specified with RMTTRAIL must precede its associated TABLE statements. Multiple RMTTRAIL statements can be used to specify different remote trails. RMTTRAIL must be preceded by a RMTHOST parameter.

FORMAT RELEASE and TRAILBYTEORDER options only apply to the Extract and not a data pump.

You can encrypt the data in this trail by using the ENCRYPTTRAIL parameter. See "ENCRYPTTRAIL | NOENCRYPTTRAIL" for more information.

Default

None

Syntax

RMTTRAIL trail_name
[, FORMAT RELEASE major.minor]
[, OBJECTDEFS | NO_OBJECTDEFS]
[, TRAILBYTEORDER {BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}]
name

The relative or fully qualified path name of the trail. Use two characters for the name. As trail files are aged, a six-character sequence number will be added to this name, for example /ggs/dirdat/rt000000001.

FORMAT RELEASE major.minor

Specifies the metadata format of the data that is sent by Extract to the trail. The metadata tells the reader process whether the data records are of a version that it supports. 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 11.2 through the current Oracle GoldenGate X.x version number, for example 11.2 or 12.1.

    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 that RELEASE versions earlier than 12.1 do not support three-part object names.

There is a dependency between FORMAT and the RECOVERYOPTIONS parameter. When RECOVERYOPTIONS is set to APPENDMODE, FORMAT must be set to RELEASE 10.0 or greater. When RECOVERYOPTIONS is set to OVERWRITEMODE, FORMAT must be set to RELEASE 9.5 or less.

See Trail Recovery Mode for additional information about Oracle GoldenGate trail file versioning and recovery modes.

The following settings are supported in Oracle Database 12.2:

  • 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, only FORMAT RELEASE 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_OBJECTDEFS

Use 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.

Examples

Example 1    
RMTTRAIL ny
Example 2   
On Linux
RMTTRAIL trails/ny, FORMAT RELEASE 19.1
Example 3   
On Windows:
EXTTRAIL trails\ny, FORMAT RELEASE 19.1
Example 4   

Two trail formats within the same sets of tables being captured:

FORMAT RELEASE  19.1 
TABLE tab1 
TABLE tab2 
FORMAT RELEASE 19.1 
TABLE tab1 
TABLE tab2
Example 5   

Example of a data pump parameter file that sends an HR schema with object definitions and an ORD schema without object definitions:

RMTTRAIL $data/ggs12.2/a1, OBJECTDEFS
TABLE hr.*;
RMTTRAIL $data/ggs12.2/a2, NO_OBJECTDEFS
TABLE ord.*;