When you clean log files be careful as some of them might still be used or could contain some kind of errors that system will need for some reason. Leave the logs which are 2-3 days old if you dont really need to delete them...
App server files:
$INST_TOP/logs/ora/10.1.2/forms - Forms dump files :
$INST_TOP/logs/ora/10.1.2/reports/cache - Reports Cache :
$INST_TOP/logs/ora/10.1.3/Apache - Apache logs
$INST_TOP/logs/ora/10.1.3/opmn - OPMN Logs
Its advisable not to remove any logs under $INST_TOP/logs/ora/10.1.3/j2ee directory since these are very important logs and are required frequently for debugging.
$INST_TOP/logs/appl/admin/log - Logs for service management
$INST_TOP/logs/appl/conc/log - Concurrent Manager logs
$INST_TOP/logs/appl/conc/out - Concurrent Manager out files
Also, please delete any of the applied patch directories and archives.
Database server
background_dump_dest,
user_dump_dest
core_dump_dest directories as they are full of trace files.
Check the location of ORACLE_HOME using du -sh command. Usually the size of ORACLE_HOME should be aounr 3-4G. If size of ORACLE_HOME (other then datafiles) is abnormally large like 7-8G or more then you need to investigate which directory is consuming more space and accordingly clean up that directory if appropriate.
In some situation if it becomes impossible to clean up the space (because there are no trace files to cleanup) and you desperately want the space to be available on the file system, then you can connect to database as sysdba and try to reduce the size of temp files using “alter database tempfile .. resize” comamnd. This will release some space and prevent database from crashing in case file system is reaching 100% full.
and finally one useful Linux command...
find . -mtime +1 -exec rm {} \ - delete log more than one day old.
Нема коментара:
Постави коментар
Напомена: Само члан овог блога може да постави коментар.