ICM Log Filled With: Could not contact Service Manager FNDSM_ The TNS alias could not be located on RAC with Multi Apps Tiers (Doc ID 1905946.1)

Last updated on MAY 25, 2016

Applies to:

Oracle Concurrent Processing - Version 12.1.1 to 12.1.1 [Release 12.1]
Information in this document applies to any platform.

Symptoms

The instance has 4 Applications tier (AP) nodes with RAC, but only one Application node existing with one concurrent manager.

(The only concurrent manager exists on the server that is named "FNDSM_SRVRAP1_PROD".)

When checking the internal concurrent manager(ICM) log, the error displays as follows:

Could not contact Service Manager FNDSM_SRVRAP2_PROD. The TNS alias could not be located, the listener process on SRVERPAP2 could not be contacted, or the listener failed to spawn the Service Manager process.
Could not contact Service Manager FNDSM_SRVRAP3_PROD. The TNS alias could not be located, the listener process on SRVERPAP3 could not be contacted, or the listener failed to spawn the Service Manager process.
Could not contact Service Manager FNDSM_SRVRAP4_PROD. The TNS alias could not be located, the listener process on SRVERPAP4 could not be contacted, or the listener failed to spawn the Service Manager process.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms