Log Transaction Display Fields
The columns of information on the Log Transaction Display screen are:
External TX ID
The Transaction ID. This column corresponds to the Transaction ID field on the More_Info pop-up screen for the Lock List display. For more information, see
Lock List Display Screen.
Database
The name of the database in which this transaction is running
Session
The session name running this transaction. Session names beginning with $ are internal transactions.
Status
The status of the transaction. Valid statuses are as follows:
ACTIVE
Active. User transactions are usually in this state. No commit has been issued.
DISTRIBUTED
The transaction is a slave transaction of a larger distributed transaction.
FORCE_ABORT
The transaction is being rolled out because the log file reached the FORCE_ABORT limit.
INACTIVE
Not Active. Internal transactions are usually in this state.
MAN_ABORT
The distributed transaction was manually rolled out.
MAN_COMMIT
The distributed transaction was manually committed.
NOABORT
The transaction cannot be aborted due to FORCE_ABORT or LOG_FILE_FULL. Distributed transactions have this status.
PROTECT
The transaction must be recoverable. User transactions always have this status.
RE-ASSOC
The transaction's connection to the master coordinating application has been lost and the transaction is awaiting reconnection in order to close the transaction.
RECOVER
The transaction has been taken over by the recovery process.
SERVER_ABORT
The server to which this transaction belongs is aborting that transaction.
SESSION_ABORT
The transaction is being rolled out because the session owning this transaction has requested the abort.
WILLING_COMMIT
The transaction is ready to commit. This applies to distributed transactions only.
Write
The number of log file write requests made by this transaction
Split
The number of times a write to the log file was split across more than one log file page and there was not a free buffer. If this occurs frequently, the number or size of the log buffers must be increased to prevent throughput problems to the log file.
Last modified date: 08/14/2024