Troubleshooting an import that is taking a long time to complete - Support and Troubleshooting

Troubleshooting an import that is taking a long time to complete Description  This article guides you through the process of troubleshooting an import that is taking a long time to complete. 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 Resolution 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 there is a significant number of records being imported. For more information, see KB0538405: Determining if there is a significant number of records being imported . Determine if a business rule script is impacting your import. For more information, see KB0538161: Determining if a business rule is running on top of a transform map . Determine if another process is running at the same time as the import. For more information, see <a title="KB0538402: Determining if another process is running at the same time as the import" href="/kb_view.do?sysparm_article=KB0538402&ni.dependent.topic=kb_knowledge.category&sysparm_category=&sysparm_ck=3dd03afd8ce46100957b906f2c8a66b083d75f74da35a18e6f25cf173c2ece1e6e1b932d&sysparm_nameofstack=&sysparm_product=&sysparm_search=KB0538402&sysparm_topic=" target="_blank" rel="noopener noreferrer">KB0538402: Determining if another process is running at the same time as the import .

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 (KB0538434) in the problem description. For more information, see Submitting an Incident .