Help Center/ Database and Application Migration UGO/ User Guide/ Object Migration/ Object Migration Implementation/ Making a Conversion Plan
Updated on 2024-11-07 GMT+08:00
View PDF
Share

Making a Conversion Plan

Scenarios

After a migration project is created, select objects to be migrated on the conversion plan page. You can select an object or a type of objects in batches.

Constraints

  • If the source database type is GoldenDB or MySQL (earlier than 8.0), there is no ROLE object in the source database. UGO does not collect ROLE objects and the number of ROLE objects is displayed as 0.
  • To migrate data, you are advised to skip the trigger migration temporarily. Otherwise, triggers may change data during migration. After data is migrated, migrate the triggers.
  • If Object Status of objects is Abnormal, their Conversion Status is Skip. It means that abnormal objects cannot be converted.

Prerequisites

  • The project status is Ready, the target database information is correct, and the connection test is successful.
  • The user connected to the target database must have the permissions to create, delete, and modify objects such as schemas, tables, programs, indexes, users, functions, and views. For details, see Viewing a Permission Check Report.

Converting Specified Objects

  1. Log in to the UGO console.
  2. In the navigation pane, choose Schema Migration > Object Migration.
  3. Locate the project to be migrated and click Migrate in the Operation column.

    Figure 1 Conversion plan

  4. Click Convert Specified Objects. The Convert Specified Objects dialog box is displayed.

    Figure 2 Converting specified objects
    • Click Download file template to download a template.
      • In the Excel file, the first column indicates schema, the second column indicates object type, and the third column indicates object name. The three columns specify an object and cannot be empty.
      • Click Convert Specified Objects to upload an Excel file. Identify all objects that meet the schema, object type, and object name requirements in the list with Convert displayed.
    • Click Add File to upload a file where there are objects to be converted.
      • The maximum size of the file is 30 MB, and the maximum number of rows is 65,535 (excluding the table header). If the content is incorrect, you can click View Error in the upload result to view the error cause. After the error is rectified, you can upload the file again.
      • After the file is uploaded successfully, the conversion status of objects is automatically updated.

Distribution Mapping of Table Objects

If the source database type is Oracle or MySQL and the target database type is GaussDB Distributed, you can perform the following operations:

  • Replicating tables: Select one or more objects and click Replicate Table above the list. The object name is suffixed with "Replicate Table".
  • Modifying distribution mapping information: Locate an object whose Object Type is TABLE and click Distribution Mapping in the Object Type column. Change the distribution type to HASH or REPLICATION and click Apply. The object name is suffixed with "replicate table" or "hash (Column name)".
  • Deleting distribution mapping information: Browse to a table object and click Distribution Mapping in the Object Type column. In the displayed dialog box, select Delete distributed mapping and click Apply. Distribution Mapping next to the object name will not be displayed.

    If you select Hash, all fields that meet the data type constraints of GaussDB distribution columns are displayed.