Oracle to DB2 Migration Process flow Steps and standard practices

Compiled by : Sudhir B Titirmare

Phases of Migration Assessment 1. 2. 3. 4. 5. 6. 7. Migration Assessment Phase Database Object Migration Phase Application Migration Phase Solution Deployment Phase Go live with application Skills Transfer and DB2 ramp up (independent of above) Sign-off for application acceptance, using jointly defined success criteria

1. Migration Assessment Phase Provide DB2 Porting Assessment Questionnaire (PAQ) to Client Client submits completed DB2 Porting Assessment Questionnaire (PAQ) Overview questionnaire to identify potential road blocks IMTE consultant uses Migration Enablement Evaluation Tool (MEET) for DB2 to quickly identify code that uses Oracle features not supported in DB2 9.7 and efforts required for migration On-site analysis of the code if considered necessary Consultant completes porting assessment document and discusses recommendations with client Consultant works with client to create a detailed migration project plan 2. Database Object Migration Phase Conversion of database structures and objects Move data from old to new system Enabling compression if required Configuration of autonomic functions Basic performance test Typical activities include: Extract source database schema Extract source database objects Create DB2 database and enable compatibility features using the DB2_COMPATIBILITY_VECTOR registry variable Review data type mapping Re-create source schema on DB2 database Re-create source database objects using original PL/SQL code Leverage capabilities of the IBM Data Movement Tool to automate as much of the process as possible Currently supports extraction and deployment of the following objects: o Tables, Views, Sequences, Constraints, Indexes, PKs, FKs o Procedures, Functions, Triggers, Packages, User-defined Types o Roles, Privileges, Synonyms Data extraction Data conversion to match the new database schema (if needed)

Loading data in a new test database Verification and acceptance testing of the new database (data quality) Testing of application with data Plan and prepare overall process of moving production database data and verify. It can be done in the time window allocated Move data to product ion database Leverage capabilities of the IBM Data Movement Tool* Automate as much of the process as possible Offers high speed and parallel data movement Extracts Oracle data to f lat files

Creates scripts to import data using high speed DB2 LOAD utility

3. Application Migration Phase Code adjustments to existing application according to porting assessment Identifies code for usage in DB2 9.7 No Database software required Security features enforce that The utility is only run by an IBMer. HTML report o Identifies unsupported code o Lists details and source code o Provides summary statistics Function and System Test Application acceptance Typical activities include: Configure DB2 access interface (JDBC, .NET, ODBC, OCI, etc) Implement required changes to the application Identify differences in SQL and error handling Identify necessary isolation level and locking requirements of the application Convert SQL syntax to be compatible with DB2 Eventually add extra code in application to deal with multiple RDBMS ( #if def , if RDBMS=DB2 then..) Implement error handling f or DB2 Modify application for unsupported API functions that cannot be mimicked by DB2 user-defined functions or procedures Function testing changes

Application Migration - Function and System Test Typical activities include: Validate test output from application for errors Capture and monitor performance data Identify bad code segments (that probably existed even before but house keeping is a good idea) Validate data integrity (data analysis, record counts & object counts) Recommend changes to configuration settings and/or the application Recommend the adopt ion of other DB2 cost -saving features/ functionality For ISVs, accelerate the Ready-For-DB2* validation process

4. Solution Deployment Phase Additional database optimization Index review Overall Solution health check 5. Go Live with Applications On-site team to help immediately in tuning and optimization of live system Educate client team on DB2 Autonomics and operational tasks ! 6. Skills Transfer and DB2 ramp up (independent of above) Build confidence on DB2 database Developer and DBA expect major changes; it is key to ensure that DB2 and Oracle have more in common than PL/SQL and skills are re-usable Learn how to exploit features that are independent of the code level o Compression

o pureScale o pureXML o pureQuery o Autonomics Good training options are available onsite for larger teams, at IBM facilities and online (eLearner Portal)

7. Sign-off for application acceptance, using jointly defined success criteria