Documentation
Advanced Search


Reference for Oracle GoldenGate for Windows and UNIX

EXTFILE

Valid For

Extract and Replicat

Description

Use the EXTFILE parameter to specify an extract file, which is a local file that will be read by a data pump Extract group on the local system, or to specify a local extract file that Replicat reads when SPECIALRUN is used.

EXTFILE must precede all associated TABLE or MAP statements. Multiple EXTFILE statements can be used to define different files.

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

Default

None

Syntax

EXTFILE file_name
[, FORMAT RELEASE major.minor]
[, MAXFILES number]
[, MEGABYTES megabytes]
[, TRAILBYTEORDER {BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}] 
file_name

Valid for Extract and Replicat. Specifies the relative or fully qualified name of the extract file.

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 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 programatically mapped back to the appropriate trail format 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. See "RECOVERYOPTIONS" for more information.

MAXFILES number

Valid for Extract. Forces a sequence of files to be created, rather than a single file. Use 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. Checkpoints are not maintained in these files. When using MAXFILES, also use MEGABYTES to set the maximum size of each file in the sequence.

MEGABYTES megabytes

Valid for Extract. Defines the maximum size of the file (or of each file created when MAXFILES is used). The size of an extract file cannot exceed 2GB.

TRAILBYTEORDER {BIGENDIAN | LITTLEENDIAN | NATIVEENDIAN}

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.

Examples

Example 1   
EXTFILE dirdat/datafile
Example 2   
EXTFILE dirdat/extdat, MAXFILES 3, MEGABYTES 2
Example 3   
EXTFILE /ggs/dirdat/extdat, FORMAT RELEASE 10.4
Close Window

Table of Contents

Reference for Oracle GoldenGate for Windows and UNIX

Expand | Collapse