By Scott Mcneil-Oracle on Apr 01, 2014
Since the launch of Oracle Enterprise Manager 12c Release 3, we have received tons of questions around managing Oracle Multitenant, an Oracle Database 12c Enterprise Edition option, and pluggable databases (PDBs)—more specifically; questions about pluggable database as a service (PDBaaS). In this blog, we provide answers to some of the common questions from people.
What qualifies a database to be pluggable?
Can the pluggable
databases be plugged and unplugged across multiple platforms such as Solaris,
AIX, and Linux?
of database consolidation, what are the differences between using VMs,
dedicated schemas and pluggable databases?
Pluggable database combines the best of all the other models and offers excellent consolidation, isolation, manageability and is suitable for any application that is certified to run on Oracle Database 12c. With the other models, we see certain shortcomings. For example, server virtualization offers good isolation but creates compliance and administrative headaches. Schema based consolidation offers ease of management and patching, but limited isolation.
How do you
track configuration drift with a pluggable database? I certainly understand
drift in the container database, but in what ways would a pluggable database
drift from its standard baseline?
What is a
zone? Is it physical? Regional?
be the DBA and SYSADMIN role in the pluggable DBaaS environment?
What if you
need custom configurations on a pluggable database? Once the database
is deployed via self-service how do you make changes?
If I'm an
application developer and I request a database with a certain pre-defined
service level, what level of permissions should I expect with that database?
Am I getting DBA or SYSDBA privileges with that request?
Are the pluggable
database as a service capabilities for Oracle Database 12c included in
Oracle Enterprise Manager 12c? Do we need a plug-in? Do we need to license
Oracle Enterprise Manager 12c Database Management Packs?
Enterprise Manager 12c Management Packs are required to be able to provide
If you have
shared memory and background processes in the container database, how
do you allocate server resources to a particular pluggable database? Can
you assign specific amount of CPU cycles, RAM and IOPS for a given pluggable
What is the
largest number of pluggable databases you can deploy on Oracle Exadata?
Can I use
pluggable database as a service if the target database is 9i or 10g?
Data Guard be configured for selective pluggable databases from a container
database? I do not want all pluggable databases to have a standby.
support pluggable databases?
For complete details of managing pluggable database as a service, be sure to watch this webcast: Delivering Pluggable Database as a Service