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 


 

 

 


 

 

 
 
 

db_block_checking tips

Oracle Database Tips by Donald BurlesonJune 15, 2015


The db_block_checking parameter is used to performs block checks for all data blocks making sure that all data in the block is consistent.  The default for db_block_checking is false, because db_block_checking imposes an additional system overhead.

This db_block_checking parameter is used primarily in diagnosing disk I/O issues in system where replicated blocks show corruption.  checks data block integrity before writing the data block to disk.  In this involves checking the internal block headers and footer, plus internal row linkages.

Block checking provides early detection of block corruption, however, it costs between 1-10% in overhead on the database.  The more DML and block writes that occur on a system (INSERT, UPDATE, DELETE), the more costly db_block_checking becomes.

WARNING:  While the Oracle documentation says that db_block_checking=true only adds a 1 to 10% overhead depending on concurrency of DML, we have seen cases where db_block_checking=true made the updates run 6x slower. 

Any errors encountered by block checking result in an ORA-600 level message in the alert log.  Before setting the db_block_checking parameter to TRUE, first execute the database verify (dbv) utility against the datafiles to make sure they are free of corruption.   Even when db_block_checking=false, Oracle still provides block checking for the system tablespace.

Note that the db_block_checking parameter can be changed with an alter system command:

alter system set db_block_checking=true scope=both;

For additional information on handling corruption, see the BC expert notes on corruption and see MOSC Note 1088018.1 - Handling Oracle Database Corruption Issues.

Also see related pages:

- db_block_checksum tips


- db_ultra_safe Tips


 

 

��  
 
 
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 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.