Let me explore error logging capabilities in ODI as below:
1) Does ODI provide inbuilt provision to capture all 3 kind of below errors-
a) Fatal error - like server environment is down, table does not exist, connection issue , system crashes etc
b) Non- Fatal error- like error occurred during transformation logic, data processing/conversion, data type mismatch when loading from character field in source to nuber field in target.
c) Business validation or user defined errors- like trying to load order without a product associated with it, a transaction record with mandatory transaction amount NULL etc.
2) Do user need to define and design own error tables to capture any category of errors mentioned above ? Both b and c categories in above can be routed to E$ tables?
3) Do I need to enable flow control in CKM for category b in above? or any other prerequisite (is it default feature of ODI and does not need to enable explicitly?)
4) I understand that E$ error table is detailed error table and holds all fields of record? Does ODI provide master or summary table as well as in-built feature ?
5) If I need to have some more fields in error table like - reprocess_status (normal data load, reprocessing erroneous records etc) , interface name (prestage, stage etc), I need to design my explicit error table?
Thanks,
Rajneesh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello All,
Let me explore error logging capabilities in ODI as below:
1) Does ODI provide inbuilt provision to capture all 3 kind of below errors-
a) Fatal error - like server environment is down, table does not exist, connection issue , system crashes etc
b) Non- Fatal error- like error occurred during transformation logic, data processing/conversion, data type mismatch when loading from character field in source to nuber field in target.
c) Business validation or user defined errors- like trying to load order without a product associated with it, a transaction record with mandatory transaction amount NULL etc.
2) Do user need to define and design own error tables to capture any category of errors mentioned above ? Both b and c categories in above can be routed to E$ tables?
3) Do I need to enable flow control in CKM for category b in above? or any other prerequisite (is it default feature of ODI and does not need to enable explicitly?)
4) I understand that E$ error table is detailed error table and holds all fields of record? Does ODI provide master or summary table as well as in-built feature ?
5) If I need to have some more fields in error table like - reprocess_status (normal data load, reprocessing erroneous records etc) , interface name (prestage, stage etc), I need to design my explicit error table?
Thanks,
Rajneesh