RMTFILE

Valid for

Extract

Description

Use RMTFILE when the remote Oracle GoldenGate trail is a flat file.

All FILE and TABLE entries after the current entry but before the next trail parameter (EXTFILE, EXTTRAIL, RMTBATCH, RMTFILE, RMTTRAIL) result in output to the current trail.

Remote Oracle GoldenGate trails are used over TCP/IP connections only. Do not specify an Expand node name in the file_name, even if the remote system is also connected with Expand. To specify a trail on a different NonStop node over an Expand connection, use the EXTFILE or EXTTRAIL parameters.

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

You must include at least one EXTFILE, EXTTRAIL, RMTBATCH, RMTFILE or RMTTRAIL entry in your parameter file. It is required for initial loads that use a trail.

Syntax

RMTFILE file_name
[, PURGE | APPEND]
[, EXTENTS (primary, secondary, maximum)]
[, MAXFILES num_files]
[, MEGABYTES megabytes]
[, OWNER group_number, user_number]
[, SECURE "[, FORMAT RELEASE major.minor] rwep"]

FORMAT RELEASE major.minor

Specifies the trail format of the data that is sent by Extract to a trail, file, or (if a remote task). The value tells the reader process whether the data records are of a version that it supports. The format depends on the version of the Oracle GoldenGate process. Newer Oracle GoldenGate versions contain different characteristic than older 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.

file_name: The remote file on the remote system.
PURGE | APPEND: Purges file_name before capturing data, or appends the extracted data to file_name.
EXTENTS (primary, secondary, maximum): Defines the primary, secondary and maximum extents when the target is a NonStop system.
MAXFILES num_files: Enables a sequence of files to be created on the target system, rather than a single file. When MAXFILES is specified, a six-digit sequence number is appended to the end of file_name for each file. MAXFILES does not actually limit the number of files created. When using MAXFILES, MEGABYTES should also be specified in order to explicitly set the maximum size of each file in the sequence.
MEGABYTES megabytes: Sets up the maximum size of the file, or sequence of files if you specified MAXFILES. The maximum size for each file is 2 gigabytes.
OWNER group_number, user_number: Determines which user group owns the RMTFILE.
SECURE "rwep": Sets the standard Guardian security for read, write, execute, and purge operations on the RMTFILE.

Example

The following example extracts data from SALES to a UNIX or Windows system, depending on region. Collectors are started dynamically by Manager. The Manager port for NY is the default, port 7809. To resolve any possible conflict, the LA port number is explicitly identified. Note that the TCPIPPROCESSNAME is also specified (the default is $ZTC0).

TCPIPPROCESSNAME $ZTC4
RMTHOST NY, MGRPORT 7809
RMTFILE /usr/dat/sales1
TABLE $DATA5.SALES.ORDERS WHERE (REGION = "EAST");
TABLE $DATA5.ACCTING.RECEIPTS WHERE (REG = "E");
RMTHOST LA, MGRPORT 7888
RMTFILE d:\dat\wstsales
TABLE $DATA5.SALES.ORDERS WHERE (REGION = "WEST");
TABLE $DATA5.ACCTING.RECEIPTS WHERE (REG = "W");