R12无法打开output和log

无法打开output和log文件，
报错An error Occurred While Attempting to Establish an Applications File Server Connection with Node FNDFS Error
遇到这个问题，可以根据metalink上的 Doc ID 117012.1检查一下，
1. Is this a Multinode Install or a Single Node Install.
- If this is a Multinode Install, you will need access to the
Middle Tier and the Backend Tier (Concurrent Processor)
8.0.6 ORACLE_HOME/network/admin/tnsnames.ora files

- If this is a Single Node Install, you need access to the
Concurrent Processor 8.0.6 ORACLE_HOME/network/admin/tnsnames.ora file

2. Run a report, is there actually a Report Output and Log file being produced at
the Operating System level?
- Check the $APPLCSF/out and the $APPLCSF/log directories
for the Request_ID out and log file
- If there are no log and output file being produces there,
Check the permissions on those directories (APPLMGR should have write)
- If $APPLCSF is not set, check the $FND_TOP/log and out for output and logs

3. Confirm that there are 2 listener processes actively running for the Instance that
you cannot view reports on -- 1 from 8.0.6 and from 8.1.6 directory structures
- type the following:
ps -ef | grep tnslsnr
- If there is only 1 listener running from the 8.1.6 directory structure
That is the Database Listener
The FNDFS listener needs to be started separately from the Database Listener
- To start the FNDFS Listener:
a. Log the Operating System Level as the APPLMGR account user
b. Set the environment for the $APPL_TOP & 8.0.6 $ORACLE_HOME (APPSORA.env)
c. Go to the $OAD_TOP/admin/scripts (Common_top area)
d. Run the following script:

adalnctl.sh start APPS_

(you can confirm the FNDFS Listener name from viewing the
8.0.6 ORACLE_HOME/network/admin/listener.ora file)

4. Check the actual machine name for the Concurrent Processor Server
- type the following:
uname -n

5. Go to the Applications and check the CONCURRENT > MANAGER > ADMINISTER screen
in the System Administrator Responsibility
The INTERNAL MANAGER NODE NAME; is it the same as what was returned from question 4?
- If it is the same then continue with next step
- If it is not the same,
Shutdown Concurrent Managers and update the FND table:
a. Go to the $OAD_TOP/admin/scripts
b. adcmctl.sh apps/apps stop
c. Connect to SQL*PLUS apps/apps

d. SQL > select target_node
from FND_CONCURRENT_QUEUES;
--------------------
This may return the name of an old machine

e. SQL > update FND_CONCURRENT_QUEUES
set target_node=''
where target_node='';

f. SQL > commit;
g. SQL > exit
h. adcmctl.sh apps/apps start


6. In the 8.0.6 TNSNAMES.ora file, look at the FNDFS_ connection string entry.
Is the hostname value the same as is in questions 4?
- The Rapid Install creates 2 or sometimes 3 FNDFS entries in the TNSNAMES.ora
a. 1 with the FNDFS_
b. 1 with the FNDFS_
c. 1 with the FNDFS_
- The one that is the correct entry is FNDFS_
(hostname being what is returned from a "uname -n")
- If this file does not contain the correct Hostname value
Make a backup of it and edit it to change the FNDFS entry.

7. Check the Network Connection for the FNDFS entry that was defined by the Rapid Install.
- At the Operating System Level
a. tnsping FNDFS_
- This should return the Hostname name and Port information
identical to the FNDFS entry in the TNSNAMES.ora file


8. Check the Following PROFILE > SYSTEM Options in The System Administrator Responsibility

CONCURRENT: Report Access Level (this must be set to USER or RESPONSIBILITY)
RRA: Service Prefix (this should be BLANK)
RRA: Enabled (this must be set to YES)
VIEWER: Text (this should be BLANK to view with the default text viewer)
- Viewer: Text can Be set to "browser" to view with Netscape or IE


9. This step should be performed in a case where there might have been patches applied
and possibly the FNDFS executable was not Relinked, or it may be
missing from the file system or corrupted.
- Shutdown the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh stop APPS_
- Rename or Move the Current FNDFS executable before relinking
a. $FND_TOP/bin
mv FNDFS FNDFS.bak
b. As APPLMGR account user
adrelink.sh force=y "fnd FNDFS"
- Start the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh start APPS_





如果配置了多个应用节点，尤其是设置负载均衡还要在每个节点上都tnsping一下FNDFS_<>(报错信息里面的内容)是否能ping通，如果报TNS-03505: Failed to resolve name

检查一下$INST_TOP/ora/10.1.2/network/admin下的tnsnames.ora文件，如果没有FNDFS_<>，那么可能是autoconfig的时候出现文件，没有其他的问题，可能在tnsnames.ora文件中手工添加FNDFS_<>，如果报lost contact错误，先<>节点上执行alalnctl.sh检查一下应用监听的状态，如果正常，那么可能问题要么是网络issue比如防火墙调整了规则，要么是配置问题，我的问题出现在sqlnet.ora文件，这个文件是autoconfig自动生成的，会有访问控制
tcp.validnode_checking = yes
tcp.invited_nodes = (XXXXXXXXX)
把节点2个主机名加入到tcp.invited_nodes里面，问题解决。

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/11289933/viewspace-1611454/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/11289933/viewspace-1611454/