Scribd
Upload
319 views2 pages

ADSO Request Deletion Fails With: Object &1 ADSO Is Locked by User &2

This article describes an issue where deleting a request from an Advanced DataStore Object (ADSO) fails with errors indicating the object is locked by another user. The cause is a deadlock on the database. The resolution is to follow instructions in HANA note 3139337 to address DML statements failing with 'transaction rolled back by an internal error' after upgrading to HANA SPS06.

Uploaded by

amakirill
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
319 views2 pages

ADSO Request Deletion Fails With: Object &1 ADSO Is Locked by User &2

This article describes an issue where deleting a request from an Advanced DataStore Object (ADSO) fails with errors indicating the object is locked by another user. The cause is a deadlock on the database. The resolution is to follow instructions in HANA note 3139337 to address DML statements failing with 'transaction rolled back by an internal error' after upgrading to HANA SPS06.

Uploaded by

amakirill
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SAP Knowledge Base Article

3213788 - ADSO Request deletion fails with: Object &1 ADSO is locked by user &2
Component: BW4-DM-RSPM (Request Status and Process Management), Version: 2, Released On: 14.11.2023

Symptom
The deletion of a request from an Advanced DataStore Object (ADSO) fails with the following errors:
RSPM001 Process &1 does not exist
RS_EXCEPTION240 Object &1 ADSO is locked by user &2
In the WorkProcess trace file and SM21, during the deletion the following messages are shown:

C *** ERROR => execute() of C_0858, #rec=0, rc=1, rcSQL=129


[dbsdbsql.cpp 2319]
C {root-id=000C296704B31EECB9FB050978C1354A}_{conn-id=00000000000000000000000000000000}_0
C *** ERROR => EXECUTE C_0858 on connection 0, rc=129
[dbslsdb.cpp 10040]
C SQLCODE : 129
C SQLERRTEXT : transaction rolled back by an internal error: Not yet implemented
C sc_p=7fe46b15a8d0,no=858,idc_p=(nil),con=0,act=1,slen=128,smax=768,#vars=4,stmt=7fd64e221e70,ta
ble=RSPMPROCESS
C UPDATE "RSPMPROCESS" SET "CHECK_DIALOG_PROCESS" = ? , "CHECK_BATCH_PROCESS" = ? , "CHECK_ODQ_TA
SKID"\
C = ? WHERE "PROCESS_TSN" = ?;
B ***LOG BYO=> deadlock aborts transaction [dbsh 1241]
B SQL code: 129, SQL text: transaction rolled back by an internal error: Not yet implemented
B ***LOG BY4=> sql error 129 performing UPD on table RSPMPROCESS [dbdbslst 5211]
B ***LOG BY0=> transaction rolled back by an internal error: Not yet implemented [dbdbslst 52
11]

Environment
SAP BW/4HANA 1.00
SAP BW/4HANA 2.00
SAP BW/4HANA 2021
SAP Netweaver 7.50
SAP HANA 2.0 Revisions >= 060.00 (SPS06)

Reproducing the Issue


Delete a request from an ADSO.

Cause
Deadlock on the database.

Resolution
Follow the instructions of the HANA note:
3139337 - DML Statements Fail With 'transaction rolled back by an internal error: Not yet implemented' After Upgrade to
SAP HANA 2.0 SPS06

Keywords
RSPM 001, RS_EXCEPTION 240,
Attributes
Key Value

Other Components BW-WHM-DBA-ADSO (DataStore Object (advanced))

Other Components BW4-DM-ADSO (DataStore Object (Advanced))

Other Components BW-WHM-DST-DTP (Data Transfer Process)

Other Components BW-WHM-DST-RSPM (BW Request Status and Process Management)

Other Components BW4-DM-DTP (ABAP Orchestration of Data Transfer Process)

Requires Action 0

Products
Products

SAP BW/4HANA all versions

SAP HANA, platform edition 2.0

SAP NetWeaver 7.5

You might also like