The query corresponding to each monitoring element to check transaction and lock information is as follows.
| Column | Description |
|---|---|
| TX_ID | Transaction ID |
| BLOCKED_TX_ID | The transaction ID that caused the wait to acquire the lock. Blank if none. |
| STATUS | A number from 0 to 6 indicating the status of the transaction is displayed as a string. BEGIN (0), PRECOMMIT (1), COMMIT_IN_MEMORY (2), COMMIT (3), ABORT (4), BLOCKED (5), END (6) |
| USER_NAME | The name of the user executing the transaction, and is displayed as 'REPLICATION' in the case of a replication transaction. |
| SESSION_ID | ID of the session in which the transaction is being executed. In the case of a replication transaction, the replication object name is displayed. |
| CLIENT_IP | The IP address of the client application related to the session. In the case of a replication transaction, it is the IP of the remote server. |
| FIRST_UPDATE_TIME | The time when the transaction first started changing operations. The transaction that only execute SELECT are 0. |
| LOCK_DESC | If the lock is set by the transaction, lock information is output. There are IX_LOCK, IS_LOCK, X_LOCK |
| TABLE_NAME | The table to acquire the lock. This is displayed in the form of 'username.tablename'. |
| CURRENT_QUERY | The query last executed or currently being executed in a transaction. In the case of a replication transaction, it shows the IP address and transaction ID of the other server. |
| DDL | Whether the transaction is DDL. / DDL (0) non-DDL (1) |
| LOGFILE# | The redo log file number associated with the transaction. A transaction that only performs SELECT is '-'. |