Re: Redo Log size

Yes but it depends on the application using the database. The redo logs hold transaction data necessary to re-do those transactions if the database should suddenly find itself holding an older version of its data (like when you have to restore a set of datafiles from backup due to a bad disk or when you abort the database and there is uncomitted data or unflushed data in process).

This being the case, these logs fill up according to the rate that transactions involving inserts, updates, and deletes are issued as well as according to the sizes of these transactions.

It is undesireable to have a transaction's record span log files so the log files should be large enough to record the longest transaction. Also, it is undesireable to have a log file fill up and still be archiving when it comes time to use it again. Finally, it is undesireable to have the log files switching off a lot.

therefore, you will want log files that are large enough to hold each of the transactions started while the logfile is active but no so large that it takes too long to archive them off. Also, your logfiles must be large enough so that your database is not spending a significant portion of its time switching between them.

I work with the Baan ERP application. From what I have seen, logfiles from 10 to 100mb are probably ok. however, I know that for smaller applications or even for Baan with low numbers of users (under 100), even 10mb may be too large.

Good Luck,

                    -dt

joe.story_at_foxinternet.net wrote in message <886012624.1600585744_at_dejanews.com>...
>Is there a optimal size for the Redo logs?
>
>-------------------==== Posted via Deja News ====-----------------------
> http://www.dejanews.com/ Search, Read, Post to Usenet
Received on Wed Jan 28 1998 - 00:00:00 CST