Re: Ora 1652: Unable to extend temp segment by 128 in temp ts

From: joel garry <>
Date: Tue, 8 Jan 2008 13:24:29 -0800 (PST)
Message-ID: <>

On Jan 8, 1:23 am, dbagtcol <> wrote:
> Thank you all for your responses. Unfortunately we had to drop this
> logic and do a select from another table(equivalent) due to time
> constraints. But I still have my query, does the outputs really make
> the temp buffer overflow even if we don't have any sorts ? And could
> there be any other reasons to cause Ora-01652 other than cartesian
> product in this case?
> Thanking all,
> gtcol

See this:

Also, show us how you defined the temp ts. Maybe you didn't do what you thought, easy mistake to make (search for temporary tablespace on metalink for lots of info).

Since you didn't post platform info, it could be something silly like using a DMT with 2k blocks...
Also, sort and aggregate init.ora parameters can make a difference, as well as autoextend (and some other obscure things can make temp usage more flagrant, I don't have time to remember right now, and there is misinformation floating about).


-- is bogus.
"Tracers work both ways." - U.S. Army Ordnance
Received on Tue Jan 08 2008 - 15:24:29 CST

Original text of this message