Measures reported by HanaTransactTest
Long-running transactions to the SAP HANA database server not only keep critical resources and database objects locked for indefinite time periods, but they can also prevent execution of other transactions, thereby degrading the overall performance of the database server. It is hence imperative that such transactions are rapidly isolated and killed. The HanaTransactTest test makes this possible!
For each type of transaction, this test reports the number of transactions that are currently open and the maximum time taken for executing transactions. Using this test, you could figure out which transaction is taking too long to execute and is currently blocking other transactions.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| openTranasctions |
Indicates the total number of transactions of this type that are currently open in the SAP HANA database server. |
Number |
This measure is a good indicator of the current workload on the database server. |
| oldestTransTime |
Indicates the maximum time taken for execution of a transaction of this type in the SAP HANA database server. |
Secs |
A low value is desired for this measure. A gradual/sudden increase in the value of this measure is a clear indicator that some transaction is taking too long to execute. This is a cause for concern, as such transactions can block other transactions from executing on the server and can even cause server performance in general to deteriorate. Under such circumstances, you can take the help of the detailed diagnosis of this measure to identify the long-running transactions. The detailed diagnosis lists the the name of the transaction, the type of the transaction, the time duration of the transachetion, and the memory utilized by the transaction, thus shedding light on long-running and resource-intensive transactions. |
|