Professional Documents
Culture Documents
Student Guide
S105465GC10
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training
course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle.
The information contained in this document is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of
such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software
documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure,
modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered
hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable
contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not
be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Module 14 – Data Management and
Migration Plan
Oracle Cloud Project Management Training for Partners
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.
Part 1
Oracle Alliances & Channels
Learning Objectives
Data Management and Migration Plan
Analyze & Plan & Configure & Validate & Transition & Sustain &
Prepare Design Build Test Go Live Realize
Corporate Data
Compliance
Growth Volume
Data
Data Decay Data Denial
Diversity
Technical Economic
Advances Factors
Major Activities
> Define and agree upon data migration scope, strategy, plan, and approach.
> Verify scope of extraction, transformation, loading, and reconciliation.
> Analyze the nature of data being transferred among different applications and source and target databases.
> Audit and profile the data, develop mapping specifications and migration code to be written.
> Identify mode of transfer (file or data) with/without transformation from source to target.
> Identify the data sources what is achievable, supportable, reasonable.
> Identify the volume and frequency of the data exchange.
> Define data transformation and migration responsibilities.
> Identify the IT landscape and business dependencies.
> Identify the SOW for data management (OLTP use case or DW use case).
> Determine data connections, data security, and import model (direct, flat files, no-SQL, FS, HFS).
> Determine data models, data retrieving, and aggregation rules.
SOURCES
Sales Customer Service Billing
Extract
Project Planning Profile & Project
Design Transform Test
Start Audit Sign-off
Load (ETL)
• Define Scope • Full Volume
• Establish Data Analysis
Governance • Understanding
Data Quality
procedures of all resources Check
• Cleanse
• Match
TARGET • Parse
CRM/ERP/DW
Work with database admins, network admins, and system admins to determine the strategy
for the migration. Some of the characteristics and factors to consider when choosing a
migration method are
Major Activities
> Provide orientation to data migration tools and templates.
> Review initial data migration sample (30-40%): Extract, Transform, Load and Key Deliverables / Artifacts
Reconciliation. • Confirmed data sheets (templates)
> Build data transformation and cleansing rules to load and test the data. • Cut over plan
> Identify / design data sources and their type (file transfer only or data • Data cleansing approach
transfer with/without transformation) and Nature (Oracle or third party) • Database migration plan and
being transferred among different applications from source to target. method
> Identify the volume and frequency of the data exchange, arrive at sizing • Cloud architecture
requirement for PaaS/Integration services.
> Design data acquiring model from data sources (data integration, data
migration, data backup, file system, etc).
> Develop rules for transferring all designated source data to fit the target.
> Finalize SOW for data management (OLTP use case or DW use case).
> Assess cloud readiness.
> Develop cloud architecture.
> Develop a migration path.
Plug/Unplug
Zero Down time
Data Pump
Migration (ZDM)
Recovery Manager
MV2ADB
Maximum Availability
Architecture
Oracle SQL
OCI Data Transfer Remote Cloning
Developer
Appliance
Other ETL Tools/Scripts YES (1) DBs, Flat files YES Some
18 Copyright © 2020, Oracle and/or its affiliates.
Migration Methods
References and links
Autonomous Database
Fully Self-Driving Database Oracle Builds and Cloud elasticity, machine learning, self–driving.
Operates Exadata Infrastructure and Databases User Instant provisioning, always online operation.
runs SQL, no Access to OS or Container DB All workloads, JSONDocuments, graphs, and more.
ORACLE
CLOUD
Exadata Cloud
DBaaS Autonomous Autonomous
Service or Cloud
VM or BareMetal Serverless Dedicated
Customer
Management Customer Customer Oracle Oracle
Software Updates Customer Initiated Customer Initiated Automatic Customer Policy Control
Part 2
Oracle Alliances & Channels
Autonomous Database
Optimized by workload
ORACLE
AUTONOMOUS
DATABASE
Autonomous
Autonomous
Transaction Processing
Data Warehouse (ADW)
(ATP)
Best for all analytic workloads: Best for TP and mixed workloads:
• Data warehouse, Data Mart • Transactions, batch, reporting, IoT
• Data lake, machine learning • Application dev, machine learning
Reduce Risk
• Be protected from attacks by automatically applying security updates.
• Mitigate breach impact by avoiding reputational damage, associated breach costs, and revenue losses.
• Eliminate human intervention and remove the most common cause of systems/data errors.
• Provisioning
• Scale-up and Scale-out
• Tuning
• Security and patching
• Fault tolerance
• Optimized
• Protection (backup and restore)
Load data into ADB Cloud using Oracle database tools and third-party integration tools. Loading data can be achieved:
• From files local to your client computer, or
• From files stored in a cloud based object store
Option Loading & Import Performance Factors & Considerations Volume of Data
Loading Data (for accessing directly) From Oracle Object Store. Data from • Copying files to Object Storage (size & Unlimited Volume
to ADB from cloud-based object store any application or data source export network bandwidth from source)
(DBMS_Cloud) PREFERRED METHOD to text (.csv or JSON); Output from 3rd • Importing from Object Store (time &
party data integration tools. Flexibility parallelism) to ADB storage
to access data stored on object • Querying directly from Object Storage from
storage from other clouds (AWS, S3 ADB (external tables)
and azure blob Storage *) • Use Data Transfer Service (HDD)* for very
large initial, one time bulk load
Loading using SQL*loader Loading Data file (Oracle data) from • Load performance depends on the network Limited to OS and Client
local files on client local machine bandwidth between your client and machine
Autonomous Data Warehouse Could
Importing Data using Oracle Data Using Data Pump Export from existing • Copying.dmp file to Object Storage (size & Medium/large Volumes
Pump Oracle Database (version 12.2.0.1 and network bandwidth)
Earlier • Size of .dmp file (processing)
• Increase CPUs dynamically to meet loading
time requirements
Importing Data Using import Wizard Using SQL Developer import wizards • Import .XLS files (limited to row limited in Local Desktop – Limited to
from Desktop tool: SQL Developer from Local Desktop (CSV, Excel, TXT) excel version) Desktop resources
* Project will need to consider and may incur outbound data transfer costs
40 Copyright © 2020, Oracle and/or its affiliates.
Moving Existing Data Marts or DWs to the Cloud
Typical activity list
Major Activities
> Second iteration of data migration (up to 60%): Map, load, validate
> Review progress (extract, transform, load, and reconciliation scope).
> Provision the cloud data stores in Oracle cloud (ATP, ADW or BDS).
> Transfer the data to the respective cloud service.
> Design and implement the mechanisms for data usage (in and out of oracle cloud data stores).
> Transfer the application and database data from the on-premises location to cloud tenancy.
> Migrate data to cloud database repository (from on-premises or from other locations).
1 2 3 4 5
Autonomous
Database DataLoad Analytics/Application Run Monitor
Setup Setup
NFSv4
NFSv4
Object Storage
Storage Gateway is an efficient tool to move data from your on-premises data center to the cloud.
Major Activities
> Load full-volume data on TEST Environment before testing commences
> Conduct unit, system, volume, online application, and batch application tests.
> Full Data Migration, transformation and loading with baselining time estimates for production preparation
> Data reconciliation and validation
> Review the progress and revalidate the cutover dates and customer readiness.
> Run data validation scripts against all data sources.
> Check and resolve ADB restrictions before transferring the data.
> Perform functional and performance tests during UAT project.
> Obtain end-client UAT final acceptance.
Major Activities
> Load, reconcile, and validate full data in production.
> Data is extracted from the source system, transformed, cleansed, and loaded into the
target system, using the migration rules.
> Transfer existing historical data to cloud database repository.
> Transfer current data to cloud database repository and create the online transfer
process.
> Conduct audit on the migrated database or application data.
> Connect the application package / analytics layer to ADB and test the connection.
Major Activities:
> Reconcile transactional data (payroll, financial period closure).
> Plan for additional data loads for subsequent phases/releases.
> Manage and monitor the autonomous database through the cloud console.
> Stop, start, and scale the ADB to manage costs effectively.
Learning
• Oracle Autonomous Database 2019 for SE-L3
• Oracle Autonomous Database Cloud 2019 Specialist
• Oracle Autonomous Database Training and Certification
Documentation
• Autonomous Data Warehouse Tools and Application Test Matrix
• MOS Note: Oracle Autonomous Database Schema Advisor (Doc ID 2462677.1)
• Autonomous Data Warehouse Service Documentation
• Autonomous Transaction Processing Documentation
• Successful Data Migration - Oracle White Paper
References
• What Is Oracle Autonomous Database?
• Think Autonomous
• Database Migration to Oracle Cloud Infrastructure: Evaluation and Planning Checklist
Analyze the on-premises deployment architecture • Determine the DB type (ATP /ADW)
• Infrastructure and Security layer • Determine the connection type (for application layer (ATP) or for analytics
- Determine machine deployment type (bare metal / Virtualized) (ADW))
- Determine network and security topology Provision / install the cloud instances for the created architecture
- Determine user management type (federated/SSO/Application only) • Provision IaaS OCI resources (VCN, compartments, etc)
- Determine disk storage topology (network, external, VM hosted, etc) • Create network topology
• Database layer • Create the security and access rules
- Determine database type, version and location (OLTP, DW+ETL, Data lake, • Provision ADB PaaS instances
etc)
Migrate data to cloud database repository (from on-premises or from other locations)
- Determine data connections, data security and import model (direct, flat
files, no-SQL, FS, HFS) • Run data validation scripts against all data sources
- Determine data models, data import/export rules, • Check and resolve ADB restrictions before transferring the data
• Database version upgrade process • Transfer existing historical data to cloud database repository
- Plan version upgrade process (to 19c) • Transfer current data to cloud database repository and create the online
- Plan migration to autonomous respecting the ADB restrictions transfer process
Create the cloud deployment architecture for new automated DB Connect the Application package / Analytics layer to ADB and test the connection
• Create deployment architecture (PreProd/Dev/test/UAT/Prod) + replication Test deployed analytics application package
rules
• Functional testing (availability tests, scaling tests, replication tests, etc)
• Create infrastructure ADB deployment model
• Performance testing
- Determine number of ADB instances
- Determine the compartments, network topology, security lists, routing
tables, network gateways, etc
- Determine the users access and roles
- Determine Object storage / Files storage architecture and security
53 Copyright © 2020, Oracle and/or its affiliates.
Conclusion
Data Management and Migration Plan
Now that you have completed this module, you should be able to:
• Identify the reasons why to migrate data and define the key drivers of data complexity
• Explain the target-driven data migration approach
• List the golden rules for successful data migration
• Describe the migration strategy and methods
• Explain the difference between the various migration tools
• Describe the database types for data management and migration purposes
• Use Autonomous Database for Autonomous Data Warehouse (ADW) and Autonomous Transaction Processing
(ATP)
• Explain the key considerations to prepare for data transformation strategy and migration management in cloud
project delivery
• Identify the key steps in developing data migration strategy and tactics
• Get familiar with data governance through DAMA DMBoK