RE: Space management failures on autoextend datafiles

[Fink, Dan]

Igor and Yechiel,     Thanks for the responses. I'm glad to hear that I am not the only one experiencing the problem.     I should have also mentioned that the tablespace is LMT with autoallocate and is nowhere near the max size.   Dan Fink -----Original Message----- From: Yechiel Adar [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 07, 2002 9:35 AM To: Multiple recipients of list ORACLE-L Subject: Re: Space management failures on autoextend datafiles Hi Paulo   When creating an index, or CTAS, oracle use temp segments while building and rename them after the build finish. So if you do not have enough space you will get: unable to allocate TEMP segment.   Yechiel Adar Mehish ----- Original Message ----- From: Paulo Gomes To: Multiple recipients of list ORACLE-L Sent: Thursday, November 07, 2002 6:04 PM Subject: RE: Space management failures on autoextend datafiles never heard on this problem but are u sure table the temp tablespace of the user executing the commeand is temp and not user_indx??? regards Paulo -----Original Message----- From: Fink, Dan [mailto:[EMAIL PROTECTED]] Sent: quinta-feira, 7 de Novembro de 2002 15:39 To: Multiple recipients of list ORACLE-L Subject: Space management failures on autoextend datafiles I have a 9.2 database running on Solaris 8. I'm creating some test tables with indexes. The USER_INDX tablespace's datafile is set to autoextend (as are TEMP and USER_DATA). When the system attempts to create indexes, instead of auotextending the datafile (there is plenty of space on the device), it throws an ORA-01652: unable to extend temp segment by 128 in tablespace USER_INDX error. If I manually resize the datafile and rerun it, no problems.   Anyone else heard of this behavior? I can't find anything on Metalink that fits the problem definition.   Dan Fink