This document discusses Oracle Database 19c and the concept of a converged database. It begins with an overview of new features in Oracle Database 19c, including direct upgrade paths, new in-memory capabilities, and improvements to multitenant architecture. It then discusses the concept of a converged database that can support multiple data types and workloads within a single database compared to using separate single-purpose databases. The document argues that a converged database approach avoids issues with data consistency, security, availability and manageability between separate databases. It notes Oracle Database's support for transactions, analytics, machine learning, IoT and other workloads within a single database. The document concludes with an overview of Oracle Database Performance Health Checks.
15. Multitenant – Licensing Changes
• For all offerings using Oracle Database 19c, if you are not licensed for
Oracle Multitenant, then you may have up to 3 PDBs in a given
container database at any time
• EE: Extra cost option – if you are licensed for Oracle Multitenant, then
you can create up to 252 PDBs.
• Exadata and ODA: Extra cost option – if you are licensed for Oracle
Multitenant, then you can create up to 4096 PDBs
• DBCS EE-HP, DBCS EE-EP, and ExaCS: Included option – you can
create up to 4096 PDBs
Oracle Database 19c New Features
15
18. Oracle NoSql EE – Licensing Changes
• The Oracle Database Enterprise Edition(EE) license now
includes Oracle NoSQL Database Enterprise Edition.
• Any customer who purchases or has purchased an Oracle Database
Enterprise Edition (DB EE) license is entitled to download and use
Oracle NoSQL Database Enterprise Edition(EE).
• Support for Oracle NoSQL Database Enterprise Edition would be
included as part of the DB EE support contract if support was
purchased.
https://blogs.oracle.com/nosql/oracle-nosql-database-version-201-is-now-available
https://docs.oracle.com/en/database/oracle/oracle-database/19/dblic/Licensing-Information.html#GUID-0F9EB85D-4610-4EDF-89C2-
4916A0E7AC87
Oracle Database 19c New Features
18
20. Next Generation Data Driven Applications
• Modern Applications require many different:
• Data Types - Relational, Document, Spatial, Graph, time, etc.
• Workloads - Transactions, analytics, ML, IoT, etc.
• Each data type and workload requires different database algorithms
to effectively manage the data and turn in into information
• Two possible Architectural Strategies:
• Use single-purpose “best-of-breed” databases for each data type and
workload
• Use a converged database for all data types and workloads
20
27. Fragmentation: It’s Harder To Develop
• Single-purpose databases require apps to use their proprietary APIs, languages, and transactions
models instead of standards like SQL
• Fragments development, locks-in the application to the single-purpose database and limits the
development tool that can be used
27
28. Fragmentation: It’s Harder To Manage
• Each single-purpose database has different operational needs and limitations, requiring unique
management and skills
28
29. Fragmentation: Data Consistency And Metadata Management
• Must continually transform data and propagate changes between applications and between single-
purpose databases
• Change propagation is inherently difficult and causes unavoidable data delays and data divergence
29
EVENT
RPC
ETL
REPLICATION
DB LINKS
EVENT
RPC
ETL
REPLICATION
DB LINKS
EVENT
RPC
ETL
REPLICATION
DB LINKS
EVENT
RPC
ETL
REPLICATION
DB LINKS
30. Fragmentation: Opens To Data Security Breaches
• Each single-purpose database has a different (and often primitive) security model and functionality
• Must separately implement security policies in every database, and re-implement in every database
when app or policies change
• Each database may not support all security policies
30
31. Fragmentation: Availability and Scalability
• Must make each single-purpose database Highly Available and Scalable using mechanisms specific
to each product
• Cannot provide a consistent SLA, RTO, or RPO across databases
31
32. Fragmentation: Your Best Is Your Weakest
• End-to-End security, availability, scalability, consistency, etc. is limited in each area by the weakest of the
databases that are used
• Combining “best-of-breed” gives “worst-of-weaknesses”
32