Scribd
Upload
5K views1 page

ETL Error Handling Strategies

Errors in an ETL process can be data errors or process errors. Data errors can be handled using row error logging, which captures errors in error tables so they can be analyzed, corrected, and reprocessed. Process errors can be addressed by configuring an email task to notify of session failures. Row error logging logs error information to tables or files for determining the cause and source of errors.

Uploaded by

sirini
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
5K views1 page

ETL Error Handling Strategies

Errors in an ETL process can be data errors or process errors. Data errors can be handled using row error logging, which captures errors in error tables so they can be analyzed, corrected, and reprocessed. Process errors can be addressed by configuring an email task to notify of session failures. Row error logging logs error information to tables or files for determining the cause and source of errors.

Uploaded by

sirini
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd

Error Handling

Identifying errors and creating an error handling strategy is very important.


The 2 types of errors in an ETL process are – Data Errors & Process Errors.

To handle Data errors we can use the Row Error Logging feature. The errors are captured into the
error tables. We can then analyse, correct and reprocess them.

To handle Process errors we can configure an email task to notify the event of a session failure.

Row Error Logging: When we configure the session with this option the Integration service logs errors
information to relational tables or to an error log file.

First time it creates the table or a file and then onwards it appends to the existing table or file. This
log file contains information such as source name, row ID, row data, transformation error code etc.
which can be used to determine the cause & source of an error.

By default the Integration service does not write the dropped rows to session log or create a reject
file. So we can enable verbose tracing to write to session log. Performance is decreased as one row at
a time is processed.

You might also like