Re: Does oracle 8i round extents up for new tables?

Oracle 8 still rounds up in dictionary managed tablespaces - I can't think why some of them are exactly 256K - but it may be to do with historical fragments, or reaching the end of the file.

But switch to locally managed tablespaces at 256K uniform extent size, and you can guarantee every extent in the tablespace will be exactly 256K.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases

Screen saver or Life saver: http://www.ud.com
Use spare CPU to assist in cancer research.

Leigh wrote in message <2603dc0c.0110310408.77f38ad_at_posting.google.com>...


>Created some new tables with initial extent size 256k and when the

>tables created the extent count is one and bytes are 286720 bytes for

>all but a few of them instead of the expected 262144 (256k). I read at

>http://www.ixora.com.au/tips/creation/extents.htm that 7.3 rounds up

>to the nearest 5 blocks however thought 8i would not do as is has not

>for a few of the tables. There is no min_extlen set for the tablespace

>either and min_extents are 1. Can anybody please shed some light on

>this one since I'm tying to get an extent size to match my multiblock

>read count.  DB is 8.1.7.2 with 8k block size.

>

>Many thanks, Leigh.