Database: Level 100
Database: Level 100
Database: Level 100
Level 100
Sanjay Narvekar
Oracle Cloud Infrastructure
October 2019
© 2019 Oracle
Safe harbor statement
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver
any material, code, or functionality, and should not be relied upon in making purchasing
decisions.
The development, release, timing, and pricing of any features or functionality described for
Oracle’s products may change and remains at the sole discretion of Oracle Corporation.
© 2019 Oracle
Objectives
© 2019 Oracle
OCI Database Service
• Mission critical, enterprise grade cloud database service with
comprehensive offerings to cover all enterprise database needs Exadata
© 2019 Oracle
Virtual Machine (VM) Database (DB) Systems
• There are 2 types of DB systems on virtual machines:
– A 1-node VM DB system consists of one VM.
– A 2-node VM DB system consists of two VMs clustered with RAC enabled.
• VM DB systems can have only a single database home, which in turn can have only a single database.
• Amount of memory allocation for the VM DB system depends on the VM shape selected during the
provisioning process.
• Size of storage is specified when you launch a VM DB system and you scale up the storage as needed
at any time.
• The number of CPU cores on an existing VM DB system cannot be changed.
• If you are launching a DB system with a virtual machine shape, you have option of selecting an older
database version. Check Display all database versions to include older database versions in the drop-
down list of database version choices.
• When a 2-node RAC VM DB system is provisioned, the system assigns each node to a different fault
domain by default.
• Data Guard within and across ADs is available for VM DB systems (requires DB Enterprise Edition).
© 2019 Oracle
VM DB Systems Storage Architecture
• ASM relies on OCI Block Volume (based on NVMe) for mirroring data
ASM • Block volumes are mounted using iSCSI
• ASM uses external redundancy relying on the triple mirroring of the
DATA RECO Block Storage
• Different Block Storage volumes are used for DATA and RECO
ASM Disk Groups • Monitors the disks for hard and soft failures
+DATA, +RECO
• These actions ensure highest level availability and performance at all
times
Block Storage
• This storage architecture is required for VM RAC DB systems
© 2019 Oracle
VM DB Systems Storage Architecture – Fast Provisioning Option
ext4 File System mounts - • Linux Logical Volume Manager manages the filesystems used by the
/u01 - BITS, /u02 – DATA and database for storing database files, redo logs, etc.
/u03 - RECO
• Block volumes are mounted using iSCSI
Logical Volumes • The available storage value you specify during provisioning
determines the maximum total storage available through scaling**
Volume Groups on VM • VM RAC DB Systems cannot be deployed using this option
• Currently supports Oracle Database 18c and 19c releases
Physical Volumes on VM
Block Storage
© 2019 Oracle
Bare Metal DB Systems
Bare Metal Server X7 • Bare Metal DB Systems rely on Bare Metal servers
Oracle Database
running Oracle Linux
ASM for 12c +, ACFS for 11g
• One-node database system:
• Single Bare Metal server
DB Management Agent
• Locally attached 51 TB NVMe storage (raw)
Oracle Linux 6.8
• Start with 2 cores and scale up/down OCPUs based
on requirement
52 CPU cores
• Data Guard within and across ADs (requires DB
768 GB RAM Enterprise Edition)
51 TB NVMe raw • If single node fails, launch another system and
restore the databases from current backups
© 2019 Oracle
Bare Metal DB Systems Storage Architecture
© 2019 Oracle
Exadata DB Systems
© 2019 Oracle
Exadata DB Systems
• Oracle manages Exadata infrastructure - servers, storage, networking, firmware, hypervisor, etc.
• You can specify zero cores when you launch Exadata; this provisions & immediately stops
Exadata
• You are billed for the Exadata infrastructure for the first month, and then by the hour after that.
Each OCPU you add to the system is billed by the hour from the time you add it
• Scaling from ¼ to a ½ rack, or from ½ to a full rack requires that the data associated with
database deployment is backed up and restored on a different Exadata DB system
Resource Base System Quarter Rack Half Rack Full Rack
X6 X7 X6 X7 X6 X7
Number of Compute Nodes 2 2 4 8
Total Minimum (Default) Number of Enabled CPU
0 22 0 44 0 88 0
Cores
Total Maximum Number of Enabled CPU Cores 48 84 92 168 184 336 368
Total RAM Capacity 720 GB 1440 GB 2880 GB 5760 GB
Number of Exadata Storage Servers 3 3 6 12
Total Raw Flash Storage Capacity 38.4 TB 38.4 TB 76.8 TB 76.8 TB 153.6 TB 153.6 TB 307.2 TB
Total Raw Disk Storage Capacity 252 TB 288 TB 360 TB 576 TB 720 TB 1152 TB 1440 TB
Total Usable Storage Capacity 74.8 TB 84 TB 106 TB 168 TB 212 TB 336 TB 424 TB
© 2019 Oracle
Exadata DB Systems Storage Architecture
© 2019 Oracle
DB Systems – VM, BM, Exadata
Virtual Machine Bare Metal
Exadata
(VM) (BM)
Storage (number of CPU (amount of available CPU can be scaled within
Scaling CPU cores on VM DB storage cannot be a ¼ , ½ and Full rack.
cannot be changed) changed) Storage cannot be scaled
Yes (one edition, but
Multiple No, single DB and
different versions Yes
Homes/Databases Home only**
possible)
Local spinning disks and
Storage Block Storage Local NVMe disks
NVMe flash cards
Real Application
Available (2-node) Not Available Available
Clusters (RAC)
Data Guard Available Available Available*
*You can manually configure Data Guard on Exadata DB systems using native Oracle Database utilities and commands. dbcli is not available on Exadata
DB systems
**The database can be a container database with multiple pluggable databases, if the edition is High Performance or Extreme Performance.
© 2019 Oracle
Database Editions and Versions
VM DB BM DB Exadata DB
DB Versions
Systems Systems Systems
Standard Edition Yes Yes No
Enterprise 11.2.0.4
Yes Yes No 12.1.0.2
Edition
12.2.0.1
High
Yes Yes No 18.1.0.0
Performance
19.3*
Extreme
Yes Yes Yes
Performance
BYOL Yes
*Note that Oracle Database 19c is only available on VM DB and Exadata DB Systems (as of September 2019)
© 2019 Oracle
Database Editions and Options
Standard Edition Enterprise Edition EE High Performance EE Extreme Performance
Adds… Adds… Adds…
• Full database instance • All standard EE features Real Application Clusters (RAC)
Multitenant
• Includes Transparent • Data Masking and
Data Encryption Subsetting Partitioning
In-Memory
• Diagnostics and Tuning Advanced
Compression
• Real Application Testing
Active Data Guard
Advanced Security,
Label Security,
Database Vault
OLAP, Advanced
Analytics, Spatial
and Graph
Management
Packs
Note that all editions include Oracle Database Transparent Data Encryption (TDE)
© 2019 Oracle
Managing DB Systems
You can use the console to perform the following tasks:
• Launch a DB System: You can create a database system
• Status check: You can view the status of your database creation and after that, you can
view the runtime status of the database
• Start, stop, or reboot DB Systems
• Billing continues in stop state for BM DB Systems (but not for VM DB)
• Scale CPU cores: scale up the number of enabled CPU cores in the system (BM DB systems
only)
• Scale up Storage: increase the amount of Block Storage with no impact (VM DB systems only)
• Terminate: terminating a DB System permanently deletes it and any databases running on it
© 2019 Oracle
Patching DB Systems
• Automated Applicable Patch Discovery: Automatic patch discovery and pre-flight checks/tests
• On demand patching: N-1 patching (previous patch is available if it hasn’t been applied), pre-check
and patching at the click of a button
• Availability during patching: For Exadata and RAC shapes, patches are rolling. For single node
systems if Active Data Guard is configured this can be leveraged by the patch service.
• 2 step process – patching is a 2 step process, one for DB System and one for the database. DB
System needs to be patched first before the database is patched
• Identity and Access Controls: Granular Permissions – its possible to control who can list patches,
apply them, etc.
© 2019 Oracle
Backup / Restore
• Managed backup and restore feature for VM/BM DB Systems; Exadata backup process requires
creating a backup config file
• Backups stored in Object or Local storage (recommended: Object storage for high durability)
• DB System in private subnets can leverage Service Gateway
• Backup options
• Automatic incremental – runs once/day, repeats the cycle every week; retained for 30 days
• On-demand, standalone/ full backups
• Restore a DB
© 2019 Oracle
Automatic Backups
• By default, automatic backups are written to Oracle owned object storage (customers will not
be able to view the object store backups)
• Default policy cannot be changed at this time
• Automatic backups enabled for the first time after November 20, 2018 on any database will
run between midnight and 6:00 AM in the time zone of the DB system's region
• You can optionally specify a 2-hour scheduling window for your database during which the
automatic backup process will begin
• These are the preset retention periods for automatic backups: 7 days, 15 days, 30 days, 45
days and 60 days.
• Backup jobs are designed to be automatically re-tried
• Oracle automatically gets notified if a backup job is stuck
• All backups to cloud Object Storage are encrypted
• Link to troubleshooting backup issues https://docs.us-phoenix-
1.oraclecloud.com/Content/Database/Troubleshooting/Backup/backupfail.htm
© 2019 Oracle
High Availability and Scalability
• Robust Infrastructure
• Region with 3 Availability Domains architecture
• Fully redundant and non-blocking Networking Fabric
• 2-way or 3-way mirrored storage for Database
• Redundant Infiniband Fabric (Exadata) for cluster networking
• Database Options to enable HA
• Database RAC Option in VMs and Exadata
• Automated Data Guard within and across ADs
• Dynamic CPU and Storage Scaling
© 2019 Oracle
Oracle Data Guard
• Robust Infrastructure
• Supported on both Virtual Machine and Bare Metal DB Systems.
• Limited to one Standby database per Primary database on OCI.
• Standby database used for queries, reports, test, or backups (only for Active Data Guard)
• Switchover
• Planned role reversal, never any data loss
• No database re-instantiation required
• Used for database upgrades, tech refresh, data center moves, etc.
• Manually invoked via Enterprise Manager, DGMGRL, or SQL*Plus
• Failover
• Unplanned failure of Primary
• Flashback Database used to reinstate original Primary
• Manually invoked via Enterprise Manager, DGMGRL, or SQL*Plus
• May also be done automatically: Fast-Start Failover
© 2019 Oracle
OCI Security Features Overview for Database Service
Security capability Features
Instance security isolation BM DB Systems
Network security and access control VCN, Security Lists, VCN Public and Private subnets, Route
Table, Service Gateway
Secure and Highly-available
VPN DRGs, VPN and FastConnect
Connectivity
User authentication & authorization IAM Tenancy, Compartments and security policies, console
password, API signing key, SSH keys
Data encryption DBaaS TDE, RMAN encrypted back-ups, Local storage and
Object storage encryption at rest
End-to-end TLS LBaaS with TLS1.2, Customer-provided certificates
Auditing OCI API audit logs
© 2019 Oracle
DB Systems Demo
Pricing – Virtual Machines
Virtual Machines Metric Pay as You Go Monthly Flex
*Prices in USD, Pricing information as of June 19, 2019. Please refer to https://www.oracle.com/database/vm-cloud-pricing.html for current pricing information
© 2019 Oracle
Pricing – Bare Metal X7 – License Included
Pay as You
Bare Metal | BM.DenseIO2.52 X7 Server Metric Monthly Flex
Go
Hosted Environment Per Hour $10.746 $7.1640
Standard Edition, 2 OCPU DB License (8 Max for Standard)
*Prices in USD, Pricing information as of June 19, 2019. Please refer to https://www.oracle.com/database/bare-metal-cloud-pricing.html for current pricing
information
© 2019 Oracle
Pricing – Bare Metal X7 – Bring Your Own License (BYOL)
Pay as You
Bare Metal | BM.DenseIO2.52 X7 Database License Metric Monthly Flex
Go
Database All Editions – BYOL (2 enabled OCPUs, 2 OCPU Hosted Environment
$10.5202 $7.0135
BYOL) Per Hour
Database All Editions – Additional Capacity - BYOL OCPU Per Hour $0.2903 $0.1935
Additional OCPUs added must be in multiples of 2, Max 8
OCPUs for DB Standard Edition
*Prices in USD, Pricing information as of June 19, 2019. Please refer to https://www.oracle.com/database/bare-metal-cloud-pricing.html for current pricing
information
© 2019 Oracle
Pricing - Exadata
Monthly Flex Monthly Flex
Metric
(X6) (X7)
Base System Hosted environment per hour NA $20.1613**
• Scalability from 1 core VM to Exadata and high-availability options – Data Guard, RAC
© 2019 Oracle
Oracle Cloud always free tier:
oracle.com/cloud/free/
29 © 2019 Oracle