Controlling Data Commit While Loading Multiple Tables
Posted: Sun Apr 29, 2012 7:44 pm
Hi,
This was a question that came in a brain storming session and I was wondering if any of you have encountered this before.
Assume, we load 10 different tables in 10 parallel jobs all within the same sequencer. Let us also assume that all these laods happen sequentially because of integrity requirements.
Now, if my last table load fails / aborts, I want to ensure that all the previous loads are undone / rolled back.
Is there any way to ensure that the commit is held back until the last job?
To the best of my knowledge, the connector seems to commit a transaction individually.
Any assistance in this matter would be very helpful. Thanks!
This was a question that came in a brain storming session and I was wondering if any of you have encountered this before.
Assume, we load 10 different tables in 10 parallel jobs all within the same sequencer. Let us also assume that all these laods happen sequentially because of integrity requirements.
Now, if my last table load fails / aborts, I want to ensure that all the previous loads are undone / rolled back.
Is there any way to ensure that the commit is held back until the last job?
To the best of my knowledge, the connector seems to commit a transaction individually.
Any assistance in this matter would be very helpful. Thanks!