Fast-Start Time-Based Recovery (FSTBR) was introduced with Oracle9i for the purpose of being able to define a target mean time to recover (MTTR) in the case of crash or instance recovery. Previously, various parameters (log_checkpoint_interval, log_checkpoint_timeout, fast_start_io_target, and db_block_max_dirty_target) needed to be set to try and control the overall MTTR from an instance or database crash. Setting these parameters was not very exact, and it was difficult to translate them into a target MTTR.
With FSTBR, a desired MTTR for the database is defined in seconds. This is done using the FAST_START_MTTR_TARGET parameter. Once this parameter is set, Oracle will configure internal database settings to try and maintain this requirement.
Note: The FAST_START_MTTR_TARGET parameter provides only an estimated MTTR value. Several factors such as IO contention can cause the actual recovery time to extend beyond the requested MTTR.
The FAST_START_MTTR_TARGET parameter can have a value set anywhere from 0 to 3600 seconds. (Setting this value to zero disables this feature, but, other parameters such as LOG_CHECKPOINT_INTERVAL are still in effect). The lower the value, the more often the database will be checkpointing. This in turn can cause performance issues. This parameter is dynamic, so, it can be altered while the database is still operating. This makes it easier to tune the performance/MTTR balance.
The FAST_START_MTTR_TARGET is calculated based on a number of assumptions made by Oracle9i when the database is first opened. Because the value is dynamic and adaptive, it will be adjusted over time as the databse is used. The longer the database is up and running, the better Oracle will be at establishing checkpoint rates that maintain the requested MTTR.
Oracle9i maintains this target MTTR by continuously checkpointing the database, as required, and advancing the checkpoint counter that indicates the position in the redo log that was last checkpointed. Oracle maintains the checkpointing operation so that it will write out changed data at a rate that maintains the requested MTTR. During instance or crash recovery, Oracle9i will start recovering the database beginning at the checkpoint counter address, rather than at the point of the last normal checkpoint (such as occurs with redo log switches), thus reducing the overall time required to perform recovery.
With the introduction of FSTBR, some parameter changes have been effected. The following table indicates the changes that have occurred:
The V$INSTANCE_RECOVERY view has changed in Oracle9i to accommodate the new functionality of FSTBR. New columns include: