Hey gang;
I have an 8.0.5.0 database running on a Solaris platform.
The developer is running a simple query which returns the error
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 7, block # 191659)
ORA-01110: data file 7: '/u08/oradata/TTCT/dynamici01.dbf'
So I run
Kevin Lange wrote:
>
> Hey gang;
> I have an 8.0.5.0 database running on a Solaris platform.
>
> The developer is running a simple query which returns the error
>
> ERROR at line 1:
> ORA-01578: ORACLE data block corrupted (file # 7, block # 191659)
> ORA-01110: data file 7: '/u08/ora
Hi,
Find the corrupted object by the following statement:
Select segment_name, segment_type
from dba_extents
where file_id= and
between block_id and block_id + blocks -1
- If it's index, recreate it.
- If not, recover the datafile
- if no backup, tell us
regards...
Kevin Lange wrote:
> Hey
Typically 1578s are due to hardware hickups or a known bug. Dbverify
will not capture all types of data corruption. The only truly safe way
to capture physical corruption of a datablock is to get it into the
buffer cache with a statement that exercises the datablock.
The easiest way to determine
There is also a Pro*C and PL/SQL routine to
fix corrupted block problems if you do not have
backups.
Peace !
Mike
-Original Message-
Sent: Tuesday, May 28, 2002 1:14 PM
To: Multiple recipients of list ORACLE-L
Hi,
Find the corrupted object by the following statement:
Select segment
Hi,
very interesting. what is the URL for these utilities ?
"Johnson, Michael" wrote:
> There is also a Pro*C and PL/SQL routine to
> fix corrupted block problems if you do not have
> backups.
>
> Peace !
>
> Mike
>
> -Original Message-
> Sent: Tuesday, May 28, 2002 1:14 PM
> To: Multip
its on Metalink search on the error number or
on corrupted block.
-Original Message-
Sent: Wednesday, May 29, 2002 11:39 AM
To: Multiple recipients of list ORACLE-L
Hi,
very interesting. what is the URL for these utilities ?
"Johnson, Michael" wrote:
> There is also a Pro*C a
I really did not think you could recreate an object in the same tablespace
once corrupted blocks were found I was wrong. It was a group of 20
indexes.Rachel told me offline to just drop and recreate the indexes.
I did that and things worked just fine.
The only other time I had this pro
