1.144 RMTTRAIL
Valid For
Extract
Description
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.
RMTTRAIL
must precede its associated
TABLE
statements. Multiple RMTTRAIL
statements can be
used to specify different remote trails.
Note:
Extract withRMTTRAIL
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.
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.
Default
None
Syntax
RMTTRAIL trail_name [, FORMAT RELEASE major.minor] [, OBJECTDEFS | NO_OBJECTDEFS] [, TRAILBYTEORDER {BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}]
-
trail_name
-
The relative or fully qualified path name of the trail. The trail name can contain only two characters.
Note:
In Microservices Architecture, the trail file name two-character prefix must start with an alphabet only./tr
would have files named/tr000000001
,/tr000000002
. -
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, andminor
is the minor version number. The X.x must reflect a current or earlier, generally available (GA) release of Oracle GoldenGate. Valid values are 12.2 through the current Oracle GoldenGate X.x version number, 19.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.
Note:
The lowest supported version is 12.2.Note:
RELEASE
versions earlier than 12.2 do not support three-part object names.Note:
If using multiple trails in a single Extract, onlyRELEASE
versions that are the same can coexist. -
TRAILBYTEORDER
{BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}
-
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 areBIGENDIAN
(big endian),LITTLEENDIAN
(little endian), andNATIVEENDIAN
(default of the local system). The default isBIGENDIAN
. See theGLOBALS
version of TRAILBYTEORDER for additional usage instructions.
Examples
- 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.*;
Parent topic: Oracle GoldenGate Parameters