Re: trace file reuse???

        I think it has to do with Oracle's trace file naming mechanism. If I remember correctly it appends the serial to the string <SID> and then tacks the.trc extension on.

        Why do you have to reconnect to the client? Just open multiple windows. Have one pointing to the directory with the trace files and one running SQL. That way you can stay connected.

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 5/24/00, 2:10:23 PM, "Gary Knopp" <gknopp_at_ascend.com> wrote regarding  

trace file reuse???:

> Hello,
> Does anyone know whether its possible to reuse a trace file
> in a client session? I've been unable to make this work.
 

> For example...
> execute dbms system.set sql trace in session(10,200,True)
> ...
> ... run sql commands here
> ...
> execute dbms system.set sql trace in session(10,200,False)

> This generates a file named 'myDB ora 12345.trc' . If I
> rename the file to 'Trial1 hold.trc' and rerun the commands again
 

> the trace file 'myDB ora 12345.trc' is not created again. I
> don't understand why the trace package doesn't handle this
condition.

> It's a real pain having to reconnect the client to test various
 query
> scenarios.
Received on Thu May 25 2000 - 00:00:00 CDT