How to Rebuild/Recreate Concurrent Manager
Applies to:
Applies to:
Oracle Applications – Version:
11.5.10.2 and above
Description:
After cloning, concurrent manager
unable to start successfully at 0 status.
Solution:
Check the following solution on test environment before
implement on production environment, rebuild concurrent manager using following
steps:
·
Stop concurrent manager and wait to clear all
processes of FNDLIBR or kill the processes
·
select *
from fnd_concurrent_processes where process_status_code='A';
·
update
fnd_concurrent_processes set process_status_code='K' where
process_status_code='A';
·
select *
from fnd_concurrent_queues where control_code='N';
·
update
fnd_concurrent_queues set control_code=null where control_code='N';
·
update
fnd_concurrent_queues set node_name=null,node_name2=null
where
concurrent_queue_name not like 'FNDSM%' and concurrent_queue_name not like
'FNDIM%'
and
concurrent_queue_name not like 'APACHE%' and concurrent_queue_name not like
'FORMS%'
and
concurrent_queue_name not like 'REPORTS%' and concurrent_queue_name not like
'MET_CL%'
and
concurrent_queue_name not like 'MET_SRV%' and concurrent_queue_name not like
'OAMGCS%';
·
select *
from fnd_concurrent_queues where concurrent_queue_name = 'FNDCRM';
·
update
fnd_concurrent_queues set control_code = 'A'
where
concurrent_queue_name = 'FNDCRM';
·
Update
fnd_concurrent_queues set target_node = null;
·
select
distinct phase_code, status_code from fnd_concurrent_requests;
·
update
fnd_concurrent_requests set phase_code = 'C' , status_code = 'C' where phase_code
!= 'P';
·
Stop all
middle tier services including the concurrent managers
·
Stop the
database
·
Start
the database
·
Connect
SQLPLUS as APPS user and run the following :
o EXEC FND_CONC_CLONE.SETUP_CLEAN;
o COMMIT;
o EXIT;
Steps to Clean Nonexistent Nodes or
IP Addresses from FND_NODES
( Note : In the case of a clone
instance, it is strongly recommended to clean the non - existing nodes )
·
Run
AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and
webtiers to repopulate the required system tables
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;
How to Create The Service Manager
'FNDSM' on Oracle Applications:
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%';
·
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"
·
Run the
CMCLEAN.SQL script from the referenced note below (don't forget to commit)
Note 134007.1 - CMCLEAN.SQL - Non
Destructive Script to Clean Concurrent Manager Tables
·
Start
the middle tier services including your concurrent manager
·
Retest
the issue
Your comments, especially which will help us improve the
functionality, will be greatly appreciated :)
