Re: why does db_block_buffers always show 0

Daniel Morgan <damorgan_at_exxesolutions.com> wrote in message news:<3F3ED56F.9A08C78_at_exxesolutions.com>...
> Anurag Varma wrote:
>
> > "Eric" <ericw24_at_yahoo.com> wrote in message news:3ji%a.9693$kp4.1283500_at_news20.bellglobal.com...
> > > Hi all,
> > >
> > > I set the parameter db_block_buffers in the parameter file, after restart,
> > > it always shows the value is 0. The other parameters I set do show the
> > > correct values. Can anyone help explain this to me? I use Oracle 9.2.0.1
> > > running on Windows 2000 service pack 3.
> > >
> > > Eric
> > >
> > >
> >
> > db_block_buffers is a deprecated parameter. So you have db_cache_size set instead?
> >
> > http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch134.htm#1015750
> >
> > Anurag
>
> Unless you are working with multiple block sizes in which case you need to configure db_cache_size
> and the caches for the additional block sizes (other than the one used by the SYSTEM tablespace).
>
> db_2k_cache_size=?
> db_4k_cache_size=?
> db_8k_cache_size=?
> db_16k_cache_size=?
> db_32k_cache_size=?

What?

In the first place, the requirement to set db_cache_size is not dependent on whether you have the odd-sized block parameters set. DB_BLOCK_BUFFERS is deprecated whether you set them or not. Hence, to suggest that you only 'need to configure db_cache)size' when you are 'working with multiple block sizes' is wrong.

In the second place, db_cache_size affects not only the block size of SYSTEM, but also of TEMP (or whatever you decide to call your temporary tablespace).

Yours in flight
Pectodectryl Received on Sun Aug 17 2003 - 17:56:08 CDT