

It is possible to delete the locks from T-Code SM12 but it is not recommended instead the users can be logged off from SM04 which automatically releases the lock.ĥ. But the locks held by a BTC process during batch processing can consume more than one hour or even days.Ĥ.

As a part of monitoring locks held by dialog process should not be more than one hour. The locks which are held for more than 12 hours are documented into checklist and escalated to next level.ģ. If more than one dialog instances are configured then the enque time can go up to 100ms(if it goes beyond then turn on the enque trace for RCA(ROOT CAUSE ANALYSIS))Ģ. Generally the enque time on the Central Instance is 1ms to 5ms. Message server obtains the lock from enque process and provides to dialog process. The Dialog Process communicates with message server and message server in turn communicates with enque process to obtain lock on behalf of the dialog process.
#Java enqueue update#
If the update request is made through an application server. When dialog identifies update then it communicates with enque process to obtain lock on the record, so that no other user modifies it and has only a display access. Based on freely available Dialog process, the dispatcher allocates a process to user request.Ĥ. The request is received by dispatcher and keeps it in wait queue.ģ. User submits the request for an update.Ģ. Generally enque processes are configured on the Central Instance (to communicate with message server)Įnque replication servers are installed in an high availability system to replicate the locks between the instances (nodes).ĮRS is installed on all the nodes and lock replication table gets replicated from Central Services lock tables.ġ.

This table resides in the main memory of the instance where enque processes are configured. Enque locks are stored in enque table which is configured by parameter Enque processes are configured by using parameter.Įnsure the enque process is configure on the CENTRAL INSTANCE to store the Enque Table. It is possible to configure more than one enque process in a massive update system. By default one enue process is installed along with Message Server. It is used to enque/deque (lock/unlock) the objects during an update.
