The four mechanisms [5mekEnizEm] which determines Oracle to take a checkpoint.

Submitted by UMBRO
on September 5, 2007 - 11:07pm

■ Set the LOG_CHECKPOINT_TIMEOUT initialization parameter
■ Set the LOG_CHECKPOINT_INTERVAL initialization parameter
■ Set the FAST_START_MTTR_TARGET initialization parameter
■ Set the size of the smallest redo log

For information on which mechanism is controlling checkpointing behavior, query the V$INSTANCE_RECOVERY view.

When a checkpoint occurs, Oracle must update the headers of all datafiles to record the details of the checkpoint. This is done by the CKPT process. The CKPT process does not write blocks to disk; DBWn always performs that work.

Oracle makes the control files and datafiles consistent to the same SCN during a database checkpoint. The only tablespaces in a consistent backup that are allowed to have older SCNs are read-only and offline normal tablespaces, which are still consistent with the other datafiles in the backup because no changes have been made to them.