Oracle on Azure IaaS 2023

1. © Microsoft Corporation
Oracle Solutions on Azure
KellynGorman–PrincipalCloudSolutionArchitect
CustomerSuccess–AzureInfrastructure

2. © Microsoft Corporation
*Two Azure Government Secret region locations undisclosed
60+
Regions worldwide
Available in
140
Countries

3. © Microsoft Corporation
Compute Services
Integration
Media & CDN Application Platform
Developer Services
Datacenter Infrastructure
Platform Services
Compute Storage
Hybrid
Cloud
Backup
StorSimple
Azure Site
Recovery
Import/Export
Networking
Data
SQL
Database
Redis
Cache
Azure AD
Health Monitoring
AD Privileged
Identity
Management
Operational
Analytics
Cloud
Services
Batch RemoteApp
Visual
Studio
Domain Services
Analytics & IoT
Data Lake
Analytics Service
IoT Hub
Security & Management
Azure Active
Directory
Multi-Factor
Authentication
Automation
Portal
Key Vault
Store/
Marketplace
VM Image Gallery
& VM Depot
Azure AD
B2C
Scheduler
Xamarin
HockeyApp
Power BI
Embedded
SQL Server
Stretch
Database
Intelligence
Cortana
Security Center
Container
Service
VM
Scale Sets
Data Lake
Store
BizTalk
Services
Service Bus
Logic
Apps
API
Management
HDInsight
Machine
Learning
Content Delivery
Network
Mobile
Engagement
Application
Insights
Event
Hubs
Stream
Analytics
API
Apps
CosmosDB
Web
Apps
Mobile
Apps
Bot Framework
Azure
Search
Notification
Hubs
Service
Fabric
Media
Services
VS Team
Services
Media
Analytics
Data
Factory
Functions
Cognitive
Services
Storage
Tables
Data
Catalog
Virtual Machines Containers App Gateway
Virtual Network Express Route Traffic Manager
DNS VPN Gateway
Load Balancer
Blob Files
Queues Disks
Synapse

4. © Microsoft Corporation
Clients
DevOps
Management
Applications
App
Frameworks
& Tools
Databases &
Middleware
Infrastructure
AZURE IS AN OPEN CLOUD PROVIDING CHOICE + FLEXIBILITY

5. © Microsoft Corporation
GEOGRAPHIES, REGIONS, AVAILABILITY ZONES, AND DATA
CENTERS
Geographies consist of one or more regions
An Azure geography ensures that data residency, sovereignty, compliance,
and resiliency requirements are honored within geographical boundaries.
Regions consist of one or three availability zones
(AZs)
Regions are bounded by network latency
Availability zones consist of one (or more) data
centers

6. © Microsoft Corporation
AVAILABILITY SETS, FAULT DOMAINS, AND UPDATE DOMAINS
Within an availability zone,
availability sets define up to 3 fault
domains and 5 update domains to
segregate compute and storage for
high-availability
Proximity placement groups ensure
that compute nodes are as close to
each other on the Azure network as
possible, allowing for constraints
such as availability sets

7. © Microsoft Corporation
The Why of Oracle on Azure
IaaS

8. On-Premises
or
Simple Data Estate Lift, Shift, EVOLVE
The Path to the Cloud

9. Leverage Azure with IaaS options or migrate to a fully managed database for
more benefits
IaaS
Azure Virtual
Machines (IaaS)
Enterprise ready Lower TCO Built-in security
Integrated with Azure data ecosystem
Proven resilience & stability
Always on Azure
Fully managed databases
Azure Database
for PostgreSQL
Azure SQL Azure
Cosmos DB
Get more with
fully managed databases
Fully
managed
Intelligent
Performance
Highly
scalable
High
Availability
Maximum
control

10. Oracle applications supported on Azure
• Microsoft Azure offering
called FlashGrid Node for
a third-party supported
Oracle RAC solution
• OS Clustering solutions
to create similar
performing options to
Oracle RAC One-Node in
a public cloud.
BYOL license for Oracle
Database on Azure
Infrastructure-as-a-Service
• JD Edwards EnterpriseOne
versions 9.2 and above
• E-Business Suite
• WebLogic Server
• Peoplesoft
• Essbase
• Hyperion
Enterprise applications supported
running on Oracle Linux or other
supported operating systems
High availability and
disaster recovery options
Customers can choose to bring
other Oracle Databases images
as well.
DATA GUARD

11. © Microsoft Corporation
The How of Oracle on Azure
IaaS

12. © Microsoft Corporation
FIVE ARCHITECTURAL PILLARS IN AZURE IAAS FOR ORACLE
DATABASE
1. Compute
2. Storage
3. Backups
4. High Availability
5. Disaster resilience

13. © Microsoft Corporation
VIRTUAL MACHINES FOR ORACLE DATABASES
Type vCPUs vRAM Max throughput (MBps) for
SCSI storage
Max IP egress rate (Mbps) for
NFS, iSCSI storage
Dds_v4 2-64 8-256 125-4000 1000-30000
Eds_v4 2-80 16-504 125-4000 1000-30000
Ms_v2 32-192 875-4096 500-2000 8000-30000
Mv2 208-416 2840-11400 1000-2000 16000-32000
Dds_v5 2-96 8-384 125-4000 12500-35000
Eds_v5 2-104 16-672 125-8000* 10000-100000
Ebds_v5* 2-64 16-512 125-4000 12500-20000
Epds_v5* 2-32 16-208 85-2000 12500-16000

14. © Microsoft Corporation
DATABASE STORAGE
Protocol Max Throughput (MBps) Min Latency (ms) Pricing Notes
Premium SSD SCSI 900/device,
Dependent on VM limit
0.7 w/ host-caching,
2 w/o host-caching
$ Snapshot capable, bursting capable,
LRS/ZRS redundancy
UltraDisk SCSI 2000/device,
Dependent on VM limit
1 $$ No snapshots, LRS redundancy- Used
mostly for Redo logs
Azure Files
premium
NFS v4.1 100 + (0.1 * GiB-provisioned) 1 $$ No snapshots, LRS/ZRS redundancy
Azure NetApp
Files
NFS v3.0
NFS v4.1
4500 0.25 $$$ Snapshot capable, LRS/GRS
redundancy
SILK iSCSI 11000
16000 max with multi-VM
0.5 $$$ Snapshot capable, thin cloning,
LRS/ZRS redundancy
ElasticSAN iSCSI 11000 per VM
32000 max with multi-VM
0.5 $$$ No snapshots, LRS/ZRS redundancy,
no clone capabilities
ANF Application
Volume
Group(AVG)
iSCSI 11000 per VM
31000 max with multi-VM
0.25-.5 $$$ Brand new, used mostly for SAP
Hana, now for Oracle.

15. ©Microsoft Corporation Azure
Availability Zone1
Why RAC Isn’t HA in Azure
Passive or Active
Dataguard
Azure VNET
Availability Zone2
OracleDB1
(primary 3-node
RAC)
Shared Storage
(Oracle ASM)
OracleDB2
(standby)
Premium Storage
(Oracle ASM)
Observer1
Observer2
Oracle Cloud Control
Redo Stream
(async)
FrontEnd1
FrontEnd2
AppServer1
Azure Premium Files
Backups
Oracle Data Guard
AppServer2

16. ©Microsoft Corporation Azure
Availability Zone1
If AZ1 Suffers Outage, RAC and Shared Storage has Outage, Must
Manually Failover with DataGuard
Passive or Active
Dataguard
Azure VNET
Availability Zone2
OracleDB1
(primary 3-node
RAC)
Shared Storage
(Oracle ASM)
OracleDB2
(Becomes Primary)
Premium Storage
(Oracle ASM)
Observer1
Oracle Cloud Control
Redo Stream
(async)
FrontEnd1
FrontEnd2
AppServer1
Azure Premium Files
Backups
Oracle Data Guard
AppServer2

17. ©Microsoft Corporation Azure
Oracle DataGaurd with FSFO, 99.995 for Database and <1 min recovery
Passive or Active
Dataguard
Azure VNET
Availability Zone1 Availability Zone2 Availability Zone3
OracleDB1
(primary)
Premium Storage
(Oracle ASM)
OracleDB2
(Active standby)
Premium Storage
(Oracle ASM)
Observer1 Observer2
Oracle Cloud Control
Redo Stream
(async)
FrontEnd1
FrontEnd2
AppServer1
AppServer2
Azure Premium Files
Far Sync Instance
(Optional)
Oracle Data Guard is configured with Fast-
start Failover

18. © Microsoft Corporation
DISASTER RESILIENCY OPTIONS
Oracle DataGuard or Active DataGuard with FSFO, TAF, and FarSync options for
active/passive redundancy
Oracle GoldenGate with one-way replication for active/passive redundancy or multi-master
replication for active/active redundancy
Azure Site Recovery* is a service by which all data changes made to storage are
propagated to a storage account with RA-GRS redundancy. Upon failure, the replicated
storage account can be used to clone VMs in the other region
*only suitable for VMs with less than 100 MBps throughput

19. © Microsoft Corporation
OPTIMIZE YOUR CLOUD SPENDING
Reduce Oracle licensing liability with
Constrained Core vCPUs
Azure offers certain VM sizes with constrained VM vCPU
count to reduce the cost of software licensing, while
maintaining the same memory, storage, I/O bandwidth,
and network bandwidth Oracle database workloads
require.
VM Type
vCPUs
alloc’d
vCPUs
active’d
vCPUs
charged by
Azure
vCPUs
licensed by
Oracle
Standard_E32ds_v4 32 32 32 32
Standard_E32-8ds_v4 32 8 32 8
Reduce your computing costs with Azure
Reserved VM Instances (RIs)
Reserved virtual machines for 1-year or 3-years and
save up to 62-72 percent vs PAYG

20. © Microsoft Corporation
LICENSING ORACLE
PRODUCTS
IN AZURE
For example: The intel core factor is 0.5, so an 8 core physical box
requires 4 cores of licensing. In Azure an 8 core VM (16 vCPUs
Hyperthreaded or 8 vCPUs non-hyperthreaded) requires 8 cores of
licensing.
According to Oracle
“When counting Oracle Processor license requirements in Authorized
Cloud Environments, the Oracle Processor Core Factor Table is not
applicable. For the purposes of licensing Oracle programs in an
Authorized Cloud Environment (Azure), customers are required to count
as follows - count two vCPUs as equivalent to one Oracle Processor
license if hyperthreading is enabled, and one vCPU as equivalent to one
Oracle Processor license if hyperthreading is not enabled.”
http://www.oracle.com/us/corporate/pricing/cloud-licensing-
070579.pdf

21. © Microsoft Corporation
LICENSING ORACLE PRODUCTS WITHIN AZURE
Do NOT accept statements about licensing or supporting Oracle products on Azure from
Oracle account teams
Insist that Oracle’s corporate License Management Services (LMS) team be consulted when
encountering any suspicious or unreasonable assertions

22. When an
Exadata
Migrates
• Purchase of Exadata was most likely
made due to 1-2 large databases.
• Rest of databases were consolidated to
make the most of the investment.
• Due to the Exadata features, there will
be hesitancy and one database will be
chosen for a POC to assess and migrate
to a public cloud.
• One Database assessment grants a view
into much of the Exadata workloads.

23. What is Oracle Exadata?
• An Engineered hardware and software solution specifically designed to run Oracle workloads
• Consists of database and cell nodes, (servers), infiniband, (fast network), PDU, (power) in a rack configuration.
• Proprietary features:
• Offloading, (using cell nodes to perform high IO workloads instead of the primary database nodes.
• Storage indexes, (indexes in memory only.)
• Result cache for faster buffer results
• Flash cache and flash logging.
• HCC, (Hybrid Columnar Compression) for faster scans of compressed data
• Can use Oracle RAC or instance caging for single database
• Software intelligence installed to know when to use Exadata features to benefit the workload

24. Can Exadata be Built in
Azure?
As Exadata is an engineered system, this solution can’t be run
inside an Azure datacenter, but-
• With Oracle Dataguard as a single Oracle instance with the
correctly scaled VM
• With Oracle Dataguard instead of RAC or use Flashgrid to use
a vendor supported solution.
• Using Goldengate or another migration with a peer-to-peer
sync solution, dual databases.
• Load balancing between Oracle database
instances.
• materialized views
• Index additions
• Compression storage solutions.

25. How is Exadata Different?
Exadata Feature Oracle from Exadata to Azure
The Oracle Exadata is an engineered system for Oracle workloads that delivers the
highest levels of database performance available. An Exadata is a “cloud in a box”
composed of database servers, Oracle Exadata Storage Servers, an InfiniBand fabric
for storage networking and all the other components required to host an Oracle
Database, along with engineered features such as cell offloading for increased IO
performance, storage indexes, Hybrid Columnar Compression, (HCC), flash cache
and logging, storage snapshots, thin cloning and other features that will benefit
workloads designed to use them.
This will be replaced with Azure VM and customers can choose what is best
suitable for their workload. Identifying the workload demand is essential and it’s
crucial not to attempt to lift and shift the Exadata hardware- it’s not a lift and
shift option, but the database workloads must be “decoupled” from the
engineered system.
Patching – Managed by Oracle contract
Patching – As it is an IaaS based solution, customers will be responsible for Oracle
level Patching, but can use Oracle Enterprise Manager lifecycle management pack
to automate OS and Oracle patching.
Cell Offloading - The storage in the Exadata Database Machine is not just dumb
storage. The storage cells are intelligent enough to process some workload inside them,
saving the database nodes from that work. This process is referred to as cell offloading.
Storage options in Azure such as Azure NetApp Files , Silk or Elasticsan can
supplement the IO demands that Exadata workloads require.
Storage indexes that will need to be physically created that currently only exist in
memory for smart scans. Smart Scan is a subset of Cell Offload Processing and is
perhaps the feature that is most highly associated with Exadata. Smart Scan allows
Oracle databases to push query information down to the storage level, specifically:
Filtration (predicate information)
Storage Indexes aren’t possible in Azure, but physical Indexes and automatic
indexing in 19c can assist in creating what may be missing from the workload.
Flash cache can run in Azure, Ultra disk can be used for flash logging solutions.
Hybrid Columnar Compression (HCC) enables very high level and high-
performance data compression for EDW Workloads. HCC organizes data into sets
of rows called compression units. Within a compression unit, HCC organizes the
data by column and then compresses the data.
No HCC support since it is an Exadata specific feature – Needs to be replaced
with other compression options (i.e. Advanced Row Compression) Silk has
significant compression and dedupe options that can rival HCC for Oracle
workloads in Azure and ANF offers close compression, too.
Oracle Exadata rarely houses ONE database, but most often has numerous
databases with a minority using the majority of Exadata benefiting features.
Identify what databases are not using the Exadata features for a lift and shift
option. The few that are should be decoupled carefully from the engineered
system.

26. WANT TO LEARN MORE?
• ORACLE ON AZURE IAAS WHITE PAPER
• MICROSOFT DATA ARCHITECTURE BLOG
• ORACLE ON AZURE GITHUB
• MICROSOFT LEARN- ORACLE ON AZURE

27. © Microsoft Corporation
Q&A KellynGorman
PrincipalCloudSolutionArchitect
CustomerSuccess,AzureInfrastructure
Microsoft
kegorman@microsoft.com
@DBAKevlar
https://linkedin.com/in/kellyngorman