Re: Corruption with active duplication

I swear, you guys are Brilliant!

On Fri, Nov 9, 2018 at 2:33 AM Sokolowski Remigiusz < Remigiusz.Sokolowski_at_nordea.com> wrote:

> There is an article on that on Metalink:
>
> Corrupt block relative dba message in the Alert Log - Definition and
> Solution (Doc ID 1950383.1)
>
>
>
> *From:* oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> *On
> Behalf Of *Mladen Gogala
> *Sent:* Friday, November 09, 2018 3:17 AM
> *To:* oracle-l <oracle-l_at_freelists.org>
> *Subject:* Corruption with active duplication
>
>
>
> Hi!
>
> I am doing an active duplication of one test database to another one, for
> another group of developers. Here is what I am getting:
>
> consistency value in tail: 0x00000001
> check value in block header: 0xb601
> computed block checksum: 0x0
> Reading datafile '/U02/oradata/test2a/data21.dbf' for corruption at rdba:
> 0x11000001 (file 68, block 1)
> Reread (file 68, block 1) found same corrupt data (no logical check)
> Hex dump of (file 69, block 1) in trace file
> /app01/oracle/diag/rdbms/test2a/test2/trace/test2_ora_25016.trc
> Corrupt block relative dba: 0x11400001 (file 69, block 1)
>
> It probably means that the source database is corrupt, yet there is
> nothing in the alert log. I will do backup validate logical, but this will
> take some time, since it's a database over 2TB. Does anyone have any idea
> how to establish whether the source DB is corrupt faster than using backup
> validate?
>
> --
>
> Mladen Gogala
>
> Database Consultant
>
> Tel: (347) 321-1217
>
>

--
http://www.freelists.org/webpage/oracle-l