Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Database file configuration for backup/recovery
I can't quite see the rationale behind switching off checkpointing by
setting _interval sky high, and then switching it back on with the (far less
useful) _timeout parameter!
Either switch it on, or switch it off. For performance, switch it off (which means setting _interval sky high and _timeout to zero).
But to limit recovery time (which is the only reason I can think of for performing additional checkpoints), log_checkpoint_interval is by far the better bet. A checkpoint every half hour (oh, ok... 1800 seconds if you must) means nothing: at 9.30am, that's probably a lot of transactions. But at 12.30pm, with everyone out to lunch, it's hardly any. So recovery time is either, er, long or short, and it's in the lap of the gods as to which. At least with an _interval, you know you've got, say, 50M of redo to replay
Regards
HJR
-- ---------------------------------------------- Resources for Oracle: http://www.hjrdba.com =============================== "Edzard" <edzard_at_volcanomail.com> wrote in message news:5d75e934.0202231550.2613bf82_at_posting.google.com...Received on Sat Feb 23 2002 - 18:12:02 CST
> Did I write log_chekpoint_interval? I meant
> log_checkpoint_timeout=1800. Log_checkpoint_interval definition
> depends on Oracle version but log_checkpoint_interval=999999 is good.
> You don't need extra checkpoint other then those caused by redo log
> switches and the above mentioned timeout of 1800 seconds.