Description of Header Fields

The following describes the fields of the Oracle GoldenGate record header. Some fields apply only to certain platforms.

Table 13-2 Oracle GoldenGate record header fields

Field Description

Hdr-Ind

Should always be a value of E, indicating that the record was created by the Extract process. Any other value indicates invalid data.

UndoFlag

(NonStop) Conditionally set if Oracle GoldenGate is extracting aborted transactions from the TMF audit trail. Normally, UndoFlag is set to zero, but if the record is the backout of a previously successful operation, then UndoFlag will be set to 1. An undo that is performed by the disc process because of a constraint violation is not marked as an undo.

RecLength

The length, in bytes, of the record buffer.

IOType

The type of operation represented by the record. See **INTERNAL XREF ERROR** for a list of operation types.

TransInD

The place of the record within the current transaction. Values are:

0 — first record in transaction

1 — neither first nor last record in transaction

2 — last record in the transaction

3 — only record in the transaction

SyskeyLen

(NonStop) The length of the system key (4 or 8 bytes) if the source is a NonStop file and has a system key. If a system key exists, the first Syskeylen bytes of the record are the system key. Otherwise, SyskeyLen is 0.

AuditRBA

Identifies the transaction log identifier, such as the Oracle redo log sequence number.

Continued

(Windows and UNIX) Identifies whether or not the record is a segment of a larger piece of data that is too large to fit within one record. LOBs, CLOBS, and some VARCHARs are stored in segments. Unified records that contain both before and after images in a single record (due to the UPDATERECORDFORMAT parameter) may exceed the maximum length of a record and may also generate segments.

Y — the record is a segment; indicates to Oracle GoldenGate that this data continues to another record.

N — there is no continuation of data to another segment; could be the last in a series or a record that is not a segment of larger data.

Partition

For Windows and UNIX records, this field will always be a value of 4 (FieldComp compressed record in internal format). For these platforms, the term Partition does not indicate that the data represents any particular logical or physical partition within the database structure.

For NonStop records, the value of this field depends on the record type:

  • In the case of BulkIO operations, Partition indicates the number of the source partition on which the bulk operation was performed. It tells Oracle GoldenGate which source partition the data was originally written to. Replicat uses the Partition field to determine the name of the target partition. The file name in the record header will always be the name of the primary partition. Valid values for BulkIO records are 0 through 15.

  • For other non-bulk NonStop operations, the value can be either 0 or 4. A value of 4 indicates that the data is in FieldComp record format.

BeforeAfter

Identifies whether the record is a before (B) or after (A) image of an update operation. Records that combine both before and after images as the result of the UPDATERECORDFORMAT parameter are marked as after images. Inserts are always after images, deletes are always before images.

IO Time

The time when the operation occurred, in local time of the source system, in GMT format. This time may be the same or different for every operation in a transaction depending on when the operation occurred.

OrigNode

(NonStop) The node number of the system where the data was extracted. Each system in a NonStop cluster has a unique node number. Node numbers can range from 0 through 255.

For records other than NonStop in origin, OrigNode is 0.

FormatType

Identifies whether the data was read from the transaction log or fetched from the database.

F — fetched from database

R — readable in transaction log

Incomplete

This field is obsolete.

AuditPos

Identifies the position in the transaction log of the data.

RecCount

(Windows and UNIX) Used for LOB data when it must be split into chunks to be written to the Oracle GoldenGate file. RecCount is used to reassemble the chunks.