cancel
Showing results for 
Search instead for 
Did you mean: 

Corrupted lock entries in SM12 - #####

ThomasKjelsrud
Participant
0 Kudos

Hi all,

We are experiencing some corrupted lock entries in SM12, and we are not able to remove them. That is, we can delete them, but after a refresh of the list they return.

This is what we see in SM12:

Cl. User Time Mode Table Lock argument

      1. ############ ##.##.#### E BKPF 300400051200043952006

      2. ############ ##.##.#### E EDIDC 3000000000036124170

      3. ############ ##.##.#### E EDIDC 3000000000040509460

      4. ############ ##.##.#### E LIKP 3000802001938

      5. ############ ##.##.#### E LIKP 3000802215063

      6. ############ ##.##.#### E LIKP 3000802541116

      7. ############ ##.##.#### E MCHA 300000000000000302508310002

      8. ############ ##.##.#### E MCHA 3000000000000003130663100

      9. ############ ##.##.#### E MCHA 300000000000000324127

      10. ############ ##.##.#### E MCHA 30000000000000032456131

      11. ############ ##.##.#### E MCHA 30000000000000032516731

      12. ############ ##.##.#### E MCHA 30000000000000032520531000

      13. ############ ##.##.#### E MCHA 3000000000000003252063100

300 KC 10:18:21 S MARM 300000000000000318669###

300 SSP 10:48:32 S VBAK 300$%&sdbatch

300 SSP 10:48:32 E VBAK 3000060209062

300 FMG 12:16:08 E MARA 300000000000000302698

300 FMG 12:16:08 E MARC 3000000000000003026983100

300 FMG 12:16:08 E MBEW 3000000000000003026983100

300 FMG 12:16:08 E MVKE 3000000000000003026983000

The entries with ###### signs appeared after our disk crash on the SAN which caused the cluster to try to failover, but didn't succeed.

Any ideas on how we can remove these entries from the lock entry list?

Thanks!

Regards,

Thomas

Accepted Solutions (1)

Accepted Solutions (1)

tim_buchholz
Active Participant
0 Kudos

Dear Thomas,

You might want to check the notes 857439 and 1008547.

If you are NOT using a standalone enqueue server, it is likely that the enqueue backup file contains corrupted entries. The right way to proceed would be to make sure that there are no pending update requests and then bring the system down. Delete the file ENQBCK in DIR_LOGGING to get rid of these.

Otherwise it would make sense to open a message on component BC-CST-EQ, since this definitely is an error.

Best Regards,

Tim

Answers (1)

Answers (1)

ThomasKjelsrud
Participant
0 Kudos

Hi again all.

So nobody knows anything about this issue? Just checking.. I am considering an OSS message to SAP, but just making one final attempt to get some input from this forum.

Thanks!

Regards,

Thomas