locally managed tablespaces

[sudip]

Hi!
What are the drawback of using Locally managed tablespaces?

[sreddy]

http://www.dbasupport.com/forums/sho...?threadid=6909
http://www.oracle.com/oramag/oracle/00-nov/o60toc.html

If you still need further info have a search on the forum threads with search string 'locally managed tablespace'.

[sudip]

Thanx a lot.

One thing I would like to mention is that
"With locally managed tablespaces, extent sizes can be managed only at the tablespace level, not the object level. You cannot create an object and use a STORAGE clause to specify an extent size other than what has been defined for the tablespace. "
So If you have a really large table you cannot specify yr own storage clause.
ALSO can I specify PCTUSED AND PCTFREE Clause in the Table creation?





[Edited by sudip on 05-17-2001 at 01:21 AM]

[sreddy]

If the Object could aquire whatever the size it needs until there is freespace available, why do you want to specify object level storage clause.

If the object needs bigger extent size make sure you have seperate LMT for bigger objects. The object(table) level parameters will be ignored.

The storage parameters NEXT, PCTINCREASE, MINEXTENTS, MAXEXTENTS, and DEFAULT STORAGE are not valid for extents that are managed locally

[sudip]

U R perfectly right.
But can I specify PCTUSED AND PCTFREE Clause in the Table creation?
I have a table which has high ratio of deletes and inserts, what will happen if the tablespace is local managed?

[pando]

pctfree and pctused are parameters at object level not tablespace level so LMT does not affect the use of pctused and pctfree

[sudip]

Wish me luck Guys. I am going ahead with creating Prod database tablespaces as LMT.
Thanx a lot.

[pando]

remember to create a LMT RBS tablespace you need to create a dummy RBS tablespace managed by dictionary


wish you all the best....