1 / 23

Fall 2001 OAUG San Diego Release 11i Upgrade Workshop

Fall 2001 OAUG San Diego Release 11i Upgrade Workshop. November 2001. Agenda. Introductions and Information Overview of Upgrade Project Question and Answer Panel Breakout Sessions. Our Facilitation Team. John Stouffer - Solution Beacon Alicia Hoekstra – KPMG

alec-mccullough
Download Presentation

Fall 2001 OAUG San Diego Release 11i Upgrade Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Fall 2001 OAUGSan Diego Release 11i Upgrade Workshop November 2001

  2. Agenda • Introductions and Information • Overview of Upgrade Project • Question and Answer Panel • Breakout Sessions

  3. Our Facilitation Team • John Stouffer - Solution Beacon • Alicia Hoekstra – KPMG • Eric Riegelman – Stonebridge • Donna Flowers – Stonebridge • Mark Clark - O2Works LLC

  4. Upgrades – Easy to Understand • Why Upgrade? • What Happens During an Upgrade? • Why Such a Big Deal? • Overview of an Approach to Managing Upgrades for Success • What Resources are needed and when • What can be expected?

  5. Why Upgrade At All? • Support Issues and Maintenance Issues • Performance Improvements • New Applications Available • Architecture Changes allow leverage of Intra/Extra Nets • New Functionality provided in Existing Modules • New AOL Features like Workflow, Self Service Layers • Critical Features Needed

  6. 30,000 Feet – The Code • Standard Code Supplied by Oracle • New Tables and other objects created • Changes made to EXISTING tables and data to conform to 11i standards • New Forms and Reports are installed for use by End Users

  7. 20,000 Feet – The Path • Pre- Upgrade Steps – Users and Tech Team • Automated Steps – Tech Team – Thousand of Scripts will run Automatically and be monitored • Post Upgrade Steps – Users and Tech Team

  8. 10,000 Feet – The System • Some New Hardware • Some New Operating System • New Database Version • Lay Down Upgrade Code • New Executable Code • Pre, During, and Post Upgrade • Go Live

  9. 5,000 Feet – Milestones • Copy of Production Database – no users in the system • On a Module by Module Basis – Category One – Category Three Steps and Programs must be run – and Any Corrections Made.. Can take Many Hours. • Auto Upgrade Process Runs – Thousands and Thousands of Scrips Run – each must complete successfully before Proceeding – WILL take a LONG Time

  10. 5,000 Feet (Con’t) • Additionally Patching to fix known Issues – more scripts that must all succeed without error. • Category Four, Five and Six Post Upgrade Steps – All must Complete Successfully – Can take many Hours • Additional Patching – Can take Many Hours • Reapply Customizations, Enhancements

  11. Why Such A Big Deal? • Uncertain Downtime – Large Number of Variables. • Uncertainty regarding “Clean” Data Before the Upgrade • Uncertainty on Oracle Standard Code being 100% First Time • Uncertainty on New Functions “Fitting” ELDEC Business Requirements • Uncertainty Around Re-Integration (and Need for) Customizations/Enhancements

  12. GOAL: Remove all uncertainty • Test Upgrade One– Round One – Identify, Understand and Measure – Post Mortem • Test Upgrade Two – Review, Note Issues, and “Squeeze” Downtime – Reapply Customizations. • Make System Available for Testing • Fix Bugs, Issues, and Gaps • Optional Additional Rounds • Create Production Cutover Plan • Production Cutover

  13. Our Approach • Establish Safe Environment for Testing • Read and Re-Read the Upgrade Manual for EACH Module and Document Required Steps • Assemble List of Customizations • Check with Support for Steps where documentation is Unclear • Use Upgrade Assistant to Track To Do List • Take A Snapshot of Production

  14. Our Approach • Per MODULE - Assign Resources to Understand and Execute Category One through Category Three Steps – and Designated Resource going forward. • Document the time required for Each Step. • Note those steps that can be done Well Before – Even in Production (cleanup)

  15. Approach Continued • When complete – Take a Baseline Backup • Run AutoUpgrade – Start Timing • Capture Timing on Long Running Jobs • Note Any jobs that break, get restarted, and any Fixes – DOCUMENT • When Complete – take another Backup • Begin Post Upgrade Steps – Again – Assign Champions to do this. Capture Timings

  16. Approach Continued • Take Post –Post-Upgrade Backup • Apply Additional Patches- Capture Timings • Backup • Verify Applications • Round One – Post Mortem • Turn System Over to Developers to Begin Design Upgrades for Customizations

  17. Customizations • Identify Them All • Pre-Analysis (get rid of some) • After Round One – Design Re-Integration • Build and Unit Test • After Round Two – Install and System Test • Review and Adjust • Load Test • Incorporate into Overall Production Plan

  18. Approach in Summary - • Read and Plan • Execute and Time • Multiple Backups • Squeeze Downtime Window • Repeat and Integrate Customization – Do for “Timing” • Test Extensively • Readjust Plan • Communication and Production Cutover

  19. What Resources are Needed and When? • Technical Resources – • DBA – Planning, Auto-Upgrade, Patching, Support and more Patching • Developers – Catalog and Design Customizations • Tech Leads – Lead Team of Developers per and Across Areas • Tech Project Managers – Planning and Execution

  20. Resources and When • Functional – • Project Lead – Planning, Execution • Business Analysts – New Features, Gap Analysis, Propose Customizations and Ex-Customizations • Testing – Application Verification, System Testing • Gap Identification – Work with Developers on New Design, Build and Test

  21. What can you Expect? • Serious Project – Just like Implementation • Drain on Resources • Cooperation Across Departments • Communication on Status • Numerous “Speed Bumps” • New User Interface • Lots of time with Oracle Support

  22. Typical Upgrade Steps • System Review and Initial Project Planning – 3-8 days (Production) • System Stabilization (Production) and Detailed Project Planning – Environment/Resource Dependent • Test Upgrade and Support – 5-7+ days (use a Complete/Current Copy of Production) • Application Testing and Support – Environment/Resource Dependent • Extensions Re-Development and Remediation – Environment/Resource Dependent • Training – Environment/Resource Dependent • System Integration Testing – Environment/Resource Dependent • Production Upgrade and Support – 3+ days

  23. Upgrade Timeline – One Example System Review/Project Planning System Stabilization Test Upgrades & Support Application Testing Redevelopment Team Training User Training Integration Testing Production Upgrade

More Related