My Oracle Support Banner

Applications Tier Listener Starts But Fails To Spawn The Service Manager FNDSM (Doc ID 1073677.1)

Last updated on MAY 05, 2023

Applies to:

Oracle Concurrent Processing - Version to 12.2 [Release 11.5 to 12.2]
Oracle Concurrent Processing - Version 12.2.6 to 12.2.6 [Release 12.2]
Information in this document applies to any platform.


When starting the Concurrent Generic Service Manager (FNDSM), all the other managers starts but the GSM fails to start. The following error occurs within the Internal Concurrent Manager (ICM) log file:

Could not contact Service Manager FNDSM_<Machine_Name>_<SID>. The TNS alias could not be located, the listener process on <Machine_Name> could not be contacted, or the listener failed to spawn the Service Manager process.

The Apps listener fails to spawn the FNDSM executable; however, All paths, port, FNDSM entries looks good within the listener.ora and tnsnames.ora files.

tnsping FNDSM_<Machine_Name>_<SID> gives "TNS-12541: TNS:no listener", Yet, lsnrctl status shows the listener is up with "Service "FNDSM" has 1 instance(s). Instance "FNDSM", status UNKNOWN, has 1 handler(s) for this service..."
No errors within in the Apps listener log.

A listener trace file shows the following error message:

"Attempted load of system pfile source /oracle/<SID>/inst/apps/<SID>_<Machine_Name>/ora/10.1.2/network/admin/listener.ora
Load contained errors
Error stack follows:
NL-00405: cannot open parameter file

Attempted load of command line source /oracle/<SID>/inst/apps/<SID>_<Machine_Name>/ora/10.1.2/network/admin/<SID>_<Machine_Name>_listener_ifile.ora
Parameter source was not loaded



The /etc/hosts file was altered recently.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.