Informatica PowerCenter has a default of 0 in the stop-on-error. If a session encounters non-fatal errors Informatica PowerCenter integration service will continue the session hence potentially can cause data loss or partial load. Surely, this can be set to 1 in a default config and then ensure all new sessions created subsequently inherit the stop-on-error set as 1 but would have thought it would have a default value of 1 instead of 0. This small “feature” has and will continue to cause so many ETL projects spend time in ensuring this is set to 1.
There are situations where the quality of the source data (or lack of it) makes it imperative to make allowance for a degree of designed data leak that can be managed externally as a step prior to loading the data into staging tables or target tables. However, a tleast we should start with a design in mind that assumes the data is clean for further downstream systems.
Use Undraleu® to perform an Automated Code Review of your Informatica PowerCenter Code and get a best practices perspective on the health of your ETL code