Database and Application Migration UGO
Database and Application Migration UGO
- What's New
- Service Overview
- Getting Started
-
User Guide
- Database Evaluation
- Object Migration
- SQL Statement Conversion
- Conversion Configuration
- SQL Audit
- Data Source Management
- Permissions Management
- Interconnection with CTS
- Best Practices
- Security White Paper
-
API Reference
- Before You Start
- API Types
- Calling APIs
-
API
- API Version Management
- Quota Management
- SQL Statement Conversion
- Evaluation Project
-
Migration Project
- Creating a Migration Project
- Querying Migration Projects
- Querying the Status of a Migration Project
- Checking Target Database Permissions
- Querying Permission Check Results
- Querying Migration Project Details
- Submitting Syntax Conversion of Objects
- Querying Syntax Conversion Progress of Objects
- Submitting Verification
- Querying the Verification Progress
- Downloading a Migration Error Report
- Deleting a Migration Project
- Permissions Policies and Supported Actions
- Appendixes
- SDK Reference
-
FAQs
-
Product Consulting
- Instance Freezing, Release, and Deletion
- Which Schemas in Source Databases Are Ignored for Migration?
- What Are the Differences Between Syntax Conversion and Migration & Verification in a Migration Project?
- What Are the Database Schema Changes After an Oracle Database Is Migrated to the Target Database?
- Why Cannot I Use Some Functions?
- What Is the Function of the dsc_ora_ext Schema Generated After Migration to the Target Database?
- What Should I Do If Data Collection Fails or Is Slow Due to the Small Values of Certain Oracle SGA Parameters?
- What Should I Do If Data Collection Fails and a Message SNAPSHOT TOO OLD Is Displayed?
- What Is the Mapping Between the GaussDB Versions Displayed on the UGO Console and Self-built GaussDB Versions?
- What Are VPCEP Resource Quotas?
-
Database Connections
- What Should I Do If I Cannot Connect to the Source Oracle Database During Database Evaluation Project Creation?
- What Should I Do If I Failed To Connect to the Source Database as User sys?
- How Do I Create GaussDB Databases Compatible with Source Databases?
- What Should I Do If My Database Fails to be Connected?
- SQL Server Connection Test Failed (Error Code=0, SQLState=08S01)
-
Evaluation Project
- How Do I Select a Connection Method?
- How Does UGO Collect Data from Source Databases?
- How Does UGO Check Database Permissions?
- What Are the Possible Causes for an Object Collection Failure?
- In GaussDB, How Do I Configure a Search Path If A Statement Without Schema Name Fails To Be Executed?
- What Is Native Compatibility, Conversion Compatibility, Partial Compatibility, or Incompatibility?
- What Is the Relationship Between Migration Risk (Top 10 risk SQL) and Risky SQL Summary?
- What Are Reconstruction Statistics and How Are Reconstruction Points Measured?
- What Should I Do If An Object Collection Error (Closed Connection) Is Displayed During Evaluation Project Creation?
- What Should I Do If "ErrorCode=4036" Is Displayed During Evaluation Project Creation?
- What Should I Do If "ErrorCode=17002" Is Displayed During Evaluation Project Creation?
- What Do I Do If the Assessment Task Is Connected but the Pre-check Fails?
- What Is the Impact of the Collection on the Source Database?
-
Migration Project
- Why Is There No Available Evaluation Project During Migration Project Creation?
- When Should I Use the Conversion Config Function?
- What Should I Do If SQL Modifications Failed to Be Saved During Object Correction?
- How Do I Solve ERROR: syntax error at or near "@"?
- What Are the Possible Causes for an Object Verification Failure?
- What Are the Impacts of GUC Parameter Settings of GaussDB on Migration?
- How Do I Set GaussDB GUC Parameters?
- Why Is the Number of Indexes Different After Oracle Data is Migrated to GaussDB?
- What Should I Do If There Are ctid, xc_node_id, and tableoid Columns in GaussDB?
- Why Is Data Inconsistent When SELECT Statements Without ORDER BY Are Used for Query in Distributed GaussDB?
-
Product Consulting
- Videos
- General Reference
On this page
Show all
Help Center/
Database and Application Migration UGO/
User Guide/
Object Migration/
Object Migration Implementation/
Verifying the Migration Result
Copied.
Verifying the Migration Result
Prerequisites
There is a project for which migration has been completed.
Procedure
- Log in to the UGO console.
- In the navigation pane, choose Schema Migration > Object Migration. The migration project list is displayed.
- Locate the project to be migrated and click Migrate in the Operation column. On the displayed page, click the Migration & Verification tab.
The Migration tab page is displayed by default.Figure 1 Going to the migration tab page
- Click Migration Verification to set the migration process. This parameter can be set only when the migration task is in the Pending, The migration is being paused, or Migration Succeeded state.
- The detailed information about the migration project is displayed, including object types, total objects, objects that have been migrated, objects that failed to be migrated, and objects that have not been migrated. If objects that failed to be converted will not be migrated, Objects Not Migrated upon Conversion Failure is also displayed.
- If the migration fails, click Details in the Operation column to go to the Object Correction page and view migration details of the object type.
- View Empty Stored Procedure: If the source database type is Oracle, you can view objects that fail to be created and failure occurrences.
- Click Download Reports, locate the required report, and click Download to download the report to the local PC for analysis. Data related to sub-objects is not included in the migration report.
- Migration statistical report: This report includes a summary of object statuses during migration and verification.
- Migration error report: This report includes failure details, such as statuses, migrated statements, and error details for each object.
- Anonymized error report: This report consists of failure details, such as statuses, migrated statements, and error details for each object, but the original and migrated SQL statements will be anonymized.
- Full migration report: This report includes failure details, such as statuses, migrated statements, and error details for each object.
- Click Migration History.
Detailed information of the migrated projects is displayed in the descending order. The information includes the serial number, total count, migration succeed, migration failed.Figure 2 Migration history
- Click Details to view information such as the total count, migration succeed, and migration failed.
- Locate an object type and click Details to view its details. The detailed information includes the schema, object name, object types, and migration status. You can search for an object by name or view details about each schema.
Figure 3 Object type details
- Locate an object and click Details to view the code.
Figure 4 Object details
Parent topic: Object Migration Implementation
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot