Re: DB CPU is much lower than CPU Time Reported by TOP SQL consumers

From: Jonathan Lewis <>
Date: Wed, 14 Nov 2012 10:16:24 -0000
Message-ID: <43081CA99CB9456A97C22ECFCD18536E_at_Primary>

One of my points was that you cannot trust the module information to be correct; unless you KNOW that each statement in the top SQL can only be called from EXACTLY one module, you may be misinterpreting the stats. Bear in mind that if SQL calls PL/SQL which calls SQL, you won't see the pl/sql in the statspack report, so the fact that you can only see one pl/sql package call doesn't mean that's the only one causing a problem.

Given my comment about upper case and naming conventions in bind variables I would also like to have seen some comment from you to the effect that you could ignore the double-counting because all the other SQL statements failed to match the pl/sql requirements.


Jonathan Lewis

Author: Oracle Core (Apress 2011)

  • Original Message ----- From: "Ls Cheng" <> To: <> Cc: "Oracle Mailinglist" <> Sent: Wednesday, November 14, 2012 9:49 AM Subject: Re: DB CPU is much lower than CPU Time Reported by TOP SQL consumers

| Hi
| I guess this isnt double counting because the top 1 SQL is a pl/sql
| running from JDBC Thin Client, I have the source code and some sql
| stataments are from this package but other top SQL statements are not
| called from this package, also the module for other top SQL statements
| from C programs.
| Adding up the top sql statements CPU usage not from the package is much
| higher than DB CPU.
| -----
| No virus found in this message.
| Checked by AVG -
| Version: 2012.0.2221 / Virus Database: 2441/5393 - Release Date: 11/13/12

Received on Wed Nov 14 2012 - 11:16:24 CET

Original text of this message