Valid For



Use the RMTFILE parameter to define the name of an extract file on a remote system to which extracted data will be written. Use this parameter for initial-load configurations. For online change synchronization, use the RMTTRAIL parameter.

The size of an extract file cannot exceed 2GB .

RMTFILE must be preceded by a RMTHOST statement, and it must precede any TABLE statements.

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




RMTFILE file_name
[, MAXFILES number]
[, MEGABYTES megabytes]
[, FORMAT RELEASE major.minor]

The relative or fully qualified name of the file.


Adds the current data to existing data in the file. If you use APPEND, do not use PURGE.


Deletes an existing file before creating a new one. If you use PURGE, do not use APPEND.


Forces a sequence of files to be created, rather than a single file. Use this option when you expect the size of a file to exceed the limit permitted by the operating system.

MAXFILES permits as many files to be created as needed. Aged files are appended with a six-digit sequence number, for example datafile000002.

When using MAXFILES, also use MEGABYTES to set the maximum size of each file in the sequence.

Checkpoints are not maintained in these files.

MEGABYTES megabytes

Defines the maximum size of the file (or of each file created when MAXFILES is used). The size of a remote file cannot exceed 2GB .

FORMAT RELEASE major.minor

Specifies the metadata format of the data that is sent by Extract to the file. 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 11.2 or 12.1. (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 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.


Sets the byte format of the metadata in the file records. This parameter does not affect the column data. Valid only for files 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   
RMTFILE /ggs/dirdat/salesny, MEGABYTES 2, PURGE
Example 2   
RMTFILE /ggs/dirdat/salesny, MEGABYTES 2, FORMAT RELEASE 10.4