In the Solution Manager System, in transaction ST22, the following dump is found:
Runtime Errors DBSQL_SQL_ERROR
Date and Time 11.02.2018 19:25:59
SQL error "SQL code: 133" occurred while accessing table "AGSDVMAS_LOG".
Database error text: "SQL message: transaction rolled back by detected
deadlock: TrexUpdate failed on table 'SAPABAP1:AGSDVMAS_LOG' with error:
transaction rolled back by detected deadlock: Deadlock detected while
executing transaction (TRANSACTION_ID=36, UPDATE_TRANSACTION_ID"
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'CX_SY_OPEN_SQL_DB' and was not caught in
"AGSDVMAS_LOG_ADD" "(FUNCTION)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated this
exception, the current program was terminated.
Information on where terminated
The termination occurred in ABAP program "SAPLAGSDVMAS_SELF_SERVICE", in
"AGSDVMAS_LOG_ADD". The main program
In the source code, the termination point is in line 25 of (Include)
Program "SAPLAGSDVMAS_SELF_SERVICE" was started as a background job.
The termination is due to exception "CX_SY_OPEN_SQL_DB" occurring in procedure
2 FUNCTION SAPLAGSDVMAS_SELF_SERVICE LAGSDVMAS_SELF_SERVICEU13 25
1 EVENT AGSDVMAS_CONTROL AGSDVMAS_CONTROL 151
>>>>> INSERT INTO agsdvmas_log VALUES ls_log.
>>>>> INSERT INTO agsdvmas_log VALUES ls_log.CTION)".
SAP Solution Manager 7.2 SP06
DBSQL_SQL_ERROR, AGSDVMAS_CONTROL, ST22, SAPLAGSDVMAS_SELF_SERVICE LAGSDVMAS_SELF_SERVICE, SQL code: 133, agsdvmas_log VALUES ls_log , KBA , SV-SMG-DVM , Data Volume Management , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.