INDEX_JOIN Hint研究

今天看Oracle92 Document，看到Index_join这个hint。以前没有留意过，于是作了个小实验，知道这个hint的就无须再看了，不知道的建议看一下下面的内容。

官方：The INDEX_JOIN hint explicitly instructs the optimizer to use an index join as an access path. For the hint to have a positive effect, a sufficiently small number of indexes must exist that contain all the columns required to resolve the query.

本部分内容属个人观点，有疑问请让我知晓。

演练如下：
SQL> create index idx_ijoin_owner
2 on t_ijoin (owner);

索引已创建。

SQL> create index idx_ijoin_object_name
2 on t_ijoin (object_name);

索引已创建。

SQL> select index_name,index_type,table_name,table_type
2 from user_indexes
3 where table_name='T_IJOIN';

INDEX_NAME INDEX_TYPE TABLE_NAME TABLE_TYPE
------------------------------ -------------------- -------------------- -----------
IDX_IJOIN_OBJECT_NAME NORMAL T_IJOIN TABLE
IDX_IJOIN_OWNER NORMAL T_IJOIN TABLE

SQL> set autot trace exp stat

注：如果遇到上述错误，参考下面链接解决：
http://sdusun.itpub.net/post/7915/250190

继续：

不加hint
SQL> set autot trace exp stat;
SQL> select owner,object_name from t_ijoin
2 where owner='SCOTT' and object_name='DEPT';

Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE
1 0 AND-EQUAL
2 1 INDEX (RANGE SCAN) OF 'IDX_IJOIN_OWNER' (NON-UNIQUE)
3 1 INDEX (RANGE SCAN) OF 'IDX_IJOIN_OBJECT_NAME' (NON-UNIQU

Statistics
----------------------------------------------------------
0 recursive calls
0 db block gets
8 consistent gets
2 physical reads
0 redo size
440 bytes sent via SQL*Net to client
503 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
1 rows processed

SQL>

添加hint
SQL> r
1 select /*+ INDEX_JOIN (T_IJOIN IDX_IJOIN_OWNER IDX_IJOIN_OBJECT_NAME) */
2 owner,object_name
3 from t_ijoin
4* where owner='SCOTT' and object_name='DEPT'

Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=4 Card=3 Bytes=102)
1 0 VIEW OF 'index$_join$_001' (Cost=4 Card=3 Bytes=102)
2 1 HASH JOIN
3 2 INDEX (RANGE SCAN) OF 'IDX_IJOIN_OBJECT_NAME' (NON-UNI
4 2 INDEX (RANGE SCAN) OF 'IDX_IJOIN_OWNER' (NON-UNIQUE) (

Statistics
----------------------------------------------------------
0 recursive calls
0 db block gets
5 consistent gets
0 physical reads
0 redo size
440 bytes sent via SQL*Net to client
503 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
1 rows processed

到这里应该能看到，使用index_join使得consistent gets降低到5，原因不难理解：select所需要的数据完全可以从索引中得到。可以想象，数据量越大，Index_join作用越明显。
缺点：经过多次试验表明，当第一次执行带有index_join这个hint的语句时，recursive calls高一些！

INDEX_JOIN 的第二种写法：

select /*+ INDEX_JOIN (T_IJOIN IDX_IJOIN_OWNER,IDX_IJOIN_OBJECT_NAME) */
owner,object_name
from t_ijoin
where owner='SCOTT' and object_name='DEPT';

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/593324/viewspace-376215/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/593324/viewspace-376215/