Oracle GoldenGate Operation Types

The following are some of the Oracle GoldenGate operation types. Types may be added as new functionality is added to Oracle GoldenGate. For a more updated list, use the SHOW RECTYPE command in the Logdump utility.

Table 10-3 Oracle GoldenGate Operation Types

Type Description Platform

1-Abort

A transaction aborted.

NSK TMF

2-Commit

A transaction committed.

NSK TMF

3-Delete

A record/row was deleted. A Delete record usually contains a full record image. However, if the COMPRESSDELETES parameter was used, then only key columns will be present.

All

4-EndRollback

A database rollback ended

NSK TMF

5-Insert

A record/row was inserted. An Insert record contains a full record image.

All

6-Prepared

A networked transaction has been prepared to commit.

NSK TMF

7-TMF-Shutdown

A TMF shutdown occurred.

NSK TMF

8-TransBegin

No longer used.

NSK TMF

9-TransRelease

No longer used.

NSK TMF

10-Update

A record/row was updated. An Update record contains a full record image. Note: If the partition indicator in the record header is 4, then the record is in FieldComp format (see below) and the update is compressed.

All

11-UpdateComp

A record/row in TMF AuditComp format was updated. In this format, only the changed bytes are present. A 4-byte descriptor in the format of 2-byte_offset2-byte_length precedes each data fragment. The byte offset is the ordinal index of the column within the source table. The length is the length of the data.

NSK TMF

12-FileAlter

An attribute of a database file was altered.

NSK

13-FileCreate

A database file was created.

NSK

14-FilePurge

A database file was deleted.

NSK

15-FieldComp

A row in a SQL table was updated. In this format, only the changed bytes are present. Before images of unchanged columns are not logged by the database. A 4-byte descriptor in the format of 2-byte_offset2-byte_length precedes each data fragment. The byte offset is the ordinal index of the column within the source table. The length is the length of the data. A partition indicator of 4 in the record header indicates FieldComp format.

All

16-FileRename

A file was renamed.

NSK

17-AuxPointer

Contains information about which AUX trails have new data and the location at which to read.

NSK TMF

18-NetworkCommit

A networked transaction committed.

NSK TMF

19-NetworkAbort

A networked transaction was aborted.

NSK TMF

90-(GGS)SQLCol

A column or columns in a SQL table were added, or an attribute changed.

NSK

100-(GGS)Purgedata

All data was removed from the file (PURGEDATA).

NSK

101-(GGS)Purge(File)

A file was purged.

NSK non-TMF

102-(GGS)Create(File)

A file was created. The Oracle GoldenGate record contains the file attributes.

NSK non-TMF

103-(GGS)Alter(File)

A file was altered. The Oracle GoldenGate record contains the altered file attributes.

NSK non-TMF

104-(GGS)Rename(File)

A file was renamed. The Oracle GoldenGate record contains the original and new names.

NSK non-TMF

105-(GGS)Setmode

A SETMODE operation was performed. The Oracle GoldenGate record contains the SETMODE information.

NSK non-TMF

106-GGSChangeLabel

A CHANGELABEL operation was performed. The Oracle GoldenGate record contains the CHANGELABEL information.

NSK non-TMF

107-(GGS)Control

A CONTROL operation was performed. The Oracle GoldenGate record contains the CONTROL information.

NSK non-TMF

115 and 117

(GGS)KeyFieldComp(32)

A primary key was updated. The Oracle GoldenGate record contains the before image of the key and the after image of the key and the row. The data is in FieldComp format (compressed), meaning that before images of unchanged columns are not logged by the database.

Windows and UNIX

116-LargeObject

116-LOB

Identifies a RAW, BLOB, CLOB, or LOB column. Data of this type is stored across multiple records.

Windows and UNIX

132-(GGS) SequenceOp

Identifies an operation on a sequence.

Windows and UNIX

134-UNIFIED UPDATE

135-UNIFIED PKUPDATE

Identifies a unified trail record that contains both before and after values in the same record. The before image in a UNIFIED UPDATE contains all of the columns that are available in the transaction record for both the before and after images. The before image in a UNIFIED PKUPDATE contains all of the columns that are available in the transaction record, but the after image is limited to the primary key columns and the columns that were modified in the UPDATE.

Windows and UNIX

160 - DDL_Op

Identifies a DDL operation

Windows and UNIX

161-

RecordFragment

Identifies part of a large row that must be stored across multiple records (more than just the base record).

Windows and UNIX

200-GGSUnstructured Block

200-BulkIO

A BULKIO operation was performed. The Oracle GoldenGate record contains the RAW DP2 block.

NSK non-TMF

201 through 204

These are different types of NonStop trace records. Trace records are used by Oracle GoldenGate support analysts. The following are descriptions.

  • ARTYPE_FILECLOSE_GGS 201 — the source application closed a file that was open for unstructured I/O. Used by Replicat

  • ARTYPE_LOGGERTS_GGS 202 — Logger heartbeat record

  • ARTYPE_EXTRACTERTS_GGS 203 — unused

  • ARTYPE_COLLECTORTS_GGS 204 — unused

NSK non-TMF

205-GGSComment

Indicates a comment record created by the Logdump utility. Comment records are created by Logdump at the beginning and end of data that is saved to a file with Logdump's SAVE command.

All

249 through 254

These are different types of NonStop trace records. Trace records are used by Oracle GoldenGate support analysts. The following are descriptions.

  • ARTYPE_LOGGER_ADDED_STATS 249 — a stats record created by Logger when the source application closes its open on Logger (if SENDERSTATS is enabled and stats are written to the logtrail)

  • ARTYPE_LIBRARY_OPEN 250 — written by BASELIB to show that the application opened a file

  • ARTYPE_LIBRARY_CLOSE 251 — written by BASELIB to show that the application closed a file.

  • ARTYPE_LOGGER_ADDED_OPEN 252 — unused

  • ARTYPE_LOGGER_ADDED_CLOSE 253 — unused

  • ARTYPE_LOGGER_ADDED_INFO 254 — written by Logger and contains information about the source application that performed the I/O in the subsequent record (if SENDERSTATS is enabled and stats are written to the logtrail). The file name in the trace record is the object file of the application. The trace data has the application process name and the name of the library (if any) that it was running with.

NSK non-TMF