Example of Troubleshooting the Import of Extension Columns

Use the guidelines that follow to troubleshoot an import failure that occurs when extension columns are added to some Siebel tables and the EIM import task failed to populate data to these columns.

To troubleshoot the import of extension columns

Delete the diccache.dat file from the <siebel server>\bin directory and test the EIM task again.
EIM will rebuild this file from the information in the repository if the file does not exist.
Run the DBCHCK utility to make sure the EIM table in the repository is in synch with the EIM table in the database. For example, use the following command:
```
dbchck /u SADMIN /p <********> /t <table owner> /r "Siebel Repository" 
/l dbchck.log /d /s <ODBC data source> <interface table name>
```
For information on running the DBCHCK utility, see Checking the Repository.
1. If the repository is not in synch with the database, log in to Siebel Tools, and in the Table object, select the EIM table records.
2. Click the Apply and Activate buttons to apply and activate all changes on the EIM table to the database.
3. Run the DBCHCK utility again.
Follow the instructions to set event logging in Viewing the EIM Log File and run the EIM task.
This generates a detailed EIM log file. Review the log file to see whether there are any errors causing the import failure.
If the extension column is:
- A foreign key or primary column, its mapping should only be created through the EIM Table Mapping Wizard, or by Oracle's Application Expert Services.
- A foreign key column, its foreign key mapping can be created by running the EIM Table Mapping Wizard on the base table of the extension column.
- A primary column for a M:M relationship (that is, an EIM table is defined in the extension primary column's Primary Inter Table property), its EIM Explicit Primary Mapping can be created by running the EIM Table Mapping Wizard on the intersection table.
- A primary column for a 1:M relationship (that is, no EIM table is defined in the extension primary column's Primary Inter Table property), its EIM Explicit Primary Mapping can be created by running the EIM Table Mapping Wizard on the primary child table (as defined in the extension primary column’s Primary Child Table property).
Check the mappings for the extension columns.
1. Log in to Siebel Tools.
2. Navigate to the EIM Interface Table object and query to select the interface table EIM Table Mapping.
  If the extension column is:
  - Not a foreign key or primary column, it should only have an Attribute Mapping under its base table’s EIM Table Mapping.
  - A foreign key column, it should not have any Attribute Mapping defined. It should have a Foreign Key Mapping.
  - A primary column, it should not have any Attribute Mapping or Foreign Key Mapping defined.
  If the extension primary column is:
  - For a M:M relationship, it should have an EIM Explicit Primary Mapping under its intersection table’s EIM Table Mapping.
  - For a 1:M relationship, it should have an EIM Explicit Primary Mapping under its primary child table’s EIM Table Mapping.