Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE:
> >1. block checking (inline). don't need to run dbv.
> OK. This makes sense. Although the risk is
> probably small - how many times have we
> experienced corrupted blocks?
more than once, due to bad hardware/drivers. wanna see it in the log as soon as it happens. in these days of quarterly sarbanes-oxley driven backup/restore/recover checks, this is a way of having a paper trail against some forms of corruption.
> >2. doesn't backup blocks that have not been written
> to.
>
> Grudgingly ok. I would keep the free space small
> for any database that I am
> not running in archivelog mode.
> I would *never* run
> a prod db in noarchivelog mode.
agreed. won't/don't have any.
think database where developers are trying out
different designs and using lots of space, re-running
test loads. not even the real dev db.
> >3. operation is in the controlfile (or rman
> catalog).
> I guess.
> >4. not platform-specific.
> *Everything* is platform specific.
> I guess is comes down to personal preference. I
> don't think I'd put myself
> in the position to allow this to happen.
> I'd argue like hell against it!
> Have a good weekend!
thanks. sure hope so, could use one.
Pd
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Fri Jun 04 2004 - 13:53:29 CDT