This document proposes a two-phase approach to help customers successfully upgrade to Oracle 19c and prevent issues. Phase 1 involves initial manual engagement to assess customers' systems and provide recommendations. Phase 2 aims to unify existing Oracle tools into a self-service upgrade review and advisory tool accessible through MOS. This would automate tasks like patch validation, upgrade performance validation using AWR extracts, and running Autonomous Health Framework on test environments to surface potential bugs. The goals are to help customers upgrade successfully in the short term and provide a long-term centralized resource for customers to utilize for database upgrade planning.

1. 19c Strategic Customer Upgrade Proposal
1 Confidential – © 2019 Oracle Internal/Restricted/Highly Restricted

2. • Requirement
• Customers Upgrading to early 19c Releases or 12.2/18.
• Many encountering multiple issues that impact both their Business and their perception of 19c.
• Many of the issues were avoidable, and Customers unaware of Oracle Recommended Best Practices.
• There are multiple historic tools available to assist Customers with Upgrade Planning
• No One-Stop Central Source Of Truth under MOS Portal for Customers to access
• PUMA, RAT Assurance, Strategic Customer Program, MOS Certification/Patching
• Delivered by Support, XTeam, RAC Assurance, Dev
• Much of the assistance provided now is manually driven, and often too late to make a difference.
• We have the tools there, just need to pull existing together, and add further enhancements
• Requesting Executive Sponsorship to ensure we get the right level of Buy-In from the various Teams to pull this together
• Goals
• Short Term
• Successful 19c Upgrades and Prevent Upgrade Delays, Major Escalations and Known Avoidable Customer Production
Impacting issues
• Long Term
• Take what is learnt from 19c Upgrade engagements, and the already available tooling, and centralize into a Holistic
that Customers can utilize as a Self Service RDBMS Upgrade Tool.
Oracle Confidential – Internal/Restricted/Highly Restricted
2
19c Strategic Customer Upgrade Proposal

3. • Manual Phase 1 Engagement Model (Caveat - This is not a Hands On Upgrade Service)
• Step 1
• Identify Points Of Contact per Strategic Account (Support Manager/Dev Manager/Account Team/TAM/Customer
• CP Team already started to discuss with Account Teams Customer Plans with Positive Feedback
• Wells Fargo and Verizon started and further to be assigned as 19c Plans starting
• Step 2
• Kick Off Meeting with Customer 'Oracle 19c Strategic Upgrade Plan Assessment and Assistance Program’/How will it
benefit the Customer.
• Provide Questionnaire Assessment Matrix to Customer for Background details of Systems to be Upgraded.
• Step 3
• Share feedback on initial review of questionnaire details, and collect further diagnostics if not already provided.
• Step 4
• Patch and RU review – Delta tooling being developed for RU Critical/Important/Recommended based on Products.
• Step 5
• Review of AWR Extracts for Testing Source and Target Environments (Manual ADAT) to validate the likeness of Testing
highlight Red Flags
• Step 6
• Ongoing regular checkpoint calls through Testing.
• Step 7
• Oracle Team to be on Standby during the Upgrade Window to help prioritize review of any issues reported
• Success
• Customer Upgraded to 19c without Major Issues
• Next Steps
• Document the steps learnt from Phase 1 into a set of actions that can be enhanced and shared
Phase 1 – Manual Engagement

4. • Self Service Upgrade Review and Advisory Tool
• Step 1
• Unify the existing tooling already available into one Interface
• Input exachk/orachk/lsinventory/questionnaire
• Validate RDBMS Version Certification matrix
• Patch Validation based on Upgrade Release and recommendations on additional fixes based on Products used.
• Step 2
• Further Automated Tooling Under Discussion
• Integration into Automatic SR and Patch Request direct from Tool
• Upgrade Performance Validation Tool
• Provide Source and Target AWR Extracts for Testing period.
• Automated ADAP Enhancement to review extracts and provide feedback on:
• Workload/Environment/Configuration Differences
• Top Executions per Extract and Queries of concern Differences between the Tests based on High Elapse
Time/Executions/Wait Differences
• Autonomous Health Framework
• Run automated AH against TFA collection(s) from Testing Cycles to provide potential Bugs and/or areas of concern
• AH to automatically collect details on Products, Versions, Configuration
• Current collections do some of this, but a Bespoke ‘Upgrade SRDC’ can collect all, along with AWR
Oracle Confidential – Internal/Restricted/Highly Restricted
4
Phase 2 –Tooling and Automation

5. • We can provide initial hands on assistance to make 19c Upgrades as pain-less as possible.
• However this approach does not scale.
• We already have many tools that can provide Self-Service Upgrade Planning andValidation.
• We cannot do the Upgrade for theCustomer, but we can highlight to the Customer
• Best Practices.
• Recommendations.
• AreasOf concern
• The main wave of 19c Upgrades to come in 2021, we can help Customers to HelpThemselves.
Oracle Confidential – Internal/Restricted/Highly Restricted
5
Summary

6. • Existing Tooling
• RAT Assurance (rat.us.oracle.com) - Includes outside of MOS access to various tools to provide Patch and
feedback
• MyOracleSupport (support.us.oracle.com)– Patch Conflict Checker, Certification Checks
• AutonomousHealthFramework (Internal) – Review collect TFA to provide Environment overview and Trace File
• RWP ADAT (Internal) – Provide DB/Query Performance Feedback from AWR Extract
Oracle Confidential – Internal/Restricted/Highly Restricted
6
Phase 2 –Tooling and Automation

7. Oracle Confidential – Internal/Restricted/Highly Restricted
7
19c Strategic Customer Upgrade ProposalTimeline
ShortTerm 2020 LongerTerm Objectives 2021
Wells Fargo/Verizon to start with + DirectAssistance toOther StratCustomers going to 19c
Phase 1
HandsOn SE
Assistance
Patch Delta Recommendation
Phase 2
MultipleTeams
already started
separate avenues
of investigation.
Pulled Support
and DevTeams
into 1 working
party to review
and deliver on:
RDBMS/OS Validation
Upgrade Performance Validation Tool ETA Under Review
AHF TFA Feedback and Config Collection
Further
Learning
Integration into MOS
Internal Available Tooling
Integration into MOS
Internal Available Tooling

8. Upgrade Details
Date Proposed
Smoke Tests
Planned
Go/NoGo Date
Fall Back
Options
Upgrade Plan
Impact
Details/SLAs
Upgrade
Timeline
Questionnaire
Products Stack
Compression Y/N
RAC Y/N
Encryption Y/N
Partitioning Y/N
Multi-Tennant Y/N
In-Memory Y/N
Audit Vault Y/N
Spatial Y/N
OGG Y/N
Other Y/N
3rd Party Tools
System Details
DBName
OLTP/DWH/Hybr
id
ADG Fall Back
/MAA Best
Practices
Instances
RDBMS Current
RDBMS
Proposed
GI Current
GI Proposed
lsinventory
Engineered/On-
Prem/CoManage
d
OS Details
Machine Config
Diagnostic
Collection
Tool Used
AWR Extract
Current
AWR Extract
Proposed
ExaWatcher/OS
Watcher
Testing TFA
Tool Used
AWR Extract
Current
AWR Extract
Proposed
Exachk/Orachk