Purge Obsolete Workflow Runtime Data Failed Or Running Too Long Time for Core Workflow Only = N (Doc ID 1551872.1)

Last updated on MAY 19, 2024

Applies to:

Symptoms

Purge Obsolete Workflow Runtime Data concurrent program failed or running too long time when running for CORE WORKFLOW ONLY = N

Parameters used:

Age: 400
Persistence Type: Permanent
Core Workflow Only: N -----> when this parameter used this is where errors and performance issues found

Default value for all other parameters.

Purge is okay when running for Core Workflow only = Y

2) Then, issue is with performance in general:

Trace file shows:

DELETE FROM WF_LOCAL_USER_ROLES LOCAL
WHERE
 LOCAL.ROLE_NAME = :B3 AND LOCAL.ROLE_ORIG_SYSTEM = :B2 AND
  LOCAL.ROLE_ORIG_SYSTEM_ID = :B1


call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 1 0.00 0.00 0 0 0 0
Execute 39 905.75 21498.34 4087692 4104437 1574 134
Fetch 0 0.00 0.00 0 0 0 0
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 40 905.75 21498.34 4087692 4104437 1574 134

-----------------------

Running the Purge API WF_PURGE.Directory will show a performance issue as well.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.