Database Reference
In-Depth Information
SQL> ALTER SESSION SET CONTAINER=pdb$seed;
Session altered.
SQL> ALTER SESSION SET CONTAINER=pdb2;
Session altered.
SQL>
Start Up and Shut Down a CDB and
Open and Close PDBs
In this section, we will discuss the methods to start up and shut down a CDB and the
methods to open and close PDBs within a CDB. In Oracle Database 12 c , the DBA starts
up a CDB in basically the same way as a non-CDB; however, there is a new set of com-
mands to start up a PDB that exists within a CDB. To shut down a CDB, the DBA uses
the same commands that would be used to shut down a non-CDB, but there is a new set
of commands to shut down a PDB.
Starting Up the CDB Using SQL*Plus
To start up the CDB using SQL*Plus, start a SQL*Plus session and connect to a CDB as a user
with administrator privileges; then issue the STARTUP command. A user with the SYSDBA,
SYSOPER, SYSBACKUP, SYSDG, or SYSKM system privileges may start up a CDB. By
default, users SYS and SYSTEM may start up a CDB.
Starting Up a CDB Instance
To start up a CDB instance, the current user must have sufficient privileges and must be
a common user whose current container is the root. When you open a CDB, its PDBs are
by default mounted but not opened, but this can be changed with a trigger. The startup
options are the same for non-CDBs and CDBs:
FORCE Performs a SHUTDOWN ABORT and then STARTUP . Can be used to force the instance to
start after there was a problem with either a previous startup attempt or shutdown.
MOUNT Mounts the database after the instance is started but does not open it for general
access, allowing for certain DBA activities such as enabling or disabling archiving.
Search WWH ::




Custom Search