Re: Question on tablespace/file allocation

"Vincent Ventrone" <vav_at_brandeis.edu> wrote in message news:9lu4bh$qh1$1_at_new-news.cc.brandeis.edu...
> > I have also read that it is good practice to set up two files for each
> > tablespace so that the files within each tablespace can be multiplexed
> > across drives to minimize loss of data (please let me know if this is
not
> a
> > good practice).
>
> Probably a good idea in theory but hard to do in practice -- AFAIK Oracle
> fills up the "current"
> extent of a table segment before allocating another one & since each
extent
> is allocated in a single file
> I don't know how you can accomplish striping this way. There is a way to
> pre-allocate multiple extents
> to a segment -- the syntax is something like "ALTER TABLE foo ALLOCATE
> EXTENT SIZE ....
> DATAFILE ..." but I've never bothered with it because Oracle will still
fill
> up the current extent
> before moving to the next one -- the next extent might be in a different
> file, but that does not give
> you any "striping" on inserts -- though it could help on full table scans.
> Besides, most systems I've
> worked on used RAID devices so that the hardware is already doing so much
> striping that anything
> the database might add on top of that is probably useless.
>

So would I be better off to just allocate one physical file for each tablespace? Received on Tue Aug 21 2001 - 14:38:46 CDT