Status Pending With 'Inactive No Manager' for Concurrent Requests
Solution:
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.
How do you check whether Trace is enabled to particular concurrent program from the back end?
Solution:
1. select CONCURRENT_PROGRAM_ID,USER_CONCURRENT_PROGRAM_NAME from apps.fnd_concurrent_programs_tl where USER_CONCURRENT_PROGRAM_NAME like '%Program Name%'; (You will get Id)
2. select concurrent_program_id,enable_trace from apps.fnd_concurrent_programs where concurrent_program_id ='concurrent program id';
Try to restart the Concurrent Manager by System Administrator responsibility.Concurrent > Managers > AdministerRestart the Standard Manager.
No Concurrent Manager is Defined to Process This Request on Shutdown of Managers
Solution:
1. Stop managers (adcmctl.cmd)
2. Open Windows Task Manager to view processes
3. Open View Concurrent Requests form and refresh screen often and wait forthe Abort Concurrent Manager request to "Complete" "Normal".
4. Refresh the Task Manager to verify FNDLIBR and all other concurrent managerprocesses are gone.
5. For routine maintenance, use Note 134007.1 CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables to clean the tables while the managers are down and then restart managers.
6. Check managers for requests in Pending status via View Concurrent Requests.
7. If after cmclean.sql, pending requests remain, the requests must be manually cancelled. This does not require shutting down of the managers.
Perform the following in SQL*Plus as the APPS user:
UPDATE fnd_concurrent_requests SET phase_code = 'C', status_code = 'E' WHERE request_id = '
8. After manually killing request, the job(s) go to Completed Error status and managers should start gracefully without any pending requests.
Concurrent manager shutdown can take a few minutes to complete, wait a few minutes and confirm that it shuts down. Concurrent Processing development team have confirmed that the concurrent manager does not terminate OS/Database processes, this must be done through some other mechanism such as DCD (Dead Connection Detection via Sqlnet) or some OS method.
