max_commit_propagation_delay默认值为700,即7秒(单位0.01s,http://www.orafaq.com/parms/parm1217.htm)。
这个参数应该配置的是RAC(Real Application Cluster)之间同步数据的频率。修改这个参数的好处就不用说了( 本人深受其苦啊 ),但是如果走另一个极端,可能会给数据库造成更大的压力
参数指定一个instance SGA中的SCN被LWGR进程刷新前所保持的最长时间,但是在11i中建议设置这个值为0后:是否会影响其它操作,比如使用RMAN备份,对LGWR进程对refresh local SCN,Global SCN的影响?
发现还是有影响的,我觉得是如果数据库的数据文件比较大(25G-30G),RMAN备份过程中,如果对这个数据文件的写操作比较多,会造成性能问题,LGWR进程刷新SCN出现等待,并导致实例Crash。
当将max_commit_propagation_delay恢复默认值后,就没有出现备份过程中的实例死掉的状况。
所以,如果不是那种非得实例间要实时同步的,就不要修改这个参数啦。
http://bbs.erp100.com/thread-19126-1-1.html
因此,凡是遇到RAC延迟造成的问题都应该通过应用层处理,根据20-80原则,大部分的应用可以忽略这个问题。
ps:
关于RAC,oracle的广告是这样解释的。Oracle RAC is a cluster database with a shared cache architecture that overcomes the limitations of traditional shared-nothing and shared-disk approaches to provide highly scalable and available database solutions for all your business。( 这里要感谢俺们的dba,呵呵,否则俺说啥也猜不出这句E文的含义 )
Aims
Since Oracle RAC allows multiple computers (instances) to access a single database simultaneously, it addresses several areas of database management. These areas include:
Functionality
Oracle RAC allows multiple computers to run Oracle RDBMS software simultaneously while accessing a single database , thus providing a clustered database.
In a non-RAC Oracle database, a single instance accesses a single database. The database consists of a collection of data files , control files, and redo logs located on disk . The instance comprises the collection of Oracle-related memory and operating system processes that run on a computer system.
In an Oracle RAC environment, two or more computers (each with an instance) concurrently access a single database. This allows an application or user to connect to either computer and have access to a single coordinated set of data.
http://en.wikipedia.org/wiki/Oracle_RAC