TRANSACTION_LOG
The TRANSACTION_LOG system table provides a read-only view of the transaction log, which stores transaction states during its lifecycle in case transaction commit fails. You can use log data to recover data manually from a transaction failure. In some cases the system can use this data to complete an interrupted transaction.
Successful transactions are automatically removed from the log upon completion of the commit or rollback operation. Failed transactions remain in the log.
Table view requires the ACCESS_TOOLS and READ_ALL_STATUS rights.
|
Column |
TDV JDBC Data Type |
Nullable |
Description |
|
TYPE |
VARCHAR(28) |
|
Indicates the type of transaction log entry, which can be: Begin transaction (manual)—Start a transaction supporting manual recovery. Begin transaction (auto)—Start a transaction supporting both manual recovery and automatic compensation. Execute SQL—Execute a SQL statement. Add work unit—Add a work unit (an insert, update, or delete action on a data source). Begin commit End commit Fail commit Begin rollback End rollback Fail rollback Server restart Begin work unit commit End work unit commit Work unit commit failure Work unit commit in doubt Begin work unit rollback End work unit rollback Work unit rollback failure Being work unit compensate End work unit compensate Work unit compensate failure |
|
SERIAL |
BIGINT |
|
Unique serial number for the transaction log entry. |
|
TIMESTAMP |
BIGINT |
|
The time when the log entry was made, to the millisecond. |
|
TRANSACTION_ID |
BIGINT |
|
The unique ID for the transaction to which this log entry applies. |
|
WORK_UNIT_ID |
BIGINT |
Yes |
For work unit entries, this is the unique ID; otherwise NULL. |
|
MESSAGE |
BLOB |
Yes |
Contains a SQL statement for Execute SQL and Add Work Unit. Contains the exception message for any failure type; otherwise NULL. |