real quick thought from mostly a lurker
Your soft parsing % probably indicates what you suspected
in string literals.The % of your physical reads is way
to high versus logical reads.Check you SQL area and see
if their are any obvious dogs in there. Your second wait
latch free
For a Hybrid Banking Application , following waits are Observed :-
Oracle ver 9.2 (Dedicated Server connections)
Solaris 8
M/c SF15K
Application mostly uses Static Queries (i.e. with Bind variables) ,
though there may be some amount of Literal SQLs too
DB Size = 250 GB
Qs How may the following
Application - Hybrid Banking Application
Oracle ver 9.2 (Dedicated Server connections)
Solaris 8
M/c SF15K
Application mostly uses Static Queries (i.e. with Bind variables) ,
though there may be a small amount of Literal SQLs too
DB Size = 250 GB
Qs How may the following waits be
Increase shared pool.
VIVEK_SHARMA wrote:
For a Hybrid Banking Application , following waits are Observed :-
Oracle ver 9.2 (Dedicated Server connections)
Solaris 8
M/c SF15K
Application mostly uses Static Queries (i.e. with Bind variables) ,
though there may be some amount of Literal
How about also looking at pinning procedures, or even tables (if small and
you have enough memory) in to the library cache too? Look for the for those
that have a high execute/parse ratio..
Get PctPinPct
Invali-
Namespace Requests Miss
