It doesn't look like you are running out of temp tablespace, unless your
temp tablespace is named PSAPREROGI
It's building the index in parallel so each process will take take up n
extents during the build and then be coalesced at the end. What are your
extent sizes on PSAPREROGI. Is it ASM? You can build the index serially if
you can handle the extra time delay.
I had the same problem last week, my final index was 5.3Gb but was taking >
13Gb during the parallel build.
You can see all of this happening by querying dba_segments during the build.
Mike
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jan 23 2006 - 13:43:09 CST
