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 |
---|---|
|
Should always be a value of |
|
(NonStop) Conditionally set if Oracle GoldenGate is extracting aborted transactions from the TMF audit trail. Normally, |
|
The length, in bytes, of the record buffer. |
|
The type of operation represented by the record. See **INTERNAL XREF ERROR** for a list of operation types. |
|
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 |
|
(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 |
|
Identifies the transaction log identifier, such as the Oracle redo log sequence number. |
|
(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.
|
|
For Windows and UNIX records, this field will always be a value of 4 ( For NonStop records, the value of this field depends on the record type:
|
|
Identifies whether the record is a before ( |
|
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. |
|
(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, |
|
Identifies whether the data was read from the transaction log or fetched from the database.
|
|
This field is obsolete. |
|
Identifies the position in the transaction log of the data. |
|
(Windows and UNIX) Used for |