Re: ** trace file

From: Mathias Magnusson <>
Date: Thu, 23 Apr 2009 08:53:40 +0200
Message-ID: <>

It sounds as if you may need to revisit your requirements. This would create a file too large to work with. Has Oracle Support requested it?

Is the job not very repetitive so that any five minutes will look virtually identical (assuming it is one single batch process). If that would be the case, you would only need a trace for a short period.

If yo need all of this trace data, then you could copy from it to another file and then truncate it ( echo '' > <file>). That resets the file pointer, while not changing the inode for the file. While you're copying and truncating the file will be written to so make sure you're not missing some data or getting half written records, you will want to pause the process. In Solaris that should be possible with the pstop command. It requires root or logging in as the owner of the process.


On Thu, Apr 23, 2009 at 3:30 AM, A Joshi <> wrote:

> Thanks Tim, Mathias,
> Wolfgang,
> 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.
> Thanks
> --- 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.
> Mathias
> I also cannot remove the file or empty the trace file. Because after
>> that nothing goes into the file. Thanks
> --

Received on Thu Apr 23 2009 - 01:53:40 CDT

Original text of this message