The enqueue log analyzer is a lightweight Java tool used to analyze the SAP enqueue logs. It provides answers to common Enqueue problems and saves your time during root cause analysis for Enqueue issues.
In this blog post, I would like to share the new enqueue log analyzer (KBA 2763999) features with you. Many new functions are introduced since the first release in 2019, and I will show the following important features one by one.
- The new version supports the new format of ENSA2.
- The new version can create an analysis report which could be shared easily and will improve the collaboration (e.g. between basis and application colleagues).
- The new version is more intelligent.
The new version supports the new log format of “Standalone Enqueue Server 2“. The ENSA2 log can be activated via “Request Trace” in SMENQ and is saved on OS level with the name “enq_requests.dat”. We could simply drag and drop the ENSA2 log into enqueue log analyzer, and it will be analyzed the same as the ENSA log.
The analysis report is a simple local HTML file that could be shown in any browser. After the report is created or saved, it could be shared with other people in any way, e.g. an email attachment. Because the report summarizes and aggregates the useful information from both the application’s perspective and the view of the enqueue itself, it will improve collaboration between your customers, colleagues, or friends. For example, if you work in the BASIS area, it will be very handy to share this report with the application experts and discuss with them based on the report instead of the enqueue log.
The following screenshot is an example of what the report looks like.
The analysis report could be created via the “Open Report” button in the GUI or the command line below.
- java -jar EnqueueLogAnalyzer.jar -s <source-file> -d <destination-directory> -f <report-filename>
- The “Open Report” button in the GUI.
Besides supporting ENSA2 and improving the collaboration by the analysis report, the most important change in this release is that the enqueue log analyzer is more intelligent. Now it can not only tell us how many rejects happened on which lock object but also show us the following conclusions.
- Who held the expensive locks and caused the rejects.
- Who triggered the rejected requests. It is the same user with the lock holder?
- Are most of the rejects blocked by one transaction, one user, or several transactions from