The application code is issuing a parse call 3 times. Taking the example of
the DBMS_SQL package, if you call the PARSE procedure three times for three
executes, you'll see three parses accounted for in the SQL Trace file. Some
of them might be soft parses, but SQL Trace (and TKPROF) still
If you don't want to change your application, get the application booster
from oraperf. That will do it for you ;-)
Setting up one environment variable and run again, this time much faster
..
Anjo.
- Original Message -
To: "Multiple recipients of list ORACLE-L" [EMAIL PROTECTED]
...Because the application requested two parse calls for this statement
from the server. The first one was a hard parse (server had never seen
the statement before), and the second one was a parse call that did not
result in a hard parse.
Cary Millsap
Hotsos Enterprises, Ltd.
Cary Millsap£¬
As for the soft parse, it also consumes cpu , how can we eleminate the
softparse?
Thanks.
2002-07-22 08:58:00 You wrote:
...Because the application requested two parse calls for this statement
from the server. The first one was a hard parse (server had never
Change the application so that it doesn't parse twice. See
www.hotsos.com/dnloads/1.Holt,Millsap2000.03.01-Scaling.pdf for details.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Upcoming events:
- Hotsos Clinic, Jul 23-25 Chicago
- Miracle Database Forum, Sep 20-22 Middlefart
If this statement is a loop and the counter works atleast twice, it would
show 2 parse calls and 2 executions. You should basically put this statement
in the main class and just bind the variables in the callable classes and
just execute the statement.
In this way it would be 1 parse call and
