Dan, I think that you've hit upon the only possible explanation, especially regarding your comment that "eventually it will get a 1555 error". The flip-side of ORA-01555 is more work spent rebuilding a consistent read... Hope that the support folks return the right answer... :-) -Tim on 5/3/04 2:05 PM, Daniel Fink at Daniel.Fink@xxxxxxx wrote: > It was the best of sql executions; it was the worst of sql > executions. > > We have a process that periodically slows down. So far, we have > not been able to pinpoint a root cause, but we continue to > pester the development/application support folks for more info. > I apologize for the limited information, but I'm hoping that we > are aiming in the right direction. > > We are smart enough that we captured a 10046 trace during a good > execution as a baseline. I have tagged the lines from this trace > file as (good). This morning, the query began slowing down > (eventually it will get a 1555 error). We turned on tracing and > those lines are tagged as (bad). ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------