My Oracle Support Banner

Auto Purge Not Clean Dangling Records (Doc ID 2650841.1)

Last updated on MARCH 26, 2020

Applies to:

Oracle SOA Suite - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

On 12.2.1.2

There are still lots of records cannot been cleaned after auto purge.

Execute SQL queries below as SOAINFRA user to see why a significant number of instances are not being purged:

I. Check the number of instances in a particular state:

select state, count(*) from cube_instance group by state;

II. Check for possible dangling records in CUBE_INSTANCE:

select count(*) from CUBE_INSTANCE where flow_id is not null and flow_id not in (select flow_id from SCA_FLOW_INSTANCE);

III. Run these queries to help determine whether there are dangling records in the audit_trail table:

select count(*) from AUDIT_TRAIL;

select count(*) from AUDIT_TRAIL ad where exists (select flow_id FROM sca_flow_instance sfi WHERE ad.flow_id=sfi.flow_id);

select count(*) from AUDIT_TRAIL ad where not exists (select flow_id FROM sca_flow_instance sfi WHERE ad.flow_id=sfi.flow_id);

select to_char(ci_partition_date,'YYYY-MM'), count(*) from audit_trail group by to_char(ci_partition_date,'YYYY-MM') order by to_char(ci_partition_date,'YYYY-MM');

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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