ENQUEUE Monitoring in SAP

ENQUEUE Monitoring:

·         Go to SM12

·         Specify the username, client and

·         Execute to display the list of lock objects as part of routine maintenance.

We need to ensure that none of the lock should be older than 1 day.

Releasing lock:  User complaints that he could not update a P.O.

·         Go to SM12

·         Check if the lock is obtained on the above transaction.

·         Identify the user and go to SM04

·         Check whether he has logged into system or not.

·         If the user is logged in get the contact details (SU01) and contact him (verbal cal or mail)

à User logs out of the system & the system (GUI) is connected to server communicate with the user & get is approval to delete the session in SM04.

Ensure that black & white (email) is obtain from the user.

ENQUEUE PROBLEMS:

1) The enqueue log table over flow

The Enqueue Process stores logs into enqueue table which is configuring the parameters. If resides on the shared memory of the instance where the enqueue process is installed.

Increase the enqueue table by 8 MB, 12 MB, and 16MB.

2) Enqueue waited response time is increasing.

Enqueue response time should be between 1 to 5 m/sec for the request coming Central Instance. If the request is coming from the Dialog Instance, enqueue response time should not beyond 100m/sec.

If the above trace hold values is crossed that we need to consider increasing enqueue process.

3) DEAD LOCK

            Apart of the transaction let us say ‘A’ is locked by user 1. Which is required by user2? User 2 requires a part of the transaction let us say ‘B’ is locked by user1. In this situation deadlock occurs. Inform the user to logout so that any of them are continued transaction.

Note: As a Basis consultant do not suggest or recommended any of the users to logout or release the locks without approval.

4) While updating a record dialog process gets the transaction ID from number range buffer from the table NRIV. It is possible that there will be no numbers are available in the buffer or NRIV interval is out of range. We need to concern respective business process owners to get a separate range for that object in NRIV.