A.Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open PDBs except PDB$SEED.

B.Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to a PDB opened in read/write mode gathers object statistics for that PDB.

C.Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics only in CDB$ROOT.

D.System statistics can be gathered only while connected to CDB$ROOT.

E.Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open pluggable databases (PDBs)

A.It recompiles all stored PL/SQLcode by using utlrp.sql.

B.It empties the RECYCLE BIN.

C.It performs prerequisite checks to verify if the Oracle database is ready for upgrade.

D.It sets all user tablespaces to "read-only" before starting the upgrade.

E.It removes the AUDSYS schema and the AUDIT_ADMINand AUDIT_VIEWERroles

F.It increases tablespace size, if required, to meet upgrade requirements.

A.If an RMAN BACKUP VALIDATE command takes noticeably less time than an actual backup, then write I/O is a likely bottleneck.

B.If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then read I/O is a likely bottleneck.F

C.If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then both read and write I/O are likely bottlenecks.

D.Data files with a high value in V$BACKUP_SYNC_IO.DISCRETE_BYTES_PER_SECOND are a potential performance bottleneck when synchronous I/O is used.

E.Data files with a high value in V$BACKUP_ASYNC_IO.SHORT_WAITS are a potential performance bottleneck when asynchronous I/O is used.

A.Any PDB not specified in the plan will be unable to execute statements in parallel.

B.PDB2 is guaranteed at least 25% of the available parallel execution processes if there is enough demand.

C.Any PDB not specified in the plan will be able to use a maximum of 16.5% of the available system resources.

D.PDB3 can use all available parallel execution processes at times.

E.PDB3 is guaranteed to receive at least 20% of the available system resources if there is enough demand.

F.PDB1 is always limited to 40% of the available system resources regardless of demand.

A.A data file can be split into multiple sections stored in different backup sets.

B.A backup set must be written to disk.

C.Blocks from multiple data files can be contained in one backup piece.

D.A backup set can contain only one backup piece.

E.Blocks from multiple data files can be contained in one backup set.

F.A backup piece can belong to only one backup set.

G.A data file can be split into multiple sections stored in different backup pieces in the same backup set.

H.A backup set must be written to media.