Re: SGA Sizing problem

Thomas,

	Thanks for your reply.
	Yes the scripts that you provide do give what ORACLE thinks
	is the size of the SGA. What I'm confused about is that the
	UNIX ipcs -b -m command value is such a different number.
	Perhaps ipcs is not giving what I thought or ...???
		Parris

Thomas J Kyte (tkyte_at_us.oracle.com) wrote:
> parris_at_walleye.esp.bellcore.com (Parris Geiser) wrote:
 

> >Running 7.1.6 on HP-UX.
 

> >db_block_buffers = 100
> >shared_pool = 3,500,000
> >log_buffer = 16,384
> >block_size = 2048.
 

> >So, the SGA should be: 3,721,184.
> >But when I do an ipcs -b -m
> >I get 4,892,680.
 

> >The question is: why such a large descrepency?????
> > Thanks.
 

> Run the following two queries in your database, they will show you exactly how
> the sga is being allocated and what it is being used for.

> compute sum of Value on report
> break on report
> column value format 999,999,999
> select * from v$sga;

> column bytes format 999,999,999
> compute sum of bytes on report
> select *
> from v$sgastat;

> The variables you listed have by far the largest effect on the SGA size but they
> are not the only things up there.
 

> Hope this helps...
 

> Thomas Kyte
> tkyte_at_us.oracle.com
> Oracle Government
Received on Fri Aug 11 1995 - 00:00:00 CEST