A.Add the file_mame_comvert clause to the statement and enable Oracle Managed Files (OMF).

B.Enable only OMF.

C.Set the pdb_file_name_convert parameter and enable OMF.

D.Set only the pdb_file_name_convert parameter.

E.Add the file_name_convert clause to the statement and set the pdb_file_name_convert parameter.

F.Add only the create_file_dest clause to the statement.

A.RMAN automatically adds any required tablespaces to the recovery set to make it self-contained.

B.RMAN always includes tablespaces containing undo segments in the recovery set.

C.It can be used to recover a truncated table.

D.It can be performed using an auxiliary instance managed by a DBA.

E.It can be performed using an auxiliary instance managed by RMAN.

F.It can be used to recover a dropped tablespace.

G.flashback database must be enabled for it to work.

H.It can be performed repeatedly until the correct time is found without using an RMAN catalog.

A.A lost password file can be re-created with SQL*PLUS.

B.A lost SPFILE can be recovered from memory using SQL*PLUS.

C.A lost index tablespace can be re-created without performing any recovery.

D.A lost TEMPFILE must always be re-created manually.

E.A lost password file can be manually re-created with the orapwd utility.

F.A lost PFILE can be re-created alert.log using SQL*PLUS.

A.Application-common Transparent Security Data Protection (TSDP) policies can be created only within an application install/patch begin-end block.

B.Application-common OLS policies can be created in an application root inside an install/patch BEGIN-END block.

C.Unified auditing can be automatically synchronized to all application PDBs in an application container.

D.Fine-grained auditing (FGA) policies in an application root are automatically synchronized to all application PDBs contained in the application container.

E.Application-common TSDP policies are always container specific.

A.A non-duplexed backup set written to SBT can be duplexed to tape by backing up the backup set that is already on tape.

B.A duplexed backup set uses the same number of SBT channels as a non-duplexed backup set for the same number of files.

C.A non-duplexed backup set written to disk can be duplexed to tape by backing up the backup set that is already on disk.

D.A duplexed backup set always uses twice as many SBT channels as a non-duplexed backup set for the same number of files.

E.A non-duplexed backup set written to disk can be duplexed to disk by backing up the backup set that is already on disk.

F.A non-duplexed backup set written to SBT can be duplexed to disk by backing up the backup set that is already on tape.