How To Truncate a Background Trace File Without Bouncing the Database
(Doc ID 564989.1)
Last updated on JANUARY 30, 2022
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document