FAST_START_MTTR_TARGET、LOG_CHECKPOINT_TIMEOUT、LOG_CHECKPOINT_INTERVAL几个参数的含义与区别

最新推荐文章于 2021-04-03 04:44:28 发布

wh62592855

最新推荐文章于 2021-04-03 04:44:28 发布

阅读量3.6k

点赞数

分类专栏： Oracle Basics 文章标签： parallel oracle cache transactions database 数据库

本文链接：https://blog.csdn.net/wanghai__/article/details/4834308

版权

本文详细解析了Oracle数据库中的FAST_START_MTTR_TARGET、LOG_CHECKPOINT_INTERVAL和LOG_CHECKPOINT_TIMEOUT参数，讨论了它们在数据库恢复中的作用和区别。FAST_START_MTTR_TARGET用于指定数据库恢复所需时间，而LOG_CHECKPOINT_INTERVAL和LOG_CHECKPOINT_TIMEOUT则分别控制检查点的频率和超时时间。此外，文章还提到了FAST_START_IO_TARGET参数的历史和自动调整检查点机制，以及FAST_START_PARALLEL_ROLLBACK参数在并行回滚中的应用。通过对这些参数的理解，可以帮助优化数据库的恢复性能和效率。

摘要由CSDN通过智能技术生成

先来看看这几个参数在官方文档中定义是怎样的

FAST_START_MTTR_TARGET

Property	Description
Parameter type	Integer
Default value	0
Modifiable	ALTER SYSTEM
Range of values	0 to 3600 seconds
Basic	No
Real Application Clusters	Multiple instances can have different values, and you can change the values at runtime.

FAST_START_MTTR_TARGET enables you to specify the number of seconds the database takes to perform crash recovery of a single instance. When specified, FAST_START_MTTR_TARGET is overridden by LOG_CHECKPOINT_INTERVAL.

LOG_CHECKPOINT_INTERVAL

Property	Description
Parameter type	Integer
Default value	0
Modifiable	ALTER SYSTEM
Range of values	0 to 2³¹ - 1
Basic	No
Real Application Clusters	Multiple instances can have different values.

LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.

Regardless of this value, a checkpoint always occurs when switching from one online redo log file to another. Therefore, if the value exceeds the actual redo log file size, checkpoints occur only when switching logs. Checkpoint frequency is one of the factors that influence the time required for the database to recover from an unexpected failure.

Notes:

· Specifying a value of 0 (zero) for LOG_CHECKPOINT_INTERVAL has the same effect as setting the parameter to infinity and causes the parameter to be ignored. Only nonzero values of this parameter are considered meaningful.

· Recovery I/O can also be limited by setting the LOG_CHECKPOINT_TIMEOUT parameter or by the size specified for the smallest redo log. For information on which mechanism is controlling checkpointing behavior, query the V$INSTANCE_RECOVERY view.

LOG_CHECKPOINT_TIMEOUT

Property	Description
Parameter type	Integer
Default value	1800
Modifiable	ALTER SYSTEM
Range of values	0 to 2³¹ - 1
Basic	No
Real Application Clusters	Multiple instances can have different values.

LOG_CHECKPOINT_TIMEOUT specifies (in seconds) the amount of time that has passed since the incremental checkpoint at the position where the last write to the redo log (sometimes called the tail of the log) occurred. This parameter also signifies that no buffer will remain dirty (in the cache) for more than integer seconds.