ETL_INFORMATICA_POWERCENTER_数据异常处理策略.docVIP

本文档不会设计具体组件的使用，主要是设计的思路。如果需要学习基础知识，请参考我其他的文档^囧^。 恩恩~，当你在ETL的时候出现异常，比如源表的关键字段和维表、关系表关联不上，那应该如何处理呢？通常的做法是把这些数据记录，然后给用户确认。以下为英文原教材引用，附上mapping脚本，没有表脚本。自认为能看懂的慢慢看，看不懂的请直接page dn。忘了告诉你，这个xml文件需要修改两个地方。试一试自己改改咯~ MAPPING TEMPLATE FOR: Error Handling Strategy USAGE: Use this template as a guide for trapping errors in a mapping, sending errors to an error table so that they can be corrected, and reloading fixed errors from the error table into the target system. TEMPLATE OBJECTS: m_Customer_Load_v61.XML m_Customer_Fixed_Error_Load_v61.XML CHALLENGE ADDRESSED: Developers routinely write mapping logic that filters records with data errors out of a data stream. However, capturing those error records so that they can be corrected and re-loaded into a target system can present a challenge. The mappings in this mapping template illustrate a process for trapping error records, assigning a severity level to each error, and sending the error rows – which include the complete source row plus additional columns for the error description and severity level – on to an error table. OVERVIEW: This mapping template provides two mappings that, taken together, illustrate a simple approach to utilizing Informatica objects in handling known types of Errors. The essential objects shown and utilized are Expression transformations that provide error evaluation code, Lookup transformations that are used to compare or find prerequisite values, and a Router transformation that sends valid rows to the warehouse and error rows to an appropriate error table. The key to the utilization of the error table in this example is to preserve the source record’s data structure for eventual correction and reprocessing. The first mapping that runs is m_Customer_Load. Each source row that is flagged as an error is loaded into the error table, along with an error description per row so that a subject matter expert can view, identify and correct errors. M_Customer_Fixed_Error_Load pulls fixed errors from