Source Database Preparation and Authorization Tips

During evaluation project creation, UGO will check the permissions of the source database. Before creating an evaluation task, perform the following operations.

• To ensure that the DDLs returned by DBMS_METADATA.GET_DDL are consistent, you can perform the following settings on the Oracle source database:
  • Ensure that there are no collation clauses (which will affect USER, TABLE, CLUSTER, VIEW, MATERIALIZED_VIEW, PROCEDURE, FUNCTION, PACKAGE, TYPE, and TRIGGER).

    In the SQLPlus: Run EXECUTE DBMS_METADATA.SET_TRANSFORM_PARAM(dbms_metadata.SESSION_TRANSFORM, 'COLLATION_CLAUSE', 'NEVER');

  • Make table constraints and indexes a part of the CREATE TABLE statements.

    In the SQLPlus: Run EXECUTE DBMS_METADATA.SET_TRANSFORM_PARAM(dbms_metadata.SESSION_TRANSFORM, 'CONSTRAINTS_AS_ALTER', false);

• You have permissions to create an evaluation project. To obtain permissions, see Permission Management.
• The source database must pass the following pre-check items.
  • Oracle as the source database: DBMS_METADATA, Dynamic View, and Schema Object Count Check permissions.
  • MySQL as the source database: query permissions and PROCESS permissions on the MySQL system database and all permissions on the databases to be migrated. In MySQL 8.0 and later versions, if there are stored procedures and functions in the source database, SHOW_ROUTINE permissions are required.
  • GoldenDB as the source database: query permissions and PROCESS permissions on the GoldenDB system database and all permissions on the databases to be migrated. For stored procedures and functions, the SHOW_ROUTINE permission is also required.
  • Microsoft SQL Server as the source database: VIEW DEFINITION permissions.

MySQL or GoldenDB as the source database: If a user is granted to the global SELECT permissions and SHOW_ROUTINE permissions. No other permissions are required.