Editing Conversion Configurations

Conversion Configuration

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. 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. Click Conversion Config.
4. In the Configuration tab, import parameter configuration.
   • You can set Parameter Configuration to Default value or Max compatibility, or import a created conversion configuration template. For details about how to create a conversion configuration template, see Creating a Configuration Template.
   • 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.
   • Locate a feature and click Edit in the Operation column to modify the current configuration of the feature and click OK. For details, see Migration Configurations.
   • After you import configuration parameters, the configuration status of features is Default value. If you edit the configuration of a feature, the configuration status will become Modified.
   • If the custom template that your project is used is deleted, your project still uses the configurations of the template, but Parameter Configuration is Default value.

Tablespace Mapping

Scenarios

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

Constraints

The following migration flows support the tablespace mapping function.

From Oracle to GaussDB

From Oracle to PostgresSQL

From DB2 for LUW to GaussDB

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 Tablespace 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.