Exceptions Table Reference

An exceptions table contains not only columns in the destination table, but also additional columns.

The following table lists the additional columns in an Exceptions table.

Column Name Type Description
ADB_OPCODE NUMBER(38) Operation code used by the adapter. The values can be:
  • 1 indicates INSERT.
  • 2 indicates UPDATE.
  • 3 indicates DELETE.
  • 4 indicates UPDATE if a row exists, otherwise INSERT.

If an incoming TIBCO Rendezvous message does not have an operation code, an INSERT operation is performed.

Note: When Subscription Service works with a parent-child table, the values of the ADB_OPCODE columns in the parent table and the child table must be the same. Or only set the value of the ADB_OPCODE column in the parent table and leave the ADB_OPCODE column in the child table empty.
ADB_UPDATE_ALL NUMBER(38) Currently not used.
ADB_TRACKINGID VARCHAR2(40) Tracking ID of a message. This column is the primary key.

Each exceptions table that is mapped to a child table is connected to the parent exceptions table by this column.

ADB_ERROR_TEXT VARCHAR2(4000) Text of an error from the database server or another source that caused the exception.
ADB_ERROR_TIME DATE Timestamp of an inserted record.

For Oracle databases, the timestamp includes the time zone information.

ADB_JOIN_ID VARCHAR(46) Joined column used to link a parent record with its child record. ADB_JOIN_ID is generated from ADB_TRACKINGID and concatenated with the record number in the group.

The exceptions table of a child table is connected to the exceptions table of a parent table by the ADB_JOIN_ID column.

An exceptions table cannot contain any user-created columns where the column name starts with ADB_. These characters are reserved for the adapter use.

Note: When you use Teradata and PostgreSQL databases to work with the exceptions table, if the operation fails, all uncommitted data will be rolled back.
Contents
Search Results