nomerge可解决访问数据字典效率低（Nomerge can solve the access data dictionary inefficient）.docVIP

下载本文档

11
0
约5.64千字
约 13页
2017-08-31 发布于河南
举报
版权申诉

nomerge可解决访问数据字典效率低（Nomerge can solve the access data dictionary inefficient）.doc

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

nomerge可解决访问数据字典效率低（Nomerge can solve the access data dictionary inefficient）

nomerge可解决访问数据字典效率低（Nomerge can solve the access data dictionary inefficient） NO merge solves the problem of inefficient access to data dictionaries The data dictionary view database access is generally more quickly, because the Oracle has made a special optimization work, but in some cases, several data dictionary are associated, CBO is not so smart, sometimes some inefficient execution plan. For example, when trying to construct a large table, you want to construct the Cartesian product of DBA_OBJECTS and another table with a small amount of data, DBA_SEQUENCES: [oracle@localhost sqlplus test/test ~]$ SQL*Plus: Release 9.2.0.4.0 - Production on Thursday, June 4, 16:39:58 2009 Copyright (c) 1982, 2002, Oracle, Corporation., All, rights, reserved. Connect to: Oracle9i, Enterprise, Edition, Release, 9.2.0.4.0 - Production With, the, Partitioning, OLAP, and, Oracle, Data, Mining, options JServer Release 9.2.0.4.0 - Production SQL SET PAGES 100 LINES 128 SQL, COL, PLAN_PLUS_EXP, FORMAT, A115 SQL SET TIMING ON SQL, SELECT, COUNT (*), FROM, DBA_SEQUENCES, DBA_OBJECTS; COUNT (*) Dear sirsre Four million five hundred and eighty-five thousand two hundred and seventy-six Time taken: 00: 31: 19.33 The query has been running for half an hour. SQL, SELECT, COUNT (*) FROM, DBA_SEQUENCES; COUNT (*) Dear sirsre One hundred and forty-six Time taken: 00: 00: 0.08 SQL, SELECT, COUNT (*) FROM, DBA_OBJECTS; COUNT (*) Dear sirsre Thirty-one thousand four hundred and six Time taken: 00: 00: 0.08 The amount of data in the two view is not very large. The Cartesian product is no more than about four million. How can it be executed for so long?: SQL EXPLAIN PLAN FOR 2, SELECT, COUNT (*), FROM, DBA_SEQUENCES, DBA_OBJECTS; Already explained. Time taken: 00: 00: 0 SQL SELECT * FROM TABLE (DBMS_XPLAN.DISPLAY); PLAN_TABLE_OUTPUT Id Operation Name | | | | Rows | Bytes | Cost | | 0 | SELECT STATEMENT | | | | | | 1 | SORT AGGREGATE | | | | | | 2 | NESTED LOOPS | | | | | | 3 | NESTED LOOPS | | | | |