You accidentally drop the CUSTOMERS table, and then recover it by using the FLASHBACK TABLE command.
Which two statements are true about the dependent objects of the CUSTOMERS table?
A.
Only the primary key constraint created for the table is flashed back, whereas all other indexes must be
retrieved separately.
B.
All the constraints defined on the table, except the referential integrity constraints, are flashed back.
C.
All the triggers associated with the table are flashed back but are disabled.
D.
Materialized views that use the CUSTOMERS table are flashed back.
E.
LOB segments associated with the CUSTOMERS table are flashed back.
Explanation:
B: Oracle Database retrieves all indexes defined on the table except for bitmap join indexes, and all triggers and constraints defined on the table except for referential integrity constraints that reference other tables.
Incorrect Answers:
A: Flashback Table restores tables while automatically maintaining associated attributes such as current indexes, triggers, and constraints, and in this way enabling you to avoid finding and restoring database-specific properties.
Furthermore. indexes on table that exist currently are reverted and reflect the state of the table at the Flashback point.
C: By default, the database disables triggers on the affected table before performing a FLASHBACK TABLE
operation. After the operation, the database returns the triggers to the state they were in before the operation (enabled or disabled). To keep triggers enabled during the flashback of the table, add an ENABLE TRIGGERS clause to the FLASHBACK TABLE
D: Flashback Table operations are not valid for the following type objects: tables that are part of a cluster, materialized views, Advanced Queuing (AQ) tables, static data dictionary tables, system tables, remote tables, object tables, nested tables, or individual table partitions or subpartitions.
References: Oracle Database, Backup and Recovery User’s Guide, 12 Release 2 (January 2017), page 18-11
BC