DB_BLOCK_CHECKSUM参数设置问题

[复制链接]
查看11 | 回复2 | 2005-10-30 17:05:33 | 显示全部楼层 |阅读模式
Oracle的文档上说,DB_BLOCK_CHECKSUM参数的可选值为(OFF,TYPICAL,FULL),但是我实际数据库里面是TRUE,这个是什么原因.
难道文档也有错误的吗?
你们的这个参数值又都是什么啊
回复

使用道具 举报

千问 | 2005-10-30 17:05:33 | 显示全部楼层
在10。2之前只有true和false两个值
10。2中For backward compatibility we preserve use of TRUE (implying TYPICAL) and FALSE (implying OFF) values.
回复

使用道具 举报

千问 | 2005-10-30 17:05:33 | 显示全部楼层
10gR2
Property Description
Parameter type String
Default value TYPICAL
Modifiable ALTER SYSTEM
Range of values OFF | TYPICAL | FULL
Basic No

DB_BLOCK_CHECKSUM determines whether DBWn and the direct loader will calculate a checksum (a number calculated from all the bytes stored in the block) and store it in the cache header of every data block when writing it to disk. Checksums are verified when a block is read - only if this parameter is TYPICAL or FULL and the last write of the block stored a checksum. In FULL mode, Oracle also verifies the checksum before a change application from update/delete statements and recomputes it after the change is applied. In addition, Oracle gives every log block a checksum before writing it to the current log.
If this parameter is set to OFF, DBWn calculates checksums only for the SYSTEM tablespace, but not for user tablespaces.
Checksums allow Oracle to detect corruption caused by underlying disks, storage systems, or I/O systems. If set to FULL, DB_BLOCK_CHECKSUM also catches in-memory corruptions and stops them from making it to the disk. Turning on this feature in TYPICAL mode causes only an additional 1% to 2% overhead. In the FULL mode it causes 4% to 5% overhead. Oracle recommends that you set DB_BLOCK_CHECKSUM to TYPICAL. For backward compatibility we preserve use of TRUE (implying TYPICAL) and FALSE (implying OFF) values.
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

主题

0

回帖

4882万

积分

论坛元老

Rank: 8Rank: 8

积分
48824836
热门排行