Log switch after 3-second timout: what is it about ?

Hi (again),
I forgot this question in one of my recent mails: in the course book Enterprise DBA Part 1A: Arch. & Admin. you can read at page 7-6 (chapter Maintaining Redo Log Files, § regarding the flushing of buffer redo entries to redo log files):
> The Oracle server sequentially records all changes made
> to the DB in the redo log buffer. The redo log buffer
> is used in a circular manner. The redo entries are
> written to one of the online redo log groups called the
> *current* online redo log group by the LGWR process under
> the following situations:
> o when a transacdtion commits
> o when the redo log buffer becomes 1/3 full
> o when there is more than a megabyte of changed records
> in the redo log buffer
> o when a timout occurs (every three seconds)
> o before the DBWn writes modified bolocks in the DB buffer
> cache to the data files

What is this "timeout" they talk about ? Does it have anything to do with the value at which you can set the LOG_CHECKPOINT_TIMEOUT ? I don't think so, so: is there a way to set it and manage it ? Or will it ALWAYS be 3 seconds, whatever your configuration and the way you've created your DB ?

Thanks...
Spendius Received on Thu Jul 17 2003 - 08:05:25 CDT