Shulou(Shulou.com)06/01 Report--

Oracle 12C introduces new features of CDB and PDB, allowing a database container (CDB) to host multiple pluggable databases (PDB) in the multi-rent user environment (Multitenant Environment) introduced by ORACLE 12C databases. The full name of CDB is Container Database, the Chinese translation is database container, and the full name of PDB is Pluggable Database. You can plug and unplug the database. Before ORACLE 12C, the instance and database had an one-to-one or many-to-one relationship (RAC): that is, an instance could only be associated with one database, and the database could be loaded by multiple instances. It is impossible for an instance to have an one-to-many relationship with a database. When entering ORACLE 12C, the instance can have an one-to-many relationship with the database. The following is a diagram of the official documentation on the relationship between CDB and PDB.

CDB component (Components of a CDB)

An CDB database container contains the following components:

ROOT component

ROOT, also known as CDB$ROOT, stores the metadata and Common User provided by ORACLE. An example of metadata is the source code of the PL/SQL package provided by ORACLE, and Common User is the user that exists in each container.

SEED component

Seed, also known as PDB$SEED, is the template you use to create a PDBS database. You cannot add or modify an object in Seed. There can be and only one Seed in a CDB.

PDBS

There can be one or more PDBS,PDBS backward compatible in CDB, and PDBS can be manipulated as before in the database, in this case, most general operations.

Each of these components can be called a container. Therefore, ROOT (root) is a container, Seed (seed) is a container, and each PDB is a container. Each container has a unique ID and name in CDB.

Here are some simple examples of CDB and PDB and maintenance management on 12.2.0.1

1. Connect to CDB database

Or use sqlplus / as sysdba to connect, the same as the previous version in

[oracle@t13s admin] $sqlplus / as sysdbaSQL*Plus: Release 12.2.0.1.0 Production on Wed Mar 15 10:39:52 2017Copyright (c) 1982, 2016, Oracle. All rights reserved.Connected to:Oracle Database 12c Enterprise Edition Release 12.2.0.1.0-64bit ProductionSYS@testdb >

2. Check whether the database is CDB.

SYS@testdb > select cdb from vested database

CDB if YES, non-CDB if NO

3. View the current container

SYS@testdb > show con_nameCON_NAME--CDB$ROOT

At this time, the connection is root, so it is displayed as CDB$ROOT. If you connect to PDB, the instance name of PDB is displayed.

4. View the information of PDB

-- 1SYS@testdb > select con_id,dbid,guid,name,open_mode from v$pdbs CON_ID DBID GUID NAME OPEN_MODE -2 172801168 4AAD025C72A1F4B0E05358E8FF0AAC40 PDB$SEED READ ONLY--2SYS@testdb > show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED-- -- 2 PDB$SEED READ ONLY NO

PDB has not been created yet, so there is only one PDB$SEED.

5. Create and delete PDB

Using CREATE PLUGGABLE DATABASE, you can create a PDB from SEED. The current container must be CDB root.

SYS@testdb > show con_nameCON_NAME--CDB$ROOTSYS@testdb > CREATE PLUGGABLE DATABASE test_pdb ADMIN USER testadm IDENTIFIED BY "rF" ROLES= (CONNECT) file_name_convert= ('/ data/oradata/testdb/pdbseed','/data/oradata/testdb/test_pdb') path_prefix='/data/oradata/testdb/test_pdb' Pluggable database created.SYS@testdb > show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED- 2 PDB$SEED READ ONLY NO 3 TEST_ PDB MOUNTED

Use DROP PLUGGABLE DATABASE to delete PDB

Drop pluggable database test_pdb including datafiles

6. Start and shut down PDB

-- start SYS@testdb > alter pluggable database test_pdb open Pluggable database altered.SYS@testdb > show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED- 2 PDB$SEED READ ONLY NO 3 TEST_ PDB READ WRITE NO-- closes SYS@testdb > alter pluggable database test_pdb close Pluggable database altered.SYS@testdb > show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED- 2 PDB$SEED READ ONLY NO 3 TEST_ PDB MOUNTED

7. Switching between containers

SYS@testdb > alter session set container=test_pdb;Session altered.SYS@testdb > show con_nameCON_NAME--TEST_PDB

8. Use sql*plus to directly connect to PDB

Check out the monitor to see how PDB is registered

[oracle@t13s admin] $lsnrctl statusLSNRCTL for Linux: Version 12.2.0.1.0-Production on 15-MAR-2017 11:23:01Copyright (c) 1991, 2016, Oracle. All rights reserved.Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=bossett13s) (PORT=1521)) STATUS of the LISTENER----Alias LISTENERVersion TNSLSNR for Linux: Version 12.2.0.1.0-ProductionStart Date 15-MAR-2017 09:35:52Uptime 0 days 1 hr. 47 min. 10 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Parameter File / oracle/app/oracle/product/12.2/db/network/admin/listener.oraListener Log File / oracle/app/oracle/diag/tnslsnr/bossett13s/listener/alert/log.xmlListening Endpoints Summary... (DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=bossett13s) (PORT=1521)) (DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=EXTPROC1521) Services Summary...Service "4abd62d724202b74e05358e8ff0a94fe" has 1 instance (s). Instance "testdb", status READY, has 1 handler (s) for this service...Service "test_pdb" has 1 instance (s). Instance "testdb", status READY, has 1 handler (s) for this service...Service "testdb" has 1 instance (s). Instance "testdb", status READY, has 1 handler (s) for this service...Service "testdbXDB" has 1 instance (s). Instance "testdb", status READY, has 1 handler (s) for this service...The command completed successfully

Need to configure tns

Test_pdb = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = 10.255.232.88) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = test_pdb)

Connect

[oracle@t13s admin] $sqlplus testadm/rF@test_pdbSQL*Plus: Release 12.2.0.1.0 Production on Wed Mar 15 11:30:21 2017Copyright (c) 1982, 2016, Oracle. All rights reserved.Connected to:Oracle Database 12c Enterprise Edition Release 12.2.0.1.0-64bit ProductionTESTADM@test_pdb >

9. Create tablespaces in PDB

SYS@testdb > alter session set container=test_pdbSession altered.SYS@testdb > create tablespace users datafile'/ data/oradata/testdb/test_pdb/users01.dbf' size 200m Tablespace created.SYS@testdb > select name from vs. Tablespace created.SYS@testdb > NAMEMAYSAUXUNDOTBS1TEMPUSERS

10. User management

Only a global user can be created in cdb (beginning with clocked #), which will be created in cdb and all pdb (but global users in pdb need additional authorization to access them in pdb). Only users that can be created in pdb are local users

SYS@testdb > show con_nameCON_NAME--CDB$ROOTSYS@testdb > create user test identified by "abcd"; create user test identified by "abcd" * ERROR at line 1:ORA-65096: invalid common user or role nameSYS@testdb > create user c##test identified by "abcd"; User created.SYS@testdb > alter session set container=test_pdb;Session altered.SYS@testdb > create user test identified by "abcd"; User created.

Reference: http://www.xifenfei.com/2013/05/oracle-12c-pdb-%E7%AE%A1%E7%90%86%E4%BB%8B%E7%BB%8D1.html

Http://www.cnblogs.com/kerrycode/p/3386917.html

Official document: http://docs.oracle.com/database/122/ADMIN/overview-of-managing-a-multitenant-environment.htm#ADMIN13507

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.