Few queries for OPP

1. How to monitor the workload of OPP

In general "Administer Concurrent Manager Screen" shows pending and running requests against each manager, but it does not show pending requests against OPP manager. The OPP uses 'Advanced Queue' to find the pending requests that it needs to process, hence it becomes difficult to configure (or) do sizing of OPP without knowing the workload. For example, "Administrator Screen" shows how many requests are pending (or) running against "Standard Managers" using this information, we can size (Increase Process) Standard Manager accordingly.

However, when the OPP begins to process a concurrent request, it will update the processor_id column of fnd_conc_pp_actions with it's concurrent_process_id.  We can use the following query to find pending requests against OPP,

SQL> select REQUEST_ID,PHASE_CODE,STATUS_CODE from fnd_concurrent_requests
where request_id in (select concurrent_request_id from fnd_conc_pp_actions where action_type >= 6 and processor_id is null)
and PHASE_CODE!='C';

get the processor id from conc -> manager -> administer -> OPP -> processes


2. Determine OPP based concurrent requests

The following query lists all OPP based concurrent requests,

select distinct b.user_concurrent_program_name
from apps.fnd_concurrent_requests a, apps.fnd_concurrent_programs_tl b
where a.concurrent_program_id = b.concurrent_program_id
and a.request_id in (select concurrent_request_id from apps.fnd_conc_pp_actions where action_type >= 6 and processor_id is null) order by 1;

3. Determine what the heap size per OPP process,

select DEVELOPER_PARAMETERS from FND_CP_SERVICES
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

4. Update the heap size,

update FND_CP_SERVICES set DEVELOPER_PARAMETERS ='J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');