3770539 - SM21 logs shows 'Database error 133 with INS access to table 'Table Name' during DTP Data Load

Symptom

After enabling Transactional deadlock runtime collection:

Transactional deadlocks

1999998

<service>_<host>.<port>.rtedump.<timestamp>.<pid>.deadlock.trc

>= 2.00.060

This runtime dump is generated when a transactional deadlock happens. It can be activated / deactivated with the following parameter (default: false, i.e. inactive):

indexserver.ini -> [transaction] -> enable_runtime_dump_on_deadlock

The minimum interval between two runtime dumps is controlled with the following parameter (default: 600, unit: s):

indexserver.ini -> [transaction] -> runtime_dump_on_deadlock_period

Below were the traces recorded:

Indexserver deadlocks also present, as it was captured before :

indexserver_xxxx.30503.770.trc

[2854684]{-1}[530/-1] 2026-06-02 18:30:08.332692 e partitioning DynamicRange.cpp(00928) : SQL preparation or execution of
'ALTER TABLE "SAPBSP"."xxxx DROP EMPTY PARTITIONS'
failed:
transaction rolled back by lock wait timeout: Lock-wait time out exceeded [OWNER=11134225003, TYPE=OBJECT_LOCK, CURRENT_MODE=INTENTIONAL_EXCLUSIVE, REQUESTED_MODE=EXCLUSIVE], owner's lockMode: INTENTIONAL_EXCLUSIVE, transID: 11134225003 at ptime/storage/cc/lock/ObjectLockManagerImpl.cpp:165
ERROR [SQL-131] transaction rolled back by lock wait timeout: Lock-wait time out exceeded [OWNER=11134225003, TYPE=OBJECT_LOCK, CURRENT_MODE=INTENTIONAL_EXCLUSIVE, REQUESTED_MODE=EXCLUSIVE], owner's lockMode: INTENTIONAL_EXCLUSIVE, transID: 11134225003 at ptime/storage/cc/lock/ObjectLockManagerImpl.cpp:165

indexserver_xxxx30503.rtedump.20260602-003322.0095407.deadlock.trc

SQL:
ALTER TABLE "SAPBSP"."xxxx" ADD PARTITION FROM OTHERS
STATEMENT-HASH: 8eebd3xxxxxxxxxxx8e0c87
STATEMENT-TRANSTOKEN: Newdb::TransToken CONTENTS - 0x00fffef8911f5200 [utid=-11131730384 cid=0 flashback_cid=0 stmt_seq=3 cloned=0 seriailzed=0 ptime_trans_refcounted=0 txsavepoint_enabled=0 subtx_id=(3,3,3587734) subtx_scope=0 subtx_parallel=0 pallel_scope=(0,0,0,0,0) parent_trans=(-1,-1,-1,-1) isolevel=1 forced_rc=1 lock_timeout=-1 used_for_ult= 0 flag_data=4112 this=0x00fffef8911f5200 parent=0x00fffbe2b5a75800 snapshot_token=0x00fffb21c3d6d2c0 trans=0x00fffbe2b6629000 stmt=0x00fff8d462f41c00]
}

{
SQL:
ALTER TABLE "SAPBSP"."xxxx ADD PARTITION FROM OTHERS
STATEMENT-HASH: 8eebd3xxxxxxxxxxx8e0c87
STATEMENT-TRANSTOKEN: Newdb::TransToken CONTENTS - 0x00fffef8911f5200 [utid=-11131730384 cid=0 flashback_cid=0 stmt_seq=3 cloned=0 seriailzed=0 ptime_trans_refcounted=0 txsavepoint_enabled=0 subtx_id=(3,3,3587734) subtx_scope=0 subtx_parallel=0 pallel_scope=(0,0,0,0,0) parent_trans=(-1,-1,-1,-1) isolevel=1 forced_rc=1 lock_timeout=-1 used_for_ult= 0 flag_data=4112 this=0x00fffef8911f5200 parent=0x00fffbe2b5a75800 snapshot_token=0x00fffb21c3d6d2c0 trans=0x00fffbe2b6629000 stmt=0x00fff8d462f41c00]
}

Environment

SAP HANA PLATFORM EDITION 2.0

Product

SAP HANA, platform edition 2.0

Keywords

Partitioning, SQL error 133, SM21, DTP, Data load, Dumps , KBA , HAN-DB , SAP HANA Database , 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.