Too many sm12 locks and sm13 updates pending in QA system

[Former Member]

HI Friends,

We have lot of locks and updates in QA system  and I want to know from where are thry originatin? Why they are blocked?

This is the details of one of lock:

Client               110
User name            SAPOPS
Table name           VBAK
Lock argument        210$%&sdbatch

Lock Owner
Lock Owner           20140219013017403000002701ERQAS00....................
Host name           ERQAS00....................
SAP System Number    1
Work Process         027
Date                 19.02.2014   01:30:17   403000

Backup flag          X
Transaction Code
Lock Object Name     EVVBAKE
Cumulative Counter   0          1

Please suggest with all possible ways to check.

[Former Member]

Thanks Loy,

Unfortunately we are still unable to find the original job. Any posible ways of other sources of SM12 apart form BG jobs?

[Former Member]

Thanks Deepak & Loy,

I have checked and updates are fine.

SM37 has too many jobs running under SAPOPS. Is there anyway we can narrow this trace-back to find the exact job making this mess?

[Former Member]

Hi,

First check only the active jobs running under SAPOPS.

If they are huge in number then try to get the insert/update command which is running on VBAK (From SM50) which gives you the exact job name.

Regards,

Nick Loy

[former_member188883]

Hi Ramu,

From the SM12 logs you can see that lock entry is generated with user SAPOPS for table VBAK using batch job.

So please check which background job is running under this user. You may check with the user and stop it for a while and monitor the lock entries again.

If the lock table is fine post stopping this job, check with user about details of the job and ask them to fine tune the program.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi,

SM13 - Updates are pending

Check whether you have your "update" active or not?

If it is active, double click on update requests and check where these updates are getting terminated (Check for ABAP dumps). There are several reasons to this, Ex: Inactive update process, unavailability of number range, database related issues, program issues etc.

SM12 - Locks last for a long time

Check whether you have long running processes (Dialog/Background)

If you do not have any long running job, then you may delete the lock entries which are not released by system

Regards,

Nick Loy

[Former Member]

Hi,

To Analyse

In SM13, select the row and click on Update modules button on top.

Then you will get rows of Modules, FM used for the object.

Select the object in error and then press F2 (error info first button).

you will get a  pop up and in that click F6(abap short dump).

Then see what is causing run time errors.

Regards

Sree