| Measurement |
Description |
Measurement Unit |
Interpretation |
| Begin_trans |
Indicates the number of transactions initiated with the Begin status by this user. |
Number |
This measure is a good indicator of the current workload of the database server.
|
| Active_trans |
Indicates the number of transactions that are active for this user. |
Number |
|
| Outside_lock_trans |
Indicates the number of transactions initiated by this user that acquired locks from outside. |
Number |
The detailed diagnosis of this measure lists the Transaction ID, Transaction flag, Transaction star time, Duration, Connection ID, Client IP address, Connection start time, Statement type and SQL Text. |
| Dead_trans |
Indicates the number of transactions that are completed by this user but the locks are yet to be released. |
Number |
|
| Prepared_trans |
Indicates the number of transactions that are being prepared for a commit by this user.
|
Number |
|
| Twophase_commit_trans |
Indicates the number of transactions for this user that are in two-phase commit status. |
Number |
Two-phase commit ensures that distributed transactions occur consistently across all databases. Two-phase commit protects against inconsistency by making sure that all databases commit the transaction, or that none commit. To ensure database integrity across all involved databases, the database engine commits database updates in two distinct phases. During the first phase, the database engine checks each database involved in a transaction to verify that it is ready to commit the transaction. During the second phase, the database engine directs the databases to commit the transaction and then verifies that they committed it properly. If there is an inconsistency, the database engine displays error messages and allows you to complete or roll back the inconsistent transaction to return the data to a consistent state. |
| Phase1_trans |
Indicates the number of transactions that are entering phase -1 for this user. |
Number |
Phase 1 indicates that though the transaction is ready to commit it is yet to send a ready to commit response. |
| Phase2_trans |
Indicates the number of transactions that are entering phase 2 status for this user. |
Number |
|
| Ready_to_commit_trans |
Indicates the number of transactions (initiated by this user) that are ready to be committed. |
Number |
|
| Limbo_trans |
Indicates the number of limbo transactions initiated by this user. |
|
A limbo transaction (also known as an in-doubt transaction) occurs if the coordinator database commits or aborts a distributed transaction, but a hardware or software failure prevents other databases from doing likewise. This is called a limbo transaction because the processing of the transaction is temporarily suspended. A limbo transaction might occur for a variety of reasons; for example, as a result of a power outage.
When a limbo transaction occurs, you must resolve the transaction to re-establish data consistency. |
| Active_JTA_trans |
Indicates the number of Java Transaction API (JTA) transactions initiated by this user that are currently active. |
Number |
|
| Idle_JTA_trans |
Indicates the number of Java Transaction API (JTA) transactions initiated by this user that are currently idle. |
Number |
|
| Prepared_JTA_trans |
Indicates the number of Java Transaction API (JTA) transactions initiated by this user that are currently idle. |
Number |
|
| Rollbackonly_JTA_trans |
Indicates the number of JTA transactions initiated by this user were rolled back due to errors encountered. |
Number |
Ideally, the value of this measure should be low. |
| commited_JTA_trans |
Indicates the number of committed JTA transactions that were initiated by this user. |
Number |
|