Forms Applet not Started From Homepage After Run of Autoconfig [ID 989464.1] | |||||
修改时间 15-JAN-2010 类型 PROBLEM 状态 MODERATED |
In this Document
Changes
Solution
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
Applies to: Oracle Applications Technology Stack - Version: 11.5.10 to 11.5.10.2 - Release: 11.5 to 11.5
Information in this document applies to any platform.
SymptomsAfter running Autoconfig the environment has problems in starting Forms functions from the Homepage. When selecting a function expected to start Forms nothing happens, but also no error is raised for the user. Calling Forms using /dev60cgi/f60cgi starts the Forms applet as expected, so Forms is available and up and running.
Investigation of the Apache log files shows the following entries
access_log_pls
error_log_pls
[Mon Jan 11 10:58:20 2010] [error] mod_plsql: /pls/xxx/fnd_icx_launch.launch HTTP-403 ORA-1017
These indicate that the request to the PLS Apache listener done as part of starting Forms responds with a 403 (Forbidden) due to login problem of MOD_PLSQL (ORA-1017 invalid username/password). This causes that the redirect to /dev60cgi/f60cgi call is not performed and Forms applet is not started.
ChangesAutoconfig was run delivering new configuration files for the environment Cause
In this case the errors were caused by the following entries in the $IAS_ORACLE_HOME/Apache/Apache/conf/apps.conf
Order deny,allow
Deny from all
Allow from %oacore_fwk_nodes%
For some reason the Autoconfig run did not replace the variable %oacore_fwk_nodes% with the list of servers granted access. SolutionTo implement a quick work-around to have Forms started properly again perform the following steps
Order deny,allow
Deny from all
Allow from %oacore_fwk_nodes%
The above steps should be considered a WORK-AROUND rather than SOLUTION. Autoconfig should deliver a proper set of configuration files without performing manual actions (which are easily forgotten).
So review the logs of the Autoconfig run to identify what went wrong preventing the %oacore_fwk_nodes% to be replaced with a list of hosts allowed to connect and have this corrected. If you can not identify a root-cause it may be useful to raise a Service Request with Oracle Support to assist with this.