Re: Re-organising a database?

joel-garry_at_home.com (Joel Garry) wrote in message news:<91884734.0304141559.10555173_at_posting.google.com>...
> tim.kearsley_at_milton-keynes.gov.uk (Tim Kearsley) wrote in message news:<725736ef.0304140119.6623ab37_at_posting.google.com>...

> It is entirely possible the compress/uncompress is your limiting
> factor, I've seen it on other vendors unix boxes of a similar size.
> Other tuning, particularly undo contention and redo log buffers may
> also impact things, not to mention rollbacks and archiving. Those
> things should all be examined, as I've seen such things make >50% cuts
> in elapsed time. Certainly I've seen some machines just crawl as the
> compress takes over, especially if the Oracle part of it would be
> processor bound anyways (as it is surprisingly often). However, I
> would look at the incremental moves the others suggested, as they may
> make more sense, depending on your actual user, sizing, integrity,
> performance and political issues.

Thanks very much to those who responded to my original post.

Joel, I'm doing some trials on import time using multiple dump files rather than one large, compressed file.

Generally, the piecemeal re-org suggested sounds probably the best way to go. I can get around the problem of the temporary extra disk space required and it does mean that the downtime can be much more distributed. In my scenario that's probably the dominant factor!

Many thanks.

Tim. Received on Tue Apr 15 2003 - 05:03:45 CDT