Query Unjustified High Execution Time Might Actually Be Spent In PL/SQL Mode (Doc ID 3048930.1)

Last updated on NOVEMBER 10, 2024

Applies to:

Symptoms

SQL statement exhibits high execution time, but it is not very clear from where the execution time could actually come.

For example, you've taken a 10046 trace file and the execution time doesn't add up. An example of this, below. Notice 28K seconds from the "Execute" section. The actual plan lines however, only indicate 1798 seconds of execution time. Unfortunately there is no hint of where the rest of the time is being spent. It is not in the Wait Times section either.

Changes

No changes, this can apply to any SQL Statement in any version

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.