Whenever I've payed attention to this it has allocated them in a
round-robin approach amongst the various datafiles as the note stated.
I believe this is how it worked in 8.0.5 (maybe earlier) and up.
- Brian
- Chuck Hamilton <chuck_hamilton_at_yahoo.com> wrote:
>
> It's always been my understanding that when a tablesapce has multiple
> datafiles, extents are allocated in 1 datafile at a time until that
> datafile is full, then it switches to the next datafile. Today I read
> a note on a metalink forum where someone stated quite authoritatively
> that extents are allocated in a striped fashion amongst the
> datafiles. For example if you have three datafiles, the first extent
> goes to file 1, the second to file 2, the third to file three, and
> then back to file 1. Is this true? Is this something that's new in
> one of the versions of 8i? I've never heard of such a thing. It would
> be great if that were true because it would distribute i/o more
> evenly. But I thought the only way to accomplish that in Oracle was
> with hash paritioning.
>
> On a similar note, I have a composite partitioned table spread across
> 3 tablespaces each with one datafile. The hash key for the
> subpartition is a sequentual number. When I bulk load into that
> tablespace, I don't see even i/o distribution amongst the data files.
> One file consistently gets 2x the # of writes as the other two. Why
> is that?
>
>
>
> ---------------------------------
> Do You Yahoo!?
> Yahoo! Shopping - Thousands of Stores. Millions of Products.
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
Received on Thu Dec 21 2000 - 13:31:48 CST
