Skip to main content

Unlock the Power of SAP HANA Performance Optimization: A Comprehensive Guide for SAP Basis Administrators [Part 2 : Deep Dive ]

In SAP systems, the performance of the underlying database plays a crucial role in delivering a seamless user experience. SAP HANA, being an in-memory database, offers exceptional speed and agility. However, it's essential to monitor and troubleshoot potential performance bottlenecks to ensure optimal system performance. In this blog post, we will explore key areas to focus on when monitoring the SAP HANA database and provide examples of how to identify and address common performance issues.


  1. Threads in the SAP HANA database represent individual tasks that execute concurrently. Monitoring thread utilization helps identify any thread-related issues, such as high thread utilization or thread exhaustion. You can use the M_SERVICE_THREADS table to gather information about active threads and their status. For example, a high number of waiting threads may indicate resource contention or blocking situations that require investigation and optimization

    1. To retrieve  thread based on SQL queries : SELECT * FROM M_SERVICE_THREADS WHERE SQL_STATEMENT_ID = '<SQL_STATEMENT_ID>';

    2. Obtain the transaction ID of the specific transaction you are interested in. You can find this information in the M_TRANSACTIONS table.

  1. Use that statement id to check the threads associated.


  1. Sessions in the SAP HANA database represent connections established by users or applications. Monitoring sessions allows you to understand the system's workload and identify any potential performance issues related to session management. The M_SESSIONS table provides insights into active sessions, including user information, SQL statements being executed, and resource consumption. By analyzing session-related metrics, such as active sessions and response times, you can pinpoint potential areas of improvement.



  1. Blocked transactions occur when one transaction is waiting for a resource held by another transaction. Monitoring blocked transactions helps identify concurrency issues and optimize transactional throughput. The M_LOCKS table provides information about locks and lock waits in the SAP HANA database. By analyzing the lock information, you can identify blocking situations and take appropriate actions to resolve them, such as optimizing transaction isolation levels or redesigning data access patterns.

  • Query to select all object that needs to be acquired by A transaction 


  • Query to select which session is holding a particular object say ‘YUT’


  1. The SQL Plan Cache in SAP HANA stores execution plans for SQL statements executed in the database. Monitoring the SQL Plan Cache allows you to analyze the efficiency of SQL execution and identify potential performance bottlenecks. The M_SQL_PLAN_CACHE table provides information about SQL execution plans, including plan reuse, plan hits, and plan evictions. By identifying inefficient or missing execution plans, you can optimize SQL statements and improve overall query performance.

  • Query to select the statement id from M_TRANSACTIONS


  • Query to check the exact plan there


  1. The Expensive Statement Trace feature in SAP HANA helps identify SQL statements consuming significant system resources. By enabling and analyzing the trace output, you can identify expensive queries and optimize their execution. The M_EXPENSIVE_STATEMENT_STATISTICS table provides details on the execution times and resource consumption of expensive SQL statements. By tuning or redesigning these statements, you can reduce resource consumption and improve overall system performance.


Sample output 



1024         | 5634           | 4213     | 1421      | 0       | 98234           | 2023-05-15 10:23:56 | 2023-05-15 10:23:56 |

2156         | 4521           | 3258     | 1263      | 0       | 87915           | 2023-05-15 12:45:19 | 2023-05-15 12:45:19 |

9876         | 3987           | 2876     | 1111      | 0       | 76981           | 2023-05-15 15:32:42 | 2023-05-15 15:32:42 |


If you get the hash value associated here , you can use that to check in M_SQL_PLAN_CACHE ( information about the SQL execution plans ) and M_SQL_PLAN_CACHE_STATEMENTS (information about individual SQL statements in the SQL plan cache)

  1. Monitoring job progress in the SAP HANA database helps ensure timely completion of critical tasks and identifies any potential issues impacting job performance. The M_JOB_PROGRESS table provides information about the progress and status of running jobs. By monitoring job progress, you can identify long-running or stuck jobs, analyze potential dependencies or resource constraints, and take corrective actions to ensure job completion within the desired timeframe.

Don’t Get confused here The background jobs in SAP HANA are defined and managed through the Job Scheduler framework, which includes the SYS.JOBS table. This table stores information about the background jobs, including their names, schedules, status, and other relevant details this is not the SAP BACKGROUND JOBS.

Scheduled backups in SAP HANA are not managed through the Job Scheduler framework or reflected in the SYS.JOBS table. The Job Scheduler is primarily responsible for executing scheduled tasks, but it does not handle the scheduling and execution of backup operations.

  1. Monitoring the load on the SAP HANA database helps assess its capacity and identify any potential performance constraints. The M_SERVICE_MEMORY and M_HOST_RESOURCE_UTILIZATION tables provide insights into resource consumption and system load. By monitoring memory, CPU, and disk utilization, you can identify periods of high load and optimize resource allocation to ensure optimal performance.




Proactively monitoring and troubleshooting performance issues in the SAP HANA database is crucial for maintaining a high-performing SAP system. By focusing on threads, sessions, blocked transactions, SQL plan cache, expensive statements, job progress, and system load, you can identify potential bottlenecks and optimize performance. Implementing these monitoring techniques and taking appropriate actions will help ensure optimal system performance, enhance user experience, and maximize the benefits of SAP HANA's in-memory capabilities.


You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont