Uploaded byAWS Germany
Migrating Oracle Databases to AWS
The document outlines a practical approach for migrating Oracle databases to AWS, highlighting the reasons for migration, available services, and common strategies, including lift-and-shift and re-platforming. It details the migration paths, environment setup, and data conversion processes, along with the necessary tools and considerations for licensing and support. Additionally, the document showcases successful migration outcomes and provides insights into optimizing cloud infrastructure costs.
In this document
Powered by AI
Overview of practical approach for migrating Oracle to AWS by Andrey Zaychikov, Specialist SA Database Migrations.
Details on AWS global infrastructure including 18 regions, 55 availability zones, and 103 edge locations.
Key reasons for Oracle customers migrating to AWS include technical debt retirement, improved security and performance.
Introduction to database distribution per workload without further details provided.
Illustration of database distribution across IT landscape with various node statistics (1320, 383, 70, 947 nodes).
Brief mention of managed database services provided by AWS.
Options available for migrating Oracle databases, Fusion Middleware and Enterprise applications to AWS.
Overview of six common application migration strategies including Lift and Shift, Re-platform, and Re-factoring.
Various migration solutions for Oracle on AWS including database configurations and post-migration outcomes.
Key considerations for licensing and support for Oracle databases, including 'Bring Your Own License' and specific support versions.
Introduction to optimizing vCPUs for EC2 instances to manage licensing costs more effectively.
Customer cases showing significant reductions in processing times, cost savings, and increased availability after migration.
General overview of various migration options available for Oracle to AWS.
Detailed approach outlined for re-platforming databases as part of the migration strategy.
Step-by-step approach for migration involving goal setting, transport methods, and environment setup.
Guideline on defining the original database source for successful migration planning.
Focus on defining the target database environment for migration.
Different migration path options from proprietary on-premises DB to AWS Managed DB services.
Benefits of splitting workloads during migration for performance and scalability.
Various methods for data transport during migration, including Amazon Snowball and VPN.
Information regarding the necessary environment setup for migration to AWS.
Key considerations and steps required for converting database schemas during migration.
Outline of procedures for efficient data transfer in the migration process.
Critical aspects of checking and testing data post-migration.
Instructions on switching applications post-data migration.
Final steps for decommissioning source databases and temporary resources post-migration.
Overview of AWS Database Migration Service (DMS) and Schema Conversion Tool (SCT) sources.
List of additional online tools for migration assessment and support.
Wrap-up of the presentation inviting questions from the audience.
Migrating Oracle Databases to AWS
- 1. © 2017, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Practical Approach for Oracle migration to AWS Andrey Zaychikov, Specialist SA Database Migrations, EMEA
- 2. AWS Global Infrastructure •Customers in 190 countries • 18 geographic Regions & • 1 Local Region • 55 availability zones • 103 edge locations New Region (coming soon) – Bahrain, Hong Kong SAR, Sweden, AWS GovCloud (US-East)
- 3. Why Oracle customersmigrate to AWS Retire technical debt Tech refresh New applications New architectures Improve security Automate operations Improve performance Simplification of s/w
- 4.
- 5. Databases in ITlanscape 1320 Nodes 383 Nodes 70 Nodes 947 Nodes
- 6.
- 7. AWS options forOracle customers Oracle Databases on AWS Database migration to AWS Fusion Middleware on AWS Oracle Enterprise Applications on AWS
- 8. Six Common ApplicationMigration Strategies Determine Migration Path Lift and Shift Automate RE-HOST Lift and Reshape RE-PLATFORM Drop & Shop REPLACE Re-architect/ Decoupling apps REFACTOR Purchase COTS/SaaS & licensing MODIFY UNDERLYING INFRASTRUCTURE Manual Install & Setup Integration Redesign Application/ Infrastructure Architecture App Code Development Full ALM / SDLC Integration Use Migration Tools Assess/Prioritize Applications Discover RETAIN RETIRE Not Moving Decommission Validation Transition Production Manual Install Manual Config Manual Deploy MANUAL
- 9. AWS migration strategiesfor Oracle customers Solution Oracle Databases Oracle Fusion Middleware on AWS Oracle Middleware to AWS Oracle Enterprise Applications on AWS Oracle Databases on AWS EC2 Oracle Databases on AWS RDS Oracle database migration to AWS Migration path Rehost Replatform Refactor Rehost Refactor Rehost Post migration Customer runs Oracle Database EE, SE, NoSQL, TimesTen, MySQL, Golden Gate on AWS Customer shifts Oracle EE, SE to AWS RDS for Oracle Customer migrates from Oracle EE, SE, NoSQL to AWS RDS OSS, Aurora or Redshift Customer runs Oracle SOA Suite, WebLogic, OBIEE, BPM and more on AWS Customer refactors their Java application Customer runs Oracle E- Business Suite, PeopleSoft, JDE, Hyperion, Siebel and more on AWS AWS Services EC2/EBS, VPC Oracle RDS RDS OSS, Aurora, Redshift, Schema Conversion Tool, Database Migration Service EC2/EBS, VPC Elastic Beanstalk, ELB, Aurora EC2/EBS, VPC, Oracle RDS
- 10. Oracle to AWSlicense and support - considerations Solution Oracle Databases Oracle Fusion Middleware on AWS Oracle Middleware to AWS Oracle Enterprise Applications on AWS Oracle Databases on AWS EC2 Oracle Databases on AWS RDS Oracle database migration to AWS Migration path Rehost Replatform Refactor Rehost Refactor Rehost License consideration BYOL. Review Oracle Cloud Licensing Policy. 2 vCPU= 1 Oracle Proc with Hyper threading enabled License included or BYOL MySQL and PostgreSQL open source BYOL Consider open source e.g. JBoss BYOL Support consideration Standard Oracle support. Oracle Database >=11.2.0.4 & >= 12.1.0.2. AWS EC2 DB optimized instances. Supported for Oracle Database >=11.2.0.4 & >= 12.1.0.2. AWS EC2 DB optimized instances. AWS RDS and Redshift are managed services. Standard Oracle support. Fully compatible AWS Elastic Beanstalk provides management features Standard Oracle support, including E- Business Suite, PeopleSoft, Siebel and more
- 11. Introducing Optimize CPUsfor Amazon EC2 Instances a) specify a custom number of vCPUs for new instances, while enjoying the same memory, storage, and bandwidth of a full- sized instance b) disable Intel Hyper-Threading Technology for workloads that perform well with single-threaded CPUsAmazon EC2 Enables Bring Your Own license (BYOL) customers to optimize their vCPU-based licensing costs!
- 12. Customers migrating Oracleto AWS include Oracle to Amazon Aurora Oracle Database on AWS Fusion Middleware Enterprise Applications Reduced processing time from 26 hours to 40 minutes Closed 2 of 6 datacenters “Enabling the business, no constraints” Supported 4x peak load, but cheaper than data center 20% TCO reduction 6x faster provision > 99.5% app availability ROI <6 months 400% lower infra TCO 1b star projections, 6 years data €500k less than on-prem “We didn’t encounter any roadblocks based on cost, functionality, or performance; we moved forward quickly and well within Sage’s budget.”
- 13. Oracle to AWSmigration options
- 14.
- 15. Approach for migration 1.Define the Goal and the Source 2. Define the Target 3. Define Transport Method 4. Setup Environment 5. Convert Schema 6. Transfer Data 7. Check Data 8. Switch Applications 9. Decommission Source algorithm noun word used by programmers when they do not want to explain what they did
- 16. Define the Goaland the Source
- 17.
- 18. Proprietary on-premises DBto AWS Managed DB service migration paths 1. One-to-One Migration 2. Migration via a Proxy 3. Migration with Schema Conversion 4. Migration with Constant Replication 5. Migration with Splitting the workloads
- 19. Example: Splitting workloads • Right hammerfor a right job • Ability to scale independently • Ability to correctly profile your workloads • Streamline the troubleshooting and optimization process • Ability to failover independently
- 20. Define Transport Method AmazonSnowball Via the Internet using VPN Gateway / Tsunami UDP Via the Internet using Direct Connect
- 21.
- 22. Convert Schema REMEMBER! Bothsource and target have limitations! 1. Data Types conversion (precision, data types emulation – ROWID, some aspects of working with NULL values, metadata, etc.) 2. Code conversion (partly Dynamic code conversion can be handled by SCT) 3. Constraints conversion 4. Functions conversion 5. Mappings and Transformation rules 6. Change Data Capture 7. Extra connection attributes
- 23.
- 24. Check Data &Test 1. Objects 2. Constraints 3. Procedures 4. Amount of data 5. Data behavior 6. Triggers 7. Conditions 8. Indexes
- 25.
- 26. Decommission Source &Temporary resources
- 27. Amazon DMS & SCT DMSSources: • Oracle (10.2 and later) • MS SQL Server (2005 and later) • MySQL (5.5, 5.6, 5.7) • MariaDB • PostgreSQL (9.4 and later) • SAP ASE (12.5, 15 and later) • MongoDB (2.6.x, 3.x and later) SCT Agents Sources: • Greenplum (4.3 and later) • MS SQL Server (2008 and later) • Netezza (7.0.3 and later) • Oracle (10 and later) • Terradata (13 and later) • Vertica (7.2.2 and later)
- 28. Other tools availableonline PLEASE NOTE that Amazon Web Services is not providing any type of warranty for the tools mentioned below. • Ora2Pg • Schema converter for Oracle to PostgreSQL (14 years of development) • Data replication capabilities • MigVisor • Tool for migration assessment and proper target selection • HPLSQL • Allows to run procedural code against any database without need to re-write the code • Orafce • Great library that allows you emulate Oracle specific functions for PostgreSQL.
- 29. © 2017, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Thank you! It is time for your questions.