Issue : In the $APPLCSF/log/
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE.
Cause - Missing entry of FNDSM_NODEAPP01 in FND_CONCURRENT_QUEUES
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
It should show some thing like - NODEAPP01 is the hostname of the application server.
FNDSM_NODEAPP01
Solution :
1)
Run below script as apps user from application node.
$FND_TOP/patch/115/sql/afdcm037.sql
And verify
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
2)
If its not updating afdcm037.sql or giving error , restore table FND_CONCURRENT_QUEUES from backup
-take backup of existing table
create table applsys.FND_CONCURRENT_QUEUES_BKP as select * from applsys.fnd_concurrent_queues;
truncate table applsys.fnd_concurrent_queues;
select count(1) from applsys.fnd_concurrent_queues;
insert into applsys.fnd_concurrent_queues select * from applsys.fnd_concurrent_queues_oldbkbp_table;
--Verify
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
It should return - FNDSM_NODEAPP01
--Start the concurrent manager.......
---------------------Enjoy----
Exact Error in .mgr file while starting concurrent manager using adcmctl.sh
----------------------------
-------Error-------
Process monitor session ended : 27-JAN-2022 09:09:36
27-JAN-2022 09:10:06
Request : 86188175
Priority : 0
Program : 0/5
State : Q
Process monitor session started : 27-JAN-2022 09:10:06
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=NODEAPP01)
An error occured in client-side routine afpsmccs for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 144.
Check for preceding errors and as well as the service manager log file for further details."
AFPPSPL-- 27-JAN-2022 09:10:06
Call to PingProcess failed for FNDOPP
AFPPSPL-- 27-JAN-2022 09:10:06
Node:(NODEAPP01), Service Manager:(FNDSM_NODEAPP01_VIJ4) currently unreachable by TNS
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=NODEAPP01)
An error occured in client-side routine afpsmccs for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 144.
Check for preceding errors and as well as the service manager log file for further details."
AFPPSPL-- 27-JAN-2022 09:10:06
Call to PingProcess failed for FNDOPP
AFPPSPL-- 27-JAN-2022 09:10:06
Node:(NODEAPP01), Service Manager:(FNDSM_NODEAPP01_VIJ4) currently unreachable by TNS
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=NODEAPP01)
..................
An error occured in client-side routine afpsmccs for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 144.
Check for preceding errors and as well as the service manager log file for further details."
AFPPSPL-- 27-JAN-2022 09:12:07
Call to PingProcess failed for FNDOPP
Process monitor session ended : 27-JAN-2022 09:12:07
========================================================================
Starting VIJ4_0127@VIJ4 Internal Concurrent Manager -- shell process ID 3458568
logfile=/mount/CVIJ4/fs_ne/inst/VIJ4_NODEAPP01/logs/appl/conc/log/VIJ4_0127.mgr
PRINTER=noprint
mailto=applmgr
restart=N
diag=N
sleep=30
pmon=4
quesiz=1
Reviver is ENABLED
+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 12.2
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
Internal Concurrent Manager started : 27-JAN-2022 09:13:55
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
27-JAN-2022 09:13:55 - Checking ICM sleep
27-JAN-2022 09:13:55
Unsuccessful in TNS ping of node AZVMEBSDEVAPP02, error reported: Listener Not Found.
Could not contact Service Manager FNDSM_AZVMEBSDEVAPP02_VIJ4. The TNS alias could not be located, the listener process on AZVMEBSDEVAPP02 could not be contacted, or the listener failed to spawn the Service Manager process.
Process monitor session started : 27-JAN-2022 09:13:55
Starting PODAMGR Concurrent Manager : 27-JAN-2022 09:13:55
Could not initialize the Service Manager FNDSM_NODEAPP01_VIJ4. Verify that NODEAPP01 has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 126.
Check for preceding errors and as well as the service manager log file for further details."
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /mount/CVIJ4/fs1/EBSapps/appl/po/12.0.0/bin/POXCON.
Check that your system has enough resources to start a concurrent manager process. Contact your system admin : 27-JAN-2022 09:13:55
Starting RCVOLTM Concurrent Manager : 27-JAN-2022 09:13:55
Could not initialize the Service Manager FNDSM_NODEAPP01_VIJ4. Verify that NODEAPP01 has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 126.
Check for preceding errors and as well as the service manager log file for further details."
Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /mount/CVIJ4/fs1/EBSapps/appl/po/12.0.0/bin/RCVOLTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system admi : 27-JAN-2022 09:13:56
Starting INVTMRPM Concurrent Manager : 27-JAN-2022 09:13:56
Could not initialize the Service Manager FNDSM_NODEAPP01_VIJ4. Verify that NODEAPP01 has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 126.
------------------------
No comments:
Post a Comment