EIM delete leaving dangling foreign keys
(Doc ID 533665.1)
Last updated on OCTOBER 24, 2018
Applies to:Siebel Enterprise Integration Manager - Version 7.7.2 SIA  and later
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2  Com/Med
Database: Oracle 184.108.40.206
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-1675639011.
***Checked for relevance on 01-Aug-2014***
During technical (performance) testing of EIM delete exact interfaces, I have found some alarming discrepancies. Basically, EIM is not processing some dependant tables properly.
We run all our EIM Delete and Merge jobs with NUM_IFTABLE_LOAD_CUTOFF=0 and so EIM should process ALL dependent tables. In fact, it would appear as though I can successfully reproduce the list of tables that EIM is processing (following on from SES work from Andy Cowling). I have so far detected this issue in EIM_ADDR_PER, EIM_ASSET and EIM_ACCOUNT and am rather concerned.
I will use EIM_ADDR_PER for example in this SR.
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