Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!pd2nf1so.cg.shawcable.net!residential.shaw.ca!sjc70.webusenet.com!news.webusenet.com!news.isc.org!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: taylorsi@mar.dfo-mpo.gc.ca (Shirley Taylor)
Newsgroups: comp.databases.oracle.server
Subject: Re: ORA-1652 no matter how big temp tablespace made
Date: 9 Sep 2003 11:07:31 -0700
Organization: http://groups.google.com/
Lines: 7
Message-ID: <d19ad877.0309091007.f71479e@posting.google.com>
References: <d19ad877.0308130638.40cbf974@posting.google.com> <1ac7c7b3.0308131209.428a5d04@posting.google.com>
NNTP-Posting-Host: 142.176.61.245
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1063130852 31997 127.0.0.1 (9 Sep 2003 18:07:32 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 9 Sep 2003 18:07:32 GMT
Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:242712

Finally this problem has been resolved. Oracle support reviewed megs
of trace files etc. Finally, something that should have been checked
first, I think:
Temp extents size = (2 * sort_area_size) + db_block_size
	
Rebuilt the temporary tablespace, locally managed, sized as listed
above. No more problem.