Database Migration Assessment (DMA)

Transcription

1 Database Migration Assessment (DMA) A compatibility analysis for deploying <organization s> Oracle schema, <schemaname>, on EnterpriseDB Postgres Plus Advanced Server. Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 1

2 Executive Summary At the request of <customer>, EnterpriseDB has performed a Database Migration Assessment (DMA) for the Oracle <schema-name> schema. This DMA was concluded by <consultant> on <date> under the direction of <EDB Sales Rep> and is being delivered to <organization contact>. EnterpriseDB has found the <schema-name> schema to have a Compatibility Index Score of <score 1 to 10> and to be a <quality> candidate for migration from Oracle to Postgres Plus Advanced Server. We estimate that the migration should take approximately <duration> weeks to complete. This document outlines: The process used for performing this DMA A summary of successful/failed migration objects percentages A summary of the objects migrated without issue or modification A summary of the objects migrated by the use of workarounds A summary of the objects that failed migration Conclusions and next steps Additionally, you will find the following appendices: A listing of the objects that required workarounds and information on the workaround applied A migrated schema dump showing what the <schema-name> schema looks like in Postgres Plus Advanced Server post-migration Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 2

3 The Database Migration Process The migration of a database schema from one DBMS to another is an iterative process that can prove to be both lengthy and complicated. As the leading independent DBMS solution provider, EnterpriseDB offers both the Postgres Plus Advanced Server and the Migration Toolkit to facilitate organizations like your own to migrate from the proprietary Oracle DBMS to an open source based DBMS in both a safe and cost-effective manner. Postgres Plus Advanced Server, while based on the excellent PostgreSQL DBMS, has been engineered from the ground up to be compatible with the Oracle flagship database and the Migration Toolkit has been designed to allow an organization to judge the relative compatibility of their existing Oracle schema with Postgres Plus Advanced Server in a non-invasive, preparatory fashion. Based on information obtained both from conversations with and schema dumps provided by your staff, we understand your existing Oracle <schema-name> schema to have the following general profile: General Information Oracle version: <version> Database name: <original db name> Schema name: <schema-name> Database size: <size MB/GB/TB> Database growth rate: <growth rate> Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 3

4 Object Counts Database Links: <# dblinks> Functions: <# functions> Indexes: <# indexes> Packages: <# packages> Package Bodies: <# package bodies> Procedures: <# procedures> Sequences: <# sequences> Tables: <# tables> Triggers: <# triggers> Types: <# types> Type Bodies: <# type bodies> Constraint Counts Check/Not Null: <# not null> Foreign Key: <# foreign keys> Primary Key: <# primary keys> Unique Key: <# unique> Migratable objects percentages The following table shows an overview of the objects identified in the <schemaname> schema and the respective breakdown of these objects into three categories: migratable as is, migratable using workarounds, and non-migratable Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 4

5 Object Type Total Count Migratable Count Workaround Count Non- Migratable Count Migratable % DATABASE LINK % FUNCTION % INDEX % PROCEDURE % SEQUENCE % TABLE % TRIGGER % VIEW % Migratable objects The following Oracle objects in the <schema-name> schema were identified by the EDB Migration Toolkit as fully compatible with Postgres Plus Advanced Server and require no additional effort to complete the migration: Object Counts Functions: <# ok functions> Indexes: <# ok indexes> Packages: <# of ok packages> Package Bodies: <# package bodies> Procedures: <# ok procedures> Sequences: <# ok sequences> Tables: <# ok tables> Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 5

6 Triggers: <# ok triggers> Types: <# ok types> Type Bodies: <# ok type bodies> Constraint Counts Check/Not Null: <# ok not null> Foreign Key: <# ok foreign> Primary Key: <# ok primary> Unique Key: <# ok unique> Migratable-via-workaround objects The following Oracle objects in the,schema-name> schema were identified by the Migration Toolkit as partially compatible with Postgres Plus Advanced Server and require additional effort to complete the migration in the form of known workarounds: Object Counts Functions: <# wrk functions > Indexes: <# wrk indexes > Packages: <# wrk packages> Package Bodies: <# wrk package bodies> Procedures: <# wrk procedures> Sequences: <# wrk sequences> Tables: <# wrk tables > Triggers: <# wrk triggers> Types: <# wrk types > Type Bodies: <# wrk type bodies> Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 6

7 Constraint Counts Check/Not Null: <# wrk not null> Foreign Key: <# wrk foreign> Primary Key: <# wrk primary> Unique Key: <# wrk unique> Non-Migratable objects The following Oracle objects in the <schema-name> schema were identified by the Migration Toolkit as incompatible with Postgres Plus Advanced Server and have no known workarounds: Object Counts Functions: <# fail functions > Indexes: <# fail indexes> Packages: <# fail packages> Package Bodies: <# fail package bodies> Procedures: <# fail procedures> Sequences: <# fail sequences> Tables: <# fail tables> Triggers: <# fail triggers> Types: <# fail types> Type Bodies: <# failtypebodies> Constraint Counts Check/Not Null: <# fail not null> Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 7

8 Foreign Key: <# fail foreign> Primary Key: <# fail primary> Unique Key: <# fail unique> Conclusions and next steps As stated above, EnterpriseDB has thoroughly investigated the <schema-name> schema and found it to be a <quality> candidate for migration from Oracle to Postgres Plus Advanced Server. We have assigned this schema an overall Compatibility Score of <score> (see bar, below) and estimate that the migration should take approximately DURATION weeks to complete. These conclusions were based on mapping the Oracle features and functionality in use in the <schema-name> schema to their appropriately equivalent features in Postgres Plus Advanced Server using a complex formula and assigning them various weight values. A visual representation of these weightings can be seen to the right. We also advise you to examine our Database Compatibility for Oracle Developer s Guide for further insight into our determinations. EnterpriseDB offers a wide range of services to assist you both during and after the migration of the <schema-name> schema from Oracle to Postgres Plus Advanced Server. The services include, but are not limited to: Performing the schema migration for you Assisting CUSTOMER personnel in performing the schema migration themselves 24x7 Technical Support Remote DBA Services Architectural Health Check PostgreSQL Training Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 8

9 For a full listing of the services available to you, please visit: We advise you to speak with <EDB sales rep> concerning any questions you might have about this Database Migration Assessment report or the services listed above. We would like to extend our thanks to the staff of <organization> for their assistance in performing this assessment and we look forward to working with you again the future. Thank You, The EnterpriseDB Team Copyright 2014 EnterpriseDB Corporation. All Rights Reserved. Page: 9