Concurrent Managers NOT coming up after cloning in 11i/R12

It is a very common issue that many times concurrent managers (CM) does not come up after apps cloning. Here are the steps to perform to resolve it

1 Query the apps.fnd_nodes tables. Many times,  the CM node entry is not there, or prod node entries are still there in fnd_nodes table. Stop the concurrent manager service and clear the fnd_nodes table by executing the folowing as apps user->
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;

2 Now Run AutoConfig on all tiers on the target system. Firstly on the DB tier and then on all the apps tier individually. This step will populate the apps.fnd_nodes table. If you query this table, then it will show you the target node entries now.

3 Start the CM services and then check the CM. If CM is up then fine else perform the following

4  Stop the concurrent manager services. Connect to apps user and run cmclean.sql script. This script can be downloaded from metalink. Remember to commit the script after execution. Start the CM services and then check the CM. If CM is up then fine else perform the following

5  Stop the concurrent manager service....and run the following statement on concurrent manager node
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"

6 Start the CM services and then check the CM.  Concurrent managers  should be up and running fine now.