Oracle to DB2 UDB Conversion Guide2003
|
| < Day Day Up > |
|
4.2 Running MTK
It is efficient to use MTK to port the database objects from Oracle to DB2 UDB, extract and load data into DB2 database. In the following sections, we demonstrate step-by-step the migration process using MTK.
4.2.1 Migration details
MTK is a multi platform migration tool. In our lab, we run MTK on AIX, Linux and Windows platform. This section describes the lab environment and database structure used for MTK demonstration.
Environment
Before we begin to describe the details of our migration from Oracle 8i to DB2 UDB v8.1 using the IBM DB2 Migration Toolkit (MTK), here is some information about the source and target environments in our laboratory:
-
Oracle source operating system:
AIX 5L™ for POWER, Version 5.1
-
MTK source O/S:
Same as above
-
MTK build:
030627.0321, converter [030627.0309]
-
DB2 target O/S:
Linux - Red Hat v8.0
-
Oracle Version:
8.1.7
-
DB2 Version:
V8.1 FixPak2
We chose to install MTK on the AIX platform because that is where the Oracle database resides. Based on our experiences unloading data with MTK, it is most effective to install the tool on the operating system where the source system resides.
Oracle source database
The Oracle source database consists of the following kinds and numbers of objects:
-
Nine tables
-
Two views
-
Four indexes
-
Six foreign keys
-
Three functions
-
Five procedures
-
Three packages
-
Seven triggers
Appendix F, "Example Oracle database" on page 397 lists the definition of these objects. You also can download the code from IBM redbook Web site. The download information is provided in Appendix G, "Additional material" on page 415.
4.2.2 Creating/Opening a MTK project
When starting MTK, the Project management screen opens requesting the user to enter required and optional information for a new project or the ability to open a previously created object. When creating a new project the following information can be entered:
-
Project Name - Required. If a project name is not entered, it will default to Unknown. The Project Name given here will become the subdirectory name created on the operating system under the install directory of MTK. Therefore, the Project Name has to conform to the operating system naming standards that MTK is installed on.
-
Source Database - Required, choices include Sybase Enterprise, Microsoft SQL Server, and Oracle 8i.
-
DB2 target Platform - Required. Choices are DB2 UDB EE/EEE v7.2 or v8.1, DB2 UDB iSeries V5R2 or V5R3.
-
Project description - Optional.
Figure 4-1 shows the Project management screen with information completed for our Oracle migration project.
|
| < Day Day Up > |
|