Entering content frameProcedure documentationDeleting Lock Entries Locate the document in its SAP Library structure

Use

Certain problems can result in locks that cannot be released again, with the result that users cannot access the locked objects.

These locks, however, can be deleted manually.

Caution

In general, you should not delete lock entries manually with the deletion functions in lock management. Unreleased locks are almost always a symptom of a different problem. When you solve the problem, the lock entry will be released automatically.

See also: Questions and Answers Regarding Locks

Prerequisites

The most frequent causes of unreleased lock entries:

You can identify locks held by update records in the list of lock entries. The locks held by the V1 part of the update record are highlighted in the list. The backup flag is also set for these logs in the detailed display.

Solution: to determine whether an update problem exists, proceed as follows:

    1. Note the lock key of the relevant lock entry. Select this entry and choose Details to display the transaction code.
    2. Choose Tools ® Administration ® Monitor ® Update (Structure linkUpdate Management) to check whether any unprocessed update records (status init or auto) exist for the user. If you find any unprocessed update records, identify the transaction code and lock key to locate the update record that is holding the lock.
    3. Note that update records with the status err do not hold locks. Locks are released automatically when an update task is terminated prematurely. If you find err update records, follow the procedure described under Structure linkAnalyzing and Rectifying Update Errors.

    4. Check whether your update server is running correctly. Choose Tools ® Administration ® Monitor ® System monitoring ® Servers or transaction sm51. Position the cursor on the application server on which an update server is running and choose Processes to display the work processes on the update server. If open update records exist and the update is running normally, you should be able to see the update processes changing.

If necessary, start the update server by choosing Tools ® CCMS.

Solution: you can release these locks by logging off the user:

    1. Choose Tools ® Administration ® Monitor ® System monitoring ® Servers or transaction sm51.
    2. Display the users of the SAP instance that are specified in the detailed display for the lock entries. Check when the user was last active in the system.

      If the user was not active for a long time, he or she may have shut down the PC without completing his/her work or SAPGUI may have terminated prematurely.

      If possible, contact the user directly. His or her work will be lost when you log him/her off.

    3. If the user's SAPGUI was terminated prematurely, you can log off the user in the user overview. The user cannot request the lost locks again, even if he or she logs on again. In this case, he or she must repeat the work carried out on the locked objects.
    4. If the user simply has not finished his/her work, he/she should be able to complete the work on the locked object normally. His or her work will be lost when you log him/her off.

Caution

Only delete lock entries if you are sure that they are invalid and can be deleted without impairing an active process (user session, update, and so on). Deleting a lock held by active users may result in data loss or inconsistencies.

Procedure

If you want to delete an individual lock entry, position your cursor on the entry and choose Lock entry ® Delete.

By choosing Lock entry ® Delete all, you can delete all the lock entries at once.

A warning is display first indicating the risks associated with deleting lock entries. Following this, a popup is displayed in which you can delete the lock entry.

Note

You can deactivate the warning for the current transaction by choosing Edit ® Suppress warning.

Result

The locks are released and can be requested again.

 

 

Leaving content frame