Hi Dave, I have used the tracefile truncation using the > operation in past (no cat /dev/null is even needed): "> db_arc1_1234.trc" (without double quotes of course). Other options are more hard-core, you could connect to the process with oradebug and issue oradebug close_trace, but I don't recommend touching background processes with oradebug. Another option would be to set log_archive_processes to 0 temporarily, wait until archivers exit and then set the parameter back to original value. I would use OS level truncate with > , this releases space back to filesystem. As with everything, test this out and verify yourself before doing it in production. -- Tanel Poder http://blog.tanelpoder.com On Fri, Oct 23, 2009 at 10:40 PM, Herring Dave - dherri < Dave.Herring@xxxxxxxxxx> wrote: > Folks, is there any way to force Oracle background processes to close and > re-open their trace files? As an example, say we've got 4 archiver > processes with 4 trace files: > > db_arc1_1234.trc > db_arc2_1235.trc > db_arc3_1236.trc > db_arc4_1237.trc > > Over time as the instance stays up and processes don't crash, these trace > files grow. If we ever want to "clean them up", it'd be great to get those > processes to close the file, then we'd copy, tar, gzip those files, then > have the process open a new file (same name). > > I could try copying the file while it's opened and then "cat /dev/null > >db_arc1_1234.trc", but I'm reluctant to test this on production and I don't > have anywhere to test this. > > The reason this is an issue is we've got trace files that have grown large > over time and previously we blindly removed these files. The problem is, > since the processes had them opened, future writes couldn't be done and if > there's a major crash (which we've had) no tracing gets written. Argg! > > David C. Herring | DBA, Acxiom Database Services > > 630-944-4762 office | 630-430-5988 cell | 630-944-4989 fax > 1501 Opus Pl | Downers Grove, IL, 60515 | U.S.A. | www.acxiom.com >