Re: Locally Managed Tablespaces

If you have tables of vastly different sizes you may be better off with system managed extent sizes.

storage parameters in table create statements are not all ignored when using LMT. The initial parameter is obeyed in as much as Oracle will allocate enough extents to satisfy the initial size request, and for system managed allocation that means that the extent size escalation kicks in immediately. I.e. if you ask for several meg initial 64K extent sizes and possibly higher ones will be skipped for that table. If that initial size request is approximately accurate (that's an oxymoron, isn't it) that's what you'd want anyways.

Smith, Ron L. wrote:

> I would like to use Locally Manages tablespaces and Uniform extent=20
> sizes, instead of the table create parameters.=20
>
> My question is, will Locally Manages tablespaces cause Oracle to ignore=20
> the table create parameters? (I hope)=20
> And, if I have some tables that are empty, and some that have a million=20
> rows, what do I use for an initial extent size?=20
> Do I allocate them all small and let the large tables go into extents?=20
>
> I don't have the luxury of putting large tables in a separate=20
> tablespace. Everything is in one schema and one tablespace.=20
>

-- 
Regards

Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
http://www.freelists.org/webpage/oracle-l