Re: shared pool size / library cache locks / too big ?
- From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
- To: "Christopher.Taylor2@xxxxxxxxxxxx" <Christopher.Taylor2@xxxxxxxxxxxx>
- Date: Sun, 2 Jun 2013 15:35:35 -0300
Wait, you have a 22G shared pool? what kind of database is it? how long
does the parsing of new sqls take? I've seen significant performance
degradation with a 2G shared pool out of a 10G SGA. Buffer cache rates were
affected as well, of course, but not nearly as much as the library cache
waits per execute.
hth
Alan.-
On Sun, Jun 2, 2013 at 2:21 PM, <Christopher.Taylor2@xxxxxxxxxxxx> wrote:
> Env: 10.2.0.4 3-node RAC.
> I've been reading a bit online about library cache lock waits and ran
> across a forum reply by Charles Hooper in discussion about
> session_cached_cursors and libary cache locks and it was discussed that
> perhaps the shared pool was oversized.
>
> I'm curious what symptoms/indicators (besides library cache lock waits) I
> can look into to determine if our shared pool (~22GB) is oversized and/or
> increase session cached cursors (20 currently)? The app is very immature
> and a mix of SQLs using binds and literals.
>
>
> Chris Taylor
> Oracle DBA
> Parallon IT&S
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
