The behaviour may be o/s dependent,
and Oracle version dependent.
One way of dealing with the problem:
alter session set tracefile_identifier = 'somthing'
closes the current trace file and opens a new
one with 'something' in the file name. So every
time you want to restart, you can just do
Folks,
I've noticed -- at least on our 9.2 instances, that it does not seem
possible to generate two trace files from the same session. Meaning, if I
start a trace in a session, then stop it, use tkprof to run some analysis,
and then erase that trace file, a second start_trace does /not/
