Re: ** trace file

From: Tim Gorman <>
Date: Mon, 20 Apr 2009 14:37:20 -0600
Message-ID: <>


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

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 Mon Apr 20 2009 - 15:37:20 CDT

Original text of this message