Forms Applet not Started From Homepage

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

- - [11/Jan/2010:10:58:20 +0700] "GET /pls/xxx/fnd_icx_launch.launch?resp_app=SYSADMIN&resp_key=SYSTEM_ADMINISTRATOR&secgrp_key=STANDARD&start_func=FND_FNDSCMOU&other_params= HTTP/1.0" 403 223

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

The below text describes a cause for this issue. However keep in mind there will be multiple causes for the errors reported. For example having changed APPS password, but still using old password in the wdbsvr.app results in the same behavior/errors as reported here.

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%

 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

1. In the access_log_pls verify the 'client' performing the request. In this case it's most likely the hostname (+domain) of the server used. Note down this value
   
2. In the apps.conf replace %oacore_fwk_nodes% with the value from 1 (for all references) and save the changes
   
3. Restart the Apache services using adapcctl.sh to have the changes picked up
4. Retest the issue to confirm Forms can be started properly
   

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.

阅读(3287) | 评论(0) | 转发(0) |

0

上一篇：如何通过串口线联接SUN V880服务器

下一篇：Purchasing Receiving Accrual Records Missing