How to Resolve Siebel EIM Errors?
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. In other cases, records get imported into the base tables, but some of the columns fail migration. This section discusses the various causes of EIM failure, how they can be tracked and finally resolved.
After EIM process is complete, the following SQL query has to be run, to check for possible errors:
SELECT if_row_batch_num, if_row_stat, if_row_stat_num, count(*)
FROM <<EIM Table Name>>
GROUP BY if_row_batch_num, if_row_stat, if_row_stat_num;
Common Errors and Resolution: The following chart lists the possible values of IF_ROW_STAT, what they indicate and some possible resolutions.
After EIM process is complete, the following SQL query has to be run, to check for possible errors:
SELECT if_row_batch_num, if_row_stat, if_row_stat_num, count(*)
FROM <<EIM Table Name>>
GROUP BY if_row_batch_num, if_row_stat, if_row_stat_num;
Common Errors and Resolution: The following chart lists the possible values of IF_ROW_STAT, what they indicate and some possible resolutions.