HANA Blocked Transactions Test

When a transaction attempts to access a database object that is already being used by another transaction, a transaction block occurs, whereby the original transaction blocks/prevents the subsequent transaction from executing on the server. If the block is not identified and released in time, then the user experience with the server will suffer! Administrators should hence be able to quickly identify blocked transactions, analyze which transactions are blocking them and why, and endeavor to clear the block quickly, so that users can continue interacting wih the server without any interruptions. This is where the HANA Blocked Transactions test helps. For every transaction type, this test reports the number of transactions of that type that are currently blocked and provides detailed diagnostics related to such transactions, so that administrators can rapidly identify the blocked transactions, accurately analyze its root-cause, and promptly remove the block.

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 in 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

Blocked Transactions

Indicates the number of transactions of this type that are currently blocked.

Number

Ideally, the value of this measure should be zero. A gradual increase in the value of this measure is a cause of concern, as it indicates a consistent rise in blocked transactions. This calls for immediate action.

The detailed diagnosis capability, if enabled lists all the blocked transactions and the users who have initiated those transactions. Using this detailed diagnosis, you can figure out the root cause of the blocking.