Re: How to seup tablespace storage

m.fangtao_at_genesis.co.nz (Meng) wrote in message news:<1ddc56b5.0108171609.5ac0f6d9_at_posting.google.com>...
> postbus_at_sybrandb.demon.nl (Sybrand Bakker) wrote in message news:<a20d28ee.0108170232.3c8828e6_at_posting.google.com>...
> > m.fangtao_at_genesis.co.nz (Meng) wrote in message news:<1ddc56b5.0108161936.1de54943_at_posting.google.com>...
> > > I am a new Oracle DBA. We will create a tablespace for a big table
> > > (more than 6GB). The table is always inserted,updated and selected.
> > > The table's row size is 268 bytes. Which tablespace storage shall I
> > > choose, locally managed or dictionary managed? If I select locally
> > > managed automatic allocation, the default initial extent is only 64k
> > > (DB_BLOCK_SIZE=8k). Do you think the value is a little bit of small?
> > > How to setup the table's storage? Do I need to modify default storage
> > > values? Thank you very much.

<snip>

Personally, with a 6gb table, I'd be inclined to set a LMT unit size in megabytes, not kilobytes. I'd imagine that a table likely to engage in segment extension at that size may need to do it quite frequently. If the tablespace is dedicated, then there should be less ST enqueue (if this is still done for space allocation with LMT - I think it is?) needed with larger units.

As I said, if it were me, I'd go for something in the region of 10-20mb at least, probably more.

I don't see what the OS block reading size has to do with LMT unit sizing fwiw. Received on Tue Sep 04 2001 - 12:48:20 CEST