on 06-22-2007 6:38 AM
hi all,
I have seen lock entries in sm12. tables are ATPENQ,VBAK. so what should i do?
please help in this regard.
regards
praveen
The purpose of lock management is to monitor the lock logic of your system. You can determine the locks that are currently set. Locks for which the backup flag is set (because they have already been transferred to the update task) are highlighted.
This enables you to detect and rectify problems, for example, by deleting locks that are no longer required.
You can display lock entries according to the following criteria
Table in which rows are locked
Lock entry argument
Client
User who set the lock
This corresponds to the entries in the lock table.
The lock entries are shown in different colors:
Blue means that the locks have already been transferred to the update task, with the result that the backup flag is set. These locks are also rewritten to the lock table when the enqueue server is restarted.
Black means that the lock (still) belongs to the dialog owner. The backup flag is not set.
By choosing Edit - > Sort by, you can display the locks according to user, time, table, or host system (host).
By double-clicking a lock entry, you can display detailed information, including the host name and number of the SAP System in which the lock was generated.
What should you do first if a problem arises?
Use the diagnosis functions:
sm12 Extras - >Diagnosis and then
sm12 Extras - >Diagnosis in update
If a problem is reported, back up the trace files dev_w, dev_disp, dev_eq and check the Syslog.
Hope this would help you in understanding SAP lock management.
Pls Reward points if useful.
Regards
Sree
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If there is lock entries over 24hrs old, they must be investigate.
1.Double click on the process, which is over 24hrs old
2.Look for the HOSTName, and Work Process.
3.Go to SM51
4.select the server which has the lock, and look for the workprocess in question.
5.If the process is still active DONOT REMOVE FROM SM12.
6.If the process is no longer active, Remove the lock from sm12.
Note: Points always encourage me to reply !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Praveen,
Check with the user are running any background jobs.
If Not you can delete the lock entires.
Regards]'
gangadhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.