Valid For



Use the RMTTRAIL parameter to specify a remote trail that was created with the ADD RMTTRAIL command in GGSCI. RMTTRAIL must be preceded by an RMTHOST parameter.

A trail specified with RMTTRAIL must precede its associated TABLE statements. Multiple RMTTRAIL statements can be used to specify different remote trails.


Extract with RMTTRAIL option, which implies writing directly to the target system, isn't supported between secure Oracle GoldenGate deployments. It's supported between multiple Oracle GoldenGate classic architecture installations and between unsecure Oracle GoldenGate MA deployment and Oracle GoldenGate classic Extract.

From Oracle GoldenGate 19c (19.1.0) onward, the primary Extract writes trail file in the same format as existing trail file format when you upgrade, unless you explicitly specify the trail file format version using the FORMAT RELEASE option. This prevents subsequent Replicats from abending if they are not upgraded.

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




RMTTRAIL trail_name
[, FORMAT RELEASE major.minor]

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

Not valid for Extract Pump. Specifies 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 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.1 through the current Oracle GoldenGate X.x version number, for example 11.2 or 12.1.

The release version is programmatically mapped back to the appropriate trail format compatibility level. The default is the current version of the process that writes to this trail.


RELEASE versions earlier than 12.1 do not support three-part object names.


If using multiple trails in a single Extract, only RELEASE versions that are the same can coexist.

The following settings are supported for Oracle Database 12.2 and higher:

  • For Oracle Database 12.2 non-CDB or higher with compatibility set to 12.1, FORMAT RELEASE 12.2 or above is supported.

  • For Oracle Database 12.2 non-CDB or higher with compatibility set to 12.2, FORMAT RELEASE 12.2 or above is supported.

  • For Oracle Database 12.2 CDB/PDB or higher with compatibility set to 12.2, only FORMAT RELEASE values 12.3 or higher are 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.


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.


Not valid for Extract Pump. 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.


Example 1   
RMTTRAIL dirdat/ny
Example 2   
RMTTRAIL /ggs/dirdat/ny, FORMAT RELEASE 12.3
Example 3   

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

RMTTRAIL ./dirdat/ra 
TABLE hr.tab1 
TABLE hr.tab2 
RMTTRAIL ./dirdat/rb
TABLE scott.tab3 
TABLE scott.tab4 
Example 4   

Example of an Extract Pump parameter file that sends an HR schema with object definitions and an ORD schema without object definitions:

RMTTRAIL /ggs19.1/dirdat/r1, OBJECTDEFS
TABLE hr.*;
RMTTRAIL /ggs19.1/dirdat/r2, NO_OBJECTDEFS
TABLE ord.*;