ALLOCATION_TYPE USER or SYSTEM for a Locally Managed Tablespace ?

From: VIVEK_SHARMA <VIVEK_SHARMA_at_infosys.com>
Date: Mon, 23 Sep 2002 09:08:33 -0800
Message-ID: <F001.004D6B5A.20020923090833@fatcity.com>

Qs In sys.dba_tablespaces , Which is Better , ALLOCATION_TYPE USER OR SYSTEM with EXTENT_MANAGEMENT being LOCAL for Both Cases ?

For Objects Existing in Locally managed Tablespaces having ALLOCATION_TYPE SYSTEM , NEXT_EXTENT has NO Value But EXTENTS has Values .

Qs Can Large Numbers of Extents in a Locally Managed Tablespace Cause a Performance Overhead ?

We Convert the ALLOCATION_TYPE from SYTEM to USER to Allow us to Control the NEXT_EXTENT Size Manually

This is Done by Running the Following 2 Commands on the respective Locally managed Tablespace execute dbms_space_admin.tablespace_migrate_from_local('TBLSPC1'); execute dbms_space_admin.tablespace_migrate_to_local('TBLSPC1');

Thanks

--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: VIVEK_SHARMA
INET: VIVEK_SHARMA_at_infosys.com

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: ListGuru_at_fatcity.com (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). Received on Mon Sep 23 2002 - 12:08:33 CDT