Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Archive Log affects performance?

Re: Archive Log affects performance?

From: Stan <stan0074_at_yahoo.com>
Date: Sun, 20 Jan 2002 04:56:25 GMT
Message-ID: <3C4A4E55.5060607@yahoo.com>


Noodles,

along with no-archive mode, create a huge private rollback segment and assign them to your update transaction (set transaction method). This would expedite your updates to run more faster.

Stan

Noodles wrote:

> Jim,
>
> The N-class box ( no-archive logging) with a test set of 1.36 million rows,
> takes 4 hours. The N-class ( with archive logging), with the same test set,
> takes 8.2 hours. I was expecting a little difference because of the N-class vs
> the K-class but a factor of 2 ?
>
> I just want to make sure I can get this update to run as FAST as possible
> because the update needs to run on 5 tables in 46 databases.
>
> TIA,
> Cliff
>
>
> << Given the machines are beefy, I don't think this will be a problem.
>
> How long is it taking with archiving - a multi-million row update shouldn't
> take that long. >>
>
>
>
Received on Sat Jan 19 2002 - 22:56:25 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US