Skip to Content
Former Member
Oct 08, 2014 at 01:04 PM

Locks/enqueues blocking for 15 minutes due to ABAP runtime error?



we had an issue that whole SAP system was inaccessible for about 15 minutes. In the beginning there were many messages for lock situations and later we couldn't even login into SAP.

Checking on STAD, we found that a user executed transaction VT02N (which generally locks many objects), but the program appeared to be SAPMS380 (this is the program for calling ABAP runtime).

After 15 minutes I see that the same user has runtime error.

Might it be the issue that all these enqueues stayed for so long, because it was trying to call the ABAP runtime error screen, or it is not connected? How can we protect system from similar issues?



2.jpg (33.7 kB)
1.jpg (172.2 kB)
1.jpg (172.2 kB)
2.jpg (33.7 kB)