Concurrent Manager Issue’s after Refresh/Cloning EBS R12 :

Concurrent Manager Issue’s after Refresh/Cloning EBS  R12 : 

The Oracle Applications are as followings:

Solution :

1. Stop all middle tier services including the concurrent managers and verify that all APPS-Tier processes are down :

2. Stop the Database and verify, that all Database processes are down.

3. Start the database.

             sqlplus apps/pwd

SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;

       SQL>COMMIT;

SQL> EXIT;

Make sure following two sqls returns no rows

SQL> select node_name "Node Name", node_mode "Mode", support_cp "C",support_web "W", support_admin "A", support_forms "F" from FND_NODES;

SQL>  select * from FND_OAM_CONTEXT_FILES;

4. Execute AutoConfig on all Tiers - first on the DB Tier and then on the APPS Tier(s) to repopulate the required system tables.

SQL>  sqlplus APPS/<Password>

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

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

a. cd $FND_TOP/patch/115/sql

b. sqlplus APPS/<Password>

c. @afdcm037.sql;

d. This script will create libraries for FNDSM and create Managers for Preexisting Nodes.

Note: Service Manager "FNDSM" cannot be created from form:

Concurrent> Manager> Define under Sysadmin Responsibility.

Check again if the FNDSM entries exist now :

a. sqlplus APPS/<Password>

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

5. Relink the binaries FNDLIBR, FNDSM FNDFS and FNDCRM :

a. cd $FND_TOP/bin

b. adrelink.sh force=y "fnd FNDLIBR"

c. adrelink.sh force=y "fnd FNDSM"

d. adrelink.sh force=y "fnd FNDFS"

e. adrelink.sh force=y "fnd FNDCRM"

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

     Run cmclean.sql script .

7. Start the Middle Tier Services including your Concurrent Manager.

8. Retest the issue 
+++++++++++++++++++++++++++++++++++++