| < Day Day Up > |
|
The data conversion process is quite complex. Before you define a porting method, you should do some tests only with a portion of the data to verify the chosen method. But the tests should cover all potential cases. We recommend that you start early with the testing.
The tasks of the test phase are:
Calculate the source data size and calculate the needed space for the files on disk.
Select the tools and the conversion method.
Test the conversion using the chosen method with small amount of data.
With the result of the test, you should be able to:
Estimate the time for the complete data conversion process.
Create a plan for development environment conversion. Use the information about to derive a complete plan.
Create a plan for production environment conversion. Use the information from development environment conversion.
Schedule the time.
The following objects influence the time and complexity of the process:
Amount of data and data changes
The more data you have to move to more time you need. Consider the data changes as well as the timestamp conversions.
System availability
You can run the data movement either during the production system is down or during the business process is running by synchronizing source and target database. Depending on the strategy you choose, you need less or more time.
Hardware resources
Be aware that you need up to three times the disk space during the data movement for:
The source data in Oracle
The unloaded data stored in the filesystem
The loaded data in the target DB2 UDB
| < Day Day Up > |
|