Import job is failing

Nithin P K

New Member
Hi All,

In SQL server 2008 (Cluster Server) one of the application job is failed with the below error. Please can you help me to resolve this error. This is a prod db & need to resolve ASAP. This is is importing data from a tool to the DB.
Error :
Executed as user: TWUTIL\svc-db-user. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 08:57:46 Error: 2013-08-27 08:57:46.71 Code: 0xC020901E Source: Process the file Lookup [77] Description: Row yielded no match during lookup. End Error Error: 2013-08-27 08:57:46.71 Code: 0xC0209029 Source: Process the file Lookup [77] Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "component "Lookup" (77)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Match Output" (79)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure. End Error Error: 2013-08-27 08:57:46.71 Code: 0xC0047022 Source: Process the file SSIS.Pipeline Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Lookup" (77) failed with error code 0xC0209029 while processing input "Lookup Input" (78). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 08:57:46 Finished: 08:57:46 Elapsed: 0.5 seconds. The package execution failed. The step failed.
 

Peter Schmitz

Administrator
Staff member
Hello and welcome!

The error description seems to indicate that when attempting to do a lookup, it did not find a match in the lookup table. This can happen when the lookup table has not been updated yet, or there is no "fall-back" record for unknown/to-be-fixed IDs.

However, the reason why the job fails is because most likely the task has been set to fail the lookup on error. Try and set it to "Redirect row" instead, and then have the error-output of the task move those records to another location (i.e. a flat text file, or a table that collects records that fail for whatever reason and have to be looked into).

Good luck!

Peter
 
Top