16 Copyright © 2004, Oracle. All rights reserved. Testing the Migrated Oracle Database

16-2 Copyright © 2004, Oracle. All rights reserved. Objectives After completing this lesson, you should be able to do the following: Use Oracle Migration Verifier to verify that the schema and data migrated successfully Apply guidelines to design and run test cases on the migrated Oracle database

16-3 Copyright © 2004, Oracle. All rights reserved. Objectives for Testing During the testing phase, you test the application and the Oracle database to make sure that the: Migrated data is complete and accurate Application functions in the same way as in the source database Oracle database schema is complete Oracle database produces the same results as the source database Applications and the Oracle database meet the operational and performance requirements

16-4 Copyright © 2004, Oracle. All rights reserved. Testing Methodology Testing can contain one or all of the following: Simple data validation Full life cycle of module testing System and acceptance testing Performance testing

16-5 Copyright © 2004, Oracle. All rights reserved. V Model with a Database Migration D evelopment phase Testing phase D atabase migration requirements System acceptance testing Database/ application design Integration testing Database object testing

16-6 Copyright © 2004, Oracle. All rights reserved. Testing the Oracle Database Oracle recommends you to use: Oracle Database Migration Verifier to help verify that the schema and data migrated successfully Test cases to verify that the Oracle database produces the same business logic results as the source database

16-7 Copyright © 2004, Oracle. All rights reserved. Database Migration Verifier Oracle Database Migration Verifier is a command-line tool: To validate the structural integrity of the database objects in a migrated database That compares your source database and the migrated Oracle database to identify any potential issues before user acceptance testing That performs verification checks and produces a report summarizing the results

16-8 Copyright © 2004, Oracle. All rights reserved. Supported Databases The following databases are supported by DMV: Third-party databases –Microsoft SQL Server 2000 –Sybase Adaptive Server 12 Oracle databases –Oracle 9.2.x –Oracle Database 10g

16-9 Copyright © 2004, Oracle. All rights reserved. System Requirements Depending on the third party and the Oracle database that you are verifying, you need the following to run DMV: JDK 1.3.x Oracle Database 10g JDBC Driver Oracle9 i Release 2 JDBC Driver Microsoft SQL Server 2000 Driver for JDBC Sybase jConnect 4.5 for JDBC

16-10 Copyright © 2004, Oracle. All rights reserved. Installing DMV To install DMV, perform the following steps: 1.Download the dmv.zip file from OTN at: 2.Extract the files to your local directory. 3.Open the ddbinfoss2k.prop property file located under the /config directory.

16-11 Copyright © 2004, Oracle. All rights reserved. Installing DMV 4.Edit the properties file to connect to the source database and Oracle database. Provide the following information: –JDBC class path –Source database URL, username, and password –Oracle database URL, username, and password 5.Save the properties file.

16-12 Copyright © 2004, Oracle. All rights reserved. Full Notes Page

16-13 Copyright © 2004, Oracle. All rights reserved. Using the DMV To use the DMV, enter the following command: The DMV must be connected to both, the source and destination database, to generate the verification report. > java -jar e:\oracle\dmv\dmv.jar e:\oracle\dmv\config\dbinfoss2k.prop HR_DMVReport.txt

16-14 Copyright © 2004, Oracle. All rights reserved. Viewing the DMV Report

16-15 Copyright © 2004, Oracle. All rights reserved. Full Notes Page

16-16 Copyright © 2004, Oracle. All rights reserved. Where Are We? Oracle Database Migration Verifier used to verify the schema and data migrated successfully Test cases used to verify that the Oracle database produces the same business results as the source database

16-17 Copyright © 2004, Oracle. All rights reserved. What to Test Design test cases to provide comprehensive coverage: Users Privileges Primary keys Foreign keys Check constraints Defaults Views Triggers Procedures Functions

16-18 Copyright © 2004, Oracle. All rights reserved. Guidelines for Creating Test Cases Guidelines for creating test cases: Prioritize testing according to business benefits. Define each test case so that it is reproducible. Identify test components, approach, and completion criteria. Create a test case for each functional area and procedure.

16-19 Copyright © 2004, Oracle. All rights reserved. Guidelines for Running Test Cases When running test cases, use the following guidelines: Record the expected result of each test case. Verify that the actual results meet the expected results. Have someone other than the test creator run the test. Track issues that you find during a testing cycle.

16-20 Copyright © 2004, Oracle. All rights reserved. Set up controlled environment. Run test cases. Test Execution Fix errors.Evaluate results. Acceptance tests FailedPassed

16-21 Copyright © 2004, Oracle. All rights reserved. Full Notes Page

16-22 Copyright © 2004, Oracle. All rights reserved. Example of Unit Test Plan Name: ______________________________ Module: _____________________________ Date test completed: __________________ Coverage log file location: _____________ Description: _________________________ Reviewed by: ________________________ Task ID Task Description Expected Result Verified (Yes/No) 1 2

16-23 Copyright © 2004, Oracle. All rights reserved. Summary In this lesson, you should have learned how to: Use Oracle Migration Verifier to verify that the schema and data migrated successfully Apply guidelines to design and run test cases on the migrated Oracle database

16-24 Copyright © 2004, Oracle. All rights reserved. Practice Overview: Testing the Migrated Oracle Database This practice covers the following topics: Interpreting the results of a DMV report Testing the migrated stored procedure Reviewing, correcting, and testing a trigger