Actually, I don't think we disagree!

I didn't say it is impossible. I said that it is NOT what one might think
from the name (e.g. the ability to recover a given tablespace to a different
point in time than the rest of the database). You have to perform the
point-in-time recovery in another database, then move the data to the
original. A clone from prior to the recovery point objective would work. A
"clone" from after the recovery point objective would not, for the same
reason that it won't work in the original database.

Don Granaman
[OraSaurus]

----- Original Message -----
From: "Ruth Gramolini" <[Email Address Removed] "LazyDBA.com Discussion" <[Email Address Removed] Sunday, December 29, 2002 1:55 PM
Subject: Re: Point in time.


> Don,
> I hate to contradict you but the ability to do a tablespace point-in-time
> recovery is one of the best things about rman. You do have to restore the
> tablespace to a clone database and export and import but it is definitely
> possible.
>
> Regards,
> Ruth
> ----- Original Message -----
> From: "Don Granaman" <[Email Address Removed] To: "LazyDBA.com Discussion" <[Email Address Removed] Sent: Friday, April 26, 2002 12:32 PM
> Subject: Re: Point in time.
>
>
> > Time-based recovery must be done at the database level, not the
tablespace
> > or datafile level, so the syntax of your command is invalid! That is
why
> > you got that particular error message - "UNTIL" is not possible with
> > "RECOVER TABLESPACE..." or "RECOVER DATAFILE...".
> >
> > Verbatim from the 8i Backup & Recovery Guide:
> > "Restore backups of all the datafiles of the database. All backups used
to
> > replace existing datafiles must have been taken before the intended time
> of
> > recovery. For example, if you intend to recover to January 2 at 2:00
p.m.,
> > then restore all datafiles with backups completed before this time."
> >
> > So, to perform a tablespace point in time recovery, it must be done in
> > another database! In any given database, you cannot recover anything
> > (tablespace or datafile) to a point prior to any other tablesapce or
> > datafile. All must be at the same SCN. I was quite disappointed when I
> > first heard about this "feature", then found out what it actually meant.
> > The 8i enhancement it is that one can use a transportable tablespace to
> move
> > the results, in addition to the older Oracle7 method described below
> > (1,2,3) - and that it now has a name (TSPITR).
> >
> > The basic algorithm is:
> > 1) restore the database (at least the minimal subset) SOMEWHERE ELSE
> > 2) recover the database to the desired point in time.
> > 3) export the desired data and import into the "real" database or
> "transport
> > the tablespace" to the "real" database.
> >
> > See:
> >
>
http://technet.oracle.com/docs/products/oracle8i/doc_library/817_doc/server.
> > 817/a76993/ostspitr.htm#421341
> >
> > Don Granaman
> > [OraSaurus]

Oracle LazyDBA home page