Re: 'alter session set sql_trace=true' bug or feature ?

Hello Holger,

"Holger Baer" <holger.baer_at_science-computing.de> wrote in message news:bs9d7c$pvi$1_at_news.BelWue.DE...
> VC wrote:
>
> Sorry if I missed something in this thread sofar, but what is actually
your
> problem? If you turn on tracing, then your goal is not to measure elapsed
wallclock
> time for the complete query, but rather create a trace file with explain
plan,
> waits etc.

The problem is that the increase is not 'wall-clock', or run-time delta but pure and solid 100% CPU time. If you'd taken the trouble of looking at the trace files, you'd discovered it yourself before rushing to comment.

>
> So while an massivly increased response time might bother you, it doesn't
render
> sql_trace useless.

Then how would you go about tuning a query for which tkprof shows CPU time 250 seconds and 210 of those seconds were contributed by the trace itself ? Please enlighten us.

Now, we also have a complex query that runs fro about 10 minutes. Enabling trace in order to obtain tkprof data makes it run close to an hour. Your recommendations ?

Rgds.

VC Received on Tue Dec 23 2003 - 07:03:37 CST