Table for Lock Objects - SM12

[Former Member]

Hi,

I want to know the table that holds the LOCK OBJECTS that are created. Or any explanation, where lock objects are stored and can be monitored. Recently, there were over 2,000 lock ojects got created which made the our R/3 (4.7) system. What is the best way to monitor this besides SM12.

Thanks

[Former Member]

Hi all,

please use functon module ENQUEUE_READ if you think it would be necessary to read lock table contents.

NEVER use function modules such as ENQUE_READ or ENQUE_REPORT !!!

The ENQUE_READ and ENQUE_REPORT FMs are for internal use only and might be removed or changed without announcement. They only work correcly a special environment which cannot be guaranteed by application programs. They definitely fail in an incorrect environment.

Reading the content of the lock table should be used for monitoring purpose only.

We advise not to implement a locking strategy on the application level which implies the reading of lock table contents. In all likelihood it will be unsafe and cause performance problems. For a safe, fast and scalable solution we advise to use atomic locking operations for check/decide/modify sequences. Use of locks with generic arguments, multi-granule-locks, optimistic locks, etc. are helpful to get a better implementation.

Regards,

Guenter

[Former Member]

Hi Guenter,

Thanks for your response.

What is (and how to use) 'atomic locking operations for heck/decide/modify sequences. '

We are on 4.7.

Thanks

Message was edited by: Naved Rehman