数据库常见的块错误和处理.PDF

数据库常见的块错误和处理 Lunar QQ: 5163721 9-1 以下内容仅限于在非生产环境测试， 不能用于生产环境数据库，所有 Internal的方法（BBED, DUL等等）， 请咨询Oracle Support部门，这些方 法未经Oracle Support建议和许可， 不能使用，否则后果自负！！ 9-2 常见错误 9-3 9-4 9-5 Physical and Logical Block Corruptions Physical Block Corruptions This kind of block corruptions are normally reported by Oracle with error ORA-1578 and the detailed corruption description is printed in the alert log. Corruption Examples are: • Bad header - the beginning of the block (cache header) is corrupt with invalid values • The block is Fractured/Incomplete - header and footer of the block do not match • The block checksum is invalid • The block is misplaced • Zeroed out blocks A block that is PHYSICAL corrupt is also called Media Corrupt Block. A Media Corrupt block is not a Soft Corrupt block. 9-6 OS Block Header • The OS Block Header is in the first datafile block. It is used by Oracle to store Operating System information. • It is the Block Zero. It is not the datafile header which is in Oracle Block 1. • Corruption in Block Zero will not cause damage to the data and in versions lower than 11g it is not detected by dbverify/rman. In 11g Dbverify has been enhanced to detect it. • dbfsize can be used to check the consistency of Block 0. • When this block is corrupted the database may be opened with no errors. Block 0 is checked by some specific database operations like CREATE CONTROLFILE or during upgrade to 11g. • ORA-1503: CREATE CONTROLFILE failed ORA-1565: error in identifying file /oradata/lunar.dbf ORA-27047: unable to read the header block of file HP-UX Error: 22: Invalid argument Additional information: