Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Corrupted data blocks in tablespace SYSTEM

Re: Corrupted data blocks in tablespace SYSTEM

From: <Riyaj_Shamsudeen_at_i2.com>
Date: Mon, 03 Dec 2001 11:18:29 -0800
Message-ID: <F001.003D391E.20011203110027@fatcity.com>


Your error message indicates file #1 associated with the system tablespace and the trace file indicates the file #6. I would do the following
        1. Check the OS error message for any hardware errors.
        2. Find what objects are corrupted. To get this information use dba_extents and the given file and block#.Here is the script for the same:



accept  h_file_id  prompt  ' Enter file_id ==>' accept  h_block_id  prompt ' Enter block_id==>' set verify off
column owner format A10
column segment_name  format A20
column segment_type  format A10
column hdrfile    format 9999
column curfile    format 9999
column curblk     format 99999999
column hdrblock   format 99999999
select  owner, segment_name, segment_type, file_id,block_id from dba_extents where file_id = &&h_file_id and
      block_id <= &&h_block_id and
      block_id + blocks > &&h_block_id;

set verify on

        3. Since the errors are in two different files, check whether these files are in the same disk or controller..
        4. Decide the course of action depending upon the above outcome.. It is possible for the disk /controller to give back the bad data. If it is an hardware problem, correct the hardware problem and then try again.

Thanks
Riyaj "Re-yas" Shamsudeen
Certified Oracle DBA
i2 technologies   www.i2.com

Kevin Bass <kevinb_at_ameripeds.com>
Sent by: root_at_fatcity.com
12/03/01 11:50 AM
Please respond to ORACLE-L

       
        To:        Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
        cc:        
        Subject:        Corrupted data blocks in tablespace SYSTEM

I have just started a project and have encountered a database problem. The previous DBA did not create any backup scripts or backup and recovery plans. Is there a way to get around this problem without re-creating the database?
 
 

When executing my script to get corrupted data block information , I get the following: ORA-01578: ORACLE data block corrupted (file # 1, block # 2660) ORA-01110: data file 1: '/u02/oradata/TIE/system01.dbf'
 
 

Trace file information.
 

Dump file /u01/app/oracle/admin/TIE/udump/tie_ora_11859.trc Oracle8 Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production
ORACLE_HOME = /u01/app/oracle/product/8.0.5

System name:    SunOS
Node name:      edi-01
Release:        5.7
Version:        Generic_106541-17
Machine:        sun4u

Instance name: TIE
Redo thread mounted by this instance: 1
Oracle process number: 12
Unix process pid: 11859, image: oracleTIE
 

*** SESSION ID:(13.50289) 2001.11.30.15.00.00.000 ***
Corrupt block relative dba: 0x0180af98 file=6. blocknum=44952. Bad header found during buffer read
Data in bad block - type:0. format:0. rdba:0x00090255 last change scn:0x0000.3c07e0da seq:0x0 flg:0xb1 consistancy value in tail 0xffffffff
check value in block header: 0x10, check value not calculated spare1:0x0, spare2:0x0, spare2:0xd40
Reread of rdba=180af98 file=6. blocknum=44952. found same corupted data ***
Corrupt block relative dba: 0x0180af98 file=6. blocknum=44952. Bad header found during buffer read
Data in bad block - type:0. format:0. rdba:0x00090255 last change scn:0x0000.3c07e0da seq:0x0 flg:0xb1 consistancy value in tail 0xffffffff
check value in block header: 0x10, check value not calculated spare1:0x0, spare2:0x0, spare2:0xd40
Reread of rdba=180af98 file=6. blocknum=44952. found same corupted data ***
Corrupt block relative dba: 0x0180af98 file=6. blocknum=44952. Bad header found during buffer read
Data in bad block - type:0. format:0. rdba:0x00090255 last change scn:0x0000.3c07e0da seq:0x0 flg:0xb1 consistancy value in tail 0xffffffff
check value in block header: 0x10, check value not calculated spare1:0x0, spare2:0x0, spare2:0xd40
Reread of rdba=180af98 file=6. blocknum=44952. found same corupted data ***
Corrupt block relative dba: 0x0180af98 file=6. blocknum=44952. Bad header found during buffer read
Data in bad block - type:0. format:0. rdba:0x00090255 last change scn:0x0000.3c07e0da seq:0x0 flg:0xb1 consistancy value in tail 0xffffffff
check value in block header: 0x10, check value not calculated spare1:0x0, spare2:0x0, spare2:0xd40
Reread of rdba=180af98 file=6. blocknum=44952. found same corupted data ***  
Corrupt block relative dba: 0x0180af98 file=6. blocknum=44952. Bad header found during buffer read
Data in bad block - type:0. format:0. rdba:0x00090255 last change scn:0x0000.3c07e0da seq:0x0 flg:0xb1 consistancy value in tail 0xffffffff
check value in block header: 0x10, check value not calculated spare1:0x0, spare2:0x0, spare2:0xd40
Reread of rdba=180af98 file=6. blocknum=44952. found same corupted data
 
 

Kevin Received on Mon Dec 03 2001 - 13:18:29 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US