Re: Initialization parameter transactions_per_rollback_segment, can you set this?
- From: Jared Still <jkstill@xxxxxxxxx>
- To: ArnoldS@xxxxxxxx
- Date: Tue, 16 Aug 2005 08:56:30 -0700
I would guess (the testing is up to you :) that the time saved during a
restart
of a job by committing each record does not come close to the time
( and frustration ) you would save by committing the whole batch once.
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
On 8/16/05, Arnold, Sandra <ArnoldS@xxxxxxxx> wrote:
>
> It needs to commit after each record so that it will be easy to recover
> at the next record to be loaded if something happens during the load.
> For instance, if you are loading 100,000 records you do not need to load
> all 1000,000 again if a problem occurs during the load. You can pick
> back up at the next record to be loaded. The process logs each unique
> identifier that it loads so that you know where it was in the process
> when it failed.
>
>
Other related posts:
