![kodu lab kodu lab](https://blog.connectedcamps.com/wp-content/uploads/2018/05/Kodu-Game-Lab.png)
How can I check if my SAP HANA database suffers from lock waits? For example, there can be “ConditionalVariable Wait” situation that are not linked to a record lock or object lock. Record and object locks are mainly linked to the application transactions while read / write locks, semaphores, mutexes and barriers are managed by SAP HANA internally.īe aware that the table above concludes from a lock type to a thread state. _lll_lock_wait / pthread_mutex_lock (Linux kernel lock).Related call stacks (SAP Note 2313619) contain: In addition to these explicit locks there can be some “hidden” lock waits of threads in status ‘Running’.
![kodu lab kodu lab](https://i.ytimg.com/vi/OX3gUZ5r88U/maxresdefault.jpg)
The nameserver topology is locked based on a file (/tmp/.hdb_lock) Locks related to integrated liveCache (if used)
![kodu lab kodu lab](https://i.pinimg.com/originals/97/eb/98/97eb981b60ce2230cd0b5212ec26ed0a.jpg)
Low level transactional memory locks (SAP HANA >= Rev. Low level locks based on semaphores, e.g. Exclusive locks (EXCLUSIVE): Set in case of DDL operations on table and in case of an explicit LOCK TABLE operation.
#Kodu lab update
Shared locks (INTENTIONAL EXCLUSIVE): Set in case of DELETE, INSERT, MERGE, SELECT FOR UPDATE, UPDATE and UPSERT operations on table.Locks on object level, typically caused by DDL operations requiring an object lock: (TableLockWaitCondStat / TransactionLockWaitCondStat) (RecordLockWaitCondStat / TransactionLockWaitCondStat)Įxclusive locks on record level, typically caused by concurrent changes of the same records by different transactions