Re: UNDO Tablespace Full

From: Brian Peasland <oracle_dba_at_nospam.peasland.net>
Date: Tue, 20 Jun 2006 18:23:35 GMT
Message-ID: <J168FM.9C1@igsrsparc2.er.usgs.gov>

ADRoman wrote:

> Chuck wrote:

>> ADRoman wrote:
>>> Chuck;
>>>
>>> Let me tell you that we have a Hybrid database (OLTP and DSS).
>>> That is the reason we use 2 undo tablespace, for OLTP 5 GB and for DSS
>>> 10 GB,
>>> Large processes are run seldomly, I mean by night or weekly. Those
>>> processes are supposed to be using the undo tablespace for DSS mode.
>>>
>>> I'm still wondering WHY the full segments are not being released, if
>>> nobody are using them??
>>> It has been 2 days and they are still full.
>>>
>>> Plese helpme with this doubt.
>>>
>>> Alonso
>> Please don't top post. It makes it harder to follow the flow of responses.
>>
>> It still doesn't matter. You need only one undo tablespace large enough
>> to hold all the undo that gets generated during the undo_retention period.
>>
>> What is your undo_retention setting?

> 
> 
> My undo_retention is 3 hours.
> 
> but, sometimes I obtain errors 1555.
> I am reading about error 1555 
> 
> Thanks.
> 

If you are receiving ORA-1555 errors, then either your UNDO tablespace is too small or your UNDO_RENTENTION is too low...or both. Querying V$UNDOSTAT will let you know the MAXQUERYLEN. Your UNDO_RETENTION should be larger than this value.

HTH,
Brian

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

Brian Peasland
oracle_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

Received on Tue Jun 20 2006 - 13:23:35 CDT