Object being locked by other user
Issue:
Step 1: The chain failed at DTP step due to Object being locked by other user.
Step 2: To read the failure message right click on the failed step and select Displaying Messages.
- The Failure message highlighted in Screenshot 1 describes that the object ODSO ****** is locked by another User (ALEREMOTE in this case).
- An exclusive lock on the object is present.
- This occurs when the object is being used by other user to update the content to the DSO and at the same time the DTP of the failed process chain runs trying to access the same object to update contents.
Exclusive locks: refers to a row or a table. Once an exclusive lock is assigned to transaction for a particular database object, other transactions cannot modify this object.They can be owned by only one transcation at a time.Any transcation that requires an exclusive lock must wait if another task currently owns an exclusive lock or a shared lock against the requested resource.
Solution:
Step 3: Navigate to SM12 to check if the lock still exists on the object, attached screen shot 2 appears where you enter the user name which has locked the content.
Step 4: Based on the user name the contents locked by that user appears. In the screen shot 3 it is observed that lock on object ODSO ***** does not exist. This indicated that the lock has been released by this user and the object is available for use.
If the lock still exists,Click on the row that holds the lock and click delete lock button (Top) to release the lock.
Note:If the lock is released forcefully then there is a chance for the loading step to fail if it uses the lock.
Step 5: Right click on the failed DTP step and repeat the process once the lock is released.