~]$ tail -50000 /path/to/alert_ORCL.log > /path/to/alert_ cp -f /path/to/alert_ /path/to/alert_ORCL.log cat /dev/null > /path/to/alert_ Additionally, this could also reduce the loss of log entries between executions. ~]$ cat /dev/null > /path/to/alert_įor convenience, I concatenate all commands in one line for executing them without any gaps. ~]$ cp -f /path/to/alert_ /path/to/alert_ORCL.logĮmpty the transitional file in order to free its space if the space is still sensitive. ~]$ tail -50000 /path/to/alert_ORCL.log > /path/to/alert_Ĭopy the temporary and transitional file back to the alert log with force option. If you want to keep most recent entries in the alert log just like trimming obsolete records off the alert log file, you may play this trick.īackup the last certain number of lines of the alert log into a second file which is temporary and transitional in the first command. Just don't forget to change the location of alert log.ĭeleting the alert log directly is also a way to do it as long as no one locks the file at that moment, the database will create a new file for the alert log afterwards.
This command can solve your space problem in a second if you have no time to think over a better solution. Whenever you want to clear alert log in a hurry or the space problem becomes serious, you can empty all content of alert log in this way: ~]$ cat /dev/null > /path/to/alert_ORCL.log In this post, I'd like to share how I reduce the size of alert log by means of trimming the content of alert log file.
#DOES CLEARING A LOGFILE RENAME IT ORACLE MANUAL#
The retention of alert log cannot be controlled by ADRCI utility, it needs manual intervention.
0 kommentar(er)
