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

相关文章
|
7月前
|
监控 关系型数据库 MySQL
innodb_buffer_pool_instances 如何根据cpu和内存进行配置
`innodb_buffer_pool_instances` 是用于配置 InnoDB 缓冲池实例数的参数。每个实例都管理缓冲池的一部分,这有助于提高并发性能。通常,你可以根据系统的 CPU 和内存来调整这个参数,以获得更好的性能。 以下是一些建议和步骤,帮助你根据 CPU 和内存进行 `innodb_buffer_pool_instances` 的配置: 1. **了解系统资源:** 首先,了解系统的硬件资源,特别是内存和CPU。检查系统上可用的物理内存和 CPU 核心数量。 2. **考虑每个实例的大小:** 在配置 `innodb_buffer_pool_instances` 时,
285 0
|
7月前
PGA memory operation
PGA memory operation
102 1
|
存储 缓存 监控
PG中的WAL:1 buffer cache
PG中的WAL:1 buffer cache
135 0
|
关系型数据库
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.
159 0
|
缓存 Oracle 关系型数据库
[20171205]rman output Memory Buffers 2
[20171205]关于rman output Memory Buffers 2.txt --//昨天在QQ上与人聊天,再次提到这个问题.感觉在链接http://blog.
999 0