Commit interval in oracle enterprise stage
Moderators: chulett, rschirm, roy
Commit interval in oracle enterprise stage
Hi ,
I am having a oracle enterprise stage as target.This job is restartable ( checkpointed the sequence from which this is called ) .I am using upsert mode .
So , if my job aborts and again i restarted the sequence ( without resetting ) then will my job load the records from the point it has failed ? or will it be dependent on environment variables
APT_ORAUPSERT_COMMIT_ROW_INTERVAL
APT_ORAUPSERT_COMMIT_TIME_INTERVAL
Thank you all
Nag
I am having a oracle enterprise stage as target.This job is restartable ( checkpointed the sequence from which this is called ) .I am using upsert mode .
So , if my job aborts and again i restarted the sequence ( without resetting ) then will my job load the records from the point it has failed ? or will it be dependent on environment variables
APT_ORAUPSERT_COMMIT_ROW_INTERVAL
APT_ORAUPSERT_COMMIT_TIME_INTERVAL
Thank you all
Nag
Nag
Sequence restartability is completely different from the restartability you mean at the job level. It will simply start the job over again and without anything specific to handle previously committed rows will just attempt to load everything again. You may be OK with the upsert mode, however, as inserts would become updates.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Craig thanks for the response .
Let me put my understanding in this way ...
If there are 4 jobs in a sequence .The sequence is restartable . My sequence got aborted during 3rd job .This 3rd job loads data in to oracle table .Suppose there are 10000 records has to be loaded and job got aborted after loading 6000 .Then if restart the sequence then again it will start from job3 but it starts loading from record 1 .
Please correct me if i am wrong .
Thanks
Nag
Let me put my understanding in this way ...
If there are 4 jobs in a sequence .The sequence is restartable . My sequence got aborted during 3rd job .This 3rd job loads data in to oracle table .Suppose there are 10000 records has to be loaded and job got aborted after loading 6000 .Then if restart the sequence then again it will start from job3 but it starts loading from record 1 .
Please correct me if i am wrong .
Thanks
Nag
Nag
You'll need to either include some handling to make a call to a job/script to backout the partial data loaded, or to make it restart (at job level) from where it left off, there is nothing built in to cater for it, so it's a design you need to come up with.
You could also, of course, have no commit level, which would mean it's all or nothing for load, but this carries implications on the database side.
You could also, of course, have no commit level, which would mean it's all or nothing for load, but this carries implications on the database side.
Mark Winter
<i>Nothing appeases a troubled mind more than <b>good</b> music</i>
<i>Nothing appeases a troubled mind more than <b>good</b> music</i>
Hi Everyone ,nagarjuna wrote:Can i make APT_ORAUPSERT_COMMIT_ROW_INTERVAL =0 to handle this ? Please let me know your thoughts on this
Just one more quick question ....what about if the load is ising sqlldr or direct load ? This env has no meaning in that case ....So what is the process or design you suggest to handle this ??
Nag