I've read the bug report (though it doesn't yet seem to be reproduced (I'll
try tomorrow)) I haven't experienced the bug symptoms on windows 2000
myself - and we have run a number of 8i instances for a number of years.
till tomorrow
--
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com
"Matt" <mccmx_at_hotmail.com> wrote in message
news:cfee5bcf.0407212320.59169c10_at_posting.google.com...
> > True - the row source stuff is not relevant
> > to the OPs 8.1.7
> >
> OK I think I have an explanation (which I am absolutely amazed about).
>
> There is a bug reported for all (most) Oracle version prior to 9.2 on
> Windows 2000 (doesn't affect NT4) which causes excessive elapsed time
> for any session with SQL_TRACE=TRUE.
>
> Bug: 2202613.
>
> My behaviour mirrors the bug symptoms. The thing that amazes me is
> that I haven't noticed this before. I guess the reason for this is
> that the extra elapsed time is added to the CPU statistic of the
> database calls.
>
> I'm also amazed that a fix hasn't been written for 8.1.7 since the bug
> has been around for 2 and a half years.
>
> This is a very serious issue for our site because performance analysis
> is an ongoing process.
>
> I guess the best course of action is to limit my tracing to level 1
> and then only enable level 8 or 12 if absolutely neccessary.
>
> I suspect that very few Oracle sites are even aware of this bug.
>
> Matt
Received on Thu Jul 22 2004 - 14:33:44 CDT
