How to Detect Corrupt Blocks Errors in Database Alert Log (No ORA-error associated with it) (Doc ID 1092464.1)

Last updated on DECEMBER 23, 2013

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.2 and later
Information in this document applies to any platform.
Checked for relevance on 23-Dec-2013

Goal

How to detect non-ORA-* error message in 10gR2 alert log ( like "Corrupt block" in the below example):

Fri Feb 5 15:55:00 2010
Page 48 is marked corrupt
Corrupt block relative dba: 0x76c00030 (file 433658331, block 48)
Bad header found during dbv:
Data in bad block:
type: 255 format: 2 rdba: 0x07786d0b
last change scn: 0x0778.1110080e seq: 0x6d flg: 0x0b
spare1: 0xc1 spare2: 0x2 spare3: 0x80e
consistency value in tail: 0x10151f07
check value in block header: 0x1110
block checksum disabled

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms