How can transactional lock waits be analyzed?

If a high number of transactional (record and object) lock waits exist, but at the same time there are also many semaphore and mutex waits, we can usually assume that the record and object lock waits are a consequence of the mutex and semaphore waits. In this case you should focus on the analysis of mutex and semaphore waits (see below). Otherwise you can use the following approaches to analyze transactional lock situations.

Current lock wait situations are visible as blocked transactions:

• View M_BLOCKED_TRANSACTIONS
• SQL: "HANA_Locks_Transactional_LockWaits_Current" (SAP Note 1969700)
• SAP HANA Studio: Performance -> Blocked Transactions
• DBACOCKPIT: Diagnostics -> Locks -> Blocked Transactions
   

Historic lock wait situations can be found in the related history table:

• View HOST_BLOCKED_TRANSACTIONS
• SQL: "HANA_Locks_Transactional_LockWaits_History" (SAP Note 1969700)
• SQL: "HANA_LoadHistory_Services" (SAP Note 1969700)