Lee wrote:
> If anyone is curious to know how things turned out:
>
> We did discover an archive log problem (from the alert log). Some device
> was getting filled up and that was the end of that. We purged some
> un-needed files on the device and cleared that up.
>
> We discovered that no one had run an Analyse for about a month, so the
> CBO had no recent table statistics to use to create optimal execution
> plans.
>
> Its still not clear whether the original problem was really intermittant
> as advertized, or simply a case of slow (or not so slow) and steady
> degredation of performance as time progresses.
>
> The saga continues, but thanx everyone for the good advice.
And on our end the problem appears to be an ASM issue and have nothing
to do with the database: A TAR has been opened.
--
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)
Received on Sun Jul 03 2005 - 13:07:22 CDT
