Troubleshooting the Unique Constraint Error When Importing Accounts or Contacts

This topic documents the causes, diagnostic steps, and solutions for troubleshooting the unique constraint error received when importing data through EIM.

Note: The error message and cause are the same for both contact data import and account data import, but there are separate diagnostic steps and solutions for each type of import data.

To resolve the problem, look for it in the list of Symptoms/Error Messages in the following table.

Symptom/Error Message Diagnostic Steps/Cause Solution

Symptom/Error Message	Diagnostic Steps/Cause	Solution
When importing Account or Contact data using EIM, the batch fails with the following error: `EIM-00107: ODBC (SQL) error.` The log file displays an error message similar to the following error shown by an Oracle database: `ODBC error 23000: [MERANT][ODBC Oracle 8 driver][Oracle 8]ORA- 00001: unique constraint (SIEBEL.S_CONTACT_U1) violated` `ODBC error 23000: [MERANT][ODBC Oracle 8 driver][Oracle 8]ORA- 00001: unique constraint (SIEBEL.S_ORG_EXT_U1) violated`	This unique constraint error usually occurs due to inconsistent data in the base tables or incorrect data populated in the interface tables. The inconsistent data may result when two different server tasks, such as Siebel EAI processes and an EIM process, are run at the same time to import the same data. For an example of this, see Example of Troubleshooting the Unique Constraint Error when Importing Accounts or Contacts.	See Example of Troubleshooting the Unique Constraint Error when Importing Accounts or Contacts.
Import of EIM contact data into the S_CONTACT table fails with this error. For diagnostic steps, see Example of Troubleshooting the Import of EIM Contact Data into the S_CONTACT Table.	See Example of Troubleshooting the Import of EIM Contact Data into the S_CONTACT Table.
Import of EIM account data into the S_ORG_EXT table. For diagnostic steps, see Example of Troubleshooting the Import of EIM Account Data into the S_ORG_EXT Table.	See Example of Troubleshooting the Import of EIM Account Data into the S_ORG_EXT Table.

When importing Account or Contact data using EIM, the batch fails with the following error:

EIM-00107: ODBC (SQL) error.

The log file displays an error message similar to the following error shown by an Oracle database:

ODBC error 23000: [MERANT][ODBC 
Oracle 8 driver][Oracle 8]ORA-
00001: unique constraint 
(SIEBEL.S_CONTACT_U1) violated

ODBC error 23000: [MERANT][ODBC 
Oracle 8 driver][Oracle 8]ORA-
00001: unique constraint 
(SIEBEL.S_ORG_EXT_U1) violated

This unique constraint error usually occurs due to inconsistent data in the base tables or incorrect data populated in the interface tables.

The inconsistent data may result when two different server tasks, such as Siebel EAI processes and an EIM process, are run at the same time to import the same data.

For an example of this, see Example of Troubleshooting the Unique Constraint Error when Importing Accounts or Contacts.

See Example of Troubleshooting the Unique Constraint Error when Importing Accounts or Contacts.

Import of EIM contact data into the S_CONTACT table fails with this error. For diagnostic steps, see Example of Troubleshooting the Import of EIM Contact Data into the S_CONTACT Table.

See Example of Troubleshooting the Import of EIM Contact Data into the S_CONTACT Table.

Import of EIM account data into the S_ORG_EXT table. For diagnostic steps, see Example of Troubleshooting the Import of EIM Account Data into the S_ORG_EXT Table.

See Example of Troubleshooting the Import of EIM Account Data into the S_ORG_EXT Table.