Re: ORA-1555 snapshot too old: why?

From: DA Morgan <damorgan_at_psoug.org>
Date: Mon, 18 Dec 2006 11:01:12 -0800
Message-ID: <1166468473.331728@bubbleator.drizzle.com>

Chuck wrote:

> hpuxrac wrote:

>> Chuck wrote:
>>> Oracle 9.2.0.7
>>>
>>> I got an ORA-1555 snapshot too old today on a export where consistent=y
>>> was set. The export failed at 6 hrs even though undo_retention was set
>>> to 8 hours. Querying v$undostat shows that during the time when the
>>> export was running a total of only 150m of undo was written. The undo
>>> tablespace is 4g. Why would I get an ora-1555 when undo_retention is set
>>> plenty high enough, and the undoblks written weren't anywhere near
>>> maxing out the undo tablespace?
>>>
>>> TIA
>> Tom Kyte has this all covered. Try looking for 1555 in
>> http://asktom.oracle.com
>>

> 
> I've already been there and searched for 1555. I didn't find anything
> related to ora-1555 that matches this case. All the responses related to
> manual rbs management, cases where undo_retention was insufficient, or
> cases where the undo tablespace size was insufficient. My case does not
> fit any of these.

I agree. I followed HPUXRAC's links too thinking there was something I had missed and found nothing like what you are reporting.

I couldn't find an example on metalink so I'd suggest opening an SR. I'll be interested in what you discover.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

Received on Mon Dec 18 2006 - 13:01:12 CST