Also, the run-time behavior of client code that connects to the PDB containing the application back end is identical to the behavior of client code that connected to the non-CDB containing this back end.Operations that act on an entire non-CDB act in the same way on an entire CDB, for example, when using Oracle Data Guard and database backup and recovery.For example, 100 servers may have one database each, with each database using 10% of hardware resources and 10% of an administrator's time.A team of DBAs must manage the SGA, database files, accounts, security, and so on of each database separately, while system administrators must maintain 100 different computers.means that a PDB behaves the same as a non-CDB as seen from a client connecting with Oracle Net.The installation scheme for an application back end that runs against a non-CDB runs the same against a PDB and produces the same result.
You must define a database as a CDB at creation, and then create PDBs and application containers within this CDB.
The DBA team is reduced from five to three, with one CDB administrator managing the CDB while two PDB administrators split management of the PDBs.
data dictionary metadata specific to a PDB in the PDB itself rather than storing all dictionary metadata in one place.
Often these databases run on different platforms on multiple physical servers.
Because of improvements in hardware technology, especially the increase in the number of CPUs, servers are able to handle heavier workloads than before.