1

Exadata Cloud at Customer on

Oracle Cloud Infrastructure:
Features and Scalability
aka
Essentials for a Successful
Exadata Cloud (at Customer)
Deployment
CAS 5075
Mathew Steinberg
Exadata Cloud at Customer Product Management
September 19, 2019
Safe Harbor

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.

Statements in this presentation relating to Oracle’s future plans, expectations, beliefs, intentions and
prospects are “forward-looking statements” and are subject to material risks and uncertainties. A detailed
discussion of these factors and other risks that affect our business is contained in Oracle’s Securities and
Exchange Commission (SEC) filings, including our most recent reports on Form 10-K and Form 10-Q
under the heading “Risk Factors.” These filings are available on the SEC’s website or on Oracle’s website
at http://www.oracle.com/investor. All information in this presentation is current as of September 2019
and Oracle undertakes no duty to update any statement in light of new information or future events.

2 Copyright © 2019 Oracle and/or its affiliates. |

Getting Customers to Production More Rapidly
Perspectives

• Exadata Cloud at Customer Product Management

• Mathew Steinberg, Exadata Cloud at Customer Product Management, Oracle

• Oracle Support Engineer

• Alpesh Kothari, PaaS Support Delivery Engineer, Oracle

• Customer, Exadata Cloud at Customer – Ford Motor Company

• Narayan Vaidyanathan, DB Engineering Lead - Global IT (Manager),
Ford Motor Company
 Essentials for a Successful Exadata Cloud
Deployment

4
5

Essentials for a Successful Exadata Cloud Deployment

• Plan

• Educate

• (Project) Manage

• OCPU Sizing
6

Planning for Success - Readiness

• Data Center Readiness
• ExaCC Configuration Information
• Networking
• Virtual Machines
• Databases, etc
• Migration
• Database, including version
• Platform: X to ExaCC
• Single Tenant to Multitenant
• New Database Features:
• Advanced Compression
• Transparent Data Encryption (TDE)
• Don’t do too much, E.g. GI/RDBMS version while migrating
• Upgrade the GI first
7

Planning for Success - Operations

• Database Management, e.g.
• Cloud Tooling (for provisioning)
• Existing tooling
• For day-day admin, monitoring, maintenance
• Key Management (Key Vault)
• Which Database options to use
• System maintenance
• Patching and Updates
• Backup and Restore
• Allow proper time for testing
• Opening an SR quickly to more quickly get more eyes on
any potential problems
8

Education
• Exadata – for customers new to Exadata
Take
• Customers new to cloud advantage
• Exadata Cloud is a service…..not all the knobs to turn of OU
• Exadata Cloud at Customer
• Database Options and new products
• Operationalize ExaCC into the customer environment – may not
match on premises practices
• New best practices
• Old habits die hard
• New workflows
Project Management
Work Together

• From Pre-Sales through Go-Live

• Be Prepared to work together

• Ensure the baton is handed off properly

9
10

Production (Prod) Workload Sizing

• On Premises (and Non-metered) Peak + Buffer
Size for the peak, plus additional
buffer = lots of idle CPU
CPU Usage

Sizing for Cloud

• Use hourly OCPU scaling for peak Buffer
• OCPUs available through OCPU Peak
Normal + Hourly Bursting
Scaling – no need to add Buffer
• Size for the normal workload CPU Usage
1

Right Size through OCPU Scaling

(Bursting) Reduces Cost
Typical OCPUs for % Time Using BYOL List % Price
OCPUs Scaling OCPU Scaling Price, Annual Reduction
($ M) Using OCPU
Scaling
76 0 0 3.50 0
52 24 5 2.45 30
36 40 10 1.84 48

• Cost Savings through OCPU Scaling

• Actual spend and savings dependent on workload profile

OCPU Scaling Reduces TCO

12

Essentials for a Successful Exadata Cloud Deployment

• Plan

• Educate

• (Project) Manage

• OCPU Sizing
Exadata Cloud at Customer on
Oracle Cloud Infrastructure:
Features and Scalability
aka
Essentials for a Successful
Exadata Cloud (at Customer)
Deployment
Alpesh Kothari
Principal Technical Analyst, PaaS Support Delivery
September 19, 2019

Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

 Agenda

1 ExaCC Customer / Oracle Roles & Responsibilities

2 ExaCC Oracle Responsibilities
3 ExaCC Customer Responsibilities

14 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

ExaCC: Roles and Responsibilities

15 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Secure Isolation: Customer & Ops Management
Customer Network

Control Plane
DB VM DB VM orchestrates
Oracle Cloud Agent Agent DB VM via
Infrastructure Dom0 Dom0
REST Calls to
Agent - no ssh
Control REST

Plane access!

Internet Internet Server Admin

Gateway IB Switch
VPN Control Switch Data files
Plane protected by
Server TDE
Customer Managed
Ops accesses
Oracle Managed control plane
Storage Storage Storage
Server Server Server
Oracle Managed (IB Fabric) server over
VPN for
maintenance
7 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential
 Agenda

1 ExaCC Customer / Oracle Roles & Responsibilities

2 ExaCC Oracle Responsibilities
3 ExaCC Customer Responsibilities

18 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Update Schedule and Communications
Question: How does the patching notification work?
• Once Patch Event is scheduled
• MOS Service Request(SR) created with Customer CSI.
• Customer can view and follow-up via SR
• Typically happens 45-60 days in advance of the Patch Event date.
• Once SR is created
• The first notification will be sent out to the customer contact on file.
• Reminder notification will be sent 40 days before, 7 days before and 1
day before the Patch Event date.

19 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Update Schedule and Communications
Question: How can a customer know if they are scheduled
for the patching event?
• Via patch notification e-mail to customer contact on file
• Patch notification e-mail sent out about 45-60 days in advance.
• To be added to the patch event notification e-mails, send an
email to patching team alias
plat_cloudatcustomer_scheduler_grp@oracle.com with e-mail
addresses.

11 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Update Schedule and Communications
Question: Do I have an ability to change the scheduled
date and request a specific date for the update event?
• With scheduled Patch Events
• Resources are planned and allocated, Requesting a specific date is not
feasible / advisable
• Changing date may significant delays before scheduled again.
• If customer absolutely cannot meet the scheduled date
• Reply back to patching team alias -
plat_cloudatcustomer_scheduler_grp@oracle.com describing the
specific situation to request an exception.
• Oracle Patching team will get back to you with proposal.

12 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Update Schedule and Communications
Question: Is there any outage during the upgrade or
Patching process? Can you elaborate?
• During Infra. patching
• Service outage or network impact is not expected
• For cell and IB patching no outage is required.
• For compute node (Dom0) patching, rolling outages are required.
• RAC DB - no outage for DB service; only the database instance will go
down in rolling fashion.
• Non-RAC DB - needs to plan for outage or fail over to surviving node.
• During OCC patching
• Possible interruption to the Cloud UI which will be communicated in the
Cloud Notification email with specific details.

13 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

ExaCC FAQ

FAQ: Infrastructure Patching in Oracle Exadata Cloud at Customer (Doc ID 2573573.1)

FAQ: Patching Oracle Database Server. (Doc ID 1446582.1)

23 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

 Agenda

1 ExaCC Customer / Oracle Roles & Responsibilities

2 ExaCC Oracle Responsibilities
3 ExaCC Customer Responsibilities

15 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Life Cycle Management
Upgrading DBaaS Tool, GI/RDBMS Software and ExaCC DomU OS

1 Updating ExaCC DB Node – DBaaS Tool (Cloud Tooling)

2 Updating ExaCC DB Node – GI and DB Software
Using DB Service Console – Cloud UI
Using CLI – exadbcpatchmulti
3 Updating ExaCC DB Node – DomU Exadata Software

16 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

ExaCC DB Node – DBaaS Tool (Cloud Tooling)
Tools and Utilities provided by the dbaastools_exa rpm a.k.a. Cloud Tooling
• DBaaS Tools is used by all of the DB service related Cloud automation
functions
• Important: Required to use the latest version before any activity
• Creating and deleting DB Services, Patching, Configure Backup and many
more
• DBaaS Tool is released frequently and generally contains new functionality
& important fixes
• DBaaS Tools include exadbcpatch, exadbcpatchmulti, dbaascli, dbaasapi etc...
• No UI to upgrade DBaaS Tool – exadbcpatch, dbaascli command to upgrade
• Can setup auto RPM upgrade to auto upgrade when new release available

17 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

DBaaS Tool – Release and Availability
New DBaaS Tool is released • DBaaS Tools
by ExaCC development
• Generally released once or twice every month
(Internal Only MOS Doc ID
2404336.1) • Latest version available within 2-3 days of release
• Average size of DBaaS tool 300-400 MB
+ 2-3 days
• Staging process is automated once new release
available
Cloud Ops Downloads
DBaaS Tool to Customer • Automation takes care for 70% of customer
OCC Core Nodes • Manual intervention required in case of 30% of
customer
Cloud Ops Stages DBaaS
Tool to OSS on customer • Updating the Cloud Tooling for Exadata Cloud
OCC Environment (Doc ID 2495335.1)

* All timelines are approximate

18 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

ExaCC DB Node – GI and DB Software
New PSU is made available • GI and DB Software
for Exadata (Doc ID • GI/DB PSUs released Every Quarter
888828.1)
• Latest version available around 1 month of release
+ 1 month* • Average size of GI/DB PSUs approx. 40 GB
Exadata Cloud • Oracle downloading and staging to customer OSS
Development Team once new Quarterly PSU available
Certifies PSU for Cloud • Oracle working to institute end to end automation
(Doc ID 2333222.1)
(Download & Staging) of Quarterly PSUs
+ 2 Weeks* • Automation takes care for 70% of customer

Cloud Ops Downloads • Manual intervention required in case of 30% of

PSU to Customer OCC customer
Core Nodes • Exadata Database Machine and Exadata Storage
Server Supported Versions (Doc ID 888828.1)
Cloud Ops Stages PSU
to Customer OCC OSS • Exadata Cloud Service Software Versions (Doc ID
2333222.1)
* All timeframes are approximate
19 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential
ExaCC DB Node – DomU Exadata Software
New DomU OS Image is • Exadata Software
made available for Exadata • DomU OS Images released once a month
(Doc ID 888828.1) • 18.1.4.4 Control Plane release provides feature to allow

+ 1 month* customers to apply DomU OS images from Cloud UI

Exadata Cloud • Average size of DomU Exadata S/W approx. 9 GB
Development Team • Oracle downloading and staging to customer OSS
Certifies DomU OS Image once new DomU Exadata S/W available
for Cloud (Doc ID 2333222.1)
• The current process of download & staging is entirely
manual which implies that it may be faster for you to
use manual download method to apply DomU OS
Cloud Ops Downloads image
DomU OS image to
Customer OCC Core • Exadata Cloud Service Software Versions (Doc ID
Nodes 2333222.1)
Cloud Ops Stages DomU • How to update the Exadata Image (OS) in Exadata Cloud
OS Image to Customer at Customer (Doc ID 2391164.1)
OCC OSS
* All timeframes are approximate
20 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential
ExaCC DB Node – DomU Exadata Software
Question: How do I know what DomU OS Image version is
available to apply in my Cloud environment?
• Screenshot shows Screen where the DomU OS image version available to
apply with Control Plane version 18.1.4.4. Prior version, only way to apply
Exadata image to DomU via manual method explained in MOS Note
2391164.1

21 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

ExaCC: EXAchk and HealthCheck
• Critical for Software maintenance planning
• EXAchk will execute checks specific to DomU DB node,
GI and DBs
• Incorrect configurations & Parameter Issues
• Recommendations, steps to correct, along with current
value
• Checks for the Configuration best practices & Critical
issues exposure
• Provides an HTML report for review
• Recommended to run during planning phase and
pre/post patching
• Automate EXAchk via Enterprise Manager

Oracle Exadata Database Machine EXAchk or HealthCheck (Doc ID 1070954.1)

Exadata Cloud SRDC: Exachk Collection (Doc ID 2094708.1)
22 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential
Learn and Apply Knowledge
https://docs.oracle.com/en/cloud/cloud-at-customer/exadata-cloud-at-
Product Documentation
customer/
https://www.oracle.com/webfolder/technetwork/tutorials/Architecture_Dia
Technical Architecture
grams/ecc_arch/ecc_arch.html
https://www.oracle.com/technetwork/database/exadata/learnmore/index.
Data Sheets
html
https://cloud.oracle.com/en_US/database/exadata-
Key Features
cloudatcustomer/features
https://docs.oracle.com/en/cloud/cloud-at-customer/exadata-cloud-at-
Patching Exadata
customer/exacc/patch.html
Frequently Asked https://docs.oracle.com/en/cloud/cloud-at-customer/exadata-cloud-at-
Questions customer/exacc/faqs-this-service.html
https://www.oracle.com/database/technologies/high-availability/exadata-
MAA Best Practices -
maa-best-practices.html
https://docs.oracle.com/en/cloud/cloud-at-customer/exadata-cloud-at-
Migration to ExaCC
customer/exacc/mig-migration-methods.html

23 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Reference Documents
• Oracle Cloud at Customer: Information Center for Customers (Doc ID 2504209.1)
• Exadata Cloud Service Software Versions (Doc ID 2333222.1)
• Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID
888828.1)
• Migration to Exadata Cloud using Simple Data Guard Approach with Minimal Downtime
(Doc ID 2386116.1)
• Oracle Exadata Database Machine EXAchk or HealthCheck (Doc ID 1070954.1)
• Exadata Cloud SRDC: Exachk Collection (Doc ID 2094708.1)
• Cloud Health Check Report For DBCS, ExaCS and ExaCC (Doc ID 2468356.1)
• Updating Cloud Tooling for ExaCC – MOS Doc 2495335.1
• How to update the Exadata Image (OS) in Exadata Cloud at Customer (Doc ID 2391164.1)
• Known Issues for Oracle Database Exadata Cloud at Customer (Doc ID 2252305.1)
• Exadata Critical Issues (Doc ID 1270094.1)

24 Copyright © 2019 Oracle and/or its affiliates. | Oracle Confidential

Oracle ExaCC Offering and ZDLRA
Implementation
34
 Oracle Databases – Legacy Hosting
Background

• ExaCC scoped for Enterprise Data Center hosted Intel x86 based databases

• 1000+ Oracle database instances hosted on 250+ servers

• 4 Oracle DB versions (Oracle 10g to 11g) hosted on 5 different SuSE OS versions

• Sub-optimal database backup, restore and clone runtimes

• Performance, outages and scalability issues

• Minimal downtime availability to perform maintenance

• Long lead time and high cost to refresh tech portfolio

35
 Oracle ExaCC Offering
Service Improvement Opportunities
• On Prem Oracle ExaCC database offering
• Opportunity to achieve database consolidation using Multitenant feature
• One Vendor ExaCC solution – server, database, monitoring and backup
• High-availability using RAC
• Disaster recovery solution for candidate applications using Active DataGuard
• Faster database provisioning and cloning using GOLD copy PDB
• Reduced rack and floor space
• Incremental Forever backup with ZDLRA
• Oracle’s Audit Vault and Database Firewall for security compliance

No POC – Just Do It!

36
 Oracle ExaCC Offering

Standard Compute Attributes ExaCC Legacy

Portal based provisioning for pre-approved architecture ✓

Automatic High Availability (for candidate apps) ✓

Higher Service model ✓

Capacity: Elastic / Auto Scaling / Performance ✓

Near Full Evergreen (multitenant database) ✓

Delivering at Market speed - Hours instead of Months ✓

Highly Resilient ✓

Efficient, Continuous Backup ✓

37
 Database Options & Benefits
DB Option Feature Advantages
ExaCC • Oracle Engineered High Performance Database server
• Faster Database Provisioning
• Scalability / Bursting Capability available as option
Multitenant • High consolidation density (Reduce hardware footprint, lower DC operational cost)
• DB Portability – Unplug / Plug PDB
• Application Isolation and PDB resource management
• Development and Testing (Hot Clone PDB, Refresh PDB, PDB Relocate, Flashback PDB)
• Rapid patching and upgrades
Active Data Guard • Read-only reporting, ad-hoc queries
• Physical block corruptions automatic detection and repair
• Planned downtime is minimized (Exadata Cell Server & Database Rolling Upgrades)
ZDLRA • Incremental-Forever Backup Architecture
• Real time redo transport
• End-to-end data validation, eliminating database backup corruption
• All backup-related processing offloaded to the Recovery Appliance (compression, backup deletion,
validation, and maintenance operations)

38
 DB Migration Methods and Monitoring
• Simple to complex DB migration methods during maintenance window
• RMAN backup/restore migration from source to target using ZDLRA
• Data Guard Standby, Sync and cutover
• Datapump export/import for complex migrations

• In-flight DB upgrades during migration with application consensus

• Oracle Enterprise Monitoring for ExaCC VMs, container and PDB monitoring
• Oracle Enterprise Monitoring for ZDLRA monitoring and DB backup configuration

39
 Journey Experience
• Long lead time to enable On-prem ExaCC services – 8 to 10 weeks
• In place capacity upgrade feature for existing non-full racks not currently supported
• Challenge sizing target ExaCC DB compared to legacy non-RAC hosting
• Lack of maturity in ExaCC DB resource management capabilities
• Lack of out-of-the-box capacity metrics reporting and forecasting utilities
• Lack of exposure to Cloud Ops performance metrics data to support triage activities
• Classic growing pains – dealing with bugs, performance issues and SR engagements
• SYSDATE de-support forcing ExaCC capacity fragmentation – need for TZ dedicated containers
• More reliable fleet patching through CloudUI
• Complex hand-shake during Collab SRs leading to longer problem resolution time
• Consolidation constraints with 12c – limitations with character set and time zone at tenant level
• Pause and resume workloads to surviving RAC nodes during planned and unplanned maintenance
without incurring session/transaction loss – product enhancement feature request

40
QUESTIONS

41