Title: RE: Dbf Files, Mount Points and Oracle 7

Wayne,

Why in the heck are you worried about tables having multiple extents? The old 'table in one big initial extent' rule died a long time ago. Please read Bhaskar Himatsingka's paper "How to Stop Defragmenting and Start Living: The Definitive Word on Fragmentation"

http://www.dbatoolbox.com/WP2001/spacemgmt/defrag.htm

Would an old USAF crew chief lead a Navy guy wrong?

Jerry Whittle
ACIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED]
618-622-4145

    -----Original Message-----
    From:   McGill Wayne China Lake CA

    I am part-time DBA for an Oracle system that for reasons
    beyond our control is frozen at 7.3.4, at least for the
    immediate future.  I am having some problems and I think
    I know how to correct them but I am asking the old-timers
    to dust off their brains to tell me if my proposals are
    O.K.

    It started when I noticed that one of the tables had gone
    into 2 extents.  Normally when this happens, I (in a nutshell),
    make a copy of the table with larger storage parameters.
    But for this table, I get the following error message:

      ORA-01658: unable to create INITIAL extent for segment
                 in tablespace ORA_DATA1

    I also noticed that this system has 3 mount points.  When I
    look at the capacity of the disks, the first is always
    89 percent full and the other two are 1 percent.  This is
    because all the DBF files for tablespaces were created on
    the first mount point.  So all the other two have are small
    control and redo-log files.

    So what I would like to do to fix all of this is to move
    some of the tablespaces onto the other 2 mount points.  I
    would also like to create a couple of new tablespaces, one
    to store two large application-related tables and another
    to store a large table that gets dropped and recreated
    everyday (a local copy of data from an external system).

    So my questions are:
      1) Is there any reason to keep all the tablespaces on one
         mount point?
      2) I know about keeping table data and indexes in different
         tablespaces but can they also be on different mount points?
      3) Any reason for not putting my 1 large temp-table into its
         own tablespace?
      4) If I can do all of this, will anything significantly change
         in Oracle 8, 9, 10, ...?

    I have read different manuals and references but I have not
    seen anything that indicates that I cannot do what I am proposing.
    I have tried this solution on a test 8.1.6 database and everything
    seems to be working.

    TIA, Wayne
    [EMAIL PROTECTED]

Reply via email to