HANA Transactions Test

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 HANA Transactions 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.

Target of the test : A SAP HANA Database Server

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every transaction type on the SAP HANA database server being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

The host for which the test is to be configured.

Port

The port number at which the specified Host listens to. By default, this will be 30015.

User

In order to monitor a SAP HANA database server, a special database user account with Monitoring privileges has to be created in every SAP HANA database instance that requires monitoring. The syntax of the script that is used for user creation is discussed in How to Monitor SAP HANA Database Server Using eG Enterprise?.

The name of such a user has to be specified here.

Password

Enter the password of the specified User.

Confirm Password

Confirm the password by retyping it here.

IsPassive

If the value chosen for this parameter is Yes, then the SAP HANA database server under consideration is a passive server in a SAP HANA cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

Exclude Transaction Type

Specify a comma-separated list of transaction types that need to be excluded from the scope of monitoring in this text box. By default, none is specified here.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Open Transactions

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 of the database server.

Oldest Transaction

Indicates the maximum time that a transaction of this type took to execute.

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 name of the transaction, the type of the transaction, the time duration of the transaction, and the memory utilized by the transaction, thus shedding light on long-running and resource-intensive transactions.