【MOS】Limitations of the Oracle Cost Based Optimizer (文档 ID 212809.1)

【MOS】Limitations of the Oracle Cost Based Optimizer (文档 ID 212809.1)



APPLIES TO:

Oracle Database - Personal Edition - Version 7.1.4.0 and later
Oracle Database - Enterprise Edition - Version 6.0.0.0 and later
Oracle Database - Standard Edition - Version 7.0.16.0 and later
Information in this document applies to any platform.

PURPOSE

This Document outlines some of the limitations that may be encountered when using the Cost Based Optimizer.

SCOPE

Cost Based Optimizer Limitations

The Cost Based Optimizer (CBO) uses a complex and comprehensive model to choose the plan with the lowest cost overall. In most cases the model picks the best access methods for accessing the data in the most efficient manner. However, even with computed statistics and column histograms it is possible for the Cost Based Optimizer to choose a sub-optimal plan. There are limitations to the Cost model that can affect queries in some circumstances. Some of these are listed and explained below:

DETAILS

  • Potential for incorrect estimation of intermediate result set cardinality

    Cardinality is the CBO estimate of the number of rows produced by a row source or combination of row sources. In some cases, the cardinality of result sets can be miscalculated. This is most common with complex predicates where the statistics do not accurately reflect the data or where predicate values are correlated. The following is an illustration of a statement featuring correlated predicates:

    >

         >   

     

      

     


  • <><> 

  •   

  •  

     

     

     

     

     

     
     
     

     

  •  


  • <> 

     

     

 
 
 
 

 
 
 
 

 



 

    

时间: 2024-11-06 07:24:13

【MOS】Limitations of the Oracle Cost Based Optimizer (文档 ID 212809.1)的相关文章

【MOS】TNSPING TNS-12543: TNS:destination host unreachable (文档 ID 1556918.1)

In this Document Symptoms Cause Solution APPLIES TO: Oracle Net Services - Version 11.2.0.3 and laterInformation in this document applies to any platform. SYMPTOMS When attempting to tnsping a remote server,  the following error occurs. ERROR -------

【MOS】EVENT: DROP_SEGMENTS - cleanup of TEMPORARY segments (文档 ID 47400.1)

[MOS]EVENT: DROP_SEGMENTS - Forcing cleanup of TEMPORARY segments (文档 ID 47400.1) ***Checked for relevance on 14-Jun-2012*** The DROP_SEGMENTS event ~~~~~~~~~~~~~~~~~~~~~~~ Available from 8.0 onwards. DESCRIPTION Finds all the temporary segments in a

【MOS】Top 5 Grid Infrastructure Startup Issues (文档 ID 1368382.1)

 Top 5 Grid Infrastructure Startup Issues (文档 ID 1368382.1) In this Document Purpose Scope Details   Issue #1: CRS-4639: Could not contact Oracle High Availability Services, ohasd.bin not running or ohasd.bin is running but no init.ohasd or other pro

【MOS】Troubleshooting &#039;enq: TX - index contention&#039; Waits (文档 ID 873243.1)

                                                                                                                                                                                                                                                          

【MOS】Top Ten Performance Mistakes Found in Oracle Systems. (文档 ID 858539.1)

In this Document Purpose Troubleshooting Steps References APPLIES TO: Oracle Database - Enterprise Edition - Version 9.2.0.8 and laterInformation in this document applies to any platform.RDBMS PURPOSE The purpose of this note is to inform reader abou

【MOS】中文文档列表 - Oracle Database (文档 ID 1533057.1)

中文文档列表 - Oracle Database (文档 ID 1533057.1) 类型: 状态: 上次主更新: 上次更新: ANNOUNCEMENT PUBLISHED 2017-2-23 2017-2-23     文档内容 详细信息 操作   Oracle 数据库技术支持通讯   安装/升级/降级/迁移相关     日常管理相关   性能相关     集群及存储相关   高可用相关   TimesTen 内存数据库 联系人 参考 适用于: Oracle Database - Enterp

Oracle诊断工具SQLT简介 (文档 ID 1677588.1、1526574.1)

Oracle诊断工具SQLT简介 (文档 ID 1677588.1.1526574.1) SQLT 使用指南 (文档 ID 1677588.1)   文档详细信息   类型: 状态: 上次主更新: 上次更新: 语言: REFERENCE PUBLISHED 2016-6-16 2016-6-16 English简体中文??? 215187.1SQLTXPLAIN (SQLT) 12.1.06 2014年1月30日 帮助诊断性能较差的 SQL 语句的工具 SQLT 概览 安全模式 安装 SQLT

【MOS】为何在查询中索引未被使用 (文档 ID 1549181.1、英文文档为67522.1)

为何在查询中索引未被使用 (文档 ID 1549181.1)   "为什么索引没有被使用"是一个涉及面较广的问题.有多种原因会导致索引不能被使用.首要的原因就是统计信息不准,第二原因就是索引的选择度不高,使用索引比使用全表扫描效率更差.还有一个比较常见的原因,就是对索引列进行了函数.算术运算或其他表达式等操作,或出现隐式类型转换,导致无法使用索引.还有很多其它原因会导致不能使用索引,这个问题在MOS(MOS即My Oracle Support)"文档1549181.1为何在查

【MOS】在不同版本和平台之间进行还原或复制 (文档 ID 1526162.1)--跨版本恢复

[MOS]关于在不同版本和平台之间进行还原或复制的常见问题 (文档 ID 1526162.1)--跨版本恢复 Questions and Answers    1) 我能用更高版本的 Oracle 还原或复制旧版本的数据库吗?    2) 我能在两个不同的补丁程序集之间进行还原或复制吗?    3) 我能在同一操作系统的不同版本之间进行还原或复制吗?    4) Oracle 的位(bit)级别(32 位或 64 位)不匹配时,可以进行还原或复制吗?    5) 可以将更高版本的备份还原到较早版