Explanation

The time needed by the specified user tasks to execute the statements is very long. You see the average execution time of a statement, the number of statements checked, and the process ID of the relevant application process.

Whether this counts as a bottleneck depends on the application structure.

Mass statements in background processes can often cause long runtimes. As well as this, situations such as locks in SQL objects, physical reads and writes, or dispatching caused by the prioritization of other tasks, can cause internal kernel wait situations that increase runtimes.

If, in SAP liveCache databases, a DB procedure takes a long time to execute, it is highly likely that other users are being blocked in the same SAP liveCache thread. This can cause unexpectedly long runtimes for other transactions or DB procedures.