A long journey to migrate from Oracle to DB2

Migration environment Configuration:

Data source:BNET Development Environment Data

Server:SunOS v880 5.8

Database:Oracle 9.2.0.4 & DB2 8.2

Migration tool:IBM DB2 Migration Toolkit 1.3

I. Table migration

1. Index length limit

In DB2, the maximum length of a field corresponding to a single index is 1024 characters.

Table Name:T_BIZPROC_INST_PARAM, T_BIZPROC_INST_ACTIVITY_PARAM

Solution:

(1) create different indexes for different fields in the case of a combined index

(2) modify the field type Length

2. Table Field Type

The NVARCHAR2 field type cannot be converted.

Table Name:T_IBSS_REL_TEST

Solution:Change to varchar Field Type

3. Table size and length limit

The table size exceeds the database page size by 4 kb.

Solution:Create a tablespace for the appropriate page (8 K)

4. The unique index and primary key fields are repeated.

DB2 does not allow fields with unique indexes to be repeated with primary key fields.

Table Name:T_NODE

Solution:Delete a unique index

5. Migration of large fields (BLOB, LONG)

Solution:

(1) DB2 migration tool

(2) write an INSERT script separately to migrate data

2. Synonym migration

1. solution:Write a script separately, for example, create alias alias_name for table_name.

Iii. Sequence migration

1. Sequence in DB2 can be in two forms:

(1) It exists independently like an ORACLE database.

(2) similar to SYBASE databases, they can be defined in Table fields.

2. solution:Because the upper limit of ORACLE sequence settings is relatively large, an error occurs if the maximum length type generated by ORACLE sequence migration through DB2 conversion tools. You need to manually Replace the DECIMAL (27,0) field type with the bigint field type with a length of 18.

Iv. Storage Process Migration

1. dynamic SQL statement syntax is different

Note: The stored procedure is not described in detail in the BNET production environment database.

• Database migration should not be ignored
• Where to go for database migration
• SQL Server database migration remedies
• SQL Server database minimal downtime migration Solution