 |
Logs, Logs Everywhere
May 26, 2004 |
|
No matter which version of Oracle's Application Server you are using, you will have to manage log files. Just about every component in Oracle Application Server 10g creates a log file. These files can, and will, quickly fill up your hard drive if you do not manage them. Run Only the Components in Production that you are Using. This seems obvious but I find that a lot of companies are running components (like Wireless) that they are not using. If you are not using it, don't start it (or shut it down after restarting) to free up the server resources the component is using. This will also reduce the components creating log files. Purge Log Files Frequently Create a script that will archive (and possible compress) the log files you need to maintain. The script could also read through a log file looking for errors and delete the file if it finds no errors. Also use OEM to set the appropriate logging levels. If you Application Server is running consistently without problems, consider reducing the logging level for certain components. Logging unnecessary data is simply a waste of resources. Where are all these Log Files? Each component has a subdirectory under the instance's $ORACLE_HOME. Each of these subdirectories has a /log subdirectory where that component writes it's log files. OC4J containers each have a subdirectory located under the: $ORACLE_HOME/j2ee/<OC4J Name>/log Each application deployed in a container will be in a subdirectory of that container with a /log directory of its own. The Web Cache may be on a seperate server, either way it writes it's log data to: $ORACLE_HOME/webcache/log Of course OHS always creates large logs and AS10g automatically rotates the logs for you. Now you do not have to manually restart OHS to change logs files. Don't Forget the Database. Finally, you must manage the ARCHIVELOG files from the asdb database. (You are running in ARCHIVELOG mode!?!?!). These file need to be maintained for as long as you are maintaining asdb backups. Remember, a backup can not be rolled forward without the ARCHIVELOG files.
Regards, John Garmany
John Garmany
|
|
