Unable to Bring Up Concurrent Managers after Running Autoconfig
(Doc ID 736024.1)
Last updated on APRIL 16, 2023
Applies to:
Oracle Concurrent Processing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]Information in this document applies to any platform.
Symptoms
After running autoconfig, unable to bring up the Concurrent Manager. The error message we are receiving is:
[Could not initialize the Service Manager <HOSTNAME_SID>. Verify that <node_name> has
been registered for concurrent processing.
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library
/u12/app/<hostname>/<node_name>/po/11.5.0/bin/POXCON.
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn
the Service Manager process.
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn the
Service Manager process.
Process monitor session started : 05-SEP-2008 00:44:44
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn the
Service Manager process.
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn the
Service Manager process.
Internal Concurrent Manager found node <node_name> to be down. Adding it to the list of unavailable nodes.
Internal Concurrent Manager found node <node_name> to be down. Adding it to the list of unavailable nodes.
Starting PODAMGR Concurrent Manager : 05-SEP-2008 00:44:58
Could not initialize the Service Manager <HOSTNAME_SID>. Verify that <node name> has been registered
for concurrent processing.
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /u12/app/<hostname>/<node_name>/po/11.5.0/bin/POXCON.
Check that your system has enough resources to start a concurrent manager process. Contact your system adm :
05-SEP-2008 03:29:56
Starting STANDARD Concurrent Manager : 05-SEP-2008 03:29:56]
been registered for concurrent processing.
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library
/u12/app/<hostname>/<node_name>/po/11.5.0/bin/POXCON.
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn
the Service Manager process.
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn the
Service Manager process.
Process monitor session started : 05-SEP-2008 00:44:44
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn the
Service Manager process.
Could not contact Service Manager <HOSTNAME_SID>. The TNS alias could not be located,
the listenerprocess on <HOSTNAME> could not be contacted, or the listener failed to spawn the
Service Manager process.
Internal Concurrent Manager found node <node_name> to be down. Adding it to the list of unavailable nodes.
Internal Concurrent Manager found node <node_name> to be down. Adding it to the list of unavailable nodes.
Starting PODAMGR Concurrent Manager : 05-SEP-2008 00:44:58
Could not initialize the Service Manager <HOSTNAME_SID>. Verify that <node name> has been registered
for concurrent processing.
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /u12/app/<hostname>/<node_name>/po/11.5.0/bin/POXCON.
Check that your system has enough resources to start a concurrent manager process. Contact your system adm :
05-SEP-2008 03:29:56
Starting STANDARD Concurrent Manager : 05-SEP-2008 03:29:56]
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 |