Symptom
- The program SBAL_DELETE is scheduled as background job and it get cancelled as below:
Internal session terminated with a runtime error DBSQL_SQL_DEADLOCK_DETECTED (see ST22)| 00 | 671 | A | - Category ABAP programming error
Runtime Errors DBSQL_SQL_DEADLOCK_DETECTED
Except. CX_SY_OPEN_SQL_DB
ABAP Program SAPLSBAL_DB_INTERNAL
Application Component BC-SRV-BAL
|Short Text |
| A deadlock has occurred while attempting to access table "BALDAT". |
| Database error number: SQL code: 133 |
| Database error text: "SQL message: transaction rolled back by detected |
| deadlock: TrexColumnUpdate failed on table 'SAPPR1:BALDAT' with error: |
| transaction rolled back by detected deadlock: Local Deadlock detected: owner |
Read more...
Environment
- SAP Netweaver release independent
- SAP S/4HANA release independent
- SAP Application Log
Product
SAP NetWeaver all versions ; SAP S/4HANA all versions
Keywords
db deadlock, application log, sbal_delete, del_app_log_perio, runtime error, dbsql_sql_deadlock_detected, cx_sy_open_sql_db, balhdr, baldats, dynamic variant, log deletion, cleanup job, basis application log. , KBA , BC-SRV-BAL , Basis Application Log , HAN-DB-PERF , SAP HANA Database Performance , 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.
SAP Knowledge Base Article - Preview