Know more about _in_memory_undo

简介:

set parameter _in_memory_undo = FALSE to disable IMU Workaround: Disable IMU (set _in_memory_undo=FALSE) PLEASE NOTE: This bug applies to single instance databases and not RAC as IMU is not enabled in RAC. 注意在RAC系统中IMU是不可用的,所以也就不必要去设置_in_memory_undo=FALSE The workaround will prevent the problem, but will not fix it. Note: _in_memory_undo is a dynamic parameter for 10g with values of TRUE or FALSE. It specifies whether there should be in memory undo for transactions. Setting this value to FALSE will disable this feature. This will cause excess redo generation. _in_memory_undo is applicable when compatibility >= 10.0 undo_management = AUTO cluster_database = FALSE Running IMU transactions may generate out-of-order redo records Disabling in memory undo (_in_memory_undo=false) can help to eliminate "In memory undo latch" contention but there may still be "undo global data" latch contention as that latch is used regardless of the setting of _in_memory_undo. The fix for this bug can help reduce contention on both latches.


本文转自maclean_007 51CTO博客,原文链接:http://blog.51cto.com/maclean/1277085

相关文章
|
存储 缓存 监控
PG中的WAL:1 buffer cache
PG中的WAL:1 buffer cache
145 0
|
存储 SQL 缓存
InnoDB之UNDO LOG介绍
undo log是InnoDB事务特性的重要组成部分。当对记录做增删改操作就会产生undo记录,undo记录会记录到单独的表空间中。 本文将从代码层面对undo log进行一个简单的介绍;主要从下面四个方面来介绍undo log:undo log组织形式与分配与记录,以及undo log的应用及其清理。从这四个方面出发,我们就可以基本了解undo log的整个生命周期。
739 1
|
关系型数据库
InnoDB redo log thread cpu usage
InnoDB 在8.0 里面把写redo log 角色的各个线程都独立出来, 每一个thread 都处于wait 状态, 同样用户thread 调用log_write_up_to 以后, 也会进入wait 状态.这里的wait 等待最后都是通过调用 os_event_wait_for 来实现, 而 os_event_wait_for 是先spin + wait 的方式实现.所以这里有两个参数会影响os_event_wait_for 函数:spins_limit,timeout.
167 0
|
关系型数据库 数据库 Oracle

热门文章

最新文章