When migrating data using the EIM, the process can fail due to several reasons. In certain cases, it is found that the EIM process was successful for migration into some of the Base tables, but failed for some other base tables.
Integration Manager (EIM) reports the following low-severity error when the foreign key value in the base table does not match with value in the interface table (Note: The following example is based on Siebel version 7.0.4 data model):
The order in which legacy data is imported is critical to make sure that relationships between dependent data elements are established correctly. Siebel interface tables do not map one-to-one with Siebel target database tables.
After upgrading Siebel applications to a higher release, certain columns that were previously not List-of-Value (LOV) bounded became LOV bounded that could cause EIM import failure Oracle Siebel highly recommends that users evaluate the potential
You can only use EIM to import bulk data from legacy systems into the Siebel database. Only ACT! 2.0 and ACT! 3.0 have File/Import functionality for data import into Siebel. You can use “Exporter for ACT!” to export ACT!