Database Reference
In-Depth Information
Certain DDL is not allowed on archived tables:
TRUNCATE
,
DROP
, and
RENAME
as well as
ALTER
commands that drop, rename, or modify a column, change
a long raw to a LOB, perform a partition or subpartition operation, or use
the
UPGRADE TABLE
clause.
Monitoring the Flashback Data Archive
The Flashback Data Archive process, FBDA, archives the historical rows of tables enabled for
archiving to the Flashback Data Archive. FBDA writes a pre-image of a row and metadata on
current rows into the flashback archive when a transaction that changes data commits. FBDA
manages the Flashback Data Archive retention and space.
Several views are available for monitoring the Flashback Data Archive. See Table 8.5 for
a description of the views.
TABle 8.5
Flashback Data Archive Views
View Name
Description
DBA_FLASHBACK_ARCHIVE
Information about Flashback Data Archive
DBA_FLASHBACK_ARCHIVE_TS
Tablespaces used for Flashback Data Archive
DBA_FLASHBACK_ARCHIVE_TABLES
Tables that are enabled for archive
Perform Flashback Database Operations
Flashback Database
was introduced in Oracle 10
g
. There is one main difference between
the other Flashback technologies and Flashback Database: Flashback Database relies on the
flashback logs as opposed to undo tablespaces.
Flashback Database allows you to flash the entire database back to a specific point in
time. This is extremely useful to recover from errors such as truncating a large table, not
completing a batch job, or dropping a user. Flashback Database recovery is also the best
choice for logical corruptions such as a bad complex transaction that gets propagated
throughout the database.
Before you can use Flashback Database, you must set up the
fast recovery
area
. Please refer to Chapter 2, “Performing Oracle User-Managed Data-
base Recoveries,” for an introduction to the fast recovery area, and refer
to Chapter 3, “Configuring and Backing Up Using RMAN,” to learn how to
configure it.
Search WWH ::
Custom Search