Concurrent Manger are getting down with the following error in the ICM log as follows,
Routine FDPCRQ encountered an ORACLE error. ORA-04031: unable to
allocate 32 bytes of shared memory ("shared pool".
Review your error messages for the cause of the error. (=<POINTER>)
.............................................................................
APP-FND-01388: Cannot read value for profile option FND_MGR_STRTUP_THRES_TIME in routine &ROUTINE.
List of errors encountered:
.............................................................................
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
Cause:
FND_NODES Table not cleaned up properly
Solution:
1) 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%';
2) If you found that FND_NODES table having incorrect node entries (old node from the Source Instance) then execute the below query to clean it up,
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
3) Then Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables.
then make sure now you are able to see the correct entries in the FND_NODES table and then start the application services.
Routine FDPCRQ encountered an ORACLE error. ORA-04031: unable to
allocate 32 bytes of shared memory ("shared pool".
Review your error messages for the cause of the error. (=<POINTER>)
.............................................................................
APP-FND-01388: Cannot read value for profile option FND_MGR_STRTUP_THRES_TIME in routine &ROUTINE.
List of errors encountered:
.............................................................................
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
Cause:
FND_NODES Table not cleaned up properly
Solution:
1) 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%';
2) If you found that FND_NODES table having incorrect node entries (old node from the Source Instance) then execute the below query to clean it up,
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
3) Then Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables.
then make sure now you are able to see the correct entries in the FND_NODES table and then start the application services.