Re: oracle total recall
From: Rumpi Gravenstein <rgravens_at_gmail.com>
Date: Tue, 3 Apr 2012 12:03:31 -0400
Message-ID: <CAEpg1wD_ftFFk2Y8dEozc99adNMWVfRfe4U115q_qw8j=mG+Gg_at_mail.gmail.com>
An elaboration of my point about flashback tables and recoverability -- your design should not only consider the features that you want to use but also how the use of those features impact your maintenance, recoverability and migration options.
Oracle support says the following about moving flashback data with Oracle 11gR2:
Date: Tue, 3 Apr 2012 12:03:31 -0400
Message-ID: <CAEpg1wD_ftFFk2Y8dEozc99adNMWVfRfe4U115q_qw8j=mG+Gg_at_mail.gmail.com>
An elaboration of my point about flashback tables and recoverability -- your design should not only consider the features that you want to use but also how the use of those features impact your maintenance, recoverability and migration options.
Oracle support says the following about moving flashback data with Oracle 11gR2:
The only option available to restore flashback tables, is by cloning the DB
> with same set of flashback parameters on the to be duplicated instance. It
> must be a point in time duplication, or point in time restore and recovery
> of the database
>
What is explicitly excluded is the ability to export/import a flashback enabled table.
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Apr 03 2012 - 11:03:31 CDT