Most recently, the disk space on the test environment server was tight, and the data in the tablespace didn't know what needed to be developed, and because the test library ran a long time, at least three years ago. So you start by cleaning up logs from the Oracle installation directory.
Found in the general these few logs, if not done regularly clean up, it is more space.
1.<user_dump_dest>/alert_<sid>.log
2. $ORACLE _home/oc4j/j2ee/oc4j_dbconsole_
Configuration file under Directory $oracle_home/oc4j/j2ee/oc4j_dbconsole_
Http-web-site.xml, wherein <access-log path= ". /log/http-web-access.log "/> Xiang Jo for
<access-log path= ". /log/http-web-access.log "split=" Day "/>
The resulting log $oracle_home/oc4j/j2ee/oc4j_dbconsole_
3.listener.log
Now say how to clear these log files.
The 1.alert alarm log can be deleted by renaming the file and then deleting it. After renaming, a Alert_<sid>.log file is automatically generated, sometimes it cannot be renamed, because the library is writing a log inside, and when it is convenient, the library is turned off and renamed.
2. You can delete Listener.log first, if not, Lsnrctl set Log_status off, then delete listener.log then Lsnrctl set log_status on
3.http-web-access.log log files under win for file attributes for AC can be directly deleted, remaining discretionary.
Linux, the first direct deletion, or not, first put dbconsole to stop, and then delete, and then dbconsole to start.
Today, I cleaned up the Http-web-access.log by the method above, and found that the log in this part was even da 5-6g.
And the previous period of time a development library on the alert log da 6g,win platform, the results of the log can not go in, the library rammed, then originally wanted to look at the alert log there is no information, the results found it difficult to open, so renamed a bit, the library on the normal operation. Record a sum here.
Reprint: http://www.linuxidc.com/Linux/2013-05/85091.htm
Clean up some log information in the Oracle installation directory