Siebel Enterprise Integration Manager Administration Guide > Importing Data > Checking Import Results >

Viewing a List of Imported Rows

The first task you should perform to check the results of the import process is to view a list of the imported rows.

To view a list of imported rows

  • Query the appropriate EIM tables for rows whose if_row_batch_num equals the batch number for the import.

These columns in each EIM table indicate whether a row was imported successfully, and they identify the pass number on which a row failed. During various passes of import processing, EIM sets the IF_ROW_STAT value to one of the values shown in Table 12.

If error flags, SQL trace flags, or trace flags were activated for the EIM process, you can also use the trace file to view the results of the EIM process. For more information on viewing the trace file, see Viewing the EIM Log File.

Table 12. IF_ROW_STAT Values


There are two rows in the base table that have the same user key but different conflict IDs. EIM cannot distinguish these rows.


The row exactly matches rows that already exist in the destination tables. This error occurs in Step 8. Note that a row may have a duplicate in the target base table, but not in other destination base tables. In this situation, EIM adds the new relation (a child or intersection table) in the other destination base tables, and does not mark the EIM table row as a duplicate.


The row was eliminated because it is a duplicate (has the same user key) of another row in the EIM table with the same batch number. In this case, MIN(ROW_ID) is the record processed, and the other records with the same user key are marked as DUP_RECORD_IN_EIM_TBL.

Do not confuse DUP_RECORD_IN_EIM_TBL with DUP_RECORD_EXISTS. DUP_RECORD_EXISTS status indicates that the same record already exists in the base table, while DUP_RECORD_IN_EIM_TBL status indicates that there are two or more EIM table records having the same user key values.


A required foreign key column in the target table could not be resolved. This error occurs in Step 4.


The row was successfully processed against all its destination base tables. This status is set after the import has been completed.

You can check the import status by using database commands to query the appropriate EIM tables for rows whose IF_ROW_STAT value is not equal to IMPORTED. The result is a list of rows that were not successfully imported.


A user-specified filter query failed for this row. This error occurs in Step 3 if the user has specified FILTER QUERY expressions.


In Step 1, EIM sets IF_ROW_STAT to this initial value for all rows in the batch. If rows still have this status value after EIM exits, a failure occurred that aborted processing for this table.


The user key was not unique in all the user key specifications on the table.


The row did not fail for the target table (although it may have been a duplicate), but did fail during processing of a secondary base table. This status is set after the import has completed.


A required picklist value in the target table could not be resolved. This error occurs for NULL or invalid bounded picklist values in Step 4.


One or more required columns for the target table were NULL. This error occurs for missing user key columns in Step 7, or when inserting new rows in Step 9.


EIM encountered an error, such as an SQL database failure, and rolled back the transaction. This status is only used when ROLLBACK ON ERROR = TRUE.


An SQL error occurred during an attempt to import this row. This error occurs for rows processed when Enable Transaction Logging is set to TRUE.

Siebel Enterprise Integration Manager Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.