Unable to View Concurrent Requests Ouput Files

ISSUE:

"Unable to view Concurrent Requests log/output files"..

We are running 11.5.10.2 and recently did a clone of production to test. However, in the test environment when I run a concurrent request I am no longer able to view the logs or outputs through Oracle.

ERROR

An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_TESTDB There may be a network configuration problem, or the TNS listener on node FNDFS_TESTDB may not be running. Please contact your system administrator.


CHECKING:

a) Check whether Concurrent Request log & Output files generated in $APPLCSF/log & $APPLCSF/out to confirm this is NOT Concurrent issue

RESEARCH:

• ADI: Unable To View Reports In ADI [ID 1018797.102]
• How To Set RRA:Service Prefix for Multiple Instances on One Server [ID 235785.1]
• Tracing the sqlnet connection in ADI [ID 223136.1]
• Troubleshooting the "Error Occurred While Attempting to Establish an Applications
File Server Connection" [ID 117012.1]

SOLUITION Path:

1. Perform the RRA Setup Diagnostic Test

This Step will identify all Profile Settings & TNSNames.ora,Hostname in
FND_CONCURRENT_QUEUES table in one go.

Ref: 11i : Oracle Application Object Library Report Review Agent Setup Test
[ID 200358.1]


Command-Line Usage Instructions

• If the latest Oracle Diagnostics patch has been installed, this diagnostic script
is already available on your system. Change directory to $IZU_TOP/bin and execute
the test from there.

• If the latest Oracle Diagnostics patch has not been installed, download and unzip
the latest Oracle Diagnostics patch (see Note 167000.1)
Once unzipped, the Oracle Diagnostics patch can be installed in the normal way
using adpatch (see Note 167000.1) or the test can be executed directly from the
patch directory. Change directory to /izu/bin and execute the test
from there.

• Run the test as follows:

UNIX
$ ./FNDValidateFNDFS115.sh

Windows NT/2000
> sh FNDValidateFNDFS115.sh

2. CrossCheck for multiple Node Name

Verify that the nodename specified in the FNDFS_ entry is the
same as the nodename in the above error message. This should also match the
node name returned from the following select statement:

SQL> select distinct LOGFILE_NODE_NAME
from FND_CONCURRENT_REQUESTS;

3. If this is Cloned Instance from PROD, then check whether any profile values still
pointing to PROD

SQL> select a.profile_option_value,b.profile_option_name from
fnd_profile_option_values a , fnd_profile_options b
where a.profile_option_id=b.profile_option_id
and upper(profile_option_value) like '%PROD%' ;

SQL> select * from fnd_profile_options where profile_option_id=&ID;
SQL> select * from fnd_profile_option_values where profile_option_id=&ID;

4. Mostly issue could be either RRA Profile setting issue or any other profile
setting pointing to PROD