Duplication can be done by having the auxiliary databaseinstance pull backup sets from the target
database instance.

A connection to an auxiliary instance is always required

A subset of the target database can be duplicated.

A new DBID is always created for the duplicated database.

A connection tothe recovery catalog instance is always required.

cloning a remote container database in interactive mode

cloning a remote pluggable database in silent mode

relocating a remote pluggable database in interactive mode

relocating a remote container database in silent mode

cloning a remote container database in silent mode

Using the Data Recovery Advisor LIST FAILURE command always requires that the databasefor which
failures are to be listed is in MOUNT state.

A failure can be closed only when it has been repaired.

Data Recovery Advisor can be used if a database is closed.

The Data Recovery Advisor CHANGE FAILURE command can be used only to changefailure
priorities.

Data Recovery Advisor can proactively check for failures.

It can berun only manually.

It is part of the DBMS_ADVISOR package.

It can recommend changes to improve the statistics gathering process.

It always analyzes all schemas in the database.

It runs automatically every night by default.

After the change, only a common user with the required privilege can create an undo tablespace in
CDB&ROOT.

Any new PDB and existing PDBs are automatically configured to use the default undo tablespace in
CDB$ROOT.

After the change, only one undo tablespace can exist in CDB$ROOT.

After the change, any user with the required privilege can create an undo tablespace in the PDBs.

Undo tablespaces existing in PDBs must be dropped before the change.

The ORCL database, the Oracle ASM instances, the +DATA and +FRA disk groups, and the
LISTENER
are started.

Only the ORCL database instance is started.

Only the ORCL database and the ASM instances are started

Only the ORCL database instance, the Oracle ASM instance, and the +DATA and +FRA disk groups
are started.

Only the ORCL database instance and the +DATA and +FRA disk groups are started.

Two or more PDBs can be duplicated with the same RMAN DUPLICATE command.

All tablespaces belonging to a PDB must be duplicated when duplicating the PDB.

The auxiliary instance is automatically created with ENABLE_PLUGGABLE_DATABASE = TRUE.

A user with SYSDBA or SYSBACKUP must be logged in with RMAN to the PDB to duplicate it.

CDB$ROOT and PDB$SEED are automatically duplicated.

Recovery begins from the beginning of the CURRENT redo log group.

Recovery begins from the last checkpoint position that wascalculated by the Database Writer before
instance failure.

Recovery begins from the start of any ACTIVE redo log group or the start of the CURRENT log group
if no other group is ACTIVE.

Recovery reads redo until the end of the redo thread. SMON rollsback any dead transactions, and then
the datanase is opened.

Recovery begins from the last checkpoint position that was recorded in the control file by the checkpoint
process (CKPT).