Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: RE: Separate Indexes and Data

RE: RE: Separate Indexes and Data

From: MacGregor, Ian A. <ian_at_SLAC.Stanford.EDU>
Date: Wed, 01 Oct 2003 08:54:37 -0800
Message-ID: <F001.005D1B2C.20031001085437@fatcity.com>


Part of the problem is self-inflicted. We currently use separate tablespaces for each major project. For instance: chemical inventory gets its own data and index tablespaces, dosimeter data gets the same, network configuration data as well. For many projects once the design has matured new segment creation is rare. The holes remain. Also data segments cannot be moved willy-nilly, users do not like getting unusable index errors. There are also tables which cannot be easily moved such as tables with longs. These were created before LOBs were available. Moving data also entails a certain amount of risk. Inside a project, we let developers create the tables and indexes which are specific to that project. Very few actually create indexes in their proper tablespaces. Corrective action creates more holes. This is one reason why I am looking at index and data segments in the same tablespace.

Ian MacGregor
Stanford Linear Accelerator Center
ian_at_SLAC.Stanford.edu
-----Original Message-----
Sent: Tuesday, September 30, 2003 4:25 PM To: Multiple recipients of list ORACLE-L

But those holes of exactly the right size for new objects to fit into. Since you'll presumably move it once it gets about 1,000 extents or so that isn't a huge amount of space that's being wasted.

Jay Miller
Sr. Oracle DBA

-----Original Message-----
Sent: Tuesday, September 30, 2003 4:45 PM To: Multiple recipients of list ORACLE-L

My criticism of the defrag paper was that it did not address what to do when a segment grew large enough to belong in a tablespace with a larger uniform extent size. Moving the segment creates holes in its original tablespace which may close only in the fullness of time. Physical backups of the files comprising the original tablespace include this wasted space, this is compounded by how many days backup you keep available, and the number of copies of backups.
--

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

Author:
  INET: JayMiller_at_tdwaterhouse.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).
--

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

Author: MacGregor, Ian A.
  INET: ian_at_SLAC.Stanford.EDU
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 Wed Oct 01 2003 - 11:54:37 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US