Re: Block Corruption, cant start DB -SOS

> There's no such thing as an incomplete crash recovery. Instance recoveries
> are, by definition, complete. If you want an incomplete recovery, you are
> required to restore all datafiles from a backup and roll them all forward to
> a point of your choosing. Since you've restored all datafiles, we're talking
> media recovery, not crash recovery.
>
> Without restoring all datafiles, your idea of rolling partway forward
> through the online logs would result in an inconsistent database, since some
> datafiles would be at different SCNs from others.

Could you tell me the difference between restore datafile and do not restore any datfile and perform an incomplete recovery? I cant see any, all datafiles header in both cases will have the smae SCN and they will be consistent.

scenario 1
Restore all datafiles with scn #100
start instance, mount the database
Recover the database thru ArchiveRedo. The scn for all datafiles is #150 The recover continue with online redologs until scn specified #153 Open the database with resetlogs

scenario 2
You got an instance crash
open and mount the database.
you query v$datafile to get the minumum #scn across all database files and discover it is #152
so you start an incomplete recovery until scn #153 all the datafiles will be with scn #153
Open the database with resetlogs

do i missing something (except the scn in control files that i havent taken in account for semplicity?)

You forgot even TableSpace Point-in-time recovery where you can perform an incomplete recovery of just a tablespace not the database, even it is a mess. Received on Fri Sep 20 2002 - 07:09:04 CDT