eygle.com   eygle.com
eygle.com eygle

« 关于Mutex的笔记 | Blog首页 | 青年汇小区业主 vs 朝阳绿化局维权的胜利 »


根据Oracle Metalink文档 Note:565424.1,CURSOR_SPACE_FOR_TIME 参数已经被Oracle放弃。

最先放弃的版本是: and
在早期的版本中,用户可以通过设置这个参数为True,使得Oracle使用更多的Shared SQL Area去保存SQL,从而提高反复执行SQL解析的速度。
然而随着Oracle Mutexes Pin机制的引入,用户已经几乎不再会从这个参数中受益,加上在某些特定的环境下,这个参数可能会导致严重Bug,随意最终,这个参数被废弃。


CURSOR_SPACE_FOR_TIME lets you use more space for cursors in order to save time. It affects both the shared SQL area and the client's private SQL area.

Values True means take the benifits of this parameter,With True setting Shared SQL areas are kept pinned in the shared pool. As a result, shared SQL areas are not aged out of the pool as long as an open cursor references them. Because each active cursor's SQL area is present in memory, execution is faster. However, the shared SQL areas never leave memory while they are in use. Therefore, you should set this parameter to TRUE only when the shared pool is large enough to hold all open cursors simultaneously.

In addition, a setting of TRUE retains the private SQL area allocated for each cursor between executions instead of discarding it after cursor execution, saving cursor allocation and initialization time



    >> 2007-10-11文章:
           结束假期 回到北京
    >> 2006-10-11文章:
    >> 2005-10-11文章:


By eygle on 2008-10-11 08:38 | Comments (1) | Beginner | OraNews | 2054 |

1 Comment

有关问题, Oracle Mutexes Pin机制是怎样代替CURSOR_SPACE_FOR_TIME的作用的?

CopyRight © 2004~2020 云和恩墨,成就未来!, All rights reserved.
数据恢复·紧急救援·性能优化 云和恩墨 24x7 热线电话:400-600-8755 业务咨询:010-59007017-7040 or 7037 业务合作: marketing@enmotech.com