I have the following case:
I have 2 separate subjobs within a job that push data into to separate tables with master/child relationship. Upon executing the Job the master SubJob succeeds and imports the data in the master table and when I got an error in the execution of the Child Subjob the whole Job halts with an error but the imported data in the master SubJob has already been committed which is creating inconsistency in may database model. I need a help in considering all data in subjobs as one unit either all of them committed in case of successful execution or rolleback in case of error. Is there a way of doing it noting that I'm using tOracleOutput components to push the data to the destination tables and tDie components to halt the system in case of error.
Solved! Go to Solution.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Pick up some tips and tricks with Context Variables