Chinaunix首页 | 论坛 | 博客
  • 博客访问: 924641
  • 博文数量: 358
  • 博客积分: 8185
  • 博客等级: 中将
  • 技术积分: 3751
  • 用 户 组: 普通用户
  • 注册时间: 2008-10-15 16:27
个人简介

The views and opinions expressed all for my own,only for study and test, not reflect the views of Any Company and its affiliates.

文章分类

全部博文(358)

文章存档

2012年(8)

2011年(18)

2010年(50)

2009年(218)

2008年(64)

我的朋友

分类: Oracle

2009-12-24 21:49:35

Tips_30 Detecting and Recovering from Database Corruption 

■Parameters Relating to Block Corruption
•DB_BLOCK_CHECKSUM(校验和):defaults to TRUE,will help detect damage introduced by the disk or I/O systems.
 Even when this parameter is on false,checksumming is still enabled for the SYSTEM tablespace.
Whenever the DBWn process writes a block to disk it will compute a checksum for the block and include it in the block header. 
When a server process reads a block, if the checksum is present it will recalculate it and compare. 
This will mean that any damage occurring in the time between the DBWn writing the block and its being read back will be detected.

•DB_BLOCK_CHECKING:defaults to FALSE,will help detect damage introduced by faulty memory.
When set to TRUE, the Oracle processes will check the block for consistency every time the buffer containing the block is accessed. 
This will mean that if corruptions are occurring in memory, they will be detected immediately, but the price is high—perhaps as much as 10 percent of processing capacity

***
Checksumming and block checking are always enabled for the SYSTEM tablespace, no matter to what these parameters are set.
***
Oracle Corporation advises leaving both these parameters on default,unless instructed otherwise by Oracle Support.

阅读(996) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~