How to repair of ignore corrupted blocks in oracle in noarchivelog mood

There is the DBMS_REPAIR package.  However, I highly recommend only using that under the direction of Oracle Support.

Hi,

thanks for the help but I dont have oracle support where I work they don't have any support from metalink... and I checked it further and I see this shows in partition only ... if I delete the data of partition table and reload that will that fix this issue?

select * from v$database_block_corruption

file | block# | blocks | corruption_change# | corruption_type |cond_id
10 | 1 | 19007437| 0 | fractured | 0

Select allOpen in new window

when I select the block from dba_extents then I see

segment_name | segment_type | block_id
tablename | partitionname | 19007437

Based on the reason for the corruption, I would say that reloading it should get around the issue.  A fractured block should be a soft error, and not a hardware problem.  If it is a disk block issue, it could come back when the block is reused.

A fractured block is curious if  you are in noarchive mode.  That would seem like someone attempted a restore at some point.  I would definitely recommend running dbverify to see if there are other issues.  The documentation for that is here -> http://docs.oracle.com/cd/B28359_01/server.111/b28319/dbverify.htm#g1010035

I also highly recommend having a supported system.  Running any kind of production system that is unsupported is just a recipe for disaster.

Hi, thanks for the replay... no I was not the in archive log mood and I found out when this happen but immediately I turn the on the archive log mood..

what happen was without no reason the database listener was not responding so what I did I restarted the  the services of listner and database from services.msc and immediately after that I didnt' check what was the issue but when I come back in the morning I run query it gives me this error....

and I run

RMAN> validate check logical database;

after 2 hours time it showed only one data files corrupted rest it didn't' show any corruption ...

if I drop and reload the 09th data only which is in the 09 partition will that solve this issue what could be the percentage ... as I think I will spend more time in troubleshooting than reloading which takes only 1 hours + time

regards

An instance crash like that will not cause a fractured block.  On the way back up, an in doubt transactions would be rolled back.  It is part of instance recovery that happens automatically without you doing anything.

Restores of fuzzy backups and complete failures of disk array cache are usually the causes of fractured blocks.  Or you could have hit a bug with your disk array, controller or the database itself.

Reloading should correct the situation, but I still highly recommend running as many verifications as you can.  You don't want to find another problem later.

Hi,

I run dbverfiy on the same datafile that gives damaged block and I get following result which I guess means only one block have issue and I think it's save to delete data of that day which reside in the partition?

Total Pages Examined         : 78643200
Total Pages Processed (Data) : 47679009
Total Pages Failing   (Data) : 1
Total Pages Processed (Index): 0
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 220667
Total Pages Processed (Seg)  : 0
Total Pages Failing   (Seg)  : 0
Total Pages Empty            : 30743524
Total Pages Marked Corrupt   : 1
Total Pages Influx           : 0
Total Pages Encrypted        : 0
Highest block SCN            : 83024023 (0.83024023)

Select allOpen in new window

reagards

Yes, I would reload that data as I said.  But, you really should run verifications on all the files.

Hi, thanks for replay... I did check all but every way I check like from RMAN, from v$ tables and also from this disk verify utility it all shows this.. but

- should I drop the partition
alter table tablename drop partition paritionname

- or just truncate the data

which one you think would be good idea?

Hi,

thanks I have truncate the parition, reload the data analyze the table and all is going well so far... hope everything will go well now...

I have run the database in archivelog mood since this happen any other suggestion to avoid these issue latter?

Archivelog mode would not have prevented this from happening.  It may have sped up the recovery, but it would not have prevented it.  Archivelog mode may not have helped the recovery either.  Depends on when the corruption happened and how many backups you have.  Archivelog mode may not have been helpful at all.

Having no idea how it happened, it is difficult to prevent from happening again.