The general HANA database transactional lock wait timeout (affecting table locks, row/record locks) is configured via parameter:
indexserver.ini > transaction > lock_wait_timeout = 1800000 (default value in ms, respectively 1800s, 30min)
However, lock wait timeout error for DDL statements related to dynamic range partitions like below are reported in indexserver trace just after 10sec, instead of expected 1800s:
<timetamp> e TableLock WaitGraph.cc(01184) :
Lock-wait time out exceeded
- Waiting transaction
[CONNID=<>, SESSIONID=<>, CLIENT_HOST=, CLIENT_IP=, CLIENT_PID=<>, DBUSER=<>, ID=<>, UPDATE_TRANSACTION_ID=<>, TYPE=<>, STATE=<>, ISOLATION_LEVEL=<>, LOCK_TIMEOUT_MS=10000]
<timestmp> e partitioning DynamicRange.cpp(00647) : SQL preparation or execution of
'ALTER TABLE "<schema_name>"."<>table_name" ADD PARTITION FROM OTHERS' failed:
transaction rolled back by lock wait timeout: Lock-wait time out exceeded
ERROR [SQL-131] transaction rolled back by lock wait timeout: Lock-wait time out exceeded
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
SAP HANA 2:
- Revisions >= 056 (SPS05)
LOCK_TIMEOUT_MS=10000, dynamic range partition, timeout, SQL-131, lock , KBA , HAN-DB , SAP HANA Database , Problem
About this pageThis 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.