了解Maclean Liu|向Maclean Liu提问 Oracle ALLSTARS 全明星(群内有多位Oracle高级售后support,N位OCM和ACE) QQ群 # QQ群号:23549328 # 已经升级到 2000人群,空位多多。欢迎有一定基础的Oracle骨友加入,现在入群需要经过Maclean的技术面试,欢迎面试,请加QQ号:47079569 为好友参加面试 2群基础群 适合刚入门的同学,会共享最佳入门实践和资料 QQ群 # QQ群号:171092051 # 已经升级到 500人的超级群,空位多多,无需面试

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.

posted on 2010-01-17 05:31  Oracle和MySQL  阅读(215)  评论(0编辑  收藏  举报

导航