Inactive No Manager

Status Pending With 'Inactive No Manager' for Concurrent Requests  

Problem Description
-------------------

Concurrent manager 11.0.x request has a status of "inactive no manager." 
The request becomes pending.


Diagnostics:
   
1.  The Internal Concurrent Manager and Standard Manager are running, but the
    requests remain in a pending status after an 'inactive no manager' error 
    occurs when the requests are submitted.  The FDNLIBR processes show from 
    the operating system.

2.  The Conflict Resolution Manager (CRM) has an amount of processes and a 
    workshift identified.  The profile option 'Concurrent: Use ICM' is set to 'No'.  
    Consequently, the CRM checks for program incompatibilities and prevents 
    programs from running when incompatible programs are already running.   
 
3.  There are no invalid objects in the database.

4.  The control_code for concurrent_queue_name = 'FNDCRM' is 'N' in the 
    FND_CONCURRENT_QUEUES table, , which means 'Target node/queue unavailable'. 
    This value should be NULL (CRM is running; target and actual process amount 
    are the same), or 'A' ('Activate concurrent manager' control status).


Solution Description
--------------------
 
Set the control_code to 'A' in fnd_concurrent_queues for the Conflict Resolution
Manager:
 
1.  Logon to Oracle Applications database server as 'applmgr'.

2.  Verify the Applications environment is setup correctly ($ORACLE_HOME 
    and $ORACLE_SID).

3.  Logon to SQL*Plus as 'APPS' and run the following SQL statement:

      update fnd_concurrent_queues
      set control_code = 'A'
      where concurrent_queue_name = 'FNDCRM';

      commit;

4.  Verify the status of the concurrent managers through the  
    Concurrent -> Manager -> Administer form.  

    If the CRM is still not active, bounce (deactivate, activate) the Internal 
    Concurrent Manager.  This is done through the Concurrent -> Manager -> 
    Administer form from the 'System Administrator' responsibility.  It can also
    be done through the CONCSUB command at the command level.       


Solution Explanation
-------------------- 
 
Setting the control_code to 'A' in the fnd_concurrent_queues table for the 
Conflict Resolution Manager indicates that this concurrent manager is to be 
activated with the parameter values specified through this table for this 
manager (MAX_PROCESSES, CACHE_SIZE, etc).