Concurrent Manager Startup Fails To Spawn The Service Manager FNDSM and Generates Error Unable to contact Applications TNS Listener for FNDSM_XXX_XXX on $NODE
(Doc ID 2567727.1)
Last updated on DECEMBER 05, 2024
Applies to:
Oracle Concurrent Processing - Version 12.2.7 to 12.2.8 [Release 12.2]Oracle Concurrent Processing - Version 12.2.6 to 12.2.6 [Release 12.2]
Oracle Concurrent Processing - Version 12.2 to 12.2 [Release 12.2]
Information in this document applies to any platform.
Symptoms
On : 12.2.7 version, Concurrent Manager Issues
ACTUAL BEHAVIOR
---------------
Concurrent Manager Startup Fails To Spawn The Service Manager FNDSM.
After server reboot the Concurrent Managers will not restart. The applications listener starts and tnsping and lsnrctl commands are successful.
Errors from logfile:
Unsuccessful in TNS ping of node XXX, error reported: Ping Timed Out.
Could not contact Service Manager FNDSM_XXX_XXXX. The TNS alias could not be located, the listener process on NODE could not be contacted, or the listener failed to spawn the Service Manager process.
Process monitor session started : 20-JUL-2019 19:11:16
Unable to contact Applications TNS Listener for FNDSM_XXX_XXXX on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=NODENAME)
An error occured in client-side routine afpsmccs for Service Manager FNDSM_XXX_XXXX. The routine returned code 144.
EXPECTED BEHAVIOR
-----------------------
Expect the Service Manager to start.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Bring up the concurrent managers.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |