Re: Archive logs causing data block corruption !!??

I think you should eliminate the possibility of datafile corruption ... run dbverify (dbv) over that datafile and see what happens.

Best regards ,

Eduardo Tavares

"TunaFish" <btaneja_at_hotmail.com> wrote in message news:26e84054.0208270843.311b4498_at_posting.google.com...
> - rebuilt a standby database from cold backup of production
> - applied 2 days worth of archive logs to bring database upto date
> - every thing went smooth
> - opened the database ok with resetlogs
> - on running 'select count(*) from ..' all tables; turned out 3 of 315
> tables
> sitting on a datafile had corrupted data blocks
>
> - started over; by this time bringing up the database from the same
> backup with
> reset logs; but did not apply the archive logs this time;
> - database came up fine; the 3 tables in question were A-ok as well;
>
>
> - started over again; restored database from same backup;
> - applied about first half of archive logs;
> - the same 3 tables were corrupted
>
>
>
> - started over again; restored database from same backup;
> - applied only the first (1) archive log;
> - the same 3 table were A-ok
>
>
> Anyone know what gives?
> Funne part is while applying archive logs there is no error; every
> thing goes smooth; database comes up fine; only while doing count(*)
> on these 3 table out of the thousand odd tables i get data block
> corruption error..
>
>
> Database opened.
> SVRMGR> select 'GS.SYR00908_POSBHD_TMP', count(*) from
> GS.SYR00908_POSBHD_TMP
> 2> ;
> 'GS.SYR00908_POSBHD_TM COUNT(*)
> ---------------------- ----------
> ORA-01578: ORACLE data block corrupted (file # 912, block # 57543)
> ORA-01110: data file 57: '/dbfprd1/p27/userb5'
>
> thanks!
> Bruce
>
Received on Wed Aug 28 2002 - 08:03:10 CDT