Skip to end of metadata
Go to start of metadata

How to create an enqueue operations trace?

This section explains a way to create an enqueue trace to analyze all lock operations in an ENSA (standalone enqueue server) instance for ABAP and JAVA enqueue service.
To check enqueue operations for an ABAP stack, follow the note 125041 and create the trace running transaction SM12.

125041  Analysis of enqueue errors with enqueue logging

If you are running a Java Application Server, the enqueue service is handled by an ENSA (standalone enqueue server) named SCS<NR>. To create the enqueue trace for a Java enqueue service you have to run it from Operating System level.
To create the enqueue trace there is a tool called ENQT that is located in the instance exe folder (/usr/sap/<SID>/<instance>/exe).
This is the syntax to enable the trace with ENQT:

enqt pf=< ENSA instance profile path> 81 1 

To disable the trace this is the command:

enqt pf=< ENSA instance profile path> 81 2

The same process works for ABAP standalone enqueue server named ASCS<NR>.

This command enables a trace for the enqueue’s operations, for this reason it is recommended to avoid a trace generation which is longer than 30 seconds which may cause performance problems.
To analyze these enqueue operations check file ENQLOG99 in the instance work folder (/usr/sap/<SID>/<instance>/work).
In the case of a classic enqueue server, each work process on the Central Instance writes its own enqueue log to the file ENQLOGxx.
For further information on this trace see note 125041.



<back to FAQ section>