|
|
做了一些尝试，目前不起作用
action one:
a. Run the following in SQL*Plus:
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
b. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers, to repopulate the required system tables.
action two:
Symptoms
Users are not able to Launch Forms from SSWA pages. Apache error_log has following entries:
1. [error] "client denied by server configuration: /tbsi/pbsilcomn/portal/TBSI_appsuat/oprocmgr-service" 2. [error] "client denied by server configuration: /tbsi/pbsilcomn/portal/TBSI_appsuat/pls"
Cause
Oracle Process Manager (OPM) & mod_sql module is not considering the Middle Tier Node as trusted.
It is more likely an issue with host_name resolution for the IP Address.
1. [error] "client denied by server configuration: /tbsi/pbsilcomn/portal/TBSI_appsuat/oprocmgr-service" shows that OPM is not considering the Middle Tier Node as trusted.
2. [error] "client denied by server configuration: /tbsi/pbsilcomn/portal/TBSI_appsuat/pls " shows
that mod_sql is not considering the Middle Tier Node as trusted.
Solution
To implement the solution, please execute the following steps:
1. Following files at $IAS_ORACLE_HOME/Apache/Apache/conf/ require the manual modification so that user can launch Forms from SSWA.
oprocmgr.conf
apps.conf
trusted.conf
security.conf
httpd_pls.conf
Note: Before making these manual changes check FND_NODES table to confirm that correct IP address of Middle Tier Node is populated in the column 'SERVER_ADDRESS' . If not then repopulate it with correct IP address and retest the issue.
@ Note 751328.1 gives the method to change the IP address (not yet published).
2. Add IP Address of the Middle Tier Node at all the occurrences of host_name.domain_name e.g. 'atg.oracle.com' or 'atg' in the aforementioned files.
3. You can find corresponding Template files at $FND_TOP/admin/template/ and can customize them
with the help of Metalink Note 270519.1
Also You can review the
NOTE.<<165195.1>> Using AutoConfig to Manage System Configurations
NOTE.<<218089.1>> Autoconfig FAQ
action three
Symptoms
When attempting to log into a new clone or fresh install using the URL
http://hoatname.domain![\"\"](\"static/image/smiley/qqbiaoqin/tq.gif\") ort/oa_servlets/AppsLogin
The following error occurs.
Cause
The issue is caused because the OPM process is not considering the Middle Tier Node as trusted. The issue can be seen in the error_log
[Wed Oct 29 12:40:40 2008] [error] [client 111.111.111.111] client denied by server configuration:
x:/oracle/testcomn/portal/test_gilthoniel/oprocmgr-service
Solution
To implement the solution, please execute the following steps on all Web Tiers:
1:- Update your autoconfig context file and change the
s_oacore_trusted_oproc_nodes to include the IPAddress as well
CHANGE
<oacore_trusted_oproc_nodes oa_var="s_oacore_trusted_oproc_nodes">HOSTNAME, HOSTNAME.DOMAIN,VIRUTALHOSTNAME,VIRUTALHOSTNAME.DOMAIN</oacore_trusted_oproc_nodes>
TO
<oacore_trusted_oproc_nodes oa_var="s_oacore_trusted_oproc_nodes">IPADDRESS, HOSTNAME, HOSTNAME.DOMAIN,VIRUTALHOSTNAME,VIRUTALHOSTNAME.DOMAIN</oacore_trusted_oproc_nodes>
2:- Run autoconfig
3:- Please retest the issue.
4:- If the issue is resolved, please migrate the solution as appropriate to other environments.
Symptoms
When attempting to log into a new clone or fresh install using the URL
http://hoatname.domainort/oa_servlets/AppsLogin
The following error occurs.
Cause
The issue is caused because the OPM process is not considering the Middle Tier Node as trusted. The issue can be seen in the error_log
[Wed Oct 29 12:40:40 2008] [error] [client 111.111.111.111] client denied by server configuration:
x:/oracle/testcomn/portal/test_gilthoniel/oprocmgr-service
Solution
To implement the solution, please execute the following steps on all Web Tiers:
1:- Update your autoconfig context file and change the
s_oacore_trusted_oproc_nodes to include the IPAddress as well
CHANGE
<oacore_trusted_oproc_nodes oa_var="s_oacore_trusted_oproc_nodes">HOSTNAME, HOSTNAME.DOMAIN,VIRUTALHOSTNAME,VIRUTALHOSTNAME.DOMAIN</oacore_trusted_oproc_nodes>
TO
<oacore_trusted_oproc_nodes oa_var="s_oacore_trusted_oproc_nodes">IPADDRESS, HOSTNAME, HOSTNAME.DOMAIN,VIRUTALHOSTNAME,VIRUTALHOSTNAME.DOMAIN</oacore_trusted_oproc_nodes>
2:- Run autoconfig
3:- Please retest the issue.
4:- If the issue is resolved, please migrate the solution as appropriate to other environments.
Symptoms
When attempting to log into a new clone or fresh install using the URL
http://hoatname.domainort/oa_servlets/AppsLogin
The following error occurs.
Cause
The issue is caused because the OPM process is not considering the Middle Tier Node as trusted. The issue can be seen in the error_log
[Wed Oct 29 12:40:40 2008] [error] [client 111.111.111.111] client denied by server configuration:
x:/oracle/testcomn/portal/test_gilthoniel/oprocmgr-service
Solution
To implement the solution, please execute the following steps on all Web Tiers:
1:- Update your autoconfig context file and change the
s_oacore_trusted_oproc_nodes to include the IPAddress as well
CHANGE
<oacore_trusted_oproc_nodes oa_var="s_oacore_trusted_oproc_nodes">HOSTNAME, HOSTNAME.DOMAIN,VIRUTALHOSTNAME,VIRUTALHOSTNAME.DOMAIN</oacore_trusted_oproc_nodes>
TO
<oacore_trusted_oproc_nodes oa_var="s_oacore_trusted_oproc_nodes">IPADDRESS, HOSTNAME, HOSTNAME.DOMAIN,VIRUTALHOSTNAME,VIRUTALHOSTNAME.DOMAIN</oacore_trusted_oproc_nodes>
2:- Run autoconfig
3:- Please retest the issue.
4:- If the issue is resolved, please migrate the solution as appropriate to other environments. |
|
楼主: tj8858
IP卡
狗仔卡
楼主
显身卡
发表于 2010-6-11 09:11
