Re: sql_trace always writes into the same file

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Thu, 20 Jun 2002 09:17:59 +0100
Message-ID: <1024562065.11920.0.nnrp-01.9e984b29@news.demon.co.uk>

It looks as if you are using shared server (formerly MTS) - this is the trace file for the S000 process.

If you want to leave the system on shared server, then there's not a lot you can do about this - but I think you might get slightly more useful output if you use

aggregate=no
with tkprof - I believe this stops tkprof from summing identical statements into a single lump if they came from different sessions.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminars
        UK            July / Sept
        Australia      July / August
        Malaysia        September
        USA (MI)        November
http://www.jlcomp.demon.co.uk/seminar.html

Lothar Armbrüster wrote in message
<8cf2adac.0206192354.23fe5e7e_at_posting.google.com>...


>Hello out there,

>today I stumbled over some inconvenience of Oracle 9.0.1.3 on W2k.

>When I set sql_trace to true, I always get the same trace file

>"<sid>S000.trc".

>I was used to get a new trace file name for every session I trace.

>On Oracle 8.1.7 I got oraNNNNN.trc with a new number for every

>session.

>Maybe some trace file number was reused but nornally I could trace

>different sessions into different trace files.

>This behaviour stopped to work for 9i.

>Is there a way to revive it?

>

>I did not find any initialization parameter to influence the naming of

>the trace file. Setting tracefile_identifier did not do any change.

>

>Any Ideas?

>

>Lothar

Received on Thu Jun 20 2002 - 03:17:59 CDT