Hi! Just create big redologs and keep them. If you definitely want to archive them after some intervals, then use archive_lag_target parameter to set maximum interval of time a logfile can accommodate redo (a logswitch will be forced after the interval since last logswitch). Also, I think it's reasonable to go with incremental checkpoints (setting fast_start_mttr_target or fast_start_io_target) instead of having your log_checkpoint_* parameters with ridiculously low values. Tanel. ----- Original Message ----- From: "Jeroen van Sluisdam" <jeroen.van.sluisdam@xxxxxxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Tuesday, April 06, 2004 11:28 AM Subject: different redo needs same database > Hi, > > I'm trying to improve my redo settings because I have logswitches during > daytime every > 2 to 4 hours and at night during batches every couple of minutes and a few > times > within 1 minutes 2 logfile switches. With statspack (interval complete day > including night( > I also see ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------