Re: ora-1652 on *undo* tablespace?

Chuck wrote:
> ORA-1652: unable to extend temp segment by 8 in tablespace UNDO1
>
> Today I saw in my alert log the above error. How does one create a
> *temp* segment in an *undo* tablespace? I've tried setting my temporary
> tablespace to UNDO1 and it failed with an error. I tried creating an
> index in UNDO1 and it failed with an error. So what caused this message
> in the alert log?
>
> RDBMS version is 9.2.0.5.
>
> Then about an hour later I user got an ora-30036 on the UNDO1
> tablespace. The tablespace should have been no where near full. It has
> 7g of datafiles assigned to it. DBA_UNDO_EXTENTS was reporting about
> 2.5g unexpired, 60m expired, and < 1m active. Yet Grid control (10g r2)
> was saying the tablespace was 100% full. It was actually only about 35%
> full. What am I missing?

The ORA-30036 error tells me your UNDO tablespace is full. Instead of querying DBA_UNDO_EXTENTS, try querying DBA_SEGMENTS for the UNDO tablespace. See if this information confirms what Grid Control is telling you.

HTH,
Brian

-- 
===================================================================

Brian Peasland
dba_at_nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown

-- 
Posted via a free Usenet account from http://www.teranews.com