Re: Switching trace files

The trace file is creating using the SPID of the session you are tracing. You need to logoff and backon to get a new SPID thus you will get a new trace file.
On really busy systems these files can be reused (rare). If you delete a file while the session is still connected (ON UNIX) it wil continue to use the resources it obtained and even continue to use more but you will not be able to see it.

Hope this Helps.

Stephen C. Ashmore
Brainbench MVP for Oracle Administration http://www.brainbench.com

"Brian Tkatch" <SPAMBLOCK.Maxwell_Smart_at_ThePentagon.com.SPAMBLOCK> wrote in message news:3c51b6e2.1513268329_at_news.alt.net...
> Is there a way to force a switch in the trace files.
>
> Case in point.
>
> ALTER SESSION SET SQL_TRACE=TRUE;
>
> SELECT Moo FROM Cow;
>
> ALTER SESSION SET SQL_TRACE=FALSE;
>
> I check udump, and I have a nice trace file. I then delete the
> tracefile because I no longer want it.
>
> I then do another trace, and nothing appears in udump. If I bounce the
> (test) server all is back to normal.
>
> max_dump_file_size is set to UNLIMITED,
>
> Do I need to switch the files?
>
> Brian
Received on Sat Jan 26 2002 - 05:43:01 CST