Re: SGA / Latch Question

From: <mrdjmagnet_at_aol.com>
Date: Tue, 30 Dec 2008 11:55:42 -0800 (PST)
Message-ID: <0783f6b8-67dd-4526-a5c2-3322a79c6b33@a26g2000prf.googlegroups.com>

On Dec 30, 1:34 pm, Mark D Powell <Mark.Pow..._at_eds.com> wrote:
> On Dec 30, 1:12 pm, mrdjmag..._at_aol.com wrote:
>
>
>
> > Hi,
>
> > This just seems weird.  I look at our SPFILE:  *.shared_pool_size=2G
>
> > I query v$parameter: 1073741824
>
> > I ran a query:
>
> > SHARED_POOL_USED SHARED_POOL_SIZE SHARED_POOL_AVAILPCT_SHARED_POOL_AVL
> > ---------------- ---------------- ------------------------------------
> >       2107.04836             1024                 0205.766441
>
> > Ok, so if I have 2GB in my spfile, and I bounced my database, why is
> > it reading 1GB, unless I'm a dork and cannot read properly.......Size
> > = 1GB and used = 2GB??
>
> > Our sql library cache miss ratio says 99%, using that Spotlight
> > utility and the latch waits are about 10%.  So, we figure we have a
> > problem.....
>
> > DUH??
>
> Please provide the folowing information:
> Full Oracle version
> values of database parameters:
> sga_max_size
> sga_target
> pga_target
> workarea_size_policy
> shared_pool_size
> db_cache_size
>
> The actual query or queries you are using since the source cannot
> always be determined just from seeing output.
>
> HTH -- Mark D Powell --

Database: 10gr2

sga_max_size=12G
sga_target=10G
pga_aggregate_target=800M    (No pga_target defined)

workarea_size_policy='AUTO'
shared_pool_size=2G
db_cache_size=3000M Received on Tue Dec 30 2008 - 13:55:42 CST