After Clone Concurrent Managers not coming up
When cloned my instance last time, I have an issue with concurrent manager not coming up using
Finally decided to stop the concurrent manager using
$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. This will applicable to both 11i and R12 instances.
Finally decided to stop the concurrent manager using
$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. This will applicable to both 11i and R12 instances.
Related
Back to top