BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

   
Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





   

 

 

 

Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation

 

 


 

 

 

 

 
 

Oracle Buffer Hit Ratio

Oracle Tips by Burleson Consulting

2007 Update:  Since the days of Oracle7 when Oracle Corporation recommended keeping the buffer cache hit ratio above a fixed threshold, research has show some important facts. 

Please read: Is the Oracle buffer hit ratio a useless metric for monitoring and tuning?


Don't be fooled by the buffer hit ratio

Many Oracle professionals misunderstand the data buffer hit ratio and claim that the data buffer hit ratio is a meaningless metric because:

  • They can re-run queries (increasing buffer gets) and adjust the metric at-will.
     

  • The Data Buffer Hit Ratio is meaningless for systems that do not frequently re-read data blocks

In reality, the Oracle data buffer hit ratio is a measure of the propensity of any given data block to be in the buffer upon re-read.

Physical disk reads are 100x slower than buffer fetches, and the data buffer hit ratio is very valuable, especially when monitoring the KEEP pool with should always have a buffer hit ratio of 100% (it's up to the Remote DBA to anticipate the growth of segments in the KEEP pool). 

See:

Monitoring the data buffer efficiency is a critical Oracle tuning task, and don't be fooled by beginners who claim that the data buffer hit ratio is meaningless simply because it does not apply in all cases.

Of course, if your database does not re-read data frequently (i.e. DSS applications) then the data buffer hit ratio is not meaningful, but that does not mean that the data buffer hit ratio is not extremely valuable as a measure of the effectiveness of any of Oracle's seven data buffers. 

The data buffer hit ratio is also incorporated into the Oracle 10g automatic memory manager (AMM) whereby Oracle detects a too-small data buffer and adjusts the data buffer region size.

The data buffer hit ratio is also incorporated into Oracle's standard buffer cache advisory utility (v$db_cache_advice).

See these related notes on tuning the data buffer cache:

 

 



Expert Remote DBA

BC is America's oldest and largest Remote DBA Oracle support provider.  Get real Remote DBA experts, call
BC Remote DBA today.

 

 

Remote DBA Service
 

Oracle Tuning Book

 

Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software

 

 

 

 

 

 

BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.



Hit Counter