Introducing Basic Functions of Conversion Configuration

Conversion Config

Scenarios

The conversion scenarios controlled by each feature parameter are different. It is difficult for users and service personnel to systematically and comprehensively understand the conversion. As a result, multiple reworks are required, affecting migration efficiency and user experience. Therefore, you can use conversion configuration to reduce the manual update configuration and quickly and accurately complete the migration.

Constraints

The system view and advanced package are converted based on the latest GaussDB version. If the target database is of an earlier version, the SQL statements after conversion may be incompatible.

Procedure

1. Log in to the UGO console.
2. In the navigation pane on the left, choose Schema Migration > Object Migration. The migration project list is displayed.
3. Locate the project to be migrated and click Migrate in the Operation column. In the Conversion Config page, you can view the features, affected object types, and current configurations of the target database.

   By default, features are sorted in descending order based on the configured usage frequency (which may be used in the actual environment).

   In the Current Configuration column, move the cursor to of each feature to view the impact of the feature. You can click View Sample to view details about the configuration information and the current configuration conversion example.

   For details about the configuration items, see Editing the Configurations During Migration from Oracle to GaussDB, Editing the Configurations During Migration from MySQL to GaussDB and Editing the Configurations During Migration from DB2 to GaussDB.

   • If the source database type is Oracle and the target database type is GaussDB:

     

     • Configure Category and click Apply.
     • When Category is set to Default or Maximum compatible, the current configuration cannot be modified.
     • When Category is set to Customize Template, you can select an existing template or create a new template. When you create a new template, you can configure features as needed based on an existing template.

       The new template name must be unique and can contain 5 to 50 characters, including only letters, digits, underscores (_), and hyphens (-). It must start with a letter and end with a letter or digit.

     • After you select a template, locate a feature and click Edit Configuration in the Operation column to modify the current configuration of the feature. After the modification, click Apply. If the target database version and deployment mode in different migration projects are the same, you can apply or modify the template you created in previous projects.
     • You can create up to 50 custom templates for each migration link.
     • Deleted templates cannot be restored. Exercise caution when performing this operation.
   • If the source database type is MySQL or DB2 and the target database is GaussDB:

     

     • Configure Category and click Apply.
     • To modify current configuration of a feature, locate the feature and click Edit Configuration in the Operation column.
   • If the source database type is Oracle and the target database type is not GaussDB, you can directly modify the current configuration of a feature.

     

Tablespace Mapping

Scenarios

You need to create mappings between tablespaces in the source and target database.

Constraints:

• If the source database type is MySQL, disable the tablespace mapping function.
• If the target database type is GaussDB(for MySQL) or RDS for MySQL, disable the tablespace mapping function.

Procedure

1. Log in to the UGO console.
2. In the navigation pane on the left, choose Schema Migration > Object Migration. The migration project list is displayed.
3. Locate a project you want to migrate and click Migrate in the Operation column. On the Conversion Config page, click Table Mapping.
   Figure 1 Tablespace mapping
   

4. To add a tablespace mapping, select the required tablespaces of the source and target databases.
5. Click Map Tablespace.

The tablespace mapping from source database to target database can be one-to-one or many-to-one.

Deleting a tablespace mapping:

Locate the tablespace to which the mapping has been added in the list, click Delete in the Operation column. In the displayed dialog box, click Delete.

Figure 2 Deleting a tablespace mapping