Oracle Multitenant Environment (三) Plan for a cdb

Below tables contains contant you need to consider while planning for a CDB.

Action Considerations for a CDB Additional Information

Plan the tables and indexes for the pluggable databases (PDBs) and estimate the amount of space they will require.


In a CDB, most user data is in the PDBs. The root contains no user data or minimal user data. Plan for the PDBs that will be part of the CDB. The disk storage space requirement for a CDB is the space required for the Oracle Database installation plus the sum of the space requirements for all of the PDBs that will be part of the CDB. A CDB can contain up to 253 PDBs, including the seed.


Part II, "Oracle Database Structure and Storage"

Part III, "Schema Objects"

Chapter 38, "Creating and Removing PDBs with SQL*Plus"


Plan the layout of the underlying operating system files your CDB will comprise.


There are separate data files for the root, the seed, and each PDB.

There is one redo log for a single-instance CDB, or one redo log for each instance of an Oracle Real Application Clusters (Oracle RAC) CDB. Also, for Oracle RAC, all data files and redo log files must be on shared storage.


Chapter 17, "Using Oracle Managed Files"

Oracle Automatic Storage Management Administrator‘s Guide

Oracle Database Performance Tuning Guide

Oracle Database Backup and Recovery User‘s Guide

Oracle Grid Infrastructure Installation Guide for information about configuring storage for Oracle RAC

Your Oracle operating system–specific documentation, including the appropriate Oracle Database installation guide.


Plan for the number of background processes that will be required by the CDB.


There is one set of background processes shared by the root and all PDBs.


"Specifying the Maximum Number of Processes"


Select the global database name, which is the name and location of the CDB within the network structure, and create the global database name for the root by setting both theDB_NAME and DB_DOMAIN initialization parameters.


The global database name of the root is the global database name of the CDB.

The global database name of a PDB is defined by the PDB name and the DB_DOMAIN initialization parameter.


"Determining the Global Database Name"


Familiarize yourself with the initialization parameters that can be included in an initialization parameter file. Become familiar with the concept and operation of a server parameter file (SPFILE). An SPFILE file lets you store and manage your initialization parameters persistently in a server-side disk file.


A CDB uses a single SPFILE or a single text initialization parameter file (PFILE). Values of initialization parameters set for the root can be inherited by PDBs. You can set some initialization parameters for a PDB by using the ALTERSYSTEM statement.(这样更改的Parameter会对只对该PDB有效吗?重启后还会保持吗?)

The root must be the current container when you operate on an SPFILE. The user who creates or modifies the SPFILE must be a common user with SYSDBASYSOPER, orSYSBACKUP administrative privilege, and the user must exercise the privilege by connecting AS SYSDBAASSYSOPER, or AS SYSBACKUP respectively.

To create a CDB, the ENABLE_PLUGGABLE_DATABASEinitialization parameter must be set to TRUE.


"Specifying Initialization Parameters"

"Using the ALTER SYSTEM SET Statement in a CDB"

"Listing the Initialization Parameters That Are Modifiable in PDBs"

"About the Current Container"

Oracle Database Reference


Select the character set.


All of the PDBs in the CDB use this character set. When selecting the database character set for the CDB, you must consider the current character sets of the databases that you want to consolidate (plug) into this CDB.


Oracle Database Globalization Support Guide


Consider which time zones your CDB must support.


You can set the time zones for the entire CDB (including all PDBs). You can also set the time zones individually for each PDB.


"Specifying the Database Time Zone and Time Zone File"


Select the standard database block size. This is specified at CDB creation by the DB_BLOCK_SIZEinitialization parameter and cannot be changed after the CDB is created.


The standard block size applies to the entire CDB.


"Specifying Database Block Sizes"


If you plan to store online redo log files on disks with a 4K byte sector size, then determine whether you must manually specify redo log block size. Also, develop a backup and recovery strategy to protect the CDB from failure.


There is a single redo log and a single control file for an entire CDB.


"Planning the Block Size of Redo Log Files"

Chapter 11, "Managing the Redo Log"

Chapter 12, "Managing Archived Redo Log Files"

Chapter 10, "Managing Control Files"

Oracle Database Backup and Recovery User‘s Guide


Determine the appropriate initial sizing for theSYSAUX tablespace.


There is a separate SYSAUX tablespace for the root and for each PDB.


"About the SYSAUX Tablespace"


Plan to use a default tablespace for non-SYSTEMusers to prevent inadvertently saving database objects in the SYSTEM tablespace.


You can specify a separate default tablespace for the root and for each PDB. Also, there is a separate SYSTEMtablespace for the root and for each PDB.


"Creating a Default Permanent Tablespace"

"About the Statements That Modify a CDB"


Plan to use one or more default temporary tablespaces.


There is a default temporary tablespace for the entire CDB. You optionally can create additional temporary tablespaces for use by individual PDBs.


"Creating a Default Temporary Tablespace"

"About the Statements That Modify a CDB"


Plan to use an undo tablespace to manage your undo data.


There is one active undo tablespace for a single-instance CDB. For an Oracle RAC CDB, there is one active undo tablespace for each instance. Only a common user who has the appropriate privileges and whose current container is the root can create an undo tablespace.

In a CDB, the UNDO_MANAGEMENT initialization parameter must be set to AUTO, and an undo tablespace is required to manage the undo data.

Undo tablespaces are visible in static data dictionary views and dynamic performance (V$) views when the current container is the root. Undo tablespaces are visible only in dynamic performance views when the current container is a PDB.

Oracle Database silently ignores undo tablespace and rollback segment operations when the current container is a PDB.


Chapter 16, "Managing Undo"

"About the Current Container"


Plan for the database services required to meet the needs of your applications.


The root and each PDB might require several services. You can create services for the root or for individual PDBs. Therefore, ensure that the planned number of services do not exceed the database service limit.

Database services have an optional PDB property. You can create services and associate them with a particular PDB by specifying the PDB property. Services with a null PDBproperty are associated with the root. You can manage services with the SRVCTL utility, Oracle Enterprise Manager Cloud Control, and the DBMS_SERVICE supplied PL/SQL package.

When you create a PDB, a new default service for the PDB is created automatically. The service has the same name as the PDB. You cannot manage this service with the SRVCTL utility. However, you can create user-defined services and customize them for your applications.


"Managing Application Workloads with Database Services"

"Managing Services Associated with PDBs"

"SRVCTL Command Reference for Oracle Restart" for information about using the SRVCTL utility with a single-instance database

Oracle Real Application Clusters Administration and Deployment Guide for information about using the SRVCTL utility with an Oracle RAC database


Familiarize yourself with the principles and options of starting up and shutting down an instance and mounting and opening a CDB.


In a CDB, the root and all of the PDBs share a single instance, or, when using Oracle RAC, multiple concurrent database instances. You start up and shut down an entire CDB, not individual PDBs. However, when the CDB is open, you can change the open mode of an individual PDB by using the ALTER PLUGGABLE DATABASE statement, the SQL*Plus STARTUP command, and the SQL*Plus SHUTDOWNcommand.


"Starting Up a Database"

"Modifying the Open Mode of PDBs"

"Modifying a PDB with the ALTER PLUGGABLE DATABASE Statement"


If you plan to use Oracle RAC, then plan for an Oracle RAC environment.


The Oracle RAC documentation describes special considerations for a CDB in an Oracle RAC environment.


See your platform-specific Oracle RAC installation guide for information about creating a CDB in an Oracle RAC environment.

Oracle Real Application Clusters Administration and Deployment Guide


Avoid unsupported features.


The Oracle Database Readme includes a list of Oracle Database features that are currently not supported in a CDB.

If you must use one or more of these features, then create a non-CDB.


Chapter 2, "Creating and Configuring an Oracle Database"

Oracle Multitenant Environment (三) Plan for a cdb

时间: 2024-10-23 10:44:44

Oracle Multitenant Environment (三) Plan for a cdb的相关文章

Oracle Multitenant Environment

About oracle mulittenant environment The multitenant architecture enables an Oracle database to function as a multitenant container database (CDB) that includes zero, one, or many customer-created pluggable databases (PDBs). A PDB is a portable colle

Oracle Multitenant Environment (四) Create One or More CDBs

Using the CREATE DATABASE Statement to Create a CDB This section describes creating a CDB using the CREATE DATABASE SQL statement. Note: Oracle strongly recommends using the Database Configuration Assistant (DBCA) instead of the CREATE DATABASE SQL s

Oracle Multitenant Environment (五) Create PDB

Creating and Removing PDBs with SQL*Plus This chapter contains the following topics: About Creating and Removing PDBs Preparing for PDBs Creating a PDB Using the Seed Creating a PDB by Plugging an Unplugged PDB into a CDB Unplugging a PDB from a CDB

Oracle Multitenant Environment (二) Purpose

Purpose of a Multitenant Environment A multitenant environment enables the central management of multiple PDBs in a single installation. By using a multitenant environment, you can accomplish the following goals: Cost reduction By consolidating hardw

学习oracle数据库引航三——数据库对象

一.表-段 表分区:便于进行删除操作等. 可以直接删除分区表(迅速). 使用while等条件时效率高. 二.索引 提高查询速度 影响DML(更新.插入.删除)效率 更新表内容同时也要更新索引的内容. 三.数据库链 database link 两台数据之间 基于分布式事务的机制. 四.表空间 可以有多个数据文件 学习oracle数据库引航三--数据库对象,布布扣,bubuko.com

oracle学习 第三章 常用的SQL*PLUS命令 ——02

今天接着昨天的RUN命令继续讲. 3.5 n(设置当前行)命令和A(PPEND)(附加)命令 设想,你输入了例3-10的查询语句 例 3-10 SQL> SELECT ename 2 FROM emp; 例 3-10 结果 看到以上输出时,您发现在SELECT子句中忘了job,sal.这时您又如何修改您的SELECT子句呢?首先您应该使用SQL*PLUS的L(LIST)命令来显示SQL缓冲中的内容. 例 3-11 SQL> L 例 3-11 结果 在例3-11显示的结果中,2后面的"

Oracle中的三种Join 方式

基本概念 Nested loop join: Outer table中的每一行与inner table中的相应记录join,类似一个嵌套的循环. Sort merge join: 将两个表排序,然后再进行join. Hash join: 将两个表中较小的一个在内存中构造一个Hash 表(对Join Key),扫描另一个表,同样对Join Key进行Hash后探测是否可以join,找出与之匹配的行. 一张小表被hash在内存中.因为数据量小,所以这张小表的大多数数据已经驻入在内存中,剩下的少量数据

Oracle学习笔记三 SQL命令

SQL简介 SQL 支持下列类别的命令: 1.数据定义语言(DDL) 2.数据操纵语言(DML) 3.事务控制语言(TCL) 4.数据控制语言(DCL)               下面是这四种SQL语言的详细笔记: Oracle学习笔记三 SQL命令(二):SQL操作语言类别 Oracle数据类型 创建表时,必须为各个列指定数据类型 以下是 Oracle 数据类型的类别: 字符数据类型 CHAR类型 当需要固定长度的字符串时,使用 CHAR 数据类型. CHAR 数据类型存储字母数字值. CH

Oracle笔记(三) Scott用户的表结构

Oracle笔记(三) Scott用户的表结构 在Oracle的学习之中,重点使用的是SQL语句,而所有的SQL语句都要在scott用户下完成,这个用户下一共有四张表,可以使用: SELECT * FROM tab; 查看所有的数据表的名称,如果现在要想知道每张表的表结构,则可以采用以下的命令完成: DESC 表名称: 1.  部门表:dept № 名称 类型 描述 1 DEPTNO NUMBER(2) 表示部门编号,由两位数字所组成 2 DNAME VARCHAR2(14) 部门名称,最多由1