How to Tweak the Performance with Workflow Concurrent Request (Doc ID 863780.1)

Last updated on NOVEMBER 08, 2016

Applies to:

Oracle Workflow - Version 12.0.6 to 12.2.2 [Release 12 to 12.2]
Information in this document applies to any platform.
Checked for relevance on 23-APR-2012

Goal

The database is being impacted by performance related issues. During an initial investigation found that two dba_jobs run frequently FND_SVC_COMPONENT.EXECUTE_REQUEST,
WF_BES_CLEANUP.CLEANUP_SUBSCRIBERS. Are these needed to run?

    SQL> select JOB, WHAT, BROKEN, to_char(NEXT_DATE, 'dd/mm/yyyy hh24:mi:ss') NEXT_RUN, INTERVAL
    from dba_jobs order by NEXT_RUN;

6642,declare errbuf varchar2(4000); retcode varchar2(4000); begin WF_BES_CLEANUP.CLEANUP_SUBSCRIBERS(errbuf, retcode); end;,24/07/2009 16:03, sysdate + 4/24
5945,FND_SVC_COMPONENT.EXECUTE_REQUEST (p_component_request_id => 10000);,25/07/200908:26,SYSDATE + (1440/(24*60))

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms