My Oracle Support Banner

Concurrent Processing - Internal Manager Log File contains messages "Could Not Initialize the Service Manager FNDSM_<HOSTNAME>_<SID>" for Non Concurrent Processing Nodes (Doc ID 754698.1)

Last updated on FEBRUARY 01, 2019

Applies to:

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

Symptoms

On 12.0.4 in Production:
When attempting to start concurrent manager, below message occurs in internal manager log file for every non concurrent processing node but concurrent manager is up and running as expected.

Messages in Internal Manager Log file:

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


Steps To Reproduce:
Use script "adstrtal.sh" to start all application services on every node. Issue can be reproduced at will with following step: adstrtal.sh start apps/<appspwd>

Business Impact:
Due to this issue, internal manager log file is having irrelevant messages related to concurrent processing which is creating confusion.

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
 Information Center, Diagnostics, & Community
References

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