One quick way to check is to fill up those blocks with dummy data and then
do the dbv. I would not hestitate to export your data, a logical backup never
hurts. Use direct=y on the export to speed up the process and/or use
a pipe to compress the file to save space depending on your resource
constraints....
Mark Powell <Mark.Powell_at_eds.com> wrote in article <01bdec79$2fff4b60$a12c6394_at_J00679271.ddc.eds.com>...
> I do not think that you need to worry about blocks within free,
> unallocated, extents showing as corrupted because when Oracle allocates an
> extent to a table or index every block in the extent is re-formatted for
> that object. Until being reallocated I believe that free extent blocks
> contain whatever garbage used to be in them.
>
> broder_at_my-dejanews.com wrote in article
> <6uta9n$a2r$1_at_nnrp1.dejanews.com>...
> > I have repaired some database corruptions - however dbv still shows
> > some file corruptions even though the blocks with the file are marked
> > as free space. We are worried that Oracle might try to reuse these
> > free blocks and end up corrupting another table. We plan to try and
> > reduce the chances of this happening by using up the free block around
> > the corrupted block by dummy tables - the alternative would be a
> > lengthy export/import of the affected tablespaces.
> >
> > Any ideas ??
> >
> > Cheers !
> >
> > -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> > http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
> >
>
Received on Wed Sep 30 1998 - 20:29:04 CDT
