Connect and share knowledge within a single location that is structured and easy to search. I have an oracle 11G instance. Its trace file are increasing day by day and causing a disk space issue. I have to delete it manually on every disk space alert. I use the command:. I can schedule this also in cronjob, but I want to know what it will effect in deleting these files and why these files are increasing so much in size.
How can I reduce these file by increasing and what will this effect in our database? Why is the database generating a bunch of trace files? A trace file would either indicate an error, in which case you would generally need to examine the trace file to determine what the error is and how to correct it, or it would indicate that someone enabled tracing for a session in order to debug an issue, in which case you would want to retain the trace file so that you can do that debugging.
Deleting trace files without looking at them means that you are almost certainly ignoring a symptom of a problem that has the potential to get worse over time. If this is a real production database rather than a toy database on your local machine, I would strongly suggest determining why the trace files are getting created in the first place and addressing whatever issue s are causing the trace files to be created.
How are we doing? Trace files have to be controlled and cleaned regularly, otherwise your disk space will be exhausted soon or later. But cleaning trace files may become a hard work, because the trace files belongs to various logging purposes and they are scattered all over the database server, it may cost you a lot of time to find them and delete trace files.
Trace files include core dump, user dump and background dump from grid, rdbms or listener. For the alert log, it's a little different, you can delete or trim it for reducing the size of the file. Please note that auditing files and the alert log are not included in trace files by definition, you have to find an integrated way to delete all trace logs, audit files, alert log and so on.
You can also use Linux command lsof to list Oracle processes accessing deleted files. Just beware this was quite buggy in early 11g releases. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more.
Clean trace files on Oracle 11g Ask Question. Asked 9 years, 6 months ago. Active 8 years, 3 months ago. You can add this script to crontab for periodically and automatically purging log files. Please notice the following two things: The listener log seldom brings you troubles, but you can also add it into the script. In a RAC environment, you should take grid's log files into account, too. Your email address will not be published.
0コメント