Events That Initiate a Full Checkpoint

In the following situations, the database server performs a full checkpoint to ensure the physical consistency of all data on disk:

• When you issue onmode -ky to shut down the database server
• When you initiate a checkpoint from the command line with onmode -c
• When you convert the database server to a newer version or revert to a previous version
• When you perform a backup or restore using ON-Bar

  The backup tool performs a full checkpoint automatically to ensure the physical consistency of all data before it writes it to the backup media.

• At the end of fast recovery or full recovery
• If the database server is about to switch to the next free log and the log following the free log contains the oldest update

  For example, suppose four logical-log files have the status shown in the following list. The database server forces a full checkpoint when it switches to logical-log file 3 if the logical-log file 4 has the oldest update. The full checkpoint advances the oldest update to logical-log file 3.

  logid

  Logical-Log File Status

  1

  U-B----

  2

  U---C--

  3

  F

  4

  U-B---L

The database server performs a full checkpoint to prevent problems with fast recovery of old log records.

For a list of situations in which you should initiate a full checkpoint, see the following section.