Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Self-Healing ORA-01578's
Hi Singer, Phillip , once it happened
1) when there was problems in someplace in the hardware (maybe memory or cpu
I don't know) in the server happened something similar(they replaced that
server) and all was ok .
2) after running checkdisk in windows, block corruption fixed.
Juan Carlos Reyes Pacheco
OCP
Database 9.2 Standard Edition
----- Original Message -----
From: "Singer, Phillip (P.W.)" <psinger1_at_ford.com>
To: <oracle-l_at_freelists.org>
Sent: Monday, April 19, 2004 12:49 PM
Subject: Self-Healing ORA-01578's
This actually happened to me Saturday Night:
Running my 4-way Linux box (4.21 Kernel) with 9.2.0 (and using a SAN for my disks) I discovered a ORA-01578. After several hours of work with Oracle support, running dbverify, and creating test queries, we determined that there really was block corruption.
We used dbms_repair to get everything but the bad block, and were getting ready to see what would happen on a tablespace recovery, when the backup group decided to stop the instance to do a cold backup (I work for a large organization, with every task subdivided, with little communication).
When the instance came back up the block corruption was gone. This is the one part of the whole affair that I find incredible. Does someone have an idea as to how bouncing an instance can fix block corruption which was proven by dbverivy?
![]() |
![]() |