Cause : TNS Listener is Down on node or Network Related Issue
1. Check your listener status
$ps -ef | grep tnslsnr
$ps -ef |grep FNDFS
If it is down you can start from using adalnctl.sh apps/****
2. Check actual Machine name for the concurrent process server are same
$uname -n
Check from Application System Administrator > concurrent > manager > Administer Responsibility
hope its same if not same then follow below steps
Stop concurrent manager and update FND table
$OAD_TOP/admin/scripts/adcmctl.sh apps/apps stop
Check Machine info
SQL > select target_node
from FND_CONCURRENT_QUEUES;
Here is the problem , this contents old machine
name , just update the new machine name here.
SQL> update_set '<newmachinename>' where '<oldmachinename>';
SQL> commit;;;;
SQL >start
3. Check TNSNAME.ora file , Have valid entry of FNDFS_<hostname>
If not entry then first take the backup of tnsfile.ora and modify
And check its ping or not
$ tnsping FNDFS_<hostname>
In our case its works , now file server connection properly
---
Next scenario : You have applied patch , And getting error FNDFS was not relink or missing
Solution :
Stop FNDFS
$OAD_TOP/admin/scripts/adalnctl stop apps/apps
Backup the current FNDFS before relinking
$ mv FNDFS FNDFS.bkp
Relink
$ adrelink.sh force=y 'FNDFS'
Start
$ OAD_TOP/admin/scripts/adalnctl start apps/apps
No comments:
Post a Comment