Re: ** trace file

From: A Joshi <>
Date: Wed, 22 Apr 2009 18:30:16 -0700 (PDT)
Message-ID: <>

Thanks Tim,


   tracefile_identifier does not seem to work for :

oradebug setospid 400

oradebug unlimit

oradebug event 10046 trace name context forever , level 12

I have a job that goes 8 hours. It is same sid, spid, pid etc. and I want a way to get a trace with different name. The trace file also grows very fast.


  • On Mon, 4/20/09, Tim Gorman <> wrote: From: Tim Gorman <> Subject: Re: ** trace file To: Cc:, "oracle-l" <> Date: Monday, April 20, 2009, 4:37 PM

Don't know if this helps, but be aware of ORADEBUG FLUSH and ORADEBUG CLOSE_FILE as well.  Might help with flushing remaining buffered output to the trace file, then closing the file-descriptor to the file.  Both may help you move the file without weirdness due to open file-descriptors....

Mathias Magnusson wrote:

  How do you empty the file? If that would be a solution for you, maybe the problem of not getting more data into it can be solved. It sounds to me as if the filename you use exists on a different inode as a result of the operation. Oracle would write to the inode it started writing to no matter what you do to the file. So if you empty it and the inode remains the same, I'd imagine new data would still show up in the file.   


          I also cannot remove the file or empty the
trace file. Because after that nothing goes into the file. Thanks



-- Received on Wed Apr 22 2009 - 20:30:16 CDT

Original text of this message