| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Slick tricks for extent size reduction in LMTS via LMTS=>DM=> LMTS ?
Ross
You can do it in the way your subject line suggests using:
1) dbms_space_admin.tablespace_migrate_from_local 2) alter tablespace (change default storage extent size and minimum extent) 3) dbms_space_admin.tablespace_migrate_to_local
However, already existing tables will retain their existing storage parameters (unless you change them at step 2) and you will have to have a dictionary managed SYSTEM tablespace to change the LMT to dictionary-managed at step 1.
dbms_space_admin.tablespace_migrate_to_local has some side effects. Although you will get the performance benefits of an LMT you will no longer get the policy enforcement of extent sizes (i.e. the ALLOCATION_TYPE column in dba_tablespaces will show as USER not UNIFORM or SYSTEM). Another is that the next extent storage attribute does not get reset on deallocation of extents (this only matters if PCTINCREASE > 0).
Ray
-----Original Message-----
From: Mohan, Ross [mailto:RMohan_at_arbinet.com]
Sent: Wednesday, July 21, 2004 12:21 AM
To: oracle-l_at_freelists.org
Subject: Slick tricks for extent size reduction in LMTS via
LMTS=>DM=>LMTS ?
I am gathering, painfully, that once you create and
partially populate a half terabyte tspace with local
ext mgmt extent size 100M there's no way to reduce
the extent size to, say, 5M.
Please someone tell me I am wrong.
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.htmlput 'unsubscribe' in the subject line.
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request_at_freelists.org
 |
 |