Siebel Enterprise Integration Manager - EIM Most frequently asked Interview Questions – Part 3

This is Siebel EIM Interview Q&A Part 3 We have collected the Siebel real time interview questions related to EIM ( enterprise integration manager) , these are asked in real interviews in most of the companies. All the best for your job interview!

1.What is the behavior of the EIM merge process?

Ans: Data from the record you select as the surviving record are preserved. Data from the other records are lost. If there are other records associated with the records you merge, those records—with the exception of duplicates—are associated with the surviving record.

2.Why is the IF_ROW_STAT column set to the value NO_SUCH_RECORD after running a merge process?

Ans: If you do not correctly populate all the user key columns, the merge process will fail and the IF_ROW_STAT column in the interface table will be set to the value NO_SUCH_RECORD. This indicates that EIM cannot find the appropriate rows to merge using the specified user keys.

3.Can EIM be used to merge rows from secondary tables?

Ans: EIM can only be used to merge rows from target base tables, and not secondary tables. For example, the target base table for EIM_ASSET is S_ASSET. EIM can only be used to merge two or more S_ASSET rows into single S_ASSET rows. You cannot use EIM to merge two or more S_ASSET_CON rows into single S_ASSET_CON rows. During EIM merge, EIM will merge rows from the target base table, and update the rows from the secondary tables to reference the surviving target base table rows. If you try to merge two secondary tables rows into one row by populating the interface table with user keys of the secondary table rows, the interface table victim and survivor rows will have the same target base table user keys values, which will cause the target base table row to be deleted.

4.What is the recommended number of rows that can be loaded in a single batch?

Ans: For an initial load, you can use 30,000 rows for a large batch. For ongoing loads, you can use 20,000 rows for a large batch. You should not exceed 100,000 rows in a large batch. Furthermore, you should limit the number of records in the interface tables to those that are being processed. For example, if you have determined that the optimal batch size for your system is 19,000 rows per patch and you are going to be running 8 parallel EIM processes, then you should have 152,000 rows in the interface table. Under no circumstances should you have more than 250,000 rows in any single interface table, since this will have a tremendous negative performance impact. NOTE: The number of rows you can load in a single batch may vary depending on your physical machine setup. To reduce demands on system resources and improve performance, you should always try to use smaller batch sizes.

5. Should EIM stop processing when multiple rows fail a pass?

Ans: EIM is designed to import large volumes of data. Most failures are caused by data errors. It is usually faster and easier to correct the data errors and resubmit the corrected rows as part of a subsequent batch than to reprocess an entire batch. EIM does not stop when failures occur.

ContentMatch