E$ tables in Oracle Data Integrator (ODI) are specifically designed to store error data encountered during the data integration process. They are not created under normal circumstances.
Purpose: E$ tables act as a repository for error details when data integration steps within ODI fail. This allows for troubleshooting and analysis of the encountered issues.
Creation: ODI creates E$ tables only under specific conditions, typically when the Knowledge Module (CKM) encounters errors during data manipulation. The CKM is responsible for various tasks like data validation, filtering, and transformation.
Key factors influencing E$ table creation by the CKM:
- Flow Control Option: The CKM option named "Flow Control" needs to be enabled. This setting instructs the CKM to track data flow and capture errors.
- Data Source and Strategy: E$ tables are typically created when dealing with single, non-journalized source datastores and using a truncate/insert or basic insert loading strategy (no updates or deletes).
In simpler terms, E$ tables are created only when:
- You want to track data flow errors with the CKM.
- You have a single source feeding data.
- The loading approach involves a complete overwrite (truncate/insert) or a basic insert into the target.
If these conditions are not met, ODI won't create E$ tables, and error handling might be limited.
No comments:
Post a Comment