Re: Export / Import from 8i to 9i and locally managed tablespace

"Howard J. Rogers" <howardjr20002_at_yahoo.com.au> wrote in message news:euHka.10032$1s1.167071_at_newsfeeds.bigpond.com...

> However, it is true that *if* you select to use ASSM, and you have a 16K
> block size, then it does indeed give you a 1M extent in autoallocated LMT
> rather than anything else. To that extent, I was wrong to suggest ASSM has
> no impact whatsoever on extent sizes, and it is perfectly possible that it
> is indeed the ASSM use by our original poster that is causing the
behaviour
> that he sees.

Interesting, though the original poster is using uniform allocation of 520k, not autoallocate and there are no 1m extents sizes anywhere. The initial size referred to in dba_segments was 1096K not 1m. However it does suggest that the oft repeated statement that autoallocate tablespaces uses sizes of 64k,1m,8m,64m and 256m needs to be qualified with 'but not all of these sizes maybe used depending on your database block size'. I wonder what happens with 32k block sizes, and if the list of usable sizes changes at all.

--
Niall Litchfield
Oracle DBA
Audit Commission UK