ABORTED Tasks are missing in the 11g Purge Verification Script
(Doc ID 2085635.1)
Last updated on SEPTEMBER 05, 2018
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0
You are using partitioning for purging as explained here:
However, when using the verification script there are some discrepancies in comparison with the purge script:
From the Chk_Part_Ok_1 function in the VERIFY_WF package and the CP_Chk_Part_Ok function in the VERIFY_FABRIC package the script is checking that the WFTASK.STATE is not DELETED, ERRORED, EXPIRED, STALE, or WITHDRAWN.
When it is not in one of these states, the verification fails and the instance then needs to be moved to a new partition before the one being checked can be dropped.
In the normal looped purge scripts (the pruneOpenECIDs function in the SOA_WORKFLOW package which is called from the delete_instances function in the SOA package), the query checks that the WFTASK.COMPONENTTYPE is BPMN and
the WFTASK.STATE is DELETED, ERRORED, EXPIRED, STALE, WITHDRAWN, or ABORTED or that the WFTASK.COMPONENTTYPE is WORKFLOW and the WFTASK.STATE is DELETED, ERRORED, EXPIRED, STALE, or WITHDRAWN before purging the instance.
Verification logic should be the same as purge logic.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document