Re: Shared Pool Tuning

Right. If no SQL is getting reused, you're better off with a smaller shared pool. It's a common mistake people make-- increase the shared pool because they're doing a lot of parsing. But your latch problems get worse, and if you're not reusing SQL, it has no benefit.

--Terry
----- Original Message -----

If I recall correctly, hard parse grabs a bunch of latches; and the bigger the shared pool, the worse the latch contention can get. Although it seems counter intuitive, I think, in this case, the piece of duct tape you apply is to REDUCE the size of the shared pool.

>-----Original Message-----
>When the
>shared pool "fills up", all that means is that additional SQL
>which gets
>hard parsed must move some other SQL out of the shared pool.
>This is not a
>problem unless the SQL moved out is needed again.

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l