Migration from Oracle to DB2: main processes and tools

Database migration can be seen as a special software development project. Different from other development projects, the requirements of this project are fixed, and the technical barriers are low. The main task is coding and testing. For database administrators, database data migration is extremely challenging. If improper measures are taken, precious data resources may be lost. To achieve smooth database data migration, well-planned and fully prepared, and completed according to certain steps. On the other hand, the success of the database migration project mainly depends on the active cooperation and orderly organization between the customer and the developer. Of course, enterprise databases usually have a large amount of data and a complicated structure. If they are done manually, it is an unimaginable big project. Therefore, the correct steps and appropriate migration tools can achieve twice the result with half the effort.

The main process of Oracle migration to DB2

Oracle migration to DB2 generally follows three major procedures: Migration evaluation, simulated migration, and formal migration.

1. Migration Evaluation

A comprehensive evaluation is a key element of migration success. The overall goal of the evaluation is to discover problems that may affect the migration process so that sufficient resources can be allocated to ensure the migration is successful. First, evaluate the application environment and application to identify potential obstacles; second, to what extent your Oracle database will adapt to DB2's hard data; and finally, analyzes Oracle database objects and processes to identify objects and processes that use features not supported in DB2.

2. Simulate migration

1) before performing a simulated migration, we must first design a data migration solution. The general design of the data migration solution mainly includes the following aspects: research on data migration-related materials, you can also query related content on the website, select the software and hardware platform for data migration, select the data migration method, select the data backup and recovery policies, and design the data migration and testing solutions.

2) create a simulated data migration environment based on the designed data migration solution. It can simulate the actual environment without affecting the actual data, then, test the effect of data migration in the data simulation migration environment. The simulated data should be backed up according to the backup policy before the simulated data migration, so that the recovery test can be conducted according to the recovery policy after the data migration.

3) Test the simulated data migration based on the designed data migration test scheme, that is, check whether the data and application software are normal after the simulated data migration, including: data Consistency testing, application software functional testing, performance testing, data backup and recovery testing, etc.

3. Formal migration

After the data simulation migration test is successful, data migration can be formally implemented. This section describes a simple test method. First, we use the DB2 compatibility feature to migrate Oracle Applications and create a compatible mode DB2 database. When Oracle Applications are enabled on DB2 V9.7, instances and databases must be in compatible mode. We also recommend that you adjust the rounding behavior to match Oracle. By setting revalidation semantics as deferred_force, you can deploy objects in no dependent order.

On UNIX systems:

$ Db2set DB2_COMPATIBILITY_VECTOR = ORA
$ Db2set DB2_DEFERRED_PREPARE_SEMANTICS = YES
$ Db2stop force
$ Db2start
$ Db2" Create Db testdb automatic storage yes On / Db2data1,
/ Db2data2, / Db2data3 DBPATH ON / Db2system PAGESIZE 32 K"
$ Db2 Update Db cfg For Testdb using auto_reval deferred_enforce
$ Db2 Update Db cfg For Testdb using decflt_rounding round_half_up
C :\ > Db2 Update Db cfg For Testdb using decflt_rounding round_half_up

 

On Windows:

C :\ > Db2set DB2_COMPATIBILITY_VECTOR = ORA
C :\ > Db2set DB2_DEFERRED_PREPARE_SEMANTICS = YES
C :\ > Db2stop force
C :\ > Db2start
C :\ > Db2" Create Db testdb automatic storage yes On C:, D: DBPATH ON E: PAGESIZE 32 K"
C :\ > Db2 Update Db cfg For Testdb using auto_reval deferred_enforce
C :\ > Db2 Update Db cfg For Testdb using decflt_rounding round_half_up

1 2 Next Page

[Content navigation]
Page 1: Main Process	Page 1: migration tools