In Oracle Multitenant Architecture, a pluggable database (PDB) is a portable set of schemas, schema objects, and non-schema objects that appears to an Oracle Net client as a non-CDB. Each PDB is a fully functioning Oracle database with its own data files, control files, and background processes. The PDB concept was introduced in Oracle Database 12c as part of the multitenant architecture.
Each PDB has a unique name within a container database (CDB).
The PDB name is specified during the creation of the pluggable database, and it
allows you to distinguish and identify different pluggable databases within a
single container database. The PDB name is used when connecting to a specific
pluggable database.
Here's an example of connecting to a pluggable database using
SQL*Plus:
sqlCopy code
sqlplus username/password@PDB_name
In this example, replace "username" and
"password" with your actual credentials, and "PDB_name"
with the name of the pluggable database you want to connect to.
When you create a new pluggable database, you specify its name
as part of the CREATE PLUGGABLE DATABASE statement. For instance:
sqlCopy code
CREATE
PLUGGABLE DATABASE pdb_name ADMIN USER pdb_admin IDENTIFIED BY password DEFAULT
TABLESPACE users DATAFILE '/path/to/datafile/pdb_name_datafile01.dbf' SIZE 100M;
In this example, "pdb_name" is the name of the new
pluggable database, and you would replace "pdb_admin" and
"password" with the desired administrative username and password.
It's important to note that the PDB name is unique within the
scope of the container database but not globally across different container
databases in the same Oracle instance.
No comments:
Post a Comment