No Concurrent Manager Is Defined To Process This Request, So It Cannot Be Processed.

No Concurrent Manager Is Defined To Process This Request, So It Cannot Be Processed. 

APPLIES TO:

Oracle Inventory Management - Version 11.5.10.CU2 to 12.2 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.

SYMPTOMS

There are stuck transactions in mtl_transactions_interface table for ship confirm receiving transactions with the following error:

ERROR
No concurrent manager is defined to process this request, so it cannot be processed.

CAUSE

The concurrent manager log shows the following:

Starting RCVOLTM Concurrent Manager : 10-MAR-2016 06:56:27
Process monitor session ended : 10-MAR-2016 06:56:27
Process monitor session started : 10-MAR-2016 06:58:27
CONC-SM TNS FAIL
Call to PingProcess failed for FNDOPP

<the above continues to loop repeatedly for some time>
. . .
Routine AFPEIM encountered an error while starting concurrent manager
RCVOLTM.
The manager is not able to start properly.
The manager has been put on a SYSTEM HOLD to allow the system administrator to address the issue.
When addressed, the "Fixed" button on the Administer Managers screen can be pressed to restart the manager.


SOLUTION

The concurrent manager log shows there is a problem with this instance, the log shows errors similar to what is reported in Note 1312632.1, please engage your DBA and perform these steps:

Please perform the following steps:

1. Stop all middle tier services including the concurrent managers. Make sure no FNDLIBR, FNDSM, or other dead processes are running.

2. Stop and then restart the database.

3. Connect to SQLPLUS as APPS user and run the following :

   EXEC FND_CONC_CLONE.SETUP_CLEAN;
   COMMIT;
   EXIT;

4. Reference Note.260887.1 regarding the Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES.

5.. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and Web tiers 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 return any value please do the following:

   cd $FND_TOP/patch/115/sql

Connect to SQLPLUS as APPS user and run the following script :

   SQL> @afdcm037.sql;

Reference Note 218893.1 How to Create The Service Manager 'FNDSM' on Oracle Applications to 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. Please run the Concurrent Manager Recovery feature to address any Concurrent Manager / Concurrent Processing issues within the Oracle Application Manager.

8. Start the middle tier services including your concurrent manager.

9. Retest the issue.

Reference metalink Doc ID 2116530.1