Re: recover from TRUNCATE TABLE via physical standby?

From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Fri, 24 Aug 2012 07:01:43 +0100
Message-ID: <CABe10sbs1yojRQRCffs=KLMpAcxPGnRBn2GcazBgTOpKe0TGfQ_at_mail.gmail.com>

I'd have thought the biggest objection to the use of Total Recall (always makes me think of the film typing that) is that it potentially exposes your organization to a significant dollar cost that they weren't expecting. Obviously if you have the relevant license (bundled with compression now I think) then it is an option.
I see nothing wrong with the original proposal, I'd sort of hope that truncate was subject to change control (and code that might dynamically run it was peer reviewed before implementation) though. On Aug 23, 2012 11:32 PM, "Adric Norris" <landstander668_at_gmail.com> wrote:

> I don't think it's quite so simple in this context. The FLASHBACK DATABASE
> command is (effectively) performing a restore/recover operation to a
> specific SCN, which can certainly be a point before the truncate occurred
> (like any point-in-time recovery).
> On Thu, Aug 23, 2012 at 4:58 PM, <james.clarence.allen_at_census.gov> wrote:
>
> > Sorry. When you truncate a table the data I'd deleted and nothing gets
> > logged.
> > You truncate and it,s gone!
> >
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

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

Received on Fri Aug 24 2012 - 01:01:43 CDT