Concurrent Manager is not started in EBS Clone

While cloning we some time face the issue that test or development instance still showing production server name entries in test's standard manager or even table FND_CONCURRENT_QUEUES have the production entries.

We had this issue and we solved it by using the below steps:-


1. Shutdown all the managers.

2. Run the CMCLEAN.SQL (don't forget to commit).
134007.1 Ext/Pub CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables

=>See if you have wrong entries in target node columns of FND_CONCURRENT_QUEUES table

3. update FND_CONCURRENT_QUEUES set target_node='Test' where target_node='Prod'
commit;

=>See if you have wrong entries in node_name columns of FND_CONCURRENT_QUEUES table

update FND_CONCURRENT_QUEUES set node_name='target node' where node_name='source node'
commit;
4. Start the Standard manager and verify the table entrie with below query.

select * from FND_CONCURRENT_QUEUES


==> Below steps will also help out more in troubleshooting Concurrent Manager issues


When we cloned outinstance, We had an issue with concurrent manager and not started

We stoped the concurrent manager

$COMMON_TOP/admin/scripts/HOST_NAME
. adcmctl.sh stop apps/password

When I have checked the ICM logfile there is an error entry as
Could not initialize the Service Manager FNDSM_HOSTNAME_SID. Verify that HOSTNAME has been registered for concurrent processing.

The cause of this issue was FND_NODES table having incorrect node entries (old node from the Source Instance) and that no Service Manager was found for the existing node.

To solve this problem, need to perform the below steps

1.  Stop all middle tier services including the concurrent managers.

2.  Stop the database.

3.  Start the database.

4.  Connect SQLPLUS as APPS user and run the following :

EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;

5.  Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables.

6.  Connect to SQLPLUS as APPS user and run the following statement :
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

If the above SQL does not returning any value then please do the following:

Go to $FND_TOP/patch/115/sql

Connect SQLPLUS as APPS user and run the following script :

SQL> @afdcm037.sql;

This script will create libraries for FNDSM and create managers for preexisting nodes.
Check again that FNDSM entries now exist:

select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

7.  Go to cd $FND_TOP/bin
$ adrelink.sh force=y "fnd FNDLIBR"
$ adrelink.sh force=y "fnd FNDSM"
$ adrelink.sh force=y "fnd FNDFS"
$ adrelink.sh force=y "fnd FNDCRM"

8.  Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).

9.  Start the middle tier services including your concurrent manager.

Now cloned instance concurrent managers became active. Above is applicable to both 11i and R12 instances.