Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 
 

Undocumented parms for using CPU-based SQL optimization

Oracle Tips by Burleson Consulting


 

Many Oracle professionals are under the mistaken impression that their optimizer is calculating optimal execution plans based on CVPU, when in reality it is being computed based on I/O costs.

 

Back in the 1990?s when 32-bit technology limited the size of the data buffer caches most Oracle databases were constrained by physical I/O (?db file sequential reads? and ?db file scattered reads?) and Oracle SQL for OLTP databases (the first_rows optimizer mode) was built to make optimal execution plan decisions based on minimizing disk reads.

 

Today the advent of 64-bit technology and cheaper RAM resources that shifted this bottleneck and many instances are now CPU-bound.  Oracle has recognized this shift and implemented CPU-based costing in Oracle 10g, but it is tricky.

 

For Oracle and 10g database the CBO has been set to create execution plans based on CPU costs. (See MOSC Note 153761.1 for details on collecting system statistics and the process to turn on CPU costing. Note that according to Bug 2820066, CPU cost is always computed regardless of optimizer mode when optimizer_index_cost_adj is set in Oracle versions less than 10.1.0.2.

 

However, CPU costing is not used unless the undocumented parameter "_optimizer_cost_model" is set to "cpu" for example: alter session set "_optimizer_cost_model"=cpu; This parameter defaults to CHOOSE. 

The Ion tool is the easiest way to analyze STATSPACK disk I/O data in Oracle and Ion allows you to spot hidden I/O trends.

 

 

 

If you like Oracle tuning, you may enjoy the new book "Oracle Tuning: The Definitive Reference", over 900 pages of BC's favorite tuning tips & scripts. 

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.


 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational