How To Truncate a Background Trace File Without Bouncing the Database
Last updated on DECEMBER 06, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 02-Sep-2016***
Please note that
Oradebug may blocked server process and instance terminated.
please refer to :How to recreate background trace file(s) that may have been accidentally deleted (Doc ID 394891.1)
This article outlines how to truncate a trace file generated by a background process without restarting the database and without breaking the logging mechanism.
Firstly, 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms