Oracle 通过rowid秒优SQL
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了Oracle 通过rowid秒优SQL，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含15166字，纯文字阅读大概需要22分钟。
内容图文
注释：前段时间，有2个SQL，每天访问至少上千次,操作不频繁时稳定在6s，频繁时13s；加2个字段的组合索引，查询还是不走索引！这种情况通过什么方式合理走索引？[不是hint]
环境：
|
AIX |
7.1 |
| >> | CPU 64 (16C) |
| >> | Mem 64 |
| Oracle | 11.2.0.3.0 |
|
>>
|
Mem 40G
|
表结构/数据情况
***** 表cs_oi_confirm_1段大小 2213MB；新建表,不存在高水位等问题..
|
COLUMN_NAME |
COLUMN_ID |
DATA_TYPE |
NULLABLE |
NUM_DISTINCT |
| CON_OI_ID | 1 | NUMBER | N |
5182502
->主键 |
| NATI_TASK_ID | 2 | NUMBER | Y | 51048 |
| SUPP_PROT_ID | 3 | NUMBER | Y | 41684 |
| BUSI_CUST_ID | 4 | NUMBER | N | 4756 |
| ORDER_ID | 5 | NUMBER | N | 317152 |
| EMP_ID | 6 | NUMBER | Y | 310560 |
| OI_STAT | 7 | NUMBER | N | 5 |
| PAY_WAY | 8 | NUMBER | Y | 3 |
| PAY_FEES_WAY | 9 | NUMBER | Y | 3 |
| INS_ACCU_NO | 10 | VARCHAR2 | Y | 0 |
| PROT_DET_ID | 11 | NUMBER | Y | 176880 |
| CHAR_COUN_TYPE | 12 | NUMBER | Y | 3 |
| PROD_PRICE_SCHM_ID | 13 | NUMBER | N | 2050 |
| PROD_SCHM_ID | 14 | NUMBER | N | 1380 |
| PROD_ID | 15 | NUMBER | N | 50 |
| EXECU_AREA_ID | 16 | NUMBER | N | 161 |
| EXECU_SUPP_ID | 17 | NUMBER | N | 101 |
| PROT_LOCAL_STAN_ID | 18 | NUMBER | Y | 268800 |
| LOCAL_STAN_ID | 19 | NUMBER | Y | 2319 |
| OI_OPE_CATEGORY | 20 | NUMBER | N | 7 |
| DECL_WAGE | 21 | NUMBER | Y | 39912 |
| QUANTITY | 22 | NUMBER | N | 2 |
| PAY_BEGIN_YM | 23 | NUMBER | Y | 179 |
| PAY_SUPP_PRICE | 24 | NUMBER | N | 138688 |
| CUST_BEGIN_DATE | 25 | DATE | N | 253 |
| CUST_END_DATE | 26 | DATE | Y | 139 |
| CUST_PER_BASE | 27 | NUMBER | Y | 35264 |
| CUST_COM_BASE | 28 | NUMBER | Y | 35936 |
| NATI_BEGIN_DATE | 29 | DATE | N | 251 |
| NATI_END_DATE | 30 | DATE | Y | 139 |
| NATI_PER_BASE | 31 | NUMBER | Y | 35264 |
| NATI_COM_BASE | 32 | NUMBER | Y | 35936 |
| NATI_PUBLISH_REP_ID | 33 | NUMBER | N | 128 |
| NATI_PUBLISH_TIME | 34 | DATE | N | 896064 |
| NATI_PUBLISH_DESC | 35 | VARCHAR2 | Y | 2 |
| NATI_PUBLISH_EDI_REP_ID | 36 | NUMBER | Y | 25 |
| NATI_PUBLISH_EDI_TIME | 37 | DATE | Y | 3566 |
| SUPP_BEGIN_DATE | 38 | DATE | N | 250 |
| SUPP_END_DATE | 39 | DATE | Y | 129 |
| SUPP_PER_BASE | 40 | NUMBER | Y | 35340 |
| SUPP_COM_BASE | 41 | NUMBER | Y | 36012 |
| SUPP_DECL_DATE | 42 | DATE | Y | 1747 |
| SUPP_EDI_DESC | 43 | VARCHAR2 | Y | 9 |
| SUPP_EDI_ADD_DESC | 44 | VARCHAR2 | Y | 345 |
| SUPP_CONF_TIME | 45 | DATE | Y | 802432 |
| NATI_CONF_TIME | 46 | DATE | Y | 772672 |
| NATI_CONF_DESC | 47 | VARCHAR2 | Y | 0 |
| NATI_ADD_DESC | 48 | VARCHAR2 | Y | 0 |
| DECL_ADD_SUB_TYPE | 49 | NUMBER | Y | 0 |
| PARENT_ID | 50 | NUMBER | Y | 5351 |
| OI_DET_CRE_YM | 51 | NUMBER | Y | 44 |
| CHARHZ | 52 | NUMBER | N | 3 |
| BILLING_HZ | 53 | NUMBER | N | 3 |
| IS_CALC | 54 | NUMBER | Y | 2 |
| REF_BACK_SUPP_BEGIN_DATE | 55 | DATE | Y | 0 |
| REF_BACK_SUPP_END_DATE | 56 | DATE | Y | 0 |
| REF_BACK_SUPP_PER_BASE | 57 | NUMBER | Y | 0 |
| REF_BACK_SUPP_COM_BASE | 58 | NUMBER | Y | 0 |
| BUSI_BEGIN_DATE | 59 | DATE | Y | 254 |
| BUSI_END_DATE | 60 | DATE | Y | 129 |
| BUSI_PER_BASE | 61 | NUMBER | Y | 35284 |
| BUSI_COM_BASE | 62 | NUMBER | Y | 35960 |
| BUSI_CONF_REP_ID | 63 | NUMBER | Y | 345 |
| BUSI_CONF_TIME | 64 | DATE | Y | 813696 |
| BUSI_CONF_DESC | 65 | VARCHAR2 | Y | 0 |
| CHAR_BEGIN_YM | 66 | NUMBER | Y | 2 |
| CATEGORY | 67 | NUMBER | N | 3 |
| SUPP_TASK_ID | 68 | NUMBER | Y | 99968 |
| BUSI_TASK_ID | 69 | NUMBER | Y | 91584 |
| OI_OPE_CATEGORY_BACKUP | 70 | NUMBER | Y | 3 |
| BUSI_CIRC_STATE | 71 | NUMBER | N | 6 |
| BUSI_CIRC_HANDLE_TYPE | 72 | NUMBER | Y | 3 |
| RECV_NATI_OUT_TIME | 73 | DATE | Y | 569 |
| RECV_NATI_OUT_USER_ROLE_ID | 74 | NUMBER | Y | 2 |
| RECV_BUSI_INTO_TIME | 75 | DATE | Y | 1354 |
| RECV_BUSI_INTO_USER_ROLE_ID | 76 | NUMBER | Y | 80 |
| RECV_BUSI_DISPH_TIME | 77 | DATE | Y | 2071 |
| RECV_BUSI_DISPH_USER_ROLE_ID | 78 | NUMBER | Y | 80 |
| RECV_ES_COOK_TIME | 79 | DATE | Y | 11 |
| RECV_ES_COOK_USER_ROLE_ID | 80 | NUMBER | Y | 9 |
| RECV_BUSI_UPDATE_BEGIN_DATE | 81 | DATE | Y | 243 |
| RECV_BUSI_UPDATE_END_DATE | 82 | DATE | Y | 137 |
| RECV_BUSI_UPDATE_PER_BASE | 83 | NUMBER | Y | 14502 |
| RECV_BUSI_UPDATE_COM_BASE | 84 | NUMBER | Y | 14667 |
| IS_DEL | 85 | NUMBER | N | 2 |
| IS_REF_BACK_HIS | 86 | NUMBER | Y | 1 |
| ORD_SEND_SUPP_ID | 87 | NUMBER | N | 57 |
| ORD_RECE_SUPP_ID | 88 | NUMBER | N | 101 |
| OI_CRE_CATEGORY | 89 | NUMBER | Y | 0 |
| LEVEL_ | 90 | NUMBER | N | 2 |
| IS_SEND_BIG_WHOLE | 91 | NUMBER | N | 3 |
| PER_PAY_PRICE | 92 | NUMBER | Y | 56080 |
| COM_PAY_PRICE | 93 | NUMBER | Y | 112944 |
| NATI_PUBLISH_BUR_ID | 94 | NUMBER | N | 155 |
| NATI_PUBLISH_ADD_DESC | 95 | VARCHAR2 | Y | 0 |
| PER_ATTACH | 96 | NUMBER | Y | 23 |
| COM_ATTACH | 97 | NUMBER | Y | 31 |
| PER_PERCENT | 98 | NUMBER | Y | 35 |
| COM_PERCENT | 99 | NUMBER | Y | 71 |
| BUSI_MNGR_APP_STAT | 100 | NUMBER | Y | 4 |
| ORD_SEND_PROD_SCHM_ID | 101 | NUMBER | N | 1073 |
| NATI_EDI_DESC | 102 | NUMBER | Y | 5 |
| NATI_EDI_ADD_DESC | 103 | VARCHAR2 | Y | 20 |
| NATI_REFU_EDI_DESC | 104 | NUMBER | Y | 6 |
| NATI_REFU_EDI_ADD_DESC | 105 | VARCHAR2 | Y | 17 |
| BAT_NUM | 106 | NUMBER | Y | 5469 |
| ORD_RECE_PROD_PRIC_SCHM_ID | 107 | NUMBER | N | 2654 |
| SEC_INV_SUBJECT | 108 | NUMBER | N | 75 |
| BILLS_TYPE | 109 | NUMBER | N | 2 |
| ACCOU_ITEM_ID | 110 | NUMBER | N | 4 |
| CHANGE_PROT_USER_ROLE_ID | 111 | NUMBER | Y | 0 |
| CHANGE_PROT_TIME | 112 | DATE | Y | 0 |
| SEND_EVA_INFO_ID | 113 | NUMBER | Y | 315168 |
| ORDER_CATE | 114 | NUMBER | N | 2 |
| CON_ACCE_ID | 115 | NUMBER | Y | 9985 |
| NATI_EDIT_COST_DESC | 116 | NUMBER | Y | 19 |
| NATI_EDIT_COST_ADD_DESC | 117 | VARCHAR2 | Y | 496 |
| SUPP_DECL_DATE_OLD | 118 | DATE | Y | 14 |
| IS_BATCH | 119 | NUMBER | Y | 2 |
| SOURCE_OI_ID | 120 | VARCHAR2 | Y | 1112064 |
| HIS_RE_BA_NUMBER | 121 | VARCHAR2 | Y | 710 |
| REAL_ORD_SEND_SUPP_ID | 122 | NUMBER | Y | 56 |
| REAL_ORD_RECE_SUPP_ID | 123 | NUMBER | Y | 100 |
| IS_EFFECT | 124 | NUMBER | Y | 2 |
|
|
|
|
|
|
parent_id is not null 总数 15899
source_oi_id is not null 总数 1113634
|
索引情况:
索引名字 |
大小(MB) |
column_name |
属性 |
| IDX_COC_SOURCE_PARENT_ID | 25 | SOURCE_OI_ID,PARENT_ID | bree |
|
PK_cs_oi_confirm_1
|
96
|
CON_OI_ID
|
bree[unique]
|
SQL 1、 查看原SQL 速度/执行计划：
|
S
QL> select to_char(wm_concat(c.con_oi_id)) from cs_oi_confirm_1 c where c.parent_id in (3141609 , 3182013) and c.supp_prot_id = 6002704 ;
TO_CHAR(WM_CONCAT(C.CON_OI_ID))
--------------------------------------------------------------------------------
3141614,3141603,3141602
Elapsed: 00:00:06.27
Execution Plan
----------------------------------------------------------
Plan hash value: 475458160
------------------------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes |
Cost
(%CPU)|Time |
------------------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 14 |
76035
(2)|00:15:13 |
| 1 | SORT AGGREGATE | | 1 | 14 | | |
|* 2 |
TABLE ACCESS FULL
| CS_OI_CONFIRM_1 | 1 | 14 | 76035 (2)|00:15:13 |
-----------------------------------------------------------------------------------------
Predicate Information (identified by operation id):
---------------------------------------------------
2 - filter("C"."SUPP_PROT_ID"=6002704 AND ("C"."PARENT_ID"=3141609 OR
"C"."PARENT_ID"=3182013))
Statistics
----------------------------------------------------------
0 recursive calls
12 db block gets
276415 consistent gets
276408 physical reads
0 redo size
570 bytes sent via SQL*Net to client
524 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
1 rows processed
SQL>
|
分析优化方案：
原sql执行6s全扫；我们上文提到，已加SOURCE_OI_ID,PARENT_ID的组合索引IDX_COC_SOURCE_PARENT_ID；
？我们分析下为啥没有走索引
**** 1 ）不加supp_prot_id = 6002704，肯定会走主键索引和组合索引；
**** 2 ）加上supp_prot_id = 6002704，CBO 可能考虑（parent_id distinct key 占整个表0.1% ，supp_prot_id 回表，组合索引‘ 后导列INDEX SKIP SCAN‘ 等情况选择了全扫）等情况选了全扫.
**** 3 ）parent_id传一个值 和supp_prot_id = 6002704 时会走索引.. [多值时 衡量全表多块读更快..]
** 分析走索引是否合理？
****通过 parent_id is not null 总数= 15899 、distinct key = 5351 信息 和确认业务传值一般不到20个，走索引还是很合理的。
？怎么叫他走索引呢 .... 避免不走索引的几项
**** 1 ） 避免supp_prot_id = 6002704回表而不走索引，可以由一个sql 改成2个sql实现，先找到唯一数据，再通过唯一数据查询表 再做回表关联；
**** 2 ）唯一数据的选择主键(con_oi_id) 或 rowid 唯一标示；
SQl1、select to_char(wm_concat( ‘‘‘‘ || con_oi_id || ‘‘‘‘ )) from cs_oi_confirm_1 c where c.parent_id in ( 3141609 , 3182013 );
SQl2、select to_char(wm_concat( ‘‘‘‘ || rowid || ‘‘‘‘)) from cs_oi_confirm_1 c where c.parent_id in ( 3141609 , 3182013 );
？我们分析下为啥没有走索引
**** 1 ）不加supp_prot_id = 6002704，肯定会走主键索引和组合索引；
**** 2 ）加上supp_prot_id = 6002704，CBO 可能考虑（parent_id distinct key 占整个表0.1% ，supp_prot_id 回表，组合索引‘ 后导列INDEX SKIP SCAN‘ 等情况选择了全扫）等情况选了全扫.
**** 3 ）parent_id传一个值 和supp_prot_id = 6002704 时会走索引.. [多值时 衡量全表多块读更快..]
** 分析走索引是否合理？
****通过 parent_id is not null 总数= 15899 、distinct key = 5351 信息 和确认业务传值一般不到20个，走索引还是很合理的。
？怎么叫他走索引呢 .... 避免不走索引的几项
**** 1 ） 避免supp_prot_id = 6002704回表而不走索引，可以由一个sql 改成2个sql实现，先找到唯一数据，再通过唯一数据查询表 再做回表关联；
**** 2 ）唯一数据的选择主键(con_oi_id) 或 rowid 唯一标示；
SQl1、select to_char(wm_concat( ‘‘‘‘ || con_oi_id || ‘‘‘‘ )) from cs_oi_confirm_1 c where c.parent_id in ( 3141609 , 3182013 );
SQl2、select to_char(wm_concat( ‘‘‘‘ || rowid || ‘‘‘‘)) from cs_oi_confirm_1 c where c.parent_id in ( 3141609 , 3182013 );
****
3
）若用主键，sql1
需要主键和组合索引关联，而用SQL2只用组合索引就可以实现；
***最后优化的SQL如下：
步骤1、select to_char(wm_concat( ‘‘‘‘ || rowid || ‘‘‘‘)) from cs_oi_confirm_1 c where c.parent_id in ( 3141609,3182013 );
步骤2、SELECT to_char(wm_concat(c.con_oi_id)) FROM cs_oi_confirm_1 c where rowid in (上结果集) and c.supp_prot_id = 6002704;
看下优化效果~
|
步骤1： SQL> select to_char(wm_concat( ‘‘‘‘ || rowid || ‘‘‘‘)) from cs_oi_confirm_1 c where c.parent_id in (3141609, 3182013); TO_CHAR(WM_CONCAT(‘‘‘‘||ROWID||‘‘‘‘)) -------------------------------------------------------------------------------- ‘AAAm6DAACAACWJ8AAR‘,‘AAAm6DAACAACWCZAAO‘,‘AAAm6DAACAACVXuAAH‘,‘AAAm6DAACAACWFfAAB‘,‘AAAm6DAACAACWFfAAC‘,‘AAAm6DAACAACWFfAAD‘ Elapsed: 00:00:00.13 Execution Plan ---------------------------------------------------------- Plan hash value: 3275894710 -------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ------------------------------------------------------------------------------------------------ | 0 | SELECT STATEMENT | | 1 | 14 | 875 (4)| 00:00:11 | | 1 | SORT AGGREGATE | | 1 | 14 | | | |* 2 | INDEX FAST FULL SCAN | IDX_COC_SOURCE_PARENT_ID | 6 | 84 | 875 (4)| 00:00:11 | -------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - filter("C"."PARENT_ID"=3141609 OR "C"."PARENT_ID"=3182013) Statistics ---------------------------------------------------------- 1 recursive calls 12 db block gets 3228 consistent gets 0 physical reads 0 redo size 678 bytes sent via SQL*Net to client 524 bytes received via SQL*Net from client 2 SQL*Net roundtrips to/from client 0 sorts (memory) 0 sorts (disk) 1 rows processed 步骤2： SQL> SELECT to_char(wm_concat(c.con_oi_id)) FROM cs_oi_confirm_1 c where rowid in (‘AAAm6DAACAACWJ8AAR‘,‘AAAm6DAACAACWCZAAO‘,‘AAAm6DAACAACVXuAAH‘,‘AAAm6DAACAACWFfAAB‘, ‘AAAm6DAACAACWFfAAC‘, ‘AAAm6DAACAACWFfAAD‘) and c.supp_prot_id = 6002704; TO_CHAR(WM_CONCAT(C.CON_OI_ID)) -------------------------------------------------------------------------------- 3141614,3141603,3141602 Elapsed: 00:00:00.01 Execution Plan ---------------------------------------------------------- Plan hash value: 1353697632 ---------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ---------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 24 |1 (0)| 00:00:01 | | 1 | SORT AGGREGATE | | 1 | 24 | | | | 2 | INLIST ITERATOR | | | | | | |* 3 | TABLE ACCESS BY USER ROWID | CS_OI_CONFIRM_1 | 1 | 24 |1 (0)| 00:00:01 | ---------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 3 - filter("C"."SUPP_PROT_ID"=6002704) Statistics ---------------------------------------------------------- 1 recursive calls 12 db block gets 101 consistent gets 0 physical reads 0 redo size 570 bytes sent via SQL*Net to client 524 bytes received via SQL*Net from client 2 SQL*Net roundtrips to/from client 0 sorts (memory) 0 sorts (disk) 1 rows processed SQL> |
效果总结:
由原elapsed time (s)6.27s提升到0.13+0.01=0.14(简单理解就是讲全扫优化成组合索引扫描)，物理逻辑读 可以看上面信息。
SQL 2、 查看原SQL 速度/执行计划：
|
SQL> select * from cs_oi_confirm_1 t where 1 = 1 AND INSTR(‘,‘ || T.SOURCE_OI_ID || ‘,‘, 1259941) > 0 and t.is_del = 0 and SOURCE_OI_ID is not null order by t.PROD_ID, t.NATI_PUBLISH_TIME DESC; ------ 一条记录...字段有些多..页面问题,,在此不做显示 Elapsed: 00:00:09.85 Execution Plan ---------------------------------------------------------- Plan hash value: 2928122185 -------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes |TempSpc| Cost(%CPU)| Time | -------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 27841 | 9923K| | 79088 (3)| 00:15:50 | | 1 | SORT ORDER BY | | 27841 | 9923K| 16M| 79088 (3)| 00:15:50 | |* 2 | TABLE ACCESS FULL | CS_OI_CONFIRM_1 | 27841 | 9923K| | 76914 (3)| 00:15:23 | ------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - filter("SOURCE_OI_ID" IS NOT NULL AND "T"."IS_DEL"=0 AND INSTR(‘,‘||"T"."SOURCE_OI_ID"||‘,‘,‘1259941‘)>0) Statistics ---------------------------------------------------------- 1 recursive calls 0 db block gets 276414 consistent gets 276408 physical reads 0 redo size 10435 bytes sent via SQL*Net to client 524 bytes received via SQL*Net from client 2 SQL*Net roundtrips to/from client 1 sorts (memory) 0 sorts (disk) 1 rows processed |
方案思路都和sql1 相同...
***最后优化的SQL如下：
步骤1、
select /*count(1)*/to_char(wm_concat(rowid)) from cs_oi_confirm_1 t where INSTR(‘,‘ || T.SOURCE_OI_ID || ‘,‘, 1259941) > 0 and T.SOURCE_OI_ID is not null
;
步骤2、
SELECT count(1) FROM cs_oi_confirm_1 t where rowid in (‘AAAm6DAACAACYp5AAF‘) and t.is_del = 0 order by t.PROD_ID, t.NATI_PUBLISH_TIME DESC;
看下优化效果~
|
步骤1： SQL> select /*count(1)*/to_char(wm_concat(rowid)) from cs_oi_confirm_1 t where INSTR(‘,‘ || T.SOURCE_OI_ID || ‘,‘, 1259941) > 0 and T.SOURCE_OI_ID is not null --非必填项,不加声明not null就不会走索引; /*and t.is_del = 0 order by t.PROD_ID, t.NATI_PUBLISH_TIME DESC*/ TO_CHAR(WM_CONCAT(ROWID)) --------------------------------------- AAAm6DAACAACYp5AAF Elapsed: 00:00:00.46 Execution Plan ---------------------------------------------------------- Plan hash value: 3275894710 -------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | -------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 15 | 875 (4)| 00:00:11 | | 1 | SORT AGGREGATE | | 1 | 15 | | | |* 2 | INDEX FAST FULL SCAN | IDX_COC_SOURCE_PARENT_ID | 55682 | 815K| 875 (4)| 00:00:11 | -------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - filter("T"."SOURCE_OI_ID" IS NOT NULL AND INSTR(‘,‘||"T"."SOURCE_OI_ID"||‘,‘,‘1259941‘)>0) Statistics ---------------------------------------------------------- 1 recursive calls 12 db block gets 3228 consistent gets 0 physical reads 0 redo size 559 bytes sent via SQL*Net to client 524 bytes received via SQL*Net from client 2 SQL*Net roundtrips to/from client 0 sorts (memory) 0 sorts (disk) 1 rows processed
步骤2：
COUNT(1) ---------- 1 Elapsed: 00:00:00.01 Execution Plan ---------------------------------------------------------- Plan hash value: 2781911543 --------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | --------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 15 | 1 (0)| 00:00:01 | | 1 | SORT AGGREGATE | | 1 | 15 | | | |* 2 | TABLE ACCESS BY USER ROWID | CS_OI_CONFIRM_1 | 1 | 15 | 1 (0)| 00:00:01 | --------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - filter("T"."IS_DEL"=0) Statistics ---------------------------------------------------------- 1 recursive calls 0 db block gets 1 consistent gets 1 physical reads 0 redo size 526 bytes sent via SQL*Net to client 524 bytes received via SQL*Net from client 2 SQL*Net roundtrips to/from client 0 sorts (memory) 0 sorts (disk) 1 rows processed SQL> |
【源于本人笔记】 若有书写错误，表达错误，请指正...
原文：http://blog.itpub.net/28602568/viewspace-1378912/
内容总结
以上是互联网集市为您收集整理的Oracle 通过rowid秒优SQL全部内容，希望文章能够帮你解决Oracle 通过rowid秒优SQL所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。
来源：【匿名】