Skip to Content

huge number of lock entires in sm12

Apr 13, 2017 at 05:36 PM


avatar image

Users were using below transaction in DIA mode and executing reports during month End:

  1. VL01N : To create the delivery
  2. VL02N: Change Delivery
  3. VT02N for PGI

we found performance issue due to:

->Huge number of lock entries (around 5K to 6K) found in SM12 ( by same user )

-> All DIA/BGD work processes are occupied in few Application servers

->Found few long running jobs, without any progress.

So Please help us to understand, how a single user can make 5000 to 6000 lock entries in production system.

And also, please guide us to prevent this in future.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Jürgen L
Apr 13, 2017 at 06:15 PM

The quickest and best solution is usually to take the phone and call this user and ask him politely what he just did, how he uses his transaction. You can also explain to him what issues you have, the users usually understand, at least it was so when I was faced with this issue some years ago. Beside of educating the users about a better selection there is also a way to restrict the number of hits in case of insufficient selections

See the OSS notes 604473 and 36248, the coding changes are probably already in your system, but you have to set the variable to make it active

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hi Jurgen,

Thank you on the suggestion. When you had faced such issue, were you able to find out on what caused such huge lock entries for the users? Could you share those details.

We are looking out for probably cause and way to prevent them in future.

Arun kumar Rajakani

Sure I was able, the user told me what he did and SAP also confirmed it in the OSS notes.


Thanks. We want to know the probable reasons, which is causing huge number of lock entries in general by single user.

Harish Karra Apr 13, 2017 at 05:53 PM


It could be a system hung situation. Look for long running process by this Id in SM66.

Kill the session if it is not active (Kill if it is just a hung session and doing nothing), Once it is cleared then all WPs will come back into normal mode.

Do additional analysis before you kill/cancel any session, look at the jobs too if it is because of any job then ask user if you can cancel it. If locks are getting generated because of space issue in tablespace then extend the tablespace. Check the status of update processes too.


Harish Karra

10 |10000 characters needed characters left characters exceeded
Jürgen L
Apr 21, 2017 at 05:07 PM

Executing a selection in VT01N without entering selection criteria or insufficient criteria will lock all selected deliveries. Was this not clear from the mentioned OSS notes?

10 |10000 characters needed characters left characters exceeded