Use Flashback Time Travel to view past states of database
objects or to return database objects to a previous state without using point-in-time media
recovery.
About Flashback Time Travel Flashback Time Travel lets you track and store transactional changes to a table over its lifetime. Flashback Time Travel is useful for compliance with record stage policies and audit reports. You can also use Flashback Time Travel in various scenarios such as enforcing digital shredding, accessing historical data, and selective data recovery.
Flashback Time Travel lets you track and store transactional changes
to a table over its lifetime. Flashback Time Travel is useful for compliance with record
stage policies and audit reports. You can also use Flashback Time Travel in various scenarios such as enforcing digital shredding, accessing
historical data, and selective data recovery.
Flashback Time Travel was called
Flashback Data Archive in previous Oracle Database versions. The Flashback Time Travel APIs and some Flashback Time Travel terms such as the
FLASHBACK ARCHIVE privilege retain the Flashback Data Archive
naming.
Each Autonomous Database instance has one
Flashback Archive named flashback_archive that supports Flashback Time Travel operations. The default
retention time for flashback_archive is 60 days. See Modify the Retention Time for Flashback Time Travel for information on changing the default retention time.
There are restrictions to enable Flashback Time Travel for a table, including the following:
You must have the FLASHBACK ARCHIVE object privilege for
flashback_archive. By default the ADMIN
user has this privilege.
Provides
notes and restrictions for using Flashback Time Travel on
Autonomous Database.
Note the following Flashback Time Travel restrictions:
You cannot enable Flashback Time Travel on tables with LONG data type or nested
table columns.
You cannot enable Flashback Time Travel on
a nested table, temporary table, external table, materialized view, Advanced
Query (AQ) table, hybrid partitioned tables, or non-table object.
Flashback Time Travel does not support DDL
statements that move, split, merge, or coalesce partitions or sub
partitions, move tables, or convert LONG columns to
LOB columns.
Adding or enabling a Constraint, including Foreign Key Constraint, on a table
that has been enabled for Flashback Time Travel fails with ORA-55610.
Dropping or disabling a Constraint (including Foreign Key Constraint) on a
table that has been enabled for Flashback Time Travel is supported.
After enabling Flashback Time Travel on a
table, Oracle recommends initially waiting at least 20 seconds before inserting
data into the table and waiting up to 5 minutes before using Flashback Query on
the table.
There is one Flashback Data Archive per Autonomous Database instance, named
flashback_archive, and you cannot create additional
Flashback Data Archives.
You cannot drop the Flashback Data Archive, flashback_archive,
within an Autonomous Database
instance.
You cannot create, modify, or drop tablespaces for the Flashback Data Archive.
Hence, you cannot run these statements:
ALTER FLASHBACK ARCHIVE flashback_archive ADD TABLESPACE;
ALTER FLASHBACK ARCHIVE flashback_archive MODIFY TABLESPACE;
ALTER FLASHBACK ARCHIVE flashback_archive REMOVE TABLESPACE;
If you enable Flashback Time Travel on a
table, but Automatic Undo Management (AUM) is disabled, error ORA-55614
occurs when you try to modify the table.
To enable Flashback Time Travel
on a table, the table cannot use any of the following Flashback Time Travel reserved words as column
names: