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: Flooding Log Files

Re: Flooding Log Files

From: Connor McDonald <mcdonald.connor.cs_at_bhp.com.au>
Date: Tue, 16 Feb 1999 17:25:07 +0800
Message-ID: <36C93973.2F4A@bhp.com.au>


jack dectis wrote:
>
> At the very least your log files should be much larger
>
> Maybe 100 - 500 meg each for starters.
>
> Maybe your log source and archive destination disks need to
>
> dedicated to those purposes as well if you really crank out the updates.
>
> Van Messner wrote:
>
> > Anyone
> >
> > One of our databases has 4 log groups of size 6M each (2 members per
> > group). The other day I used an alter index..rebuild to rebuld a 300MB
> > index that had thrown 100 extents. ARCH had trouble keeping up and I could
> > see from the alert log that log groups filled faster than they could be
> > archived. The rebuild took about fifteen minutes and not much else was
> > putting a load on the database at the time.
> > Is index rebuilding generally this demanding of ARCH? And if the index
> > is in an "INDEX" tablespace should the rebuild need resources from the
> > SYSTEM tablespace?
> > Running a Novell server, Oracle 7.3, DB size of maybe 50G and around
> > 1500 objects.
> >
> > Thanks for your knowledge
> >
> > Van

100-500 Meg each !? That seems very high for redo log files....

We run 6 x 40m on a 80G system, 400 or so concurrent users, and I can't remember the last time we got redo waits...

--



Connor McDonald
BHP Information Technology
Perth, Western Australia
"Never wrestle a pig - you both get dirty and the pig likes it..." Received on Tue Feb 16 1999 - 03:25:07 CST

Original text of this message

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