How to recreate background trace file(s) that may have been accidentally deleted
(Doc ID 394891.1)
Last updated on NOVEMBER 06, 2019
Applies to:Oracle Database - Standard Edition - Version 220.127.116.11 to 18.104.22.168 [Release 9.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
Oracle Real Application Cluster
Oracle Rdbms (Single Instance)
The goal of this document is to help recreate the trace files for background processes (like lmon,lms,pmon,ckpt) which have been deleted or renamed to some other file. There are many reasons why customers delete trace files. Some examples are
- Customers have jobs which go in and delete trace files which have not been written into for X days.
- Lack of space on the file system containing these traces
- Accidental as in file to be deleted was ora_lms1_10945.trc but the command given was rm -r ora_lms1*
In the end, it does not matter why these traces are deleted but the importance of these trace files come up when these trace files are requested by Oracle support for any issue that the customer has opened an Service request for.
It is a bad idea to delete trace files of background processes which are still active. If an automated job has been implemented to remove inactive trace files then it is recommended that the job skips the deleting / archiving or moving of files that are open.
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