Performance Issues Caused by Purge Obsolete Workflow Runtime Data
Last updated on DECEMBER 24, 2015
Applies to:Oracle Workflow - Version 11.5.9 to 184.108.40.206 [Release 11.5 to 11.5.10]
Information in this document applies to any platform.
Running concurrent request "Purge Obsolete Workflow Runtime Data" takes a long time to run and starts generating lots of trace files in user_dump_dest.
Current SQL statement for this session:
DELETE FROM WF_ITEM_ACTIVITY_STATUSES WHERE ITEM_TYPE = :B2 AND ITEM_KEY = :B1
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