Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Troubleshooting ORA-01555 while using AUM
To summarise this post and the followups: I think you have said you have:
undo_retention = 2 hours
13 GB of undo tablespace, but 8GB
of that are reported in dba_free_space
an export that can fail with
"snapshot too old" after only 40 minutes.
v$undostat shows:
Zero for 'stolen unexpired'
Zero for 'space errors'.
non-zero for 'snapshot too old'.
It does look as if something is going
wrong somewhere. What is the maximum
value in the column maxquerylen ? Does
the column expstealcnt give you any clues
about extents moving 'legally' from one
segment to another ?
-- Regards Jonathan Lewis http://www.jlcomp.demon.co.uk The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html March 2004 Hotsos Symposium - The Burden of Proof Dynamic Sampling - an investigation March 2004 Charlotte OUG (www.cltoug.org) CBO Tutorial April 2004 Iceland June 2004 UK - Optimising Oracle Seminar "Tech Geek" <Tech_Geek_at_Gawab-IHateSpam.com> wrote in message news:gno0c.10382$C65.9964_at_nwrddc01.gnilink.net...Received on Mon Mar 01 2004 - 02:38:50 CST
> Hi Gurus,
>
> I am trying to troubleshoot the dreaded ORA-01555 - Snapshot too old
errors.
> Here is the relevant info:
>
> OS : Sun Solaris 2.8
> Oracle: Oracle9i Rel 2 (9.2.0.4)
> undo_retention = 7200 (2 hours)
>