How to Prevent "File does not exist" Errors in the error_log?

PURPOSE
——-
This article explains the changes needed in the httpd.conf file to remove some
of the non-troublesome errors in the error_log.

SCOPE & APPLICATION
——————-
This document applies to users who are web deploying forms Oracle AS and hit
Bug 1878975 and and Bug 2376588 and Bug 4569261. Due to these bugs the error_log
will have the following error messages
File does not exist: d:/ora9ias2/forms90/java/java/awt/KeyboardFocusManager.class
File does not exist: d:/ora9ias2/forms90/java/java/awt/KeyboardFocusManager.class
File does not exist: d:/ora9ias2/forms90/java/oracle/forms/registry/default.dat
According to Bug 2376588, these are valid, non-trouble some errors. However, it
causes unnecessary confusion to users and also contribute to significant
increase in file size of the error_log.


How to prevent “File does not exist” errors in the error_log?
————————————————————-

These entries can be removed by setting the LogLevel directive in httpd.conf
file to level “Critical". You can change this setting using the Enterprise
manager(EM) website OR by editing httpd.conf.
Method 1: Using the EM website
——————————-
1. Navigate to the Oracle HTTP Server Home Page on the Oracle Enterprise
Manager Web site. Scroll to the Administration section.
2. Select Server Properties in the Administration section. This opens the Server
Properties Page.
3. Scroll to the Logging section of the Server Properties Page.
4. Select the logging level as “Critical” from the Error Logging Level drop-down menu. The
logging level indicates the severity of the error being reported.
5. Scroll to the end of the page and click Apply to accept the changes. If you do
not click Apply, you will lose your changes. If you make a mistake or want to
undo any changes, click Revert.
Enterprise Manager displays a confirmation page, which confirms that the
appropriate configuration files have been updated.
6. Click Yes to restart the HTTP Server so the changes will take effect. Click No to
restart the server later.
Method 2: Editing httpd.conf
—————————-
Open the httpd.conf file for the “Business Intelligence and Forms” instance.
Look for the section “LogLevel". Set it to “crit’.
For example:
LogLevel crit
Information on Loglevel directive
———————————
LogLevel adjusts the verbosity of the messages recorded in the error. The
following levels are available, in order of decreasing significance:
Level Description
—– ———–
emerg Emergencies
alert Action must be taken immediately.
crit Critical Conditions
error Error conditions.
warn Warning conditions.
notice Normal but significant condition.
info Informational.
debug Debug-level messages
When a particular level is specified, messages from all other levels of higher
significance will be reported as well. E.g., when LogLevel info is specified,
then messages with log levels of notice and warn will also be posted.
Using a level of at least crit is recommended.
RELATED DOCUMENTS
—————–
Apache documentation at http://httpd.apache.org/docs/mod/core.html#loglevel
Oracle Application Server Administrator?s Guide