mohammadzahid
asked on
SQL Area HIT RATIO
I have a question more like confirmation before adding more memory to shared pool. My statistics on shared pool show output of
sql> select gethitratio from v$librarycache where namespace = 'SQL AREA';
.1684 and is consistence from the last 7 days.
Will adding more memory to shared pool area improve gethitratio of SQL Area?
sql> select gethitratio from v$librarycache where namespace = 'SQL AREA';
.1684 and is consistence from the last 7 days.
Will adding more memory to shared pool area improve gethitratio of SQL Area?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ick! Don't let your developers know those parameters exist! :)
They are a horrible crutch that Oracle invented.
Yes, I'll agree those parameters "sort of" help the bind variable problem.
However, they introduce other inefficiencies, like ignoring constants
that really are constant.
The REAL and ONLY fix is to address the coding practices.
You should be able to go through v$sqlarea and look at the statements you find
and pick out the ones that are the most frequently used.
Then address the top abusers. You may be able to drastically improve your parsing and performance by getting the developers to fix just a few areas of code.
They are a horrible crutch that Oracle invented.
Yes, I'll agree those parameters "sort of" help the bind variable problem.
However, they introduce other inefficiencies, like ignoring constants
that really are constant.
The REAL and ONLY fix is to address the coding practices.
You should be able to go through v$sqlarea and look at the statements you find
and pick out the ones that are the most frequently used.
Then address the top abusers. You may be able to drastically improve your parsing and performance by getting the developers to fix just a few areas of code.
Your developers or vendor (or both) probably aren't using bind variables.