Your multitenant container database (CDB) contains pluggable databases (PDBs), you are
connected to the HR_PDB. You execute the following command:
SQL > CREATE UNDO TABLESPACE undotb01
DATAFILE ‘u01/oracle/rddb1/undotbs01.dbf’ SIZE 60M AUTOEXTEND ON;
What is the result?
A.
It executes successfully and creates an UNDO tablespace in HR_PDB.
B.
It falls and reports an error because there can be only one undo tablespace in a CDB.
C.
It fails and reports an error because the CONTAINER=ALL clause is not specified in the
command.
D.
It fails and reports an error because the CONTAINER=CURRENT clause is not specified in the
command.
E.
It executes successfully but neither tablespace nor the data file is created.
Explanation:
Interesting behavior in 12.1.0.1 DB of creating an undo tablespace in a PDB. With
the new Multitenant architecture the undo tablespace resides at the CDB level and PDBs all share
the same UNDO tablespace.
When the current container is a PDB, an attempt to create an undo tablespace fails without
returning an error.
E is correct
E
E
SQL> CREATE UNDO TABLESPACE undotb01 DATAFILE ‘/u01/app/oracle/db12cm/undotbs01.dbf’ SIZE 60M AUTOEXTEND ON;
Tablespace created.
SQL> select tablespace_name from dba_tablespaces;
TABLESPACE_NAME
——————————
SYSTEM
SYSAUX
TEMP
USERS
SQL> select name from dba_datafiles;
select name from dba_datafiles
*
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> show parameter undo
NAME TYPE VALUE
———————————— ———– ——————————
temp_undo_enabled boolean FALSE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
SQL> !ls -lrth /u01/app/oracle/db12cm/undotbs01.dbf
ls: cannot access /u01/app/oracle/db12cm/undotbs01.dbf: No such file or directory
So Answer is Definitely E — No Errors/No Warnings, No datafiles, No tablespace