Which DDL operation is supported on the table after enabling Flashback Data Archive?

You enabled Flashback Data Archive on the INVENTORY table. Which DDL operation is
supported on the table after enabling Flashback Data Archive?

A.
Drop the table.

B.
Partition the table

C.
Truncate the table.

D.
Add a column to the table.

E.
Rename a column in the table.

Show Hint

← Previous question

Next question →

Leave a Reply 7

GuanYing Wu

The answer is wrong?
http://docs.oracle.com/cd/E11882_01/appdev.112/e17125/adfns_flashback.htm#BJFFDCEH
Flashback Data Archive supports many DDL statements, including some that alter the table definition or move data. For example:

ALTER TABLE statement that does any of the following:

Adds, drops, renames, or modifies a column
Adds, drops, or renames a constraint
Drops or truncates a partition or subpartition operation
TRUNCATE TABLE statement

RENAME statement that renames a table

Some DDL statements cause error ORA-55610 when used on a table enabled for Flashback Data Archive. For example:

ALTER TABLE statement that includes an UPGRADE TABLE clause, with or without an INCLUDING DATA clause

ALTER TABLE statement that moves or exchanges a partition or subpartition operation

DROP TABLE statement

If you must use unsupported DDL statements on a table enabled for Flashback Data Archive, use the DBMS_FLASHBACK_ARCHIVE.DISASSOCIATE_FBA procedure to disassociate the base table from its Flashback Data Archive. To reassociate the Flashback Data Archive with the base table afterward, use the DBMS_FLASHBACK_ARCHIVE.REASSOCIATE_FBA procedure.

Justyna

It seems that not only D is correct but C and E as well.

lisa

yes, i do think so…

Helcio

I agree with CDE is correct:

Oracle Database 11g Release 2 (11.2) users can now use most DDL commands on tables that are being tracked with Flashback Data Archive. This includes:

Add, Drop, Rename, Modify Column
Drop, Truncate Partition
Rename, Truncate Table
Add, Drop, Rename, Modify Constraint

For more complex DDL (for example, upgrades and split table), the Disassociate and Associate PL/SQL procedures can be used to temporarily disable Total Recall on specified tables. The Associate procedure enforces schema integrity after association; the base table and history table schemas must be the same.

This feature makes it much easier to use the Total Recall option with complex applications that require the ability to modify the schema.