In this Document
Oracle Server - Enterprise Edition - Version: 10.2.0.1
Information in this document applies to any platform.
This article outlines how to truncate a trace file generated by a background process without restarting the
database and without breaking the logging mechanism.
In the first place you should investigate why this tracing is being written. If it is due to an event setting then this
event needs to be disabled otherwise the tracing will just restart after the file has been truncated.
1. First identify the process id of the background process in question, in this example I will use LGWR
2. Secondly, use oradebug to set the orapid and therby attach to the background process
3. Rename the trace file at the Operating System level
4. Next close the trace file:
When the background process needs to write to the trace file again it will create a new logfile.
How To Truncate a Background Trace File Without Bouncing the Database [ID
Modified 12-SEP-2008 Type HOWTO Status MODERATED
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has
not been subject to an independent technical review.
SQL> select pid, program from v$process where program like '%LGWR%';
6 oracle@besun21 (LGWR)
SQL> oradebug setorapid 6
Unix process pid: 21955, image: oracle@besun21 (LGWR)
SQL> oradebug close_trace
Page 1 of 2
Back to top
Rate this document
Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Page 2 of 2
Back to top
https://support.Page 2 of 2
Related Products Oracle Database Products > Oracle Database > Oracle Database > Oracle Server .oracle.1