Data Migration & Data Integrity - Validation

Googly

Member
We have a requirement to move complete JDE Data from DB2 to Oracle.

Can you share your thoughts about the following?
1. Challenges / Issues of Data Migration
2. Possible ways of validating “Data Integrity, after migrating data.
A. If there is a way to check data integrity, other than using "Integrity Reports".
B. If we use "Integrity Reports" over this huge data, approximately how much time will it take?
 
1) Here (link is a handy thread that was active only a few days ago. (Search is a useful feature.)

2) The only ways I know of are to 1 - Watch your record counts before and after, and 2 - run comparison reports both before and after, and compare the two sets of numbers for any discrepancies. There should also be logs from the system with any errors encountered.

A) Integrity reports are not the way to check for data integrity issues after a database platform migration. Integrity reports are there to check for various problems such as detail transaction records without headers, batches out of balance, etc. If you had integrity issues before, you will have them afterward, so maybe you could run them beforehand and correct any issues that arise, since you wind up doing so anyway.

B) Integrity reports can take a long time to run (hours), especially header/detail reports running over G/L. You get much better use of your time by running balance sheet and other such summary reports on the old database, and comparing them to the same reports run on the new database. Of course, nobody can tell you how much time it will take, because we don't know how much data you have.
 
Back
Top