SlideShare a Scribd company logo
Oracle 12c Multitenant
Architecture
Introduction of CDB and PDB
Databases
(Reference – Oracle documentation)
1
What is Multitenant
• Multi-tenancy is an design in which a single
instance of a software application serves multiple
customers. Each client is called a tenant.
• With a multitenant architecture, a software
application is designed to provide all tenant a
committed share of the instance including its
data, configuration, user management, tenant
individual functionality and non-functional
possessions.
Check detailed contents on
http://dbaboss.com/
2
• It has been an organizational outlandish when multiple
databases are running in one machine. The backups need to
be run independently. Each database has memory footmark
and each database has background processes. This increases
the capacity of the server on what it can lever in terms of the
loads. By joining into one container database and at the same
time keeping all of them as separate databases are a great
thing from association, performance, capacity and operational
perspective. This is going to help in a very big way for
consolidation on many enterprises and at the same time it will
reduce the server footprint significantly giving the maximum
Return on Investments (ROI) on the middleware database
technologies.
Check detailed contents on
http://dbaboss.com/
3
Oracle 12c Multitenant Architecture
Overview
• A new selection for Oracle Database 12c,
Oracle Multitenant supplies a new
architecture that allows a multitenant
container database to hold many pluggable
databases. At present database can simply be
accepted with no application changes
required. Oracle Multitenant fully
complements other options, including Oracle
Real Application Clusters and Oracle Active
Data Guard.
Check detailed contents on
http://dbaboss.com/
4
• The multitenant architecture empowers 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 transportable collection of
schemas, schema objects, and nonschema
objects that appears to an Oracle Net client as
a non-CDB. All Oracle databases before Oracle
Database 12c were non-CDBs.
Check detailed contents on
http://dbaboss.com/
5
What is CDB, PDB and Seed Database
• Container Database (CDB):
The primary database that comprises numerous plugged-in databases.
Numerous operations can be performed at the container level to reduce
management costs. A database is generated as either a CDB or a non-CDB.
On the apparent this seems very similar to a conventional Oracle database, as
it contains most of the working parts you will be already familiar with (control
files, data files, undo, tempfiles, redo logs etc.). It also lines the data
dictionary for those objects that are owned by the root container and those
that are visible to all PDBs.
A container is a pool of schemas, objects, and related structures in a
multitenant container database (CDB) that appears logically to an application
as a separate database. Within a CDB, each container has a unique ID and
name.
It also called root container.
Check detailed contents on
http://dbaboss.com/
6
• Pluggable Database (PDB):
A set of schemas, objects, and non-schema objects that can be
plugged and unplugged from a container database. The PDB
appears to Oracle Net and end users as a Non cdb database in
and of itself but is actually managed within a container that may
have many PDBs. Since the CDB comprises most of the working
parts for the database, the PDB only needs to contain
information precise to itself. It does not need to worry about
controlfiles, redo logs and undo etc. As an alternative it is just
made up of datafiles and tempfiles to handle it's own objects.
This contains it's own data dictionary, containing information
about only those objects that are specific to the PDBSeed
Database.
PDBs isolate data and operations so that from the standpoint of
a user or application, each PDB appears as if it were a traditional
non-CDB.
Check detailed contents on
http://dbaboss.com/
7
• The maximum limit to the total number of Pluggable databases
within a container database is close to 250. So you can have up to
250 pluggable databases or PDBs within one container database or
CDB. It is clear that there is one-to-many relationship between CDB
and PDBS.
• (Seed PDB):
A default PDB that the system uses as a template to quickly
facilitate other user-created PDBs. Within, it’s called PDB$SEED
• Below picture refer in Oracle docs
Check detailed contents on
http://dbaboss.com/
8
Check detailed contents on
http://dbaboss.com/
9
Check detailed contents on
http://dbaboss.com/
10
Check detailed contents on
http://dbaboss.com/
11
• The new multitenancy choice in Oracle Database 12c that permits you to
create several virtual databases (PDB) called pluggable databases or containers
in a single physical database called container database (CDB). The CDB is the
one that has the Oracle instance connected with it, i.e. it has the background
processes such as pmon, smon and the memory areas such as buffer cache
and large pool. The PDBs do not have their own instance; but take up house
inside the CDB, with some extra storage private to them. This preparation
permits you to address the PDBs as independent databases. So you can create
a user called, say, DBABOSS in every PDB, as an alternative of creating a new
database for creating these users. This is highly useful in case of applications
that require a specifically named schema, e.g. PeopleSoft have need of a user
so-called SYSADM. If you want to place numerous PeopleSoft applications
inside one database, you can't, since you can't create more than one user with
the name SYSADM. So you had to resort to producing several databases to
hold several copies of the application. Each of these databases had its own
memory and resource overheads. In a multitenancy model you can create
several PDBs instead of actual databases. Each PDB can then have a user
named SYSADM and run its copy of the PeopleSoft application but without
consuming any extra memory and CPU.
Check detailed contents on
http://dbaboss.com/
12
• While these PDBs are accommodated in a single CDB, they have the many of the
individualities of a regular independent database. For instance you can set a
specific optimizer limitation to different values in different PDBs. You can, of
course, start and shutdown a PDB leaving other PDBs in the CDB unaffected. You
can back up PDBs independently, as RMAN knows which specific files are relevant
for the PDBs. You can restore individual PDBs, even perform a point in time
recovery for a PDB while the others are running.
• This allows you to create a accurate "cloud database" where you can host as
numerous databases as you want without increasing the memory and CPU
footmark. This is principally useful when you have financial limitations that prevent
creation of supplementary databases forcing difficulties in development cycles.
You can spin up a PDB very quickly to host the development effort, or even clone it
from another PDB from either the same CDB or a different one, even a different
server. This ability of creating virtual databases unfastens the database
provisioning from hardware provisioning. All the PDBs share the same resources. If
the overall request becomes too high, all you have to do add the resources to the
CDB and all the PDBs get the benefit immediately. Perhaps the biggest advantage
is seen during upgrades. Instead of upgrading multiple databases, all you have to
do is to upgrade the CDB and all PDBs in it are directly upgraded
Check detailed contents on
http://dbaboss.com/
13
Benefits
• Achieve many databases as one.
• Come across service-level prospects with
built-in workload resource management.
• Keep the isolation of separate databases
without shifting applications or access rights.
• Increase scalability and server consumption.
• Oracle multitenant databases were developed
to help companies take advantage of
virtualization.
Check detailed contents on
http://dbaboss.com/
14
• High association compactness.
The many pluggable databases in a single container database share its
memory and background processes, permitting you operate many
more pluggable databases on a precise platform than you can single
databases that use the old architecture. This is the equal profit that
schema-based association brings. But there are noteworthy barriers to
adopting schema-based consolidation, and it causes ongoing operating
problems. The new architecture removes these adoption barriers and
operating problems.
Check detailed contents on
http://dbaboss.com/
15
• Speedy provisioning and cloning using SQL.
. A pluggable database can be unplugged from one container database
and plugged into another. Instead, you can clone one, within the same
container database, or from one container database to another. These
operations, together with creating a pluggable database, are done with
new SQL commands and take just seconds. When the fundamental file
system supports thin provisioning, many terabytes can be cloned
almost instantaneously simply by using the keyword snapshot in the
SQL command
Check detailed contents on
http://dbaboss.com/
16
• New standards for rapid patching and upgrades.
The deal of time and effort to patch one container database results in
patching all of its many pluggable databases. To patch a single
pluggable database, you simply unplug/plug to a container database at
a different Oracle Database software version.
• Accomplish many databases as one.
By combining existing databases as pluggable databases,
administrators can manage many databases as one. For example, tasks
like backup and disaster recovery are performed at the container
database level.
• Vibrant between-pluggable database resource management.
Oracle Database 12c Resource Manager is extended with specific
functionality to instantly control the competition between the
pluggable databases within a container database
Check detailed contents on
http://dbaboss.com/
17
What is extra
• Unplug and Plug PDB
What is additional? We can plug out (unplug) a database from
one container database and then plug in into another container
database. This is attractive cool feature. This could be useful in
many situations. Migrating databases to new platform. Migrating
databases to new hardware. Migrating databases to new DB
releases. Moving databases to different systems. Enhancing high
availability of databases by moving between systems
Check detailed contents on
http://dbaboss.com/
18

More Related Content

PPTX
Presentation day2 oracle12c
PPTX
Presentationday3oracle12c
PPTX
Presentation day4 oracle12c
PPTX
Oracle 12c - Multitenant Feature
PPTX
Presentation day5 oracle12c
PDF
Oracle 12c PDB insights
PDF
Oracle 12c Multitenant architecture
PPTX
Database Consolidation using the Oracle Multitenant Architecture
Presentation day2 oracle12c
Presentationday3oracle12c
Presentation day4 oracle12c
Oracle 12c - Multitenant Feature
Presentation day5 oracle12c
Oracle 12c PDB insights
Oracle 12c Multitenant architecture
Database Consolidation using the Oracle Multitenant Architecture

What's hot (20)

PPTX
Simplify Consolidation with Oracle Database 12c
PDF
Exploring Oracle Database 12c Multitenant best practices for your Cloud
PPTX
Oracle 12c Multi Tenant
PDF
Oracle database 12c introduction- Satyendra Pasalapudi
PDF
Reduce planned database down time with Oracle technology
PDF
Oracle Database 12c Multitenant for Consolidation
PPTX
Database Consolidation using Oracle Multitenant
PDF
Oracle 12c and its pluggable databases
PPTX
Using oracle12c pluggable databases to archive
PDF
Plugging in oracle database 12c pluggable databases
PPTX
Oracle 12c Architecture
PDF
Oracle database 12c intro
PDF
Oracle database high availability solutions
PDF
RMAN in 12c: The Next Generation (WP)
PDF
DBA 101 : Calling all New Database Administrators (WP)
PDF
12 Things about Oracle WebLogic Server 12c
PDF
RMAN in 12c: The Next Generation (PPT)
PDF
Oracle 12.2 sharded database management
PPTX
Product Update: EDB Postgres Platform 2017
 
PPTX
Oracle database upgrade to 12c and available methods
Simplify Consolidation with Oracle Database 12c
Exploring Oracle Database 12c Multitenant best practices for your Cloud
Oracle 12c Multi Tenant
Oracle database 12c introduction- Satyendra Pasalapudi
Reduce planned database down time with Oracle technology
Oracle Database 12c Multitenant for Consolidation
Database Consolidation using Oracle Multitenant
Oracle 12c and its pluggable databases
Using oracle12c pluggable databases to archive
Plugging in oracle database 12c pluggable databases
Oracle 12c Architecture
Oracle database 12c intro
Oracle database high availability solutions
RMAN in 12c: The Next Generation (WP)
DBA 101 : Calling all New Database Administrators (WP)
12 Things about Oracle WebLogic Server 12c
RMAN in 12c: The Next Generation (PPT)
Oracle 12.2 sharded database management
Product Update: EDB Postgres Platform 2017
 
Oracle database upgrade to 12c and available methods
Ad

Viewers also liked (8)

PDF
Cosas que “probablemente” no sabes pero deberías de saber en Oracle 12c
PPTX
Oracle database 12c new features
PPTX
Best New Features of Oracle Database 12c
PPTX
Oracle Multitenant - organized by Orient ITM - 12 Jul 2014
PDF
Introduction to Oracle Clusterware 12c
PPSX
Oracle database 12c new features
PPS
Oracle Database Overview
PDF
Überblick zu Oracle Database 12c Release 2
Cosas que “probablemente” no sabes pero deberías de saber en Oracle 12c
Oracle database 12c new features
Best New Features of Oracle Database 12c
Oracle Multitenant - organized by Orient ITM - 12 Jul 2014
Introduction to Oracle Clusterware 12c
Oracle database 12c new features
Oracle Database Overview
Überblick zu Oracle Database 12c Release 2
Ad

Similar to Presentation day1oracle 12c (20)

PPTX
Simplify Consolidation with Oracle Pluggable Databases
PDF
DBAM-01.pdf
PDF
Database Administration & Management - 01
PPTX
apex-42-in-12c-1970039.pptx apex oracle
PDF
Oracle RAC, Oracle Data Guard, and Pluggable Databases: When MAA Meets Oracle...
PDF
Delphix database virtualization v1.0
PPTX
Introduction to NoSQL
PDF
Under The Hood of Pluggable Databases by Alex Gorbachev, Pythian, Oracle OpeW...
PPTX
MongoDB
PDF
2. Fundamentals of Databases RDMS DBMS.pdf
PPTX
Real world business workflow with SharePoint designer 2013
PDF
NA14G05 - A DB2 DBAs Guide to pureScale.pdf
PPT
Compact, Compress, De-Duplicate (DAOS)
PDF
Security Multitenant
PDF
What is new on 12c for Backup and Recovery? Presentation
DOCX
Db2 Important questions to read
PPTX
AzureDocumentDB
PDF
Challenges Management and Opportunities of Cloud DBA
PPTX
SQL Saturday San Diego
PDF
Consolidate and prepare for cloud efficiencies
Simplify Consolidation with Oracle Pluggable Databases
DBAM-01.pdf
Database Administration & Management - 01
apex-42-in-12c-1970039.pptx apex oracle
Oracle RAC, Oracle Data Guard, and Pluggable Databases: When MAA Meets Oracle...
Delphix database virtualization v1.0
Introduction to NoSQL
Under The Hood of Pluggable Databases by Alex Gorbachev, Pythian, Oracle OpeW...
MongoDB
2. Fundamentals of Databases RDMS DBMS.pdf
Real world business workflow with SharePoint designer 2013
NA14G05 - A DB2 DBAs Guide to pureScale.pdf
Compact, Compress, De-Duplicate (DAOS)
Security Multitenant
What is new on 12c for Backup and Recovery? Presentation
Db2 Important questions to read
AzureDocumentDB
Challenges Management and Opportunities of Cloud DBA
SQL Saturday San Diego
Consolidate and prepare for cloud efficiencies

Recently uploaded (20)

PPTX
Introduction to Basics of Ethical Hacking and Penetration Testing -Unit No. 1...
PDF
168300704-gasification-ppt.pdfhghhhsjsjhsuxush
PPTX
IBA_Chapter_11_Slides_Final_Accessible.pptx
PPT
Reliability_Chapter_ presentation 1221.5784
PDF
Galatica Smart Energy Infrastructure Startup Pitch Deck
PDF
Fluorescence-microscope_Botany_detailed content
PPTX
IB Computer Science - Internal Assessment.pptx
PPTX
AI Strategy room jwfjksfksfjsjsjsjsjfsjfsj
PPTX
oil_refinery_comprehensive_20250804084928 (1).pptx
PPTX
STUDY DESIGN details- Lt Col Maksud (21).pptx
PPTX
MODULE 8 - DISASTER risk PREPAREDNESS.pptx
PPTX
ALIMENTARY AND BILIARY CONDITIONS 3-1.pptx
PDF
BF and FI - Blockchain, fintech and Financial Innovation Lesson 2.pdf
PPTX
Acceptance and paychological effects of mandatory extra coach I classes.pptx
PPTX
Microsoft-Fabric-Unifying-Analytics-for-the-Modern-Enterprise Solution.pptx
PPTX
Supervised vs unsupervised machine learning algorithms
PDF
Clinical guidelines as a resource for EBP(1).pdf
PDF
TRAFFIC-MANAGEMENT-AND-ACCIDENT-INVESTIGATION-WITH-DRIVING-PDF-FILE.pdf
PPTX
iec ppt-1 pptx icmr ppt on rehabilitation.pptx
Introduction to Basics of Ethical Hacking and Penetration Testing -Unit No. 1...
168300704-gasification-ppt.pdfhghhhsjsjhsuxush
IBA_Chapter_11_Slides_Final_Accessible.pptx
Reliability_Chapter_ presentation 1221.5784
Galatica Smart Energy Infrastructure Startup Pitch Deck
Fluorescence-microscope_Botany_detailed content
IB Computer Science - Internal Assessment.pptx
AI Strategy room jwfjksfksfjsjsjsjsjfsjfsj
oil_refinery_comprehensive_20250804084928 (1).pptx
STUDY DESIGN details- Lt Col Maksud (21).pptx
MODULE 8 - DISASTER risk PREPAREDNESS.pptx
ALIMENTARY AND BILIARY CONDITIONS 3-1.pptx
BF and FI - Blockchain, fintech and Financial Innovation Lesson 2.pdf
Acceptance and paychological effects of mandatory extra coach I classes.pptx
Microsoft-Fabric-Unifying-Analytics-for-the-Modern-Enterprise Solution.pptx
Supervised vs unsupervised machine learning algorithms
Clinical guidelines as a resource for EBP(1).pdf
TRAFFIC-MANAGEMENT-AND-ACCIDENT-INVESTIGATION-WITH-DRIVING-PDF-FILE.pdf
iec ppt-1 pptx icmr ppt on rehabilitation.pptx

Presentation day1oracle 12c

  • 1. Oracle 12c Multitenant Architecture Introduction of CDB and PDB Databases (Reference – Oracle documentation) 1
  • 2. What is Multitenant • Multi-tenancy is an design in which a single instance of a software application serves multiple customers. Each client is called a tenant. • With a multitenant architecture, a software application is designed to provide all tenant a committed share of the instance including its data, configuration, user management, tenant individual functionality and non-functional possessions. Check detailed contents on http://dbaboss.com/ 2
  • 3. • It has been an organizational outlandish when multiple databases are running in one machine. The backups need to be run independently. Each database has memory footmark and each database has background processes. This increases the capacity of the server on what it can lever in terms of the loads. By joining into one container database and at the same time keeping all of them as separate databases are a great thing from association, performance, capacity and operational perspective. This is going to help in a very big way for consolidation on many enterprises and at the same time it will reduce the server footprint significantly giving the maximum Return on Investments (ROI) on the middleware database technologies. Check detailed contents on http://dbaboss.com/ 3
  • 4. Oracle 12c Multitenant Architecture Overview • A new selection for Oracle Database 12c, Oracle Multitenant supplies a new architecture that allows a multitenant container database to hold many pluggable databases. At present database can simply be accepted with no application changes required. Oracle Multitenant fully complements other options, including Oracle Real Application Clusters and Oracle Active Data Guard. Check detailed contents on http://dbaboss.com/ 4
  • 5. • The multitenant architecture empowers 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 transportable collection of schemas, schema objects, and nonschema objects that appears to an Oracle Net client as a non-CDB. All Oracle databases before Oracle Database 12c were non-CDBs. Check detailed contents on http://dbaboss.com/ 5
  • 6. What is CDB, PDB and Seed Database • Container Database (CDB): The primary database that comprises numerous plugged-in databases. Numerous operations can be performed at the container level to reduce management costs. A database is generated as either a CDB or a non-CDB. On the apparent this seems very similar to a conventional Oracle database, as it contains most of the working parts you will be already familiar with (control files, data files, undo, tempfiles, redo logs etc.). It also lines the data dictionary for those objects that are owned by the root container and those that are visible to all PDBs. A container is a pool of schemas, objects, and related structures in a multitenant container database (CDB) that appears logically to an application as a separate database. Within a CDB, each container has a unique ID and name. It also called root container. Check detailed contents on http://dbaboss.com/ 6
  • 7. • Pluggable Database (PDB): A set of schemas, objects, and non-schema objects that can be plugged and unplugged from a container database. The PDB appears to Oracle Net and end users as a Non cdb database in and of itself but is actually managed within a container that may have many PDBs. Since the CDB comprises most of the working parts for the database, the PDB only needs to contain information precise to itself. It does not need to worry about controlfiles, redo logs and undo etc. As an alternative it is just made up of datafiles and tempfiles to handle it's own objects. This contains it's own data dictionary, containing information about only those objects that are specific to the PDBSeed Database. PDBs isolate data and operations so that from the standpoint of a user or application, each PDB appears as if it were a traditional non-CDB. Check detailed contents on http://dbaboss.com/ 7
  • 8. • The maximum limit to the total number of Pluggable databases within a container database is close to 250. So you can have up to 250 pluggable databases or PDBs within one container database or CDB. It is clear that there is one-to-many relationship between CDB and PDBS. • (Seed PDB): A default PDB that the system uses as a template to quickly facilitate other user-created PDBs. Within, it’s called PDB$SEED • Below picture refer in Oracle docs Check detailed contents on http://dbaboss.com/ 8
  • 9. Check detailed contents on http://dbaboss.com/ 9
  • 10. Check detailed contents on http://dbaboss.com/ 10
  • 11. Check detailed contents on http://dbaboss.com/ 11
  • 12. • The new multitenancy choice in Oracle Database 12c that permits you to create several virtual databases (PDB) called pluggable databases or containers in a single physical database called container database (CDB). The CDB is the one that has the Oracle instance connected with it, i.e. it has the background processes such as pmon, smon and the memory areas such as buffer cache and large pool. The PDBs do not have their own instance; but take up house inside the CDB, with some extra storage private to them. This preparation permits you to address the PDBs as independent databases. So you can create a user called, say, DBABOSS in every PDB, as an alternative of creating a new database for creating these users. This is highly useful in case of applications that require a specifically named schema, e.g. PeopleSoft have need of a user so-called SYSADM. If you want to place numerous PeopleSoft applications inside one database, you can't, since you can't create more than one user with the name SYSADM. So you had to resort to producing several databases to hold several copies of the application. Each of these databases had its own memory and resource overheads. In a multitenancy model you can create several PDBs instead of actual databases. Each PDB can then have a user named SYSADM and run its copy of the PeopleSoft application but without consuming any extra memory and CPU. Check detailed contents on http://dbaboss.com/ 12
  • 13. • While these PDBs are accommodated in a single CDB, they have the many of the individualities of a regular independent database. For instance you can set a specific optimizer limitation to different values in different PDBs. You can, of course, start and shutdown a PDB leaving other PDBs in the CDB unaffected. You can back up PDBs independently, as RMAN knows which specific files are relevant for the PDBs. You can restore individual PDBs, even perform a point in time recovery for a PDB while the others are running. • This allows you to create a accurate "cloud database" where you can host as numerous databases as you want without increasing the memory and CPU footmark. This is principally useful when you have financial limitations that prevent creation of supplementary databases forcing difficulties in development cycles. You can spin up a PDB very quickly to host the development effort, or even clone it from another PDB from either the same CDB or a different one, even a different server. This ability of creating virtual databases unfastens the database provisioning from hardware provisioning. All the PDBs share the same resources. If the overall request becomes too high, all you have to do add the resources to the CDB and all the PDBs get the benefit immediately. Perhaps the biggest advantage is seen during upgrades. Instead of upgrading multiple databases, all you have to do is to upgrade the CDB and all PDBs in it are directly upgraded Check detailed contents on http://dbaboss.com/ 13
  • 14. Benefits • Achieve many databases as one. • Come across service-level prospects with built-in workload resource management. • Keep the isolation of separate databases without shifting applications or access rights. • Increase scalability and server consumption. • Oracle multitenant databases were developed to help companies take advantage of virtualization. Check detailed contents on http://dbaboss.com/ 14
  • 15. • High association compactness. The many pluggable databases in a single container database share its memory and background processes, permitting you operate many more pluggable databases on a precise platform than you can single databases that use the old architecture. This is the equal profit that schema-based association brings. But there are noteworthy barriers to adopting schema-based consolidation, and it causes ongoing operating problems. The new architecture removes these adoption barriers and operating problems. Check detailed contents on http://dbaboss.com/ 15
  • 16. • Speedy provisioning and cloning using SQL. . A pluggable database can be unplugged from one container database and plugged into another. Instead, you can clone one, within the same container database, or from one container database to another. These operations, together with creating a pluggable database, are done with new SQL commands and take just seconds. When the fundamental file system supports thin provisioning, many terabytes can be cloned almost instantaneously simply by using the keyword snapshot in the SQL command Check detailed contents on http://dbaboss.com/ 16
  • 17. • New standards for rapid patching and upgrades. The deal of time and effort to patch one container database results in patching all of its many pluggable databases. To patch a single pluggable database, you simply unplug/plug to a container database at a different Oracle Database software version. • Accomplish many databases as one. By combining existing databases as pluggable databases, administrators can manage many databases as one. For example, tasks like backup and disaster recovery are performed at the container database level. • Vibrant between-pluggable database resource management. Oracle Database 12c Resource Manager is extended with specific functionality to instantly control the competition between the pluggable databases within a container database Check detailed contents on http://dbaboss.com/ 17
  • 18. What is extra • Unplug and Plug PDB What is additional? We can plug out (unplug) a database from one container database and then plug in into another container database. This is attractive cool feature. This could be useful in many situations. Migrating databases to new platform. Migrating databases to new hardware. Migrating databases to new DB releases. Moving databases to different systems. Enhancing high availability of databases by moving between systems Check detailed contents on http://dbaboss.com/ 18