Qs What is the advantage of having dba_tablespaces.ALLOCATION_TYPE = "UNIFORM" OVER dba_tablespaces.ALLOCATION_TYPE = "USER" ?
With ALLOCATION_TYPE = "UNIFORM" , NEXT_EXTENT Size of the Object can NOT be Manually defined in the Table Creation Script <storage (NEXT <Value>)> which is allowed when having allocation_type="USER" . This allows Objects with Different NEXT_EXTENT Sizes to be Created in the SAME LOCALLY managed Tablespace & thus reduces Total Number of Extents for the respective Table. Our Application does have Objects of Dissimilar Sizes Existing tin the Same Tablespace . Does ALLOCATION_TYPE = "UNIFORM" automatically imply NO Fragmentation Irrespective of the Number of Extents of the Object (in a Locally Managed Tablespace) ? Does it further imply NO further need to Look at Number of Extents of an Object in a Locally Managed Tablespace ? NOTE Allocation_type can be made = "USER" by using the stored procedures :- dbms_space_admin.tablespace_migrate_from_local / dbms_space_admin.tablespace_migrate_to_local Am i still Lost in the World of Oracle 7 ? Thanks -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: VIVEK_SHARMA INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
