# Information Schema INNODB\_TRX Table
The [Information Schema](https://mariadb.com/docs/server/reference/system-tables/information-schema) `INNODB_TRX` table stores information about all currently executing InnoDB transactions.
It has the following columns:
| Column | Description |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| TRX\_ID | Unique transaction ID number. |
| TRX\_STATE | Transaction execution state; one of RUNNING, LOCK WAIT, ROLLING BACK or COMMITTING. |
| TRX\_STARTED | Time that the transaction started. |
| TRX\_REQUESTED\_LOCK\_ID | If TRX\_STATE is LOCK\_WAIT, the [INNODB\_LOCKS.LOCK\_ID](https://mariadb.com/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_locks-table) value of the lock being waited on. NULL if any other state. |
| TRX\_WAIT\_STARTED | If TRX\_STATE is LOCK\_WAIT, the time the transaction started waiting for the lock, otherwise NULL. |
| TRX\_WEIGHT | Transaction weight, based on the number of locked rows and the number of altered rows. To resolve deadlocks, lower weighted transactions are rolled back first. Transactions that have affected non-transactional tables are always treated as having a heavier weight. |
| TRX\_MYSQL\_THREAD\_ID | Thread ID from the [PROCESSLIST](https://mariadb.com/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-processlist-table) table (note that the locking and transaction information schema tables use a different snapshot from the processlist, so records may appear in one but not the other). |
| TRX\_QUERY | SQL that the transaction is currently running. |
| TRX\_OPERATION\_STATE | Transaction's current state, or NULL. |
| TRX\_TABLES\_IN\_USE | Number of InnoDB tables currently being used for processing the current SQL statement. |
| TRX\_TABLES\_LOCKED | Number of InnoDB tables that have row locks held by the current SQL statement. |
| TRX\_LOCK\_STRUCTS | Number of locks reserved by the transaction. |
| TRX\_LOCK\_MEMORY\_BYTES | Total size in bytes of the memory used to hold the lock structures for the current transaction in memory. |
| TRX\_ROWS\_LOCKED | Number of rows the current transaction has locked. locked by this transaction. An approximation, and may include rows not visible to the current transaction that are delete-marked but physically present. |
| TRX\_ROWS\_MODIFIED | Number of rows added or changed in the current transaction. |
| TRX\_CONCURRENCY\_TICKETS | Indicates how much work the current transaction can do before being swapped out, see the [innodb\_concurrency\_tickets](https://mariadb.com/docs/server/server-usage/storage-engines/innodb/innodb-system-variables) system variable. |
| TRX\_ISOLATION\_LEVEL | [Isolation level](https://mariadb.com/docs/server/sql-statements/administrative-sql-statements/set-commands/set-transaction#isolation-levels) of the current transaction. |
| TRX\_UNIQUE\_CHECKS | Whether unique checks are on or off for the current transaction. Bulk data are a case where unique checks would be off. |
| TRX\_FOREIGN\_KEY\_CHECKS | Whether foreign key checks are on or off for the current transaction. Bulk data are a case where foreign keys checks would be off. |
| TRX\_LAST\_FOREIGN\_KEY\_ERROR | Error message for the most recent foreign key error, or NULL if none. |
| TRX\_ADAPTIVE\_HASH\_LATCHED | Whether the adaptive hash index is locked by the current transaction or not. One transaction at a time can change the adaptive hash index. |
| TRX\_ADAPTIVE\_HASH\_TIMEOUT | Whether the adaptive hash index search latch shoild be relinquished immediately or reserved across all MariaDB calls. 0 if there is no contention on the adaptive hash index, in which case the latch is reserved until completion, otherwise counts down to zero and the latch is released after each row lookup. |
| TRX\_IS\_READ\_ONLY | 1 if a read-only transaction, otherwise 0. |
| TRX\_AUTOCOMMIT\_NON\_LOCKING | 1 if the transaction only contains this one statement, that is, a [SELECT](https://mariadb.com/docs/server/reference/sql-statements/data-manipulation/selecting-data/select) statement not using FOR UPDATE or LOCK IN SHARED MODE, and with autocommit on. If this and TRX\_IS\_READ\_ONLY are both 1, the transaction can be optimized by the storrage engine to reduce some overheads |
The table is often used in conjunction with the [INNODB\_LOCKS](https://mariadb.com/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_locks-table) and [INNODB\_LOCK\_WAITS](https://mariadb.com/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_lock_waits-table) tables to diagnose problematic locks and transactions.
[XA transactions](https://mariadb.com/docs/server/reference/sql-statements/transactions/xa-transactions) are not stored in this table. To see them, `XA RECOVER` can be used.
## Example
```sql
-- session 1
START TRANSACTION;
UPDATE t SET id = 15 WHERE id = 10;
-- session 2
DELETE FROM t WHERE id = 10;
-- session 1
USE information_schema;
SELECT l.*, t.*
FROM information_schema.INNODB_LOCKS l
JOIN information_schema.INNODB_TRX t
ON l.lock_trx_id = t.trx_id
WHERE trx_state = 'LOCK WAIT' \G
*************************** 1. row ***************************
lock_id: 840:40:3:2
lock_trx_id: 840
lock_mode: X
lock_type: RECORD
lock_table: `test`.`t`
lock_index: PRIMARY
lock_space: 40
lock_page: 3
lock_rec: 2
lock_data: 10
trx_id: 840
trx_state: LOCK WAIT
trx_started: 2019-12-23 18:43:46
trx_requested_lock_id: 840:40:3:2
trx_wait_started: 2019-12-23 18:43:46
trx_weight: 2
trx_mysql_thread_id: 46
trx_query: DELETE FROM t WHERE id = 10
trx_operation_state: starting index read
trx_tables_in_use: 1
trx_tables_locked: 1
trx_lock_structs: 2
trx_lock_memory_bytes: 1136
trx_rows_locked: 1
trx_rows_modified: 0
trx_concurrency_tickets: 0
trx_isolation_level: REPEATABLE READ
trx_unique_checks: 1
trx_foreign_key_checks: 1
trx_last_foreign_key_error: NULL
trx_is_read_only: 0
trx_autocommit_non_locking: 0
```
*This page is licensed: CC BY-SA / Gnu FDL*
{% @marketo/form formId="4316" %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://mariadb.com/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_trx-table.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.