Dameng database tutorial: DM8 data migration tool usage tutorial (oracle migration to DM8)

DM Data Migration Tool

DM data migration tool DM DTS provides functions such as migrating mainstream large databases to DM, DM to DM, files to DM, and DM to files.

Thanks to DM database's industry-leading compatibility with current mainstream large-scale relational database systems, it remains highly compatible with them at the storage level, syntax level, and interface level. With the help of the DM graphical interface and the use of wizards to guide DTS in each migration step Tools make porting very easy.

Migration preparation

1. stop application
2. Confirm users to be migrated (schema, database)
3. Record the number of objects to be migrated in the original database
4. Record the names of all objects to be migrated in the original database
5. Record the data volume (number of rows) of the table to be migrated in the original database
6. Create target data and instances
7. Create the table space and user for the target data

Start the migration tool

• Start DM data migration tool in Windows environment

Click [Start Interface], select [Dameng Database] menu, click [DM Data Migration Tool] to enter the data migration tool, as shown in the figure below:

• Start DM data migration tool in Linux environment

Enter the database installation path/tool ​​directory and run ./dts to start the DM data migration tool.

migration process

New Construction and Migration

Click the button to create a new project, enter the project name and project description, and click [OK] to create the project, as shown in the figure below:

Right-click and select [New Migration], enter the migration name and migration description, and you can create the migration, as shown in the following figure:

Enter the migration name: Oracle-DM, click the [OK] button to complete the creation of the migration, as shown in the following figure:

Select the newly created migration to view the welcome interface of the migration tool, which introduces the support of the migration tool and other information, as shown in the following figure:

Select data source and destination database

Click [Next] on the welcome interface and select the migration method. Take Oracle migration to DM database as an example, as shown in the following figure:

Enter the information of the data source (Oracle database): host name (IP), port, service name (Oracle default service name ORCL), role (default), user name and password, as shown in the following figure:

To confirm that the database information is correct, leave it open and Oracle listening is started.

Then enter the information of the destination database (DM database): host name (IP), port (DM default port 5236), user name and password, as shown in the figure below:

To confirm that the DM database information is correct, leave it open.

Specify object copy or query

Select source mode and destination mode.

• The copied objects include: schema and schema objects, directories, public synonyms, context, etc. It supports copying different objects according to different data sources.
• Schema and schema objects include: schema, table, view, materialized view, sequence, stored procedure/function, package, class, synonym and custom type. The supported schema and schema objects are different depending on the data source.

Select migration object

Here, select the specific tables, views, stored procedures, etc. to be migrated. Users can select specific tables, views, and stored procedures based on their names.

Set table mapping relationship

Set the mapping relationship of the table, including column mapping, table creation strategy, data copying strategy, and whether to manually edit the SQL for creating the table.

Migration strategy options: Migration strategies can be set, including table definition, primary key, constraints, indexes, data, read and write row number settings and other parameters, allowing users to adjust the strategy. As shown below:

Review migration tasks

Review the tasks to be performed listed in the list. Users can view the important parameters and modification conditions of the migration process, and click [Finish] to proceed to the next step. If modifications are required, click [Previous] to make modifications. As shown below:

Click [Finish] to start data migration, as shown in the following figure:

verify the data

Query the number of objects to be migrated in the database after migration. The example statement is as follows:

select object_type,count(*) from all_objects where owner=SCOTT group by object_type order by 1;

As shown below:

Query the names of all objects to be migrated in the database after the record migration, as shown in the following figure:

After completing the data migration, we still need to verify the migrated data. Tables, views, stored procedures, and sequences all exist and are consistent with the original data. After confirming that there are no abnormalities in the data, make a full backup of the migrated database.

Notice

During the migration process, you may encounter a situation where the original object name does not match the migrated object name, but the number is the same. This situation is mainly a constraint class object. Because the original library used automatic naming by the system, it will also be automatically named by the system after migration. Although the names are different, the content and functions are the same.

---

links：

https://eco.dameng.com/document/dm/zh-cn/start/tool-dm-migrate.html