Abstract
In order to tune index usage, it is important to understand the various types of index access paths available to the cost optimizer. The chapter summarizes the most important index access paths available to the optimizer. Often, Oracle database administrators are bewildered when the optimizer chooses not to use what they believe is a very useful index but does a full table scan instead. This chapter devotes attention to exploring some reasons why the optimizer might prefer a full table scan to using an index. You’ll also learn how to force the optimizer to use (or not to use) an index. Oracle provides a large number of index-related hints to enable you to control the behavior of the optimizer regarding index usage. You’ll find descriptions of the key index-related hints in this chapter.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
