Oracle multitenant Environment (iii) 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 would require.	in a CDB, most user data was in the Pdbs. the root contains no user data Or minimal user Data. plan for the PDBs, that'll be is part of the CDB. The disk storage space requirement for a CDB are the space required for the Oracle Database installation plus the sum of th E space requirements for any of the PDBs that would be is 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," Creating and removing PDBs with Sql*plus "
Plan the layout of the underlying operating system files your CDB would comprise.	There is 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 a Oracle Real application Clusters (Oracle RAC) CDB. Also, for Oracle RAC, all data files and redo log files must is on shared storage.	Chapter, "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 Databas E Installation Guide.
Plan for the number of background Processes that'll be required by the CDB.	There was 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 b Y setting both the db_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  initializatio n parameter.	"Determining the Global Database Name"
Familiarize yourself with the initialization parameters so 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 your 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 (p FILE). Values of initialization parameters set for the root can is inherited by PDBs. You can set some initialization parameters for a PDB by using the  ALTER SYSTEM  stateme NT. (Will the changed parameter be valid for the PDB only?) Will it remain after the reboot? ) The root must is the current container if you operate on a spfile. the user who creates or modifies the SP FILE must be a common user with  SYSDBA ,   sysoper , or sysbackup   Administrative privilege, and the user must exercise the privilege by connecting  as   sysdba< /code>,  as sysoper , or  as   sysbackup   respectively. To create a CDB, the  enable_pluggable_database initialization parameter must is set to  TRUE .	"Specifying Initialization Parameters" "Using the ALTER SYSTEM SET Statement in a CDB" "Listing the initialization Parameters that is modifiable in PDBs" "About the current Container" Oracle Database Reference
Select the character set.	All of the PDBs in the CDB with this character set. When selecting the database character set for the CDB, you must consider the current character sets of the databases You want to consolidate (plug) into the 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 was specified at CDB creation by the DB_BLOCK_SIZE initialization parameter and cannot was 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 bytes 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 are a single redo log and a single control file for an entire CDB.	"Planning the Block Size of Redo Log Files" Chapter one by one, "Mana Ging the Redo log " Chapter," Managing archived Redo Log Files " Chapter," Managing Control Files " Span class= "italic" >oracle Database Backup and Recovery User ' s Guide
Determine the appropriate Initial sizing for the sysaux  tablespace.	There was a separate  sysaux  tablespace for the Root and for each PDB.	"about the Sysaux tablespace"
Plan to use a default tablespace For non- system users to prevent inadvertently saving database objects in THE&NBSP; system   Tablespace.	You can specify a separate default tablespace for the root and for each PDB .  also, there is a separate  SYSTEM tablespace 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-Modify a CDB"
Plan to use a undo tablespace to manage your undo data.	There are one active undo tablespace for a single-instance CDB. For a Oracle RAC CDB, there are one active undo tablespace for each instance. only a common user who has the APPROPRI Ate privileges and whose current container are the root can create an undo tablespace. In a CDB, the  undo_management  initialization parameter must bes set to  AUTO , and an undo tablespace are required to manage the undo data. Undo tablespaces is visible in static data dictionary views and dynamic Performance (v$) views while the current Contai NER is the root. Undo tablespaces is 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, "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 does not exceed the database service limit. Database Services has an optional  PDB  property. You can create services and associate them with a particular PDB by specifying THE&NBSP; pdb  property. Services with a null , PDB property is associated with the root. You can manage services with the SRVCTL utility, Oracle Enterprise Manager Cloud Control, and the  dbms_service< /code> 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 USI ng the SRVCTL utility with a single-instance database oracle Real application Clusters Adminis Tration and Deployment Guide  for information on 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 any of the PDBs share a single instance, or, when US ing Oracle RAC, multiple concurrent database instances. You start up and shut a entire CDB, not individual PDBs. However, when the CDB was open, you can change the open mode of a individual PDB by using the  ALTER   ; pluggable   DATABASE  statement, the sql*plus  STARTUP   command, and the sql*plus  SHUTDOWN command.	"Starting up a Database" "Modifying the Open Mode of PDBs" "Modifying a PDB with the ALTER pluggable DATABASE Statement"
If you plan the use of 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 Information about creating a CDB on 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 is currently not supported in a CDB. If you must with one or more of the these features, then create a non-cdb.	Chapter 2, "Creating and configuring an Oracle Database"