SAP Knowledge Base Article - Preview

3218476 - How-To: Troubleshooting SAP HANA Blocked transactions that happened in the past


You would like to know the root cause of the blocked transactions that is currently not occurring, but was blocked in the past.

Tools such as the Performance Monitor, system views and the SQL Plan Cache are available to help you.


The Performance Monitor opens displaying the load graph for the selected resource: CPU, disk, or memory. The load graph initially visualizes resource usage of all hosts and services listed on the left according to the default KPI group of the selected resource.

You can access the Performance Monitor on the Database Overview page, with the Monitoring or All view selected, you access the Performance Monitor page by clicking the title, the graph, or Monitor Performance on the following cards:

- Memory Usage
- CPU Usage
- Disk Usage

You can also click the Monitor Performance link on the Monitor card.


For the SQL Plan Cache view to get an insight into the workload of the database as it lists all statements currently cached in the SAP HANA database.

You can access to it On the Database Overview page, with the Monitoring or All view open, click the title or View all on the SQL Statements card to open the SQL Statements page.

Select the SQL Plan Cache tab.



SAP HANA, platform edition


SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0


Blocked transaction, HANA, Performance, SQL, Plan cache, wait situation, monitoring, lock_wait, statement, root cause,  , KBA , HAN-DB-PERF , SAP HANA Database Performance , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.