Concurrent Manager Not Starting After EBS Cloning

Concurrent Manager Not Starting After EBS Cloning

Symptoms:

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:

The issue is caused by problems with the clone process. .

Solution:

Carry out the following steps :

1- Repeat perl adcfgclone.pl  dbTier.

2- Repeat perl adcfgclone.pl  appsTier .

3-  Relink the following executables by running:

adrelink  force=y "fnd FNDSM"

adrelink force=y "fnd FNDLIBR"

adrelink force=y "fnd FNDFS"

adrelink force=y "fnd FNDCRM"

4-  Run FNDCPASS to recerate all passwords.

5- Run adautocfg.sh  on application node.

Reference metalink Doc ID 1622433.1