housekeeping of OAS log files

From: EdStevens <quetico_man_at_yahoo.com>
Date: Mon, 10 Dec 2007 09:04:55 -0800 (PST)
Message-ID: <7ddf89d0-02cc-4e2d-aa08-4febb7794ea4@s8g2000prg.googlegroups.com>

Platform: OAS 10 on HPUX 11

Tracking down some disk consumption issues and am looking at all of the logs created by the various parts of the OAS installation. For similar files under dbcontrol there are configuration settings to limit the size and number of 'generations' of various log files, but I'm not finding anything like that for these. In fact, one bit of documentation (which I don't have at hand at the moment) even said point blank that this functionality doesn't exist for the OAS logs.

Currently, I'm running a daily cron job to truncate all of these files, but can't help but thinking there must be a more elegant way of dealing with them. I could run a script that rolls them over every day and keeps only so many generations, but I've found quite a bit of Oracle's logging seems to be going to the inode rather than the file name. (For instance, if you rename the listener.log to listener.log. 1, the listener will not initialize a new listener.log but will instead continue to write to listener.log.1 until such time as the listener is restarted.)

Anyone have any other suggestions?

Here's the files I'm dealing with:

./j2ee/home/application-deployments/BC4J/home_default_island_1/
application.log
./j2ee/home/application-deployments/IsWebCacheWorking/
home_default_island_1/application.log
./j2ee/home/log/home_default_island_1/default-web-access.log
./j2ee/home/log/home_default_island_1/global-application.log
./j2ee/home/log/home_default_island_1/jms.log
./j2ee/home/log/home_default_island_1/rmi.log
./j2ee/home/log/home_default_island_1/server.log
./j2ee/OC4J_BI_Forms/application-deployments/formsapp/
OC4J_BI_Forms_default_island_1/application.log
./j2ee/OC4J_BI_Forms/application-deployments/reports/
OC4J_BI_Forms_default_island_1/application.log
./j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1/default-web-
access.log
./j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1/global-
application.log
./j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1/jms.log
./j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1/rmi.log
./j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1/server.log
./opmn/logs/ipm.log
./opmn/logs/ons.log
./reports/logs/rep_$HOSTNAME/rwserver.log
./sysman/j2ee/application-deployments/Oc4jDcmServlet/application.log
./sysman/log/em-application.log
./sysman/log/em-web-access.log
./sysman/log/emagent.log
./sysman/log/emagent.trc
./sysman/log/emagentfetchlet.log
./sysman/log/emagentfetchlet.trc
./sysman/log/rmi.log
./sysman/log/server.log

The following files always show an mtime of the current date. The item before each file name is the approximate number of records written to the file, per minute. You can see that the ...default_island_1/default-web-access.log is particularly busy.

8/min   ./j2ee/home/log/home_default_island_1/default-web-access.log
-----   ./j2ee/home/log/home_default_island_1/global-application.log
2/min   ./j2ee/home/log/home_default_island_1/server.log
30/min  ./j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1/

default-web-access.log
2/min ./j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1/ server.log
0.1/min ./sysman/log/em-web-access.log Received on Mon Dec 10 2007 - 11:04:55 CST