Troubleshooting an import that does not complete or is missing data
This article guides you through the process of troubleshooting an import that does not complete or is missing data. It provides steps to help you eliminate common causes for your problem by verifying that the configuration of your networking is correct.
Symptoms may include the following:
- No rows are returned
- Connectivity issues (log message)
- Import takes a really long time
- Import does not complete
- Import stopped in the middle
- Import says complete, but not all data is present
- User cannot log in through LDAP
- Scheduled import does not run at the defined time
- Data discrepency after report
- Data is truncated
- Import fails after upgrade
Determine whether any of the troubleshooting steps below are true for your environment. Each step provides a link to an article that can help you eliminate possible causes and take corrective action as necessary.
- Determine if the import set picked up all records from the ECC queue. For more information, see KB0538460: Troubleshooting Import - Missing data when importing JDBC source via MID server.
- Determine if the column length is too short for the import set. KB0538123: Troubleshooting Import: Missing data when column length is too short for import.
- Determine if there is an LDAP configuration issue impacting the import. KB0538124: Troubleshooting Import: Missing data as a result of LDAP configuration issue.
- Determine if LDAP attribute data is too large. KB0538128: Troubleshooting Import: Missing data as a result of LDAP large attribute data.
- Determine if there is a date format issue causing the data to be truncated. KB0538141: Troubleshooting Import: Missing data as a result of a wrong date format.
|Note: If your problem still exists after trying the steps in this article: Submit an incident to Technical Support and note this Knowledge Base article ID (KB0538437) in the problem description. For more information, see Submitting an Incident.|