cancel
Showing results for 
Search instead for 
Did you mean: 

Not able to delete lock entries

Former Member
0 Kudos

Hi

I have a problem in deleting old locks. In SM12 I see some lock entries in SM12 because of this there are updates waiting in SM13. When We try to delete these entries, these are not getting deleted. Why this happens and in this situation how to delete these entries?

Thanks in advance

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I think the reason for the issue is that the lock entries are corrupted

Please refer to the note 19306 which mentions about this.Though the not

is applicable to the release 30F, it can aslo be applicable to the

later releasese.

  1. 19306 - Enqueue lock entries with #### fields

Please perform the recommendations provided.You can also perform the

recommendations provided in the note 857439.

  1. 857439 - Locks without lock owners are not removed.

Best Regards,

Aditya.

Former Member
0 Kudos

Adithya

Note 19306 is not available on market place.

Former Member
0 Kudos

Adithya

Note No. 857439 was applied and problem solved. Now there are no old lock entries exists in the system

Points given

Answers (4)

Answers (4)

Former Member
0 Kudos

Following is the display of SM12 lock entries

100 PCSDEVL 25.09.2008 E MBEW 100ÐÏ À¡± Á##########0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100#### #SHEET1u2026# #` 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100##Q ##C #C ######0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100##### #####Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# ### # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # # ###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # #!###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # #"###~ 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # ##### # # 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # #####Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # #$###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # #%###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # #&###Ý# 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # #$###~ 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MARA 100# # # ##Ò¾@×# #~ # 0 1

100 PCSDEVL 25.09.2008 E MARC 100# # # ##Ò¾@×# #~ #0001 0 1

100 PCSDEVL 25.09.2008 E MBEW 100# # # ##Ò¾@×# #~ #0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MVKE 100# # # ##Ò¾@×# #~ #000101 0 1

100 PCSDEVL 25.09.2008 E MBEW 100##################0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### ### ### 0001@@@@@@@@@@ 0 1

100 PCSDEVL 25.09.2008 E MBEW 100### ### ### ###Þu0178u01780001@@@@@@@@@@ 0 1

Former Member
0 Kudos

I tried executing Temse check as per link. But still locks exists in SM12

JPReyes
Active Contributor
0 Kudos

because of this there are updates waiting in SM13

4 months???...I don't think this updates are suppost to be waiting.... do a TEMSE consistency check and remove inconsistencies. Then check again SM12 to see if the locks are still there.

regards

Juan

Former Member
0 Kudos

Dear Vitthal,

I second that. Check the following link for procedure:

http://help.sap.com/saphelp_nw70/helpdata/en/fc/04ca3bb6f8c21de10000000a114084/content.htm

Regards,

Veera

Edit:

By the way can you share more details on the lock entries? This may help zeroing in on the problem.

Edited by: Veeraraagavan R on Jan 7, 2009 1:42 PM

Former Member
0 Kudos

Dear Vitthal,

Did you try deleting/terminating the respective user's session using sm04?

Regards,

Veera

Former Member
0 Kudos

Veera

These lock entries are 4 months old?