9.0.2.x access_logs: how best to minimize in production?

Question

In 9.0.2.x on Windows 2000, bugs prevent the correct use of CustomLog to minimize over-writing to the OHS (Apache) access_logs by DMS and OPMN. The only way to overcome this is with a lengthy workaround. Fun. The following is the default found in httpd.conf and builds monster access_logs:
CustomLog logs/access_log common
I have instead tried to use TransferLog. However, there are other bugs that inhibit its use and one must update the OHS config anyway or the webserver won't re-start. This is a very bad thing. None of the following statements in httpd.conf work:
TransferLog "|rotatelogs.exe D:\ora9ias\apps\apache\apache\logs\access_log 86400"
TransferLog "|rotatelogs.exe logs/access_log 86400"
TransferLog "|rotatelogs.exe logs\access_log 86400"
TransferLog "|rotatelogs.exe access_log 86400"
Is there a simpler more elegant way to keep the log files from growing so large? My only instance is in production and I'd like to avoid making any uninformed changes to the architecture. Daily rollover is preferred but not critical. Thanks! -- Mike
[Note:  Per MetaLink, at least one of the TransferLog statements should have worked, especially the third.  I could get the OHS (Apache) to start, but beyond creating a zero byte access log, it never began to write to it.]

Answer 1

Hi,
Try the following:
1. Backup $ORACLE_HOME/j2ee/*/config/default-web-site.xml
2. Edit $ORACLE_HOME/j2ee/*/config/default-web-site.xml to change the following:
<access-log path="../log/*_default_island_1/default-web-access.log"/>
to :
<access-log path="../log/*_default_island_1/default-web-access.log" split="day" suffix="yyyyMMdd"/>
This should create a new file every day in the format default-web-access20030522.log. Change the split to "week", etc. as you see fit. More information can be found on http"//www.orionserver.com/docs/access-log-format.html
I've been able to get that to work for a 903 middle-tier but not for 9021 OC4J. Good Luck.