My SQL Area has really bad performance.
Everything else looks GREAT. How can I tune ONLY the Sql Area? My shared pool sizing seems right on. Just the SQL Area is messed up. Any advice out there?
- Magnus
ps: I looked up some archives regarding this but nothing mentioned how to specifically tune just the SQL Area.
Just found this on Metalink - don't know if it's relevant:
How to pin:
- a cursor associated with a SQL statement
1. Issue SQL statement to load it into the shared pool.
2. Determine the ADDRESS and HASH_VALUE of the SQL statement. This can
usually be obtained from calling DBMS_SHARED_POOL.SIZES. For example,
in the output from the SIZES procedure above you can determine that:
ADDRESS = 70378A10
HASH_VALUE = -614308548
for the SQL statement:
select ename from emp where empno = 7788
If the information cannot be determined from SIZES, then check the view
V$SQLAREA.
3. Issue the following statement to keep the cursor:
Yes, you're right - you can pin any stored obect - I just wasn't sure about individual SQL statements, although the above I found on metalink seems to indicate you can.
I'm really not sure - Never actually tried pinning anything other than Packages/Procedures myself
Bookmarks