Examine the initialization parameter that is set in the PFILE:
DB_CREATE_FILE_DEST =’/u01/app/oracle/oradata/’
You execute the following command to create theCDB1. container database (CDB):
SQL>CREATEDATABASECDB1
DEFAULTTABLESPACE users
DEFAULTTEMPORARY TABLESPACEtemp
UNDO TABLESPACEundotbsl
ENABLEPLUGGA3LEDATABASE
SEED
SYSTEMDATAFILESSIZE125M AUTOEXTEND ON NEXT10M MAXSIZEUNLIMITED
SYSAUXDATAFILESSIZE100M;
Which three statements are true?
A.
It creates a multitenant container database with a root and a seed pluggable database
(PDB) that are opened in read-write and read-only modes, respectively.
B.
The files created for both the root and seed databases use Oracle Managed Files (OMF).
C.
It creates a multitenant container database with the root and seed databases opened and
one PDB mounted.
D.
It sets the users tablespace as the default for both the root and seed databases.
E.
undotbs1 is used as the undo tablespace for both the root and seed databases.
F.
It creates a multitenant container database with the root database opened and the seed
database mounted.
Right answer is B D E
http://docs.oracle.com/database/121/ADMIN/cdb_create.htm#ADMIN13529
With Oracle Managed Files and the following CREATE DATABASE statement, the CDB creates the SYSTEM and SYSAUX tablespaces, creates the additional tablespaces specified in the statement, and chooses default sizes and properties for all data files, control files, and redo log files. Note that these properties and the other default CDB properties set by this method might not be suitable for your production environment, so it is recommended that you examine the resulting configuration and modify it if necessary.
CREATE DATABASE newcdb
USER SYS IDENTIFIED BY sys_password
USER SYSTEM IDENTIFIED BY system_password
EXTENT MANAGEMENT LOCAL
DEFAULT TABLESPACE users
DEFAULT TEMPORARY TABLESPACE temp
UNDO TABLESPACE undotbs1
ENABLE PLUGGABLE DATABASE
SEED
SYSTEM DATAFILES SIZE 125M AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED
SYSAUX DATAFILES SIZE 100M;
A CDB is created with the following characteristics:
The CDB is named newcdb. Its global database name is newcdb.us.example.com, where the domain portion (us.example.com) is taken from the initialization parameter file. See “Determining the Global Database Name”.
The passwords for user accounts SYS and SYSTEM are set to the values that you specified. The passwords are case-sensitive. The two clauses that specify the passwords for SYS and SYSTEM are not mandatory in this release of Oracle Database. However, if you specify either clause, then you must specify both clauses. For further information about the use of these clauses, see “Protecting Your Database: Specifying Passwords for Users SYS and SYSTEM”.
The DEFAULT TABLESPACE clause creates and names a default permanent tablespace for this CDB.
The DEFAULT TEMPORARY TABLESPACE clause creates and names a default temporary tablespace for this CDB. See “Creating a Default Temporary Tablespace”.
The UNDO TABLESPACE clause creates and names an undo tablespace that is used to store undo data for this CDB. In a CDB, an undo tablespace is required to manage the undo data, and the UNDO_MANAGEMENT initialization parameter must be set to AUTO. If you omit this parameter, then it defaults to AUTO. See “Using Automatic Undo Management: Creating an Undo Tablespace”.
Redo log files will not initially be archived, because the ARCHIVELOG clause is not specified in this CREATE DATABASE statement. This is customary during CDB creation. You can later use an ALTER DATABASE statement to switch to ARCHIVELOG mode. The initialization parameters in the initialization parameter file for newcdb relating to archiving are LOG_ARCHIVE_DEST_1 and LOG_ARCHIVE_FORMAT. See Chapter 12, “Managing Archived Redo Log Files”.
The ENABLE PLUGGABLE DATABASE clause creates a CDB with the root and the seed.
SEED is required for the tablespace_datafile clauses.
The SYSTEM DATAFILES clause specifies attributes of the seed’s SYSTEM tablespace data file(s) that differ from the root’s.
The SYSAUX DATAFILES clause specifies attributes of the seed’s SYSAUX tablespace data file(s) that differ from the root’s.
Sorry , It’s A B D , not B D E !
Undo is used only at the root not the seed.
http://avdeo.com/2015/01/16/creating-oracle-12c-multitenant-container-database/
ABE
The seed actually doesn’t use anything since it’s read-only, but any PDB created from the seed will use the undotbs1 undo tablespace.
Each PDB can have its own default tablespace, but cannot change the undo tablespace.
Thanks Steve!
B for DB_CREATE_FILE_DEST =’/u01/app/oracle/oradata/’
A, B, E
1* SELECT NAME, CON_ID, DBID, CON_UID, OPEN_MODE FROM V$CONTAINERS ORDER BY CON_ID
SQL> /
NAME CON_ID DBID CON_UID OPEN_MODE
——– ———- ———- ———- ———-
CDB$ROOT 1 1433207794 1 READ WRITE
PDB$SEED 2 327330637 327330637 READ ONLY
PDB2 4 3484124700 3484124700 MOUNTED
SQL>
You are correct. Thank you.
ABE
ABE
ABE