關於 cursor_sharing = similar
ZT
http://hi.baidu.com/slash_gao/blog/item/c96db24332e558179313c611.html
我們先看看在表沒有分析無統計資料情況下的表現
SQL> alter session set cursor_sharing = similar;
Session altered.
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4948
parse time elapsed 4468
parse count (total) 170148
parse count (hard) 1619 (硬分析次數)
parse count (failures) 80
SQL> select count(*) from t where object_id = 1000;
COUNT(*)
----------
0
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4948
parse time elapsed 4468
parse count (total) 170172
parse count (hard) 1620
parse count (failures) 80
SQL> /
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4948
parse time elapsed 4468
parse count (total) 170176
parse count (hard) 1620
parse count (failures) 80
SQL> select count(*) from t where object_id = 1000;
COUNT(*)
----------
0
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4948
parse time elapsed 4468
parse count (total) 170178
parse count (hard) 1620
parse count (failures) 80
SQL> select count(*) from t where object_id = 1001;
COUNT(*)
----------
0
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4948
parse time elapsed 4468
parse count (total) 170180
parse count (hard) 1620(即使object_id發生變化依然沒有硬解析)
parse count (failures) 80
我們再來看分析表和欄位資訊後的表現
SQL> analyze table t1 compute statistics for table for columns object_id;
Table analyzed.
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4973
parse time elapsed 4495
parse count (total) 170982
parse count (hard) 1640
parse count (failures) 80
SQL> select count(*) from t1 where object_id = 5000;
COUNT(*)
----------
0
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4973
parse time elapsed 4495
parse count (total) 170984
parse count (hard) 1641
parse count (failures) 80
SQL> select count(*) from t1 where object_id = 5000;
COUNT(*)
----------
0
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4973
parse time elapsed 4495
parse count (total) 171008
parse count (hard) 1641 (重複執行沒發生變化)
parse count (failures) 80
SQL> select count(*) from t1 where object_id = 5001;
COUNT(*)
----------
0
SQL> select name,value from v$sysstat where name like '%parse%';
NAME VALUE
---------------------------------------------------------------- ----------
parse time cpu 4973
parse time elapsed 4495
parse count (total) 171010
parse count (hard) 1642 (當object_id變化的時候產生硬分析)
parse count (failures) 80
SQL>
SQL> select sql_text,child_number from v$sql where sql_text like 'select count(*) from t1 where%';
SQL_TEXT
--------------------------------------------------------------------------------
CHILD_NUMBER
------------
select count(*) from t1 where object_id = :"SYS_B_0"
0
select count(*) from t1 where object_id = :"SYS_B_0"
1
可以看出若存在object_id的 histograms ,則每次是不同的 值 的時候都產生硬解析 ,若不存在 histograms ,則不產生硬解析 。換句話說,當表的欄位被分析過存在histograms的時候,similar 的表現和exact一樣,當表的欄位沒被分析不存在histograms的時候,similar的表現和force一樣。這樣避免了一味地如force一樣轉換成變數形式,因為有hostograms的情況下轉換成變數之後就容易產生錯誤的執行計劃,沒有利用上統計資訊。而exact呢,在沒有hostograms的情況下也要分別產生硬解析,這樣的話,由於執行計劃不會受到資料分佈的影響(因為沒有統計資訊)重新解析是沒有實質意義的。而similar則綜合了兩者的優點。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/7199859/viewspace-551869/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 關於cursor_sharing=similarMILA
- 關於cursor_sharing = similar(ZT)MILA
- 關於cursor_sharing = similar (zt)MILA
- CURSOR_SHARING=SIMILARMILA
- cursor_sharing=similar深度剖析MILA
- cursor_sharing : exact , force , similarMILA
- 有關引數cursor_sharing=similar的測試MILA
- ANNOUNCEMENT: Deprecating the cursor_sharing = ‘SIMILAR’MILA
- cursor_sharing = similar , exact 區別MILA
- cursor_sharing=similar 與 直方圖MILA直方圖
- cursor_sharing設定為similar 的弊端MILA
- Cursor_sharing=SIMILAR取值與直方圖(上)MILA直方圖
- Cursor_sharing=SIMILAR取值與直方圖(下)MILA直方圖
- oracle實驗記錄 (cursor_sharing(2)SIMILAR)OracleMILA
- [20140802]cursor_sharing=similar.txtMILA
- Oracle 11g 中 cursor_sharing 設定為SIMILAR 導致的問題OracleMILA
- 10203設定CURSOR_SHARING為SIMILAR導致物化檢視重新整理失敗MILA
- Cursor_sharing,Histogram,Analyze之間的關係Histogram
- Cursor_sharing,Histogram,Analyze之間的關係(轉)Histogram
- oracle cursor_sharing [轉]Oracle
- oracle引數-cursor_sharingOracle
- 【Leetcode】800. Similar RGB ColorLeetCodeMILA
- AtCoder Beginner Contest 282 G - Similar PermutationMILA
- Oracle 的 cursor_sharing引數Oracle
- 關於IT,關於技術
- LeetCode之Leaf-Similar Trees(Kotlin)LeetCodeMILAKotlin
- NJUST 1746 Similar Number(南京邀請賽 J題)MILA
- 繫結變數和cursor_sharing變數
- cursor_sharing和substr函式索引函式索引
- 關於
- 關於~
- ORACLE中Cursor_sharing引數詳解Oracle
- 小心設定cursor_sharing=force引數
- 『類自然數教室:1~8』(A similar Natural number classroom:1~8)MILAOOM
- ursor_sharing=SIMILAR 引發大量的 cursor: mutex SMILAMutex
- zt_繫結變數和cursor_sharing變數
- 關於RedisRedis
- 關於REMREM