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

Last updated on OCTOBER 04, 2016

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 FNDSM_SRVEBSUAT1_UAT. The TNS alias could
  not be located, the listener process on SRVEBSUAT1 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=SRVEBSUAT1, Inst=, SM Name=FNDSM_SRVEBSUAT1_UAT, 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 FNDSM_SRVEBSUAT1_UAT. The TNS alias could
  not be located, the listener process on SRVEBSUAT1 could not be contacted,
  or the listener failed to spawn the Service Manager process.
 Node list before Update
 Node=SRVEBSUAT1, Inst=, SM Name=FNDSM_SRVEBSUAT1_UAT, Up=0
 Node list after Update
 Node=SRVEBSUAT2, Inst=, SM Name=, Up=1
 Node=SRVEBSUAT1, Inst=, SM Name=FNDSM_SRVEBSUAT1_UAT, 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



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