RE: LOCALLY MANAGED TABLESPACE

[Deshpande, Kirti]

Title: RE: LOCALLY MANAGED TABLESPACE

In a  'converted/migrated'  LMT, tables/indexes can not take advantage of UNIFORM or SYSTEM (autoallocate) policy of extent management. Those objects still grow with their old 'next' extent sizes. For full benefits of LMT, consider creating new LMT tablespaces and moving objects to them. Search Metalink. There are a number of documents/notes on converting DMT to LMT.

 

- Kirti

 

-----Original Message-----
From: Jamadagni, Rajendra [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 25, 2002 8:04 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: LOCALLY MANAGED TABLESPACE

The only issue we faced was convincing the management that in LMT having 150 extents is not really a problem.

Raj
______________________________________________________
Rajendra Jamadagni              MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.
QOTD: Any clod can have facts, but having an opinion is an art!

-----Original Message-----
Sent: Thursday, October 24, 2002 1:49 PM
To: Multiple recipients of list ORACLE-L

Hi
I am thinking to change our few dictinary manages tablespace to locally
managed tablespace.Can any one experienced any issues with locally managed
tablespace?
Do any one experience what gain after changing to locally managed
tablespace?

Thx
-Seema