Oracle OpenWorld 2019S A N F R A N C I S C O

Copyright © 2019 Oracle and/or its affiliates.

The preceding 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.

Safe Harbor

Copyright © 2019 Oracle and/or its affiliates.

Maximum Availability Architecture - Best Practices for Oracle Database 19c

Lawrence To, Senior Director , MAA, Oracle

Program Agenda

• MAA Promise to our Customers• Improvements in Bronze• Improvements in Silver• Improvements in Gold• Improvements in Platinum• Cloud MAA• Q & A

4

Average cost of downtime per hour

Average cost of unplanned data center outage or disaster

Average amount of downtime per year

Percentage of companies that have experienced an unplanned data center outage in the last 24 months

Impact of Database Downtime

91%

$10M$350K

Source: Gartner, Data Center Knowledge, IT Process Institute, Forrester Research

87 hours

5

Provide the best HA, DR and data protection solution for Oracle databases

Continue to enhance validated MAA solutions

Your success is truly our success!!!

Copyright © 2019 Oracle and/or its affiliates.

MAA Solutions: On-Premises to Cloud

On-Premises

On-Premises Exadata and Recovery Appliance

DBCS/ExaCS/ExaCC

Autonomous Database

MAA Reference Architectures and Best Practices

MAA integrated Engineered Systems(config practices, exachk, lowest brownouts, HA QoS, data protection)

Adding MAA Config and Life Cycle Operations, Shifting Admin Ownership

to Oracle with MAA SLAs

7

Oracle MAA Reference ArchitecturesAlign Oracle Capabilities with Customer Service Level Requirements

Business Critical

Mission Critical

Dev, Test, Prod

Extreme Critical

Single Instance with RestartOnline MaintenanceValidated Backup/Restore

Silver +Physical ReplicationComprehensive Data Protection

Gold +Logical Active/Active ReplicationAdvanced HA Options

GOLD

BRONZESILVER

PLATINUM

Bronze +Database HAActive/Active ClusteringApplication Continuity

Maximum Availability Architecture - Best Practices for the Database 19c

Improvements in Bronze

Copyright © 2019 Oracle and/or its affiliates.

Copyright © 2019 Oracle and/or its affiliates.

Outage MatrixUnplanned Outage RTO / RPO*

Recoverable node or instance failure Minutes to hour

Disasters: corruptions and site failures Hours to days. RPO since last backup or near zero with ZDLRA

Planned Maintenance

Software/hardware updates Minutes to hour

Major database upgrade Minutes to hour

SingleInstance Database

Primary Availability Domain Secondary Availability Domain

Local Backup Replicated Backups

Dev, Test, Prod - Single Instance Database with Backups

• Single Instance with ClusterwareRestart

• Advanced backup/restore with RMAN

• Optional ZDLRA with incremental forever and near zero RPO

• Storage redundancy and validation with ASM

• Multitenant Database/Resource Management with PDB features

• Online Maintenance

• Inherent corruption protection

• Flashback technologies

BRONZE

* RPO=0 unless explicitly specified

Pluggable Database Backup, Restore and Recovery

• Backup and restore pluggable database …

• Create Restore Point ‘before_event’ for pluggable database…• Normal or Guaranteed Restore Point• Clean Restore Point

• Flashback Pluggable Database

• Complete ZDLRA support

Copyright © 2019 Oracle and/or its affiliates.

12

Recovery Appliance Recommended

CloudStorage

Remote Replica

Tape

End-to-End Oracle Recovery ValidationNear Zero Data Loss for DR

Day 1 Full

a

Day 2 Changes

Day N ChangesVirtual Full Backup

EM Real-Time Protection Status

& Space Monitoring

Day 1 StateDay 2 StateDay N State

Databases

Transactional Block Changes

No More Full Backups,Incremental Forever

Oracle DB 12c-19c on Any Platform

RA SF normally replicates to RA Austin

When Primary Appliance (RA SF) is not available, backups and redo are redirected to Replica Appliance (RA Austin)

• Virtual fulls are created as normal – full recoverability supported

• Size Replica per Recovery Window Goal (RWG) requirement:1x full backup + N RWG days of incremental and redo/arch log backups Bare minimum: 1x full backup + 1 day redo/arch logs backups.

When Primary is back online, Replica backups are transferred

• Backups are ingested and processed into virtual fulls

• Normal backups to upstream can be restarted immediately

• Virtual fulls for new backups are created after all transferred backups have completed processing

13

X

High Availability for Backup & Recovery

RA SF

Replication

RA SF RA Austin

RA Austin

Replication

RA SF RA Austin

Backups toReplica

Appliance

Replica Appliance Backups transferred to Primary

Configuring High Availability ZDLRA Client for Backup and Recovery (Doc ID 2432144.1)

Monitoring RA’s Health

• Monitor the Appliance1 on a daily basis• EM Unified Management Dashboard

• Review twice daily• EM notifications

• Review and act on notifications and alerts• Run exachk Monthly and review findings

• How To update exachk outside ZDLRA Install, Patching and Upgrade (Doc ID 2399688.1)• Use diff to compare month to month • Run pre and post patching

• Review Capacity Planning Report Monthly or Bi-Monthly

As you support more databases or expand data/recovery retention, more capacity is required.

14Updated Practices: Maintenance and Operational Best Practices

1While it is an appliance, it needs minimum monitoring activities

15

MAA Score CardMAA architectural readiness and configuration practices

Database and Exadata Health ChecksAssessment Report

Health Score, Summary, Findings

Findings & Recommendations

How to Solve the problem?

Note: Automated Orachk/Exachk Healthcheck MOS 107954.1 updated frequently

Maximum Availability Architecture - Best Practices for the Database 19c

Improvements in Silver

Copyright © 2019 Oracle and/or its affiliates.

Copyright © 2019 Oracle and/or its affiliates.

Prod/Departmental

SILVER

Bronze +• Real Application Clustering (RAC)• Application Continuity

Unplanned Outage RTO/RPO*

Recoverable node or instance failure Seconds

Disasters: corruptions and site failures Hours to days. RPO since last backup or near zero with ZDLRA

Planned Maintenance

Software/hardware updates Zero

Major database upgrade Minutes to hour

Outage Matrix

RAC Database

Primary Availability Domain Secondary Availability Domain

Local Backup Replicated Backups

* RPO=0 unless explicitly specified

Oracle Real Application Clusters (Oracle RAC)

• Utilizes two or more instances of an Oracle Database concurrently

• Very Scalable• All instances active; Add capacity online; Ideal for

database consolidation

• Highly Available• Auto-failover of services to an already running

instance; Outage is transparent to user, in-flight transactions succeed; Zero downtime rolling maintenance

Database Tier

ApplicationTier

Database Services

Primary Database

Node Failure, Instance Failure, Rolling Maintenance

18

Checklist for Achieving Zero Application Downtime

1. Use Oracle Clusterware Service (never use default service)

2. Use Recommended Connection String

3. Configure FAN for Connection Pool

4. Drain your service

5. Use Application Continuity or Transparent Application Continuity

Copyright © 2019 Oracle and/or its affiliates.

1) MAA Whitepaper: Application Checklist for Continuous Service for MAA Solutions2) Using RHPhelper to Minimize Downtime During Planned Maintenance on Exadata (MOS 2385790.1)

3. Fleet Patch and Provisioning incorporates MAA practices

Copyright © 2019 Oracle and/or its affiliates.

Maximum Availability Architecture - Best Practices for the Database 19c

Improvements in Gold

Copyright © 2019 Oracle and/or its affiliates.

Copyright © 2019 Oracle and/or its affiliates.

Outage MatrixUnplanned Outage RTO/RPO*

Recoverable node or instance failure Seconds

Disasters: corruptions and site failures Seconds. RPO zero or seconds

Planned Maintenance

Software/hardware updates Zero

Major database upgrade Seconds

Primary Region Secondary Region

Local backup

Remote StandbyPrimaryLocal

StandbyLocal

backup

AD2 AD1

Mission Critical

Silver +• Active Data Guard• Comprehensive Data ProtectionMAA Architecture: • At least one standby required

across AD or region. • Primary in one data center(or AD)

replicated to a Standby in another data center

• Local backups on both primary and standby

GOLD

* RPO=0 unless explicitly specified

Active Data Guard OverviewPrimary

Open Read-WriteStandby

Open Read-Only

Zero Data Loss at any Distance

Automatic Block Repair

Offload read only or read mostly workloads to the

standby database

• Synchronous zero data loss replication

• Database rolling upgrade to reduce downtime for planned maintenance

• Automatic failover for High Availability

DML Redirection

Multi-instance Redo Apply for RAC

(In Memory supported)

23

Data Guard Creation Practices

• Benefit: Fastest and easiest Data Guard deployment for your environment

• New master MOS note that directs you to the best way to deploy a Data Guard standby

• Key Tip - If you are 12.1.0.2 or higher then use RMAN restore from service method

24

My Oracle Support Note 1617946.1-How to Create a Data Guard Standby using RMAN Duplicate (RAC or Non-RAC)

Recently Updated MOS Note 2064368.1: Assessing and Tuning Network Performance for Instantiation and Migration

Data Guard Network Performance

• Benefit: Assessing and Tuning Network Performance for Data Guard Transport

• Using oratcptest tool to:• Assess network bandwidth prior to deployment• Tune ASYNC transport

• send_buffer_size• recv_buffer_size• Operating system socket limits

• Determine network roundtrip latency with SYNC transport

25

Recently Updated MOS Note 2064368.1: Assessing and Tuning Network Performance for Data Guard Transport

Data Guard Async Transport Benefits

• Learn to push ASYNC performance to provide near zero data loss protection

• Describe transport lag accurately• Diagnose and tune ASYNC transport

• Network performance• Identify bottlenecks

• Troubleshoot reasons for ASYNC transport lag• Leverage AWR and custom MAA queries

26

Best Practices for Asynchronous Redo Transport - Data Guard and Active Data Guard

Data Guard Sync Transport Benefits

• Achieve zero data loss with minimal performance impact• Tune SYNC performance

• Test results that illustrate performance gains when using best practices• Size online log file properly to improve performance by 30%

• Frequent log switches force a checkpoint on the standby which results in increased I/O thereby affecting performance

• Configure single member standby redo log on fast storage

27

Best Practices for Synchronous Redo Transport - Data Guard and Active Data Guard

Data Guard Failover Benefits

• Decrease downtime• Minimize impact for various

outage in a Data Guard configuration• Test results with outage repair

times• Test instructions and expected

outcome

28

MAA Best Practice Paper: Automatic Resolution of Outages to Restore Zero Data Loss ProtectionMAA Best Practice Paper: Data Guard Role Transition Best Practices

Extend Footprint of ADG Applications

• DML Re-direction is automatically performed from an Active Data Guard standby to the primary (ACID uncompromised)

• New parameter ADG_REDIRECT_DML controls DML Redirection• New ADG_REDIRECT_DML and ADG_REDIRECT_PLSQL

• “Read-Mostly, Occasional Updates” applications

supported for Oracle Database 19c

Support for DML Re-direction

29

(Active) Data Guard Features 19c

19c Data Guard Hidden Gems• New Parameters for tuning automatic outage resolution with Data Guard• Flashback Database enhancements with Data Guard• Buffer Cache on Active Data Guard preserved after role transition for RAC• Improved Data Guard Multi-Instance Redo Apply with in-Memory• Active Data Guard DML Redirection

Previous 12.2 and Up Key Features worth mentioning again• DG Broker support for multiple automatic failover targets• DG Broker support for HA observer • Block Comparison tool for validation• Active Data Guard In-Memory support

Multi-Instance Redo Apply Performance

• Utilizes all RAC nodes on the Standby database to parallelize recovery• OLTP workloads on Exadata show great scalability

Lower Latency Active Data Guard Standby Databases

190 380 7401480700

1400

2752

5000

0

1000

2000

3000

4000

5000

6000

7000

1 Instance 2 Instances 4 Instances 8 Instances

Batch

OLTP

StandbyApplyRate

MB/sec

34

Database Rolling Upgrade to 19c

Database Rolling Upgrade with DBMS_ROLLING• Pre-checks and early problem detection• Fault tolerant, resumable and rollback capabilities• Three Role Transition Steps: Start, Switchover, Finish• Potential Maintenance Window: Hours • Potential Database and Application Downtime: Seconds

Confidential – Oracle Internal/Restricted/Highly Restricted

Automated Database Upgrades using Oracle Active Data Guard and DBMS_ROLLING

Architecture for consolidating databases and simplifying operations

Oracle Multitenant

GL OE

AP Self-contained PDB for each application• Portability (via pluggability)• Rapid provisioning (via clones)• Applications run unchanged• PDB upgrades via plug/unplug

Shared memory and background processes• More applications per server

Common operations performed at CDB level• Manage many as one (upgrade, backups, HA)• Granular control• Simple DR

PDBs

Root

CDB

MAA and Multitenant• Solutions for planned / unplanned outages

36

PDB Failover: Normal Runtime

PDB1 PDB2CDB 1

Read-Write

CDB 1StandbyRead- OnlyData Guard

CDB 2Read-Write

PDB4

PDB2 PDB3PDB1 PDB3

37

Unplug/plug PDB2 from CDB1 standby to CDB2 and failover application connections

PDB Failover after PDB 2 Outage

PDB1

CDB 1Read-Write

CDB 1StandbyRead- OnlyData Guard

CDB 2Read-Write

PDB4

PDB2PDB1 PDB2 PDB3 PDB3

PDB2

38

Confidential – Oracle Internal/Restricted/Highly Restricted

Multitenant “Gold” MAA Unplanned Outages Key Features for Solution RTO RPO

Recoverable node or instance failure Real Application Cluster (RAC)Application Continuity (AC/TAC)

Secs Zero

Disasters: corruptions and site failures Active Data Guard Fast-Start Failover

Secs Zero or Secs

PDB unrecoverable failure or “sick” PDB(NEW)

PDB Failover (unplug/plug)Another target CDB on the same cluster required (MOS 2088201.1)

Secs Zero or Secs

Planned Maintenance Solution RTO

Software and hardware updates RAC, AC or TAC Zero

Major database upgrade Active Data Guard DBMS_ROLLING Secs

Migration to remote CDB (NEW) PDB Relocate Mins

Migration plus upgrade (NEW) PDB Relocate + Upgrade Mins

Updated MAA Best Practices Papers: Best Practices For Database Consolidation On Oracle Exadata Database Machine

Refreshable PDB SwitchoverPer-PDB replica with only two CDBs to manage!Server1

CDB1

CDB2

Server2

1. create pluggable database Red;4. create pluggable database Brown;6. create pluggable database Grey

from Grey@CDB2_Linkrefresh mode every 2 minutes;

2. create pluggable database Redfrom Red@CDB1_Linkrefresh mode every 2 minutes;

3. create pluggable database Gold;5. create pluggable database Grey;

40

Refreshable PDB SwitchoverPlanned switchoverServer1

CDB1

CDB2

Server2

1. alter pluggable database Greyrefresh mode every 2 minutesfrom Grey@dblink switchover;

41

Refreshable PDB SwitchoverUnplanned switchoverServer1

CDB1

CDB2

Server2 1. alter pluggable database Greyrefresh;

2. alter pluggable database Greyrefresh mode none;

3. alter pluggable database Greyopen read write;

42

Does not interoperate with Data Guard Fast-Start Failover, auto-block repair, DB rolling upgrade so NOT part of Gold MAA

Maximum Availability Architecture - Best Practices for the Database 19c

Improvements in Platinum

Copyright © 2019 Oracle and/or its affiliates.

Copyright © 2019 Oracle and/or its affiliates.

Gold +• GoldenGate Active/Active

Replication• Optional Editions Based

Redefinition MAA Architecture: • Each GoldenGate “primary” replica

protected by RAC and Active Data Guard

• Primary in one data center (or AD) replicated to another Primary in remote data center (or AD)

• Oracle GG & Editions Based Redefinition for zero downtime application upgrade

• Local backups on both sites• Achieve zero downtime through

custom failover to GG replica

Extreme Critical

PLATINUM Primary Region Secondary Region

Local backup

Local backup

AD2 AD1

GG Replication

AD1 AD2

Standby StandbyPrimary Primary

Outage Matrix

* RPO=0 unless explicitly specified ** application failover is custom

Unplanned Outage RTO/RPO*

Recoverable node or instance failure Seconds

Disasters: corruptions and site failures Zero**

Planned Maintenance

Software and hardware updates Zero

Major database upgrade, application upgrade, migration

Zero**

45

Oracle GoldenGate Microservices Architecture

SourceOracle & Non-OracleDatabase(s)

TargetOracle & Non-Oracle

Database(s)

Capture: committed transactions are captured (and can be filtered) as they occur by reading the transaction logs.

Trail: stages and queues data for routing.

Distribution Server/Receiver: distributes data for routing to target(s).

Route: data is compressed, encrypted for routing to target(s).

Capture

Delivery

TrailFiles Dist.

Service

TrailFiles

Delivery

Capture

Bi-directional

LAN / WAN / InternetOver TCP/IP

TrailFiles

TrailFiles

Delivery: applies data with transaction integrity.

Dist. Service

Receiver Service

Receiver Service

Key GoldenGate Improvements Simplify Platinum1. GoldenGate Hub simplifies migration and administration by

offloading work from source and target • New GoldenGate cloud market place automates GG hub deployment• Cross endianness capture enables cross platform migration• Upcoming Zero Downtime Migration integration with GoldenGate

2. GoldenGate Microservices simplifies administration and management

Copyright © 2019 Oracle and/or its affiliates.

Oracle Database Migration with an Oracle GoldenGate Hub Configuration

Oracle GoldenGate Microservices Architecture with Oracle Real Application Clusters Configuration Best Practices

Future: Zero Downtime Migrationwww.oracle.com/goto/zdm

Oracle GoldenGate

• Transparent Role Transitions in Data Guard Configurations• No manual intervention required with FSFO and DG Broker

• Configuration makes use of:• Oracle Grid Infrastructure Bundled Agent (XAG)• DBFS or ACFS for shared GoldenGate files (trails and checkpoint files)• Role based services• Integrated Extract (with HANDLEDLFAILOVER option for ASYNC DG)• Microservices Architecture for simpler administration

MAA Best Practices

47

Updated: MAA Best Practice Paper: Transparent Role Transitions with

Data Guard and Oracle GoldenGate

Sample Deployment

48

Observer

Primary Database Standby Database

Redo Transport(SYNC or ASYNC)

Integrated Extract LogMining

Server

Trail and other OGG FilesIn DBFS

Redo Transport

OCI Connection

File I/OWarehouse

BidirectionalGoldenGate Replication

Sample Deployment – Post Role Transition

49

Observer

(OLD) Primary Database (NEW) Primary Database

Redo Transport(SYNC or ASYNC)

Integrated ExtractLogMining

Server

Trail/Checkpoint/BR FilesIn DBFS

LogMiningServer

Redo Transport

OCI Connection

File I/O

Warehouse

BidirectionalGoldenGate Replication

Alternate Platinum Option: ShardingHighly scalable, fault tolerant architecture for Internet Applications

• Custom Built Application optimized to use shard keys

• Horizontal partitioning of data across independent databases (shards)– Each shard holds a subset of the data– Can be single-node or RAC or PDB– Replicated for high availability

• Shared-nothing architecture:– Shards don’t share any hardware (CPU,

memory, disk), or software (clusterware)

A single logical DB sharded into N physical Databases

Server1

Database

Table1Shard1

Server2

Table1Shard2

Server3

Table1Shard3

Deployment of a System-Managed SDB with Data Guard

51

Clients

Data GuardFast-Start Failover

RegionAvailabilty_Domain1

Shard Catalogshardcat_stdby

Shard Directorshdir3,4

RegionAvailability_Domain2

Shardgroupshgrp2

Shardgroupshgrp1

…

…

Shard Directorshdir1,2

Shard Catalogshardcat

Connection Pools

Connection Pools

Primaries

HA Standbys

Use Sharding with Active Data Guard, RAC or Oracle GoldenGateSharding Configuration Options

Active Data Guard with Fast-Start Failover

GoldenGate ‘chunk-level’ active-active replicationwith automatic conflict detection/resolution

Optionally – complement replication with Oracle RAC for server HA

52

https://www.oracle.com/database/technologies/high-availability/sharding.html

Maximum Availability Architecture - Best Practices for the Oracle Database 19c

Cloud MAA

Copyright © 2019 Oracle and/or its affiliates.

MAA Evolution from On-Premises to Autonomous

On-Premises

On-Premises Exadata

ExadataCloud

Autonomous Database

54

• Architecture• Database Management (Tooling)• Configuration, Tuning • Lifecycle Operations (Tooling)• Application Performance

• Choosing the SLA policy• Application performance

• Infrastructure Management

• Architecture• Database Management• Configuration, Tuning• Lifecycle operations• Application Performance• Infrastructure

Management• Architecture• Configuration, Tuning• Database Management• Lifecycle Operations• Application Performance

• Blueprints• Feedback to

products & features

• Blueprints• Exadata is the best

integrated MAA DB platform

• Oracle owns and manages the best integrated MAA DB platform

• Cloud automation for provisioning and life cycle operations

• Oracle owns and manages Infrastructure

• Policy driven deployments

• MAA Integrated cloud• Fully automated Self-

Driving, Self-Securing, Self-Repairing Database

CustomerOracle

MAA Deployment Automation in the Cloud

• Simple UI / CLI / REST interfaces being configured for MAA topologies

• Databases are provisioned with MAA parameter configurations• MAA made easy in the Cloud

• Oracle Cloud Infrastructure (or) • Cloud at Customer

55

Primary

Regi

on #

1

Standby

Regi

on #

2GO

LD (D

R)

AD #

1AD

#2

PLAT

INU

M (H

A)

GG replication

Primary

FSFO

FSFO

Standby

BRO

NZE

Single Instance

DB Backup Service RACSI

LVER

(HA)

DB Backup Service

Cloud Configuration Best Practices

- Exadata Cloud deployment has built-in Exadata and MAA best practices- Target: 100% score at deployment time- Refer to Oracle Exadata Database Machine exachk or HealthCheck (Doc ID

1070954.1)

Copyright © 2019 Oracle and/or its affiliates.

In the Cloud, ExaCS and ExaCC are Deployed with Exadata and MAA Best Practices

MAA Cloud Life CycleLife Cycle Operations MAA Practices

Create Cloud Databases Uses Exadata MAA templates or MAA templates if done via UI or Cloud APIsDo NOT use custom scripts or DBCA

Migration to Cloud Zero Downtime Migration (ZDM) uses MAA practices with Data GuardLogical migration can use GG hub which will be available in ZDM in the future

Infrastructure Software Updates

Zero Database DowntimeZero Application Downtime requires Continuous Availability - Application Checklist for Continuous Service for MAA Solutions

DB/GI Software Updates Zero Database Downtime Zero Application Downtime requires Continuous Availability - Application Checklist for Continuous Service for MAA SolutionsMAA collaborating with cloud to add more prereqs and Data Guard supportFleet Patch and Provisioning in the Cloud

Copyright © 2019 Oracle and/or its affiliates.

MAA Cloud Life CycleLife Cycle Operations MAA Practices

Exadata OS Updates How to update the Exadata System Software (DomU) to 19c from 18c on the Exadata Cloud Service in OCI (Doc ID 2521053.1)How to update the Exadata System Software (DomU) on the Exadata Cloud Service in OCI (19.x to 19.x) (Doc ID 2566035.1)

Backup/Restore Use Automatic Backup/Restore with MAA practicesOracle Cloud Infrastructure Exadata Backup & Restore Best Practices using Cloud Object Storage

Health Checks Oracle Exadata Database Machine exachk or HealthCheck (Doc ID 1070954.1)

Real Time Monitoring and Alerting

Enterprise ManagerOracle Enterprise Manager for Exadata Cloud, Exadata Health and Resource Utilization Monitoring - Exadata Database Machine KPIs and Exadata Health and Resource Utilization Monitoring - Adaptive Thresholds

Copyright © 2019 Oracle and/or its affiliates.

Autonomous Database CloudHigh Availability Policy

• Exadata in a single AD with nightly backup replicated across other ADs

• Protects from the common sources of downtime such as hardware failures, software crashes, and quarterly software updates

• Service Uptime SLA per Month: 99.95% < 22 minutes of downtime*

• Suitable for test, development and non-mission critical production databases

59

* SLA excludes AD or Regionfailures, data corruptions andcertain planned maintenancetasks like major upgrades

DB Backup Service

Region #1

Database Backups

Primary Database

Autonomous Database CloudExtreme Availability Policy

• Exadata with Active Data Guard and Backup

• Protection from hardware failures, crashes, corruptions, patches, upgrades, disasters

• Service Uptime SLA per Month: 99.995NRX% (NRX = No Ridiculous Exclusions)• 99.995% Uptime = at most 2m 12s of downtime per month• Goal is for application impact from any one event to be well under 30 seconds

• Suitable for Mission Critical production databases

60

Primary Database

Region #1, AD #1 Region #1, AD #2

Backup

Standby Database

Active Data

Guard

Provide the best HA, DR and data protection solution for Oracle databases

Continue to enhance validated MAA solutions

Your success is truly our success!!!

Copyright © 2019 Oracle and/or its affiliates.

What’s Ahead

Thursday

2:15-3:00 Best Practices for the Most Impactful Oracle Database 18c and 19c Features (TIP4855)Moscone South 215/216

Copyright © 2019 Oracle and/or its affiliates.

Questions & Answers

• Lawrence To, Senior Director, MAA, Oracle