Updated on 2023-01-12 GMT+08:00

Modifying Objects

Scenarios

If a project is migrated for the first time, you need to manually modify the objects whose Conversion Status is Failed during object correction. Otherwise, the next step cannot be performed.

If a project is not migrated the first time, you need to manually modify the objects whose Migration Status is Failed. Otherwise, the next step cannot be performed.

The modified statements will run on the target database. Do not use statements that cause the drop of other tables and object types, or statements that cause malicious activities such as consuming too much CPU, memory and other side effects over target database.

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. On the displayed page, click the Object Correction tab.
  4. Locate an object you want to modify and click Modify in the Operation column.

    You can view the schema name, object type, object name, split object name, and migration status on the page.

    Correct management, storage, code, and job objects in sequence.

  5. View the error information. If any, modification suggestions are displayed.

    Figure 1 Object details

  6. Click Modify in the Operation column to go to the Object Correction page or directly click the Object Correction tab.

    Figure 2 Object correction

  7. Modify SQL statements.

    • Export: Click Export SQL to export the SQL file of the target database. Exported file name: Object name.sql.
    • Import: Click Import SQL to directly import the modified SQL file. After the SQL file is uploaded, all changes are automatically saved.
    • Compare: This function is disabled by default. If this function is enabled, the detailed code comparison between the source and target databases is displayed. In this case, the SQL statements cannot be edited.
    • Copy: Click next to Source or Target to copy the SQL statements to the clipboard.
    • Full screen: You can click next to the target end to enter the full-screen editing mode. To exit the full-screen editing, click or click the edit box and press Esc.
    • Update dependency data: If this function is enabled, all dependent objects are also verified. This function is enabled by default and can be disabled. It is available only after the object migration is verified.
    • Ignore: If you enable this function, the modifications will not be saved. This function is disabled by default and can be enabled.
    • Reset: Before saving the modified code, you can click Reset to clear all modifications. If the modification has been saved, you can only perform a rollback operation.
    • Save: Click Save to save the modifications for target database code. The modification records will be generated and saved in the history.

  8. After the modification, click Save. The modification record is saved in the Modification History area in the current page.

    In the Modification History area, locate the history record and click Rollback in the Operation column to roll back to the latest modification record.

  9. Click the drop-down icon next to History ID to compare the code before and after modification.

    Figure 3 Modification history

  • After the modification, the conversion status or migration status of the object changes from Failed to Manual.
  • If there are failed items in the migration status, migration verification cannot be started.
  • For details about batch object modification, see Updating Statements in Batches.