1. Reference for Oracle GoldenGate
  2. Oracle GoldenGate Classic Architecture
  3. Summary of Extract Parameters (Classic Architecture)
  4. RMTTASK

RMTTASK

Valid For

Extract in Classic Architecture

Description

Use the RMTTASK parameter for an initial-load Extract to initiate a Replicat processing task during an Oracle GoldenGate direct load or a direct bulk load to SQL*Loader. RMTTASK directs Extract to communicate directly with Replicat over TCP/IP and bypasses the use of a Collector process or trail storage. RMTTASK also directs Extract to request that Manager start Replicat automatically, and then stop Replicat when the run is finished. Tasks do not use checkpoints.

Dependent parameters are as follows:

  • A RMTHOST statement must follow each RMTTASK statement in the initial-load Extract parameter file.

  • EXTRACT must be used in the initial-load Extract parameter file.

  • REPLICAT must be used in the initial-load Replicat parameter file.

  • SOURCEISTABLE must be used in the ADD EXTRACT command.

  • SPECIALRUN must be used in the ADD REPLICAT command.

RMTTASK is only allowed to be used once in the Extract parameter file.

RMTTASK does not support encryption of any kind. To use encryption, you can use the initial-load method that writes data to a file, which is read by Replicat to load the data.

RMTTASK supports all Oracle data types, including BLOB, CLOB, NCLOB, LONG, UDT, and XML.

When using RMTTASK, do not start Replicat with the START REPLICAT command. Replicat is started automatically during the task.

See the Instantiating Oracle GoldenGate with an Initial Load in Administering Oracle GoldenGate for more information about performing initial data loads.

Default

None

Syntax

RMTTASK REPLICAT, GROUP group_name
[FORMAT RELEASE major.minor]
GROUP group_name

The group name of the Initial Load Replicat on the target system.

FORMAT RELEASE major.minor

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.

Note:

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

Note:

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.

Example

RMTTASK REPLICAT, GROUP initrep, FORMAT RELEASE 12.3