|
dba_object_size only shows some fixed calculations
from stored code (how big is the code segment etc..), but it doesn't show how
much memory a loaded object actually uses in shared pool.
If you want to know library cache usage, use
v$db_object_cache or x$kglob directly.
If you want to know shared pool usage, then you
have to start taking shared pool heapdumps....
Tanel.
----- Original Message -----
Sent: Tuesday, January 13, 2004 11:09
PM
Subject: RE: Shared Pool
fragmentation
dba_object_size.parsed_size
Raj
--------------------------------------------------------------------------------
Rajendra dot Jamadagni at nospamespn dot
com
All Views expressed in this
email are strictly personal.
QOTD:
Any clod can have facts, having an opinion is an art !
On
a side note, before I kill myself with the Friendly Manual, does anyone have
a fast way to determine how much space in the shared pool a package is
using?
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i
DBA
Is there a way to catch
shared_pool fragmentation before you get the 4031 errors? I have
looked at Steve Adams site which has scripts to show the free lists chunks
in the shared pool. At what point do I know that it is fragmented
too much? I know that I can prevent this by using bind variables,
and keeping objects, but until I can modify all the apps, I would like to
know a little before these errors happen. Any
ideas?
Thanks,
Rick Stephenson
This email and any files transmitted with it
are confidential and intended solely for the use of the individual or
entity to which they are addressed. This message contains confidential
information and is intended only for the individual named. If you are not
the named addressee you should not disseminate, distribute or copy this
e-mail. Please notify the sender immediately by e-mail if you have
received this e-mail by mistake and delete this e-mail from your system.
If you are not the intended recipient you are notified that disclosing,
copying, forwarding or otherwise distributing or taking any action in
reliance on the contents of this information is strictly prohibited.
|
