Hello Friends,
What happens in case of deadlocks in SAP HANA? If anyone know the complete scenario then please explain that here.
Thank You.
Deadlocks in SAP HANA
Updated May 19, 2018
Comments
Recommended Posts:
- What is SAP HANA
- SAP HANA Training Tutorials for Beginners
- SAP HANA In-Memory Database
- SAP HANA Database Architecture
- SAP HANA Modeling Guide
- Rename HANA Schema
- SAP HANA Sidecar
- SAP HANA Calculation View
- SAP HANA Hints
- SAP HANA Excel Integration
- SAP HANA vs S/4HANA
- SAP HANA SQL Operators
- SAP HANA Data Provisioning
- SAP HANA Persistence layer
- SAP HANA Replication Modes
- SAP HANA DXC
- SAP HANA License Types
- SAP HANA Audit
- SAP HANA Interview Questions
- SAP HANA Certification Cost in India
×
Deadlocks are situations where two or more transactions lock each other cross-wise so that no transaction will ever be able to proceed. If SAP HANA recognizes a deadlock (typically in combination with record locks), one of the transaction will be terminated and the following error is issued:
SQL error 133: transaction rolled back by detected deadlock
This behavior is different from other databases like Oracle where a deadlock will only terminate the current DML operation and not the whole transaction.
Read Here about How to check if SAP HANA database suffers from lock waits?