A.v$session_wait and v$session both contain details of the event on which a waiting session is currently waiting.

B.v$session_event displays all waits for all past and existing sessions if the wait has occurred at least once for a session.

C.v$service_event displays wait counts for every wait event whether waited on or not, for each service.

D.v$session_wait and v$session both contain details of the event on which a non-waiting session last waited.

E.v$session_wait_class displays waits broken down by wait class only for waiting sessions.

A.After the change, each existing PDB has to be reopened for the new undo mode to take effect.

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

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

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

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

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

A.Run the SQL Tuning Advisor.

B.Run the SQL Access Advisor.

C.Run the Memory Advisor for the Program Global Area.

D.Run the Memory Advisor for the shared pool.

E.Run the Memory Advisor for the System Global Area.

A.Transparent encryption of backups uses an encryption wallet.

B.A database uses the same encryption key for every encrypted backup.

C.Encrypted backups can only be written to disk.

D.A password encryption of backups uses the password while creating and restoring backups.

E.Image copy backups can be created by using password encryption.

A.to allow database duplication without a connection to the auxiliary instance.

B.to store backups that would cause the controlfile to become too large.

C.to report on the database schema at an earlier point in time.

D.to store backup metadata that would cause the controlfile to become too large.

E.to allow database duplication without a connection to the target instance.