| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Help with Shared Pool Problem
Ron,
I have to disagree w/ Ganesh. A SQL, once execution completes, should =
be=20
eligible for flushing, unless it was kept. You don't have something
running that would keep existing cursors into the library cache, do you?
I would tend to doubt that you do, but, if you did, that would certainly
cause problems.
I think you want to go here:
http://www.ixora.com.au/scripts/pool.htm
and review some of the scripts, expecially shared_pool_lru_stats.sql,
shared_pool_free_lists.sql, and shared_pool_summary.sql
Steve covers what these scripts do, but, briefly, the summary shows you what kinds of objects are taking space in the shared pool. The free_lists script shows you how fragmented the free lists are, (which can lead to ORA-4031) and finally, the lru_stats script can give you some idea of whether your shared pool is undersized.
Check the website and Steve's book for more details as to how it all works and how to interpret the outputs of these scripts,=20 especially the lru_stats script.
Hope that helps,
-Mark
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Smith, Ron L.
Sent: Thursday, October 14, 2004 9:48 AM
To: Ganesh Raja
Cc: shaharul.anuar_at_intecbilling.com; oracle-l_at_freelists.org
Subject: RE: Help with Shared Pool Problem
So you are saying there is no LRU processing taking place? Nothing is ever aged out or overwritten?
Ron
-----Original Message-----
From: Ganesh Raja [mailto:ganesh.raja_at_gmail.com]=3D20
Sent: Thursday, October 14, 2004 8:33 AM
To: Smith, Ron L.
Cc: shaharul.anuar_at_intecbilling.com; oracle-l_at_freelists.org
Subject: Re: Help with Shared Pool Problem
There is No Aging happening .. Let us assume that u are Calling a Select Stmt Again and Again with different Parameters to it and also same parameters .. As Far as Oracle is concerened your stmts have not aged . They are new since it has now only been created or it has been used in the past few mins.
So oracle tries to create new space for the stmt that u are trying to parse now and it fails there ..
HTH
~
Ganesh
On Thu, 14 Oct 2004 08:08:35 -0500, Smith, Ron L. <rlsmith_at_kmg.com>
wrote:
> I know the reason for the Shared pool filling up is because the=3D20
> programs do not use bind variables.
>=3D20
> My question was, why do the old SQL statements not get aged out =
and=3D20
> free up space for new statements?
>=3D20
>=3D20
>=3D20 >=3D20
>=3D20
>=3D20
>=3D20 >=3D20
>=3D20
>=3D20
> =3D3D =3D3D3D distribution or copying of the message is prohibited. =
Please =3D
let
> me know immediately by return e-mail if you have received =3D3D3D =
this=3D20
> message by mistake, then delete the e-mail message. Thank you.
> --
> http://www.freelists.org/webpage/oracle-l
>=3D20
>=3D20
>=3D20 >=3D20 >=3D20 >=3D20
> =3D3D distribution or copying of the message is prohibited. Please let =
=3D
me=3D20
> know immediately by return e-mail if you have received =3D3D this =3D
message=3D20
> by mistake, then delete the e-mail message. Thank you.
> --
> http://www.freelists.org/webpage/oracle-l
>
Important Notice!!
If you are not the intended recipient of this e-mail message, any use, =
=3D
distribution or copying of the message is prohibited.
Please let me know immediately by return e-mail if you have received =3D
this message by mistake, then delete the e-mail message.
Thank you.
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Thu Oct 14 2004 - 09:14:23 CDT
 |
 |