Step 1: Create an Evaluation Project

Scenarios

This section describes the process of creating an evaluation project.

An evaluation project evaluates source databases and allows you to migrate the database objects to the selected target database.

Prerequisites

• Connection to the source database is successful, and all pre-check items are passed.
• You have permissions to create an evaluation project. To obtain permissions, see Permission Management.
• You must have the following permissions for the source database to be migrated: DBMS_METADATA, Dynamic View, and Schema Object Count Check. If the source database type is DB2, you must have the DBADM or DATAACCESS permission. Otherwise, the pre-check fails and the next step cannot be performed.

You are advised to use a database in a non-production environment.

Procedure

1. Log in to the UGO console.
2. In the navigation pane on the left, choose Schema Migration > DB Evaluation.
3. Click Create Project in the upper right corner.
4. Read Source Database Preparation and Authorization Tips and click Start Create.
5. Enter the basic information on the Basic Details page. For details about the parameters, see Table 1.
   After the basic information is entered, the Test Connection button is available.

   Figure 1 Evaluation project creation
   

   Table 1 Parameter description

   Parameter	Description
   Project Name	Specifies the project name displayed in the project list. The name must contain 5 to 50 characters, start with a letter, and end with a digit or letter. Only letters, digits, underscores (_), and hyphens (-) are allowed.
   (Optional) Exception Notification Mode	SMN Topic Specifies whether to report exceptions through Simple Message Notification (SMN). To create an SMN topic, see Creating a Topic. NOTE: Follow-up Operation After the topic is created, you can add a subscription. After the subscription has been confirmed, alarm notifications will be sent to the subscription endpoint via SMN.
   (Optional) Target DB Analysis	Select Skip Target DB Evaluation: UGO will only collect data and not analyze the target database. There are only recommended target databases in the Target DB Analysis tab when you view evaluation project details. Select this option if you already have a confirmed target database. Deselect Skip Target DB Evaluation: UGO will analyze different databases to produce summary and evaluation reports. Database analysis takes some time after data collection. This option is selected by default. NOTE: If the source database type is DB2, this option is selected by default and cannot be deselected.
   (Optional) Source DB Type	Select a source database type. Currently, the supported source database are ORACLE 10g, 11g, 12c, 18c, and 19c and MySQL 5.6, 5.7 and 8.0. By default, the source database type is ORACLE-11g. If you want to select DB2 11.1, PostgreSQL 11, or PostgreSQL 12 as the source database, submit an application by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console. NOTE: If the source database type is MySQL, run the following command on the source database to enable the CPU count function. SET GLOBAL innodb_monitor_enable = cpu_n;
   (Optional) Network Type	Public Network: An elastic IP address (EIP) is used to connect to the source database. If the source database network is restricted by the IP address trustlist, add the EIP to the source database network trustlist to ensure that the UGO can connect to the source database. EIP in CN South-Guangzhou: 124.71.59.255 EIP in AP-Singapore: 110.238.109.54 EIP in LA-Santiago: 159.138.116.198
   (Optional) Connection Method	Select Service Name or Connection string. Service Name is used by default. The following uses the service name as an example. Subsequent parameters vary depending on your selection of this parameter. NOTE: For connection string, the standard JDBC is used to connect to the source database. If the source database type is DB2, only Service Name can be selected for connection.
   (Optional) Host Type	Select Hostname or Host IP Address.
   Source DB Name	Enter the name of the database to be evaluated. NOTE: This parameter is not displayed when the source database type is MySQL.
   Hostname or Host IP Address	Enter the host name or host IP address based on the selected host type.
   Host Port	Enter a database port.
   User Name	Enter the username of the source database. You are advised to use the administrator username.
   Password	Enter the password of the source database. The value contains up to 50 characters.
   (Optional) SSL Type	Select No SSL. Currently, One Way SSL is unavailable. No SSL: The SSL security protocol is disabled. There may be potential security risks. One Way SSL: The target database will be authenticated and transmission will be encrypted. Upload: Upload the root certificate file in JKS format. Trust Store Password: Enter the password of the trust store used to access the certificate. NOTE: If you select One Way SSL, enter the correct uploaded file and entered password, which are private information of users. Secure Socket Layer (SSL) is an encryption-based Internet security protocol for establishing an encrypted link between a server and a client. It provides privacy, authentication, and integrity to Internet communications.
   Data Collected From (Optional)	Select DBA views or All views (default value). DBA views: UGO collects data from objects in the entire source DB instance. All views: UGO collects data from all objects owned and accessed by the source DB user.
   (Optional) Tag	Use predefined tags in Tag Management Service (TMS). Predefined tags are visible to all service resources that support the tagging function. For details, see Tag Management Service User Guide. Enter a key and a value, and click Add. You can add up to 20 tags. For details, see Managing Tags.

6. Click Start Test next to the Test Connection field.
   • If the connection succeeded, the Next button is available.
   • If the connection test failed, error message "Unable to connect to DB" is displayed.

7. (Optional) Test network stability. A successful network stability test only means that there is little network latency or packet loss, or no packet loss at the current time. It takes 10s to 15s to complete.
8. Click Next to go to the Precheck page.
   All item check results are displayed. If the result of a check item is Failed or Alarm, the related reasons and suggestions are displayed. You can also click Recheck All Permissions to check the permissions again.

   Figure 2 Prechecking permissions of Oracle 11g
   

   

   If any item fails to be checked, the failure cause and modification suggestions are displayed. After the modification is complete, click Recheck All Permissions.

   Oracle as the source database type:

   • If the permission check for DBMS_METADATA, Dynamic View or Schema Object Count Check fails, the next step cannot be performed.
   • If Check Result is Alarm, some objects could not be collected because of permissions, but the evaluation project can still be created successfully.

   MySQL as the source database type: All check item results must be Success, or you cannot go to the next step.

   DB2 as the source database type: There is only one check item DB2 Object Collection Check. If the check item fails, you cannot go to the next step.

9. After all check items are passed, click Next to go to the Schema Assessment Scope page.
   Figure 3 Selecting evaluation scope
   

   Table 2 Parameter description

   Parameter	Description
   Select Object Type for Collection	By default, all object types are selected. You can also manually select the object types to be collected as required.
   Select Target Database	Select your required target databases. To select all target databases, click . The target databases that you did not select will not be evaluated.
   Dynamic SQL Evaluation	Yes: Incompatible syntax contained in dynamic SQL statements of an object is parsed. No: Incompatible syntax contained in dynamic SQL statements of an object is not parsed.
   Dynamic SQL Evaluation with all Single Quotes	Yes: Single quote content of all object statements is parsed. No: In object statements, only single quote content with keyword EXECUTE IMMEDIATE or DBMS_SQL.PARSE is parsed.
   Dynamic SQL Upper Line Number	Number of lines to be truncated before the line where the incompatible syntax is located
   Dynamic SQL Lower Line Number	Number of lines to be truncated after the line where the incompatible syntax is located
   Select Schema for Collection	(Optional) Manually select schemas to be collected and click . You can also select all schemas. If there are many schemas, you can search for them by schema name. The names and number of selected schemas are displayed on the right list. NOTICE: If there are multiple schemas with the same name (case-insensitive), select one of them. Oracle Lightweight Jobs are collected as part of PROGRAM object type.

   

   • Only the database objects are collected within the user permission scope, that is, within the selected schemas.
   • After you select object types to be collected, UGO will evaluate their compatibility with the target object types and then migrate them.
   • All collected data is stored in the source database of the tenant. The database password encrypted before being saved. Related data is visible only to you on the UGO console.
   • After you delete migration tasks or deregister UGO, the data is deleted.
   • Dynamic SQL evaluation is available only for Oracle databases.

10. Click Next to go to the Confirmation page.
    The basic information, pre-check results, selected target databases, selected and unselected schemas and object types are displayed.

    Figure 4 Confirmation
    

11. Verify the settings and click Create. A message is displayed, indicating that the project is created successfully.
12. Click OK to go to the DB Evaluation page. You can view the evaluation project you created in the list.
    Data collection, project evaluation, pre-migration evaluation are required. You can view the status in the Evaluation Status column. You can stop a project that is being evaluated or resume a stopped project.

    Figure 5 Viewing the created project
    

    

    • You can create up to 10 evaluation projects.
    • Before Evaluation Status of an evaluation project becomes Evaluation - Success. Confirm Target DB Pending, you can stop and continue the creation of the project. When Evaluation Status becomes Evaluation - Success. Confirm Target DB Pending, you can confirm a target database or re-evaluate objects as needed. However, if the source database type is DB2, re-evaluation is not supported.
    • The evaluation time varies depending on the number of objects selected.
    • After the evaluation is complete, you can click the project name to view its details. For details, see Viewing Project Details.
    • During data collection, the system periodically automatically retries the connection to the source database. Next connection retry time: Current time + Time required for checking the connection and network stability + Sleep retry interval. After a connection test, there is several second delay before a network stability check can be performed. You may see a few seconds difference between the two retry times.