Re: Flooding Log Files

Maybe the user should just ALTER INDEX REBUILD... NOLOGGING, and forget about resizing redologs. What's the use of logging an index create? The next backup will get them anyway.

--
Jeremiah Wilton http://www.wolfenet.com/~jeremiah

On Mon, 15 Feb 1999, 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:
>
> > 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?
Received on Tue Feb 16 1999 - 09:27:27 CST