Keep the log file size under the limit

A fellow DBA fixed an Oracle Grid Control’s Apache Server problem which had been causing a quick fill-up of the Oracle home directory on a Linux server. 

The culprit identified is the size of the following log file grew over the 2GB limit:
/app/oracle/product/gc/oms10g/Apache/Apache/logs/access_log

Once the limit reached, core dumps are triggered continuously till the file system is filled up which in turn cause the grid control agent stop and then other service failures as well.

The fix is to put the log file size under the 2GB limit by regularly (monthly, or even weekly) rotating the log file.

By the way, this log file in normal circumstances will not grow as big as 2GB, but it can surely happen on a Linux/Unix sever which may run multi-years without rebooting, if not a good file rotation in place.

Advertisements
This entry was posted in Blogroll. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s