1 select INITIAL_EXTENT, 2 NEXT_EXTENT, 3 EXTENT_MANAGEMENT, 4 ALLOCATION_TYPE, 5 SEGMENT_SPACE_MANAGEMENT 6 from dba_tablespaces 7* where TABLESPACE_NAME = 'PSAPREROGI' SQL> / INITIAL_EXTENT NEXT_EXTENT EXTENT_MAN ALLOCATIO SEGMEN -------------- ----------- ---------- --------- ------ 16384 40960 DICTIONARY USER MANUAL SQL> -----Original Message----- From: Michael McMullen [mailto:ganstadba@xxxxxxxxxxx] Sent: Monday, January 23, 2006 1:43 PM To: Roger Xu; Oracle-L@Freelists. Org (E-mail) Subject: Re: ORA-01652: unable to extend temp segment 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 For technical support please email tech_support@xxxxxxxxxxx or you can call (972)721-8257. This email has been scanned for all viruses by the MessageLabs Email Security System. This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material. ____________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. Any questions please call 972-721-8257 or email your request to tech_support@xxxxxxxxxxxx -- //www.freelists.org/webpage/oracle-l