Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle Block Size and Solaris 2.6

Re: Oracle Block Size and Solaris 2.6

From: Stephen Harris <sweh_at_mpn.com>
Date: 8 Dec 1998 20:04:38 GMT
Message-ID: <74k0om$7hc$2@nebula.mpn.com>


satar_at_my-dejanews.com wrote:

: I was reffering to Oracle 7 and not in parallel Execution mode...but you

Apparently 7.3 acts quite differently to 7.1. The large block recommendation from the instructors was for 7.3.

: should check out "Chapter 15: Tuning I/O" of the same documentation. It has
: the advantages and disadvantages of certain block sizes.

Yah. Doesn't really say much that isn't obvious :-)

: I too, took the Oracle 7 DBA Master's Program from Oracle Education, and
: never heard anyone suggest a block_size as 8k or 16k. In all actuality, it
: really depends on the type of Database you are creating. The reason I suggest
: 2k, is that I can always adjust the db_file_multiblock_read_count to meet my

I've just checked our production databases... all the web servers fronted databases are running with a block size of 4K (Solaris 2.5.1). The Financials and page-layout databases are running with a block size of 8K (HPUX 10.20).
: that I am restricted on my Group by and Order by and Select statements. Can
: you imagine if I set up a db_block_size of 8k or 16k for a customer who in
: turn, creats an OLTP database?

With sufficient memory (for a good sized SGA) and a good disk layout then I would have though 8K should work out pretty good. Our HPUX machines are rarely maxed out on IO, using 8K blocks.

--

rgds
Stephen Received on Tue Dec 08 1998 - 14:04:38 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US