SAP ABAP Message Class SODQ Message Number 018 (Exclusive TSN not received because object &2 is locked by user &1)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-BW-SRV (Application Component) BW Generation Tool and Set Object
     SODQS (Package) Operational Delta Queue Services
Attribute
Message class SODQ  
Short Description Operational Delta Queue    
Message Number 018  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20130531   
Message Text
Exclusive TSN not received because object &2 is locked by user &1
Help Document

Diagnosis

This application has requested an exclusive TSN (Transaction Sequence Number) but the TSN has not been received. The system tried for seconds to lock object exclusively. However, table was locked by user in a different SAP transaction.

System Response

Once the maximum waiting time of seconds has expired, the system will stop trying to lock object exclusively.

Procedure

Procedure for System Administration

In the lock table (Tools > Administration ==> Monitor -> Lock Entries or Transaction SM12), check which work process has locked object and how long the object has been locked. Check if the process that set the lock is still active. For example, an application process that writes to the delta queue might have set a read lock. Then the process terminates with a core dump, without deleting the lock. In this case, you can delete the lock entry from the lock table manually.

History
Last changed on/by 20140121  SAP 
SAP Release Created in   702