My Oracle Support Banner

Concurrent Manager Not Starting After EBS Cloning (Doc ID 1622433.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Request Processing

When attempting to start the concurrent manager after recent clone, the following is shown in the Internal Concurrent manager log:

ERROR
-----------------------
 07-FEB-2014 12:42:03 - Node list before TNS Update
 Could not contact Service Manager <service_name>. 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.
 07-FEB-2014 12:42:04 - Node list after TNS Update
 Node=<node_name>, Inst=, SM Name=<service_name>, Up=0

  Process monitor session started : 07-FEB-2014 12:42:04
  Queue size posting session started : 07-FEB-2014 12:42:04
 Could not contact Service Manager <service_name>. 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.
 Node list before Update
 Node=<node_name>, Inst=, SM Name=<service_name>, Up=0
 Node list after Update
 Node=<node_name>, Inst=, SM Name=, Up=1
 Node=<node_name>, Inst=, SM Name=<service_name>, Up=0
 No default node found.
 0: Target processes raised to Min
 Set max processes for queue (0/0) to 100, and sleep seconds to 30
 4: Target processes raised to Min



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


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