ICM Log Filled With: Could not contact Service Manager FNDSM_ The TNS alias could not be located on RAC with Multi Application Tiers
(Doc ID 1905946.1)
Last updated on JANUARY 12, 2023
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.
When checking the internal concurrent manager(ICM) log, the error displays as follows:
Could not contact Service Manager. The TNS alias could not be located, the listener process on <node name> could not be contacted, or the listener failed to spawn the Service Manager process.
Could not contact Service Manager. The TNS alias could not be located, the listener process on <node name> could not be contacted, or the listener failed to spawn the Service Manager process.
Could not contact Service Manager. The TNS alias could not be located, the listener process on <node name> could not be contacted, or the listener failed to spawn the Service Manager process.
Could not contact Service Manager. The TNS alias could not be located, the listener process on <node name> could not be contacted, or the listener failed to spawn the Service Manager process.
Could not contact Service Manager. The TNS alias could not be located, the listener process on <node name> could not be contacted, or the listener failed to spawn the Service Manager process.
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 |