ORACLE-SQL优化案例.doc
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ORACLE SQL 优化 案例
- 资源描述:
-
一个哥们QQ问我,这个SQL怎么优化,它要跑160秒 view plaincopy to clipboardprint? 1. SQL> explain plan for select a.so_region_code so_region_code, 2. 2 a.so_county_code so_county_code, 3. 3 a.so_org_id so_org_id, 4. 4 d.org_type_id org_type_id, 5. 5 a.op_id op_id, 6. 6 nvl(c.brand, 0) brand, 7. 7 e.res_code, 8. 8 a.busi_code, 9. 9 a.so_nbr, 10. 10 decode(a.isnormal, 11. 11 2, 12. 12 -count(distinct a.so_nbr), 13. 13 0, 14. 14 count(distinct a.so_nbr), 15. 15 0) so_amount, 16. 16 sum(decode(b.book_item_id, 23000002, item_total, 0)) / 100 sim_fee, 17. 17 sum(decode(b.book_item_id, 23000001, item_total, 0)) / 100 sim_fee_add, 18. 18 sum(decode(b.book_item_id, 27000003, item_total, 0)) / 100 sim_fee_discount, 19. 19 sum(decode(b.book_item_id, 21000013, 0, b.item_total)) / 100 total_fee 20. 20 from zk.cm_busi_201108 a, 21. 21 zk.cm_busi_charge_201108 b, 22. 22 zk.cm_user c, 23. 23 xg.sys_organizations d, 24. 24 zy.res_sim e 25. 25 where a.so_nbr = b.so_nbr(+) 26. 26 and a.serv_id = c.serv_id 27. 27 and c.sim_id = e.sim_id 28. 28 and a.so_org_id = d.org_id 29. 29 and (b.book_item_id in (23000001, 23000002, 27000003) or 30. 30 a.busi_code in (1, 31. 31 2, 32. 32 4, 33. 33 5, 34. 34 8, 35. 35 11, 36. 36 14, 37. 37 15, 38. 38 17, 39. 39 18, 40. 40 19, 41. 41 21, 42. 42 24, 43. 43 25, 44. 44 28, 45. 45 99, 46. 46 101, 47. 47 104, 48. 48 105, 49. 49 201, 50. 50 204, 51. 51 205, 52. 52 206, 53. 53 2201, 54. 54 1023, 55. 55 1006, 56. 56 3312, 57. 57 2251)) 58. 58 and a.op_id != 71010264 59. 59 and a.so_date >= to_date('20110831000000', 'yyyymmddhh24miss') 60. 60 and a.so_date <= to_date('20110831235959', 'yyyymmddhh24miss') 61. 61 and a.so_county_code =7111 62. 62 and a.so_nbr is not null 63. 63 group by a.so_region_code, 64. 64 a.so_county_code, 65. 65 a.so_org_id, 66. 66 d.org_type_id, 67. 67 a.op_id, 68. 68 c.brand, 69. 69 e.res_code, 70. 70 a.busi_code, 71. 71 a.so_nbr, 72. 72 a.isnormal; 73. 74. 已解释。 75. 76. 已用时间: 00: 00: 00.03 77. SQL> 78. SQL> select * from table(dbms_xplan.display); 79. 80. PLAN_TABLE_OUTPUT 81. ---------------------------------------------------------------------------------------------------- 82. 83. ---------------------------------------------------------------------------------------------------- 84. | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Pstart| Pstop | 85. ---------------------------------------------------------------------------------------------------- 86. | 0 | SELECT STATEMENT | | 59 | 11741 | 1703 (1)| | | 87. | 1 | SORT GROUP BY | | 59 | 11741 | 1703 (1)| | | 88. |* 2 | FILTER | | | | | | | 89. |* 3 | HASH JOIN OUTER | | | | | | | 90. | 4 | TABLE ACCESS BY LOCAL INDEX ROWID | RES_SIM | 1 | 26 | 32 (4)| | | 91. | 5 | NESTED LOOPS | | 46 | 7820 | 1670 (1)| | | 92. | 6 | NESTED LOOPS | | 49 | 7056 | 146 (2)| | | 93. | 7 | NESTED LOOPS | | 46 | 5244 | 53 (2)| | | 94. |* 8 | TABLE ACCESS BY INDEX ROWID | CM_BUSI_201108 | 46 | 4784 | 7 (15)| | | 95. |* 9 | INDEX RANGE SCAN | DX_BUSI_SO_DATE_201108 | 166K| | 3 (34)| | | 96. | 10 | TABLE ACCESS BY INDEX ROWID | SYS_ORGANIZATIONS | 1 | 10 | 2 (50)| | | 97. |* 11 | INDEX UNIQUE SCAN | PK_SYS_ORGANIZATIONS | 1 | | | | | 98. | 12 | TABLE ACCESS BY GLOBAL INDEX ROWID| CM_USER | 1 | 30 | 3 (34)| ROWID | ROW L | 99. |* 13 | INDEX UNIQUE SCAN | PK_ZK_CM_USER | 1 | | 2 (50)| | | 100. | 14 | PARTITION RANGE ALL | | | | | 1 | 10 | 101. |* 15 | INDEX RANGE SCAN | IDX_SIM_SIM | 1 | | 31 (4)| 1 | 10 | 102. | 16 | TABLE ACCESS FULL | CM_BUSI_CHARGE_201108 | 474 | 13746 | 32 (4)| | | 103. ---------------------------------------------------------------------------------------------------- 104. 105. Predicate Information (identified by operation id): 106. --------------------------------------------------- 107. 108. 2 - filter("B"."BOOK_ITEM_ID"=23000001 OR "B"."BOOK_ITEM_ID"=23000002 OR "B"."BOOK_ITEM_ID"=27000 109. "A"."BUSI_CODE"=1 OR "A"."BUSI_CODE"=2 OR "A"."BUSI_CODE"=4 OR "A"."BUSI_CODE"=5 OR "A"."BUSI 110. "A"."BUSI_CODE"=11 OR "A"."BUSI_CODE"=14 OR "A"."BUSI_CODE"=15 OR "A"."BUSI_CODE"=17 OR "A"." 111. "A"."BUSI_CODE"=19 OR "A"."BUSI_CODE"=21 OR "A"."BUSI_CODE"=24 OR "A"."BUSI_CODE"=25 OR "A"." 112. "A"."BUSI_CODE"=99 OR "A"."BUSI_CODE"=101 OR "A"."BUSI_CODE"=104 OR "A"."BUSI_CODE"=105 OR "A 113. "A"."BUSI_CODE"=204 OR "A"."BUSI_CODE"=205 OR "A"."BUSI_CODE"=206 OR "A"."BUSI_CODE"=1006 OR 114. "A"."BUSI_CODE"=2201 OR "A"."BUSI_CODE"=2251 OR "A"."BUSI_CODE"=3312) 115. 3 - access("A"."SO_NBR"="B"."SO_NBR"(+)) 116. 8 - filter("A"."SO_COUNTY_CODE"=7111 AND "A"."OP_ID"<>71010264 AND "A"."SO_NBR" IS NOT NULL) 117. 9 - access("A"."SO_DATE">=TO_DATE(' 2011-08-31 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "A"."SO_D 118. 2011-08-31 23:59:59', 'syyyy-mm-dd hh24:mi:ss')) 119. 11 - access("A"."SO_ORG_ID"="D"."ORG_ID") 120. 13 - access("A"."SERV_ID"="C"."SERV_ID") 121. 15 - access("C"."SIM_ID"="E"."SIM_ID") 122. 123. 已选择40行。 124. 125. 已用时间: 00: 00: 00.20 CM_BUSI_201108 是大表,有3千多万的数据,CM_USER也是一个大表,有3千多万的数据 其他表都是小表 注意观察第9行,CBO认为它返回166k的数据,回表的时候又过滤有filter过滤,这个时候CBO认为它返回46行,先不管这46行 CBO计算是对是错,单单就是索引扫描返回166k到表 CM_BUSI_201108 去做166k次应该也很耗费时间。所以给出优化建议 对表CM_BUSI_201108进行分区,可以根据SO_DATE做range分区,另外SO_COUNTRY_CODE可以查看值多不多,如果不多可以做 range-list分区 他最终只做了range分区,并且让他创建了一个本地有前缀的组合索引(他最开始创建的是global索引,没有起到优化效果) create index YI_XXX ON CM_BUSI_201108(SO_DATE,SO_COUNTRY_CODE) LOCAL 执行计划如下: view plaincopy to clipboardprint? 1. -------------------------------------------------------------------------------------------------------------------------- 2. | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Pstart| Pstop | 3. -------------------------------------------------------------------------------------------------------------------------- 4. | 0 | SELECT STATEMENT | | 17 | 3264 | 635 (1)| | | 5. | 1 | TABLE ACCESS BY LOCAL INDEX ROWID | RES_SIM | 1 | 26 | 32 (4)| | | 6. | 2 | NESTED LOOPS | | 17 | 3264 | 635 (1)| | | 7. | 3 | NESTED LOOPS | | 18 | 2988 | 75 (2)| | | 8. |* 4 | FILTER | | | | | | | 9. | 5 | NESTED LOOPS OUTER | | | | | | | 10. | 6 | NESTED LOOPS | | 17 | 1870 | 24 (5)| | | 11. |* 7 | TABLE ACCESS BY LOCAL INDEX ROWID| CM_BUSI_201108 | 17 | 1700 | 7 (15)| 6 | 6 | 12. |* 8 | INDEX RANGE SCAN | YI_XXX | 61917 | | 3 (34)| 6 | 6 | 13. | 9 | TABLE ACCESS BY INDEX ROWID | SYS_ORGANIZATIONS | 1 | 10 | 2 (50)| | | 14. |* 10 | INDEX UNIQUE SCAN | PK_SYS_ORGANIZATIONS | 1 | | | | | 15. |* 11 | INDEX RANGE SCAN | PK_CM_BUSI_CHARGE_201108 | 1 | 26 | 2 (50)| | | 16. | 12 | TABLE ACCESS BY GLOBAL INDEX ROWID | CM_USER | 1 | 30 | 3 (34)| ROWID | ROW L | 17. |* 13 | INDEX UNIQUE SCAN | PK_ZK_CM_USER | 1 | | 2 (50)| | | 18. | 14 | PARTITION RANGE ALL | | | | | 1 | 10 | 19. |* 15 | INDEX RANGE SCAN | IDX_SIM_SIM | 1 | | 31 (4)| 1 | 10 | 20. -------------------------------------------------------------------------------------------------------------------------- 21. 22. Predicate Information (identified by operation id): 23. --------------------------------------------------- 24. 25. 4 - filter("B"."BOOK_ITEM_ID"=23000001 OR "B"."BOOK_ITEM_ID"=23000002 OR "B"."BOOK_ITEM_ID"=27000003) 26. 7 - filter("A"."OP_ID"<>71010264) 27. 8 - access("A"."SO_DATE">=TO_DATE(' 2011-08-31 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "A"."SO_COUNTY_CODE"=7111 AND 28. "A"."SO_DATE"<=TO_DATE(' 2011-08-31 23:59:59', 'syyyy-mm-dd hh24:mi:ss')) 29. filter("A"."SO_COUNTY_CODE"=7111) 30. 10 - access("A"."SO_ORG_ID"="D"."ORG_ID") 31. 11 - access("A"."SO_NBR"="B"."SO_NBR"(+)) 32. 13 - access("A"."SERV_ID"="C"."SERV_ID") 33. 15 - access("C"."SIM_ID"="E"."SIM_ID") 分区之后,需要过滤的数据量大大减少,这样嵌套循环执行的次数也大大减少,最终SQL能在4秒左右跑完,其实这个优化方案并不是最优的,由于不能连接到他的数据库,这个SQL的优化就暂时告一段落。分区对SQL的优化还是非常有帮助的。 帮网友调SQL 原SQL如下(要跑1个多小时): view plaincopy to clipboardprint? 1. SELECT * 2. FROM (SELECT A.INVOICE_ID, 3. A.VENDOR_ID, 4. A.INVOICE_NUM, 5. A.INVOICE_AMOUNT, 6. A.GL_DATE, 7. A.INVOICE_CURRENCY_CODE, 8. SUM(NVL(B.PREPAY_AMOUNT_APPLIED, 0)) PAID_AMOUNT, 9. A.INVOICE_AMOUNT - SUM(NVL(B.PREPAY_AMOUNT_APPLIED, 0)) REMAIN 10. FROM ap.AP_INVOICES_ALL A, APPS.AP_UNAPPLY_PREPAYS_V B 11. WHERE A.INVOICE_ID = B.INVOICE_ID(+) 12. AND A.ORG_ID = 126 /*:B4*/ 13. AND A.SOURCE = 'OSM IMPORTED' /*:B3*/ 14. AND A.INVOICE_NUM BETWEEN NVL( /*:B2*/ null, A.INVOICE_NUM) AND 15. NVL( /*:B1*/ null, A.INVOICE_NUM) 16. GROUP BY A.INVOICE_ID, 17. A.INVOICE_NUM, 18. A.INVOICE_AMOUNT, 19. A.VENDOR_ID, 20. A.GL_DATE, 21. A.INVOICE_CURRENCY_CODE) 22. WHERE REMAIN > 0 ; B是一个视图,定义如下: view plaincopy to clipboardprint? 1. CREATE OR REPLACE VIEW APPS.AP_UNAPPLY_PREPAYS_V AS 2. SELECT AID1.ROWID ROW_ID, 3. AID1.INVOICE_ID INVOICE_ID, 4. AID1.INVOICE_DISTRIBUTION_ID INVOICE_DISTRIBUTION_ID, 5. AID1.PREPAY_DISTRIBUTION_ID PREPAY_DISTRIBUTION_ID, 6. AID1.DISTRIBUTION_LINE_NUMBER PREPAY_DIST_NUMBER, 7. (-1) * AID1.AMOUNT PREPAY_AMOUNT_APPLIED, 8. nvl(AID2.PREPAY_AMOUNT_REMAINING, AID2.AMOUNT) PREPAY_AMOUNT_REMAINING, 9. AID1.DIST_CODE_COMBINATION_ID DIST_CODE_COMBINATION_ID, 10. AID1.ACCOUNTING_DATE ACCOUNTING_DATE, 11. AID1.PERIOD_NAME PERIOD_NAME, 12. AID1.SET_OF_BOOKS_ID SET_OF_BOOKS_ID, 13. AID1.DESCRIPTION DESCRIPTION, 14. AID1.PO_DISTRIBUTION_ID PO_DISTRIBUTION_ID, 15. AID1.RCV_TRANSACTION_ID RCV_TRANSACTION_ID, 16. AID1.ORG_ID ORG_ID, 17. AI.INVOICE_NUM PREPAY_NUMBER, 18. AI.VENDOR_ID VENDOR_ID, 19. AI.VENDOR_SITE_ID VENDOR_SITE_ID, 20. ATC.TAX_ID TAX_ID, 21. ATC.NAME TAX_CODE, 22. PH.SEGMENT1 PO_NUMBER, 23. PV.VENDOR_NAME VENDOR_NAME, 24. PV.SEGMENT1 VENDOR_NUMBER, 25. PVS.VENDOR_SITE_CODE VENDOR_SITE_CODE, 26. RSH.RECEIPT_NUM RECEIPT_NUMBER 27. FROM AP_INVOICES AI, 28. AP_INVOICE_DISTRIBUTIONS AID1, 29. AP_INVOICE_DISTRIBUTIONS AID2, 30. AP_TAX_CODES ATC, 31. PO_VENDORS PV, 32. PO_VENDOR_SITES PVS, 33. PO_DISTRIB展开阅读全文
咨信网温馨提示:1、咨信平台为文档C2C交易模式,即用户上传的文档直接被用户下载,收益归上传人(含作者)所有;本站仅是提供信息存储空间和展示预览,仅对用户上传内容的表现方式做保护处理,对上载内容不做任何修改或编辑。所展示的作品文档包括内容和图片全部来源于网络用户和作者上传投稿,我们不确定上传用户享有完全著作权,根据《信息网络传播权保护条例》,如果侵犯了您的版权、权益或隐私,请联系我们,核实后会尽快下架及时删除,并可随时和客服了解处理情况,尊重保护知识产权我们共同努力。
2、文档的总页数、文档格式和文档大小以系统显示为准(内容中显示的页数不一定正确),网站客服只以系统显示的页数、文件格式、文档大小作为仲裁依据,个别因单元格分列造成显示页码不一将协商解决,平台无法对文档的真实性、完整性、权威性、准确性、专业性及其观点立场做任何保证或承诺,下载前须认真查看,确认无误后再购买,务必慎重购买;若有违法违纪将进行移交司法处理,若涉侵权平台将进行基本处罚并下架。
3、本站所有内容均由用户上传,付费前请自行鉴别,如您付费,意味着您已接受本站规则且自行承担风险,本站不进行额外附加服务,虚拟产品一经售出概不退款(未进行购买下载可退充值款),文档一经付费(服务费)、不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
4、如你看到网页展示的文档有www.zixin.com.cn水印,是因预览和防盗链等技术需要对页面进行转换压缩成图而已,我们并不对上传的文档进行任何编辑或修改,文档下载后都不会有水印标识(原文档上传前个别存留的除外),下载后原文更清晰;试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓;PPT和DOC文档可被视为“模板”,允许上传人保留章节、目录结构的情况下删减部份的内容;PDF文档不管是原文档转换或图片扫描而得,本站不作要求视为允许,下载前可先查看【教您几个在下载文档中可以更好的避免被坑】。
5、本文档所展示的图片、画像、字体、音乐的版权可能需版权方额外授权,请谨慎使用;网站提供的党政主题相关内容(国旗、国徽、党徽--等)目的在于配合国家政策宣传,仅限个人学习分享使用,禁止用于任何广告和商用目的。
6、文档遇到问题,请及时联系平台进行协调解决,联系【微信客服】、【QQ客服】,若有其他问题请点击或扫码反馈【服务填表】;文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“【版权申诉】”,意见反馈和侵权处理邮箱:1219186828@qq.com;也可以拔打客服电话:0574-28810668;投诉电话:18658249818。




ORACLE-SQL优化案例.doc



实名认证













自信AI助手
















微信客服
客服QQ
发送邮件
意见反馈



链接地址:https://www.zixin.com.cn/doc/5916246.html