3669351 - RECORD_LOCK in NON_KEY_EXCLUSIVE Mode Causes Transaction Rollback in SAP HANA Database

Symptom

In RT dumps, you may encounter blocked transactions, and upon further investigation, you may observe blocked statements "waits for RECORD_LOCK in NON_KEY_EXCLUSIVE mode."

You may also receive a dump with error messages such as: Database error text: "transaction rolled back by lock wait timeout: TrexColumnUpdate failed on table '' with error: transaction rolled back by lock wait timeout: Lock wait time out exceeded [OWNER=16413115804, TYPE=RECORD_LOCK, CURRENT_MODE=NON_KEY_EXCLUSIVE, REQU."

Environment

SAP HANA version 2.0 SPS 06 or higher.

Keywords

HANA, Locks, RECORD_LOCK, Hang, Database, Performance, Freeze, NON_KEY_EXCLUSIVE, Lock wait timeout, Transaction rollback, Concurrent modifications, DML operation, COMMIT, Table size, Job scheduling, Workload optimization , KBA , HAN-DB-PERF , SAP HANA Database Performance , Problem

About this page

This 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.