Concurrent Requests stay in Pending/Standby and Inactive/No Manager status forever

In Oracle E Business Suite, It has been observed that when attempting to submit any request, request fails with Inactive No Manager Phase/Status Combination and sometimes concurrent manager does not pick up any request it stays in Pending/Standby status

Review the following points when the concurrent request is in Inactive phase with No Manager status and pending standby status


Verify that Internal Concurrent Manager(ICM) is up and running.

Use any one navigation mentioned below to check the status details of Internal Manager.

i. Oracle Applications Manager(OAM) > Site Map > Monitoring > Availability 

   > Internal Concurrent Manager > View Status.
                          OR
ii. System Administrator Responsibility > Concurrent > Manager > Administer

If Concurrent Managers are up and running fine however not processing any requests then there can be few reasons:

1. Specialization rules prohibits processing any requests

 i.Verify if Include Specialization Rule Exists for the Standard Manager.

if exists then remove the same as below:

1. Log into Applications.
2. Navigate: System Administrator / Concurrent / Manager / Define.
3. Query for 'Standard Manager'.
4. Click Specialization Rules.
5. Remove any Include Rules from the Specialization Rules for Standard Manager.
6. Restart the Managers to test.

***Any "Include" entry is highly unadvisable for Standard Manager***

ii.Verify that there is at least one active concurrent manager with/without specialization rules that allow the concurrent program to run.

Run the following query to check whether any specialization rule defined for any concurrent manager that includes/excludes the concurrent program

SELECT    'Concurrent program '
       || fcp.concurrent_program_name
       || ' is '
       || DECODE (fcqc.include_flag, 'I', 'included in ', 'E', 'excluded from ')
       || fcqv.user_concurrent_queue_name specialization_rule_details
  FROM fnd_concurrent_queues_vl fcqv, fnd_concurrent_queue_content fcqc, fnd_concurrent_programs fcp
 WHERE fcqv.concurrent_queue_id = fcqc.concurrent_queue_id 
  AND fcqc.type_id = fcp.concurrent_program_id 
  AND fcp.concurrent_program_name = '<PROGRAM_SHORT_NAME>';

Make sure that Concurrent Manager whose specialization rule includes the concurrent program is up and running.


2. Program with Run alone flag is submitted with pending or running status

Run alone means exactly what it says. It means that it runs alone, no other requests can be running. It also means that it cannot start until no other requests are running.

Run the Below query to identify the programs that are Run alone flag enabled.

select request_id from fnd_concurrent_requests
where CONCURRENT_PROGRAM_ID in (
SELECT CONCURRENT_PROGRAM_ID
FROM FND_CONCURRENT_PROGRAMS_VL
WHERE RUN_ALONE_FLAG='Y');  

Remove Run alone: Y for the Concurrent Program returned in above query


3. All the Managers are all busy

Verify if manager is busy, increase the processes for CM if needed

4. If nothing worked above, then perform below action plan if requests are in inactive no manager status

1. Deactivate manager
2. Remove all specialization rules
 a. Login to Oracle Applications as System Administrator responsibility
 b. Navigate to: Concurrent > Manager > Define > Query for desired 
manager
 c. Click Specialization Rules tab 
 d. Delete entries
3. Activate manager 
4. Add specialization rules back
 a. Login to Oracle Applications as System Administrator responsibility
 b. Navigate to: Concurrent > Manager > Define > Query for desired 
manager
 c. Click Specialization Rules tab 
 d. Add entries

FYI:

The concurrent request queue view is used internally to map requests to managers. This view would be regenerated when concurrent managers are created, or specialization rules are altered.

"Build Concurrent Request Queue View" concurrent request internally gets submitted when concurrent managers are created, or specialization rules are altered.

However, If required we can manually regenerate the concurrent request queue view for concurrent managers by entering the following command as an applmgr user at operating system prompt.

FNDLIBR FND FNDCPBWV apps/<pwd> SYSADMIN 'System Administrator' SYSADMIN