After doing a clone all the concurrent managers do not start

After Doing a Clone All the Concurrent Managers Do Not Start
Sometimes after cloning, all the concurrent managers are not coming up. Finally I found that its unusual but in Oracle Application Release 11i and 12  also have the same problem.
The symptom of the issue is that, after doing a clone when attempting to start the concurrent manager using the below :

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

Errors found in ICM logfile as
Could not initialize the Service Manager FNDSM__. Verify that has been registered for concurrent processing. 

The reason for this issue is that, 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 issue,
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;

(Note :  The same "afdcm037.sql" is used for Release 12 also ).
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.
10.  Retest the issue

Also see the document from Metalink
NOTE:218893.1 - How to Create The Service Manager 'FNDSM' on Oracle Applications
NOTE:260887.1 - Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES
NOTE:134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables

Related Posts by Categories