Should we delete grid infrastructure logs if it gets too big [message #632542] |
Mon, 02 February 2015 21:14 |
|
juniordbanewbie
Messages: 250 Registered: April 2014
|
Senior Member |
|
|
Hi all,
grid@ORAC01:~> du -d 0 -h $GRID_HOME/log
5.0G /u01/app/11.2.0.3/grid/log
from http://www.oracle.com/technetwork/articles/linux/part2-085179.html
Quote:
Oracle produces many extraneous files: trace files, log files, dump files, and so on. Unless they are cleaned periodically, they can fill up the filesystem and bring the database to a halt.
To ensure that doesn't happen, simply search for the files with extension "trc" and remove them if they are more than three days old. A simple command does the trick:
find . -name "*.trc" -ctime +3 -exec rm {} \;
To forcibly remove them prior to the three-day limit, use the -f option.
find . -name "*.trc" -ctime +3 -exec rm -f {} \;
If you just want to list the files:
find . -name "*.trc" -ctime +3 -exec ls -l {} \;
if the log files get too big, should we delete the log files. If yes according to MOS 1050908.1
Quote:
In Grid Infrastructure cluster environment:
Assuming a Grid Infrastructure environment with node name rac1, CRS owner grid, and two separate RDBMS owner rdbmsap and rdbmsar, here's what it looks like under $GRID_HOME/log in cluster environment:
which should be the ones that should be deleted.
thanks a lot!
|
|
|
|