Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Migrating Objects

Updated on 2025-02-22 GMT+08:00

Migrate the objects based on the created migration task.

Procedure

  1. On the Object Migration page, locate the project that you want to migrate and click Migrate in the Operation column.

    On the Conversion Plan page, the collection objects and types for the project are displayed on the left. For details, see Viewing the Database Evaluation Result.
    Figure 1 Conversion plan
    • User password:
      • If you want to convert the object type USER, you must set a password to complete the conversion. The same password will be used for all USER object creation on the target database. After the migration, the individual user passwords must be changed manually. If you do not want to convert the object type USER, select the desired USER objects and click Skip Conversion. Then, the Conversion Status of the objects becomes Skip. To continue the conversion, select the desired objects and click Convert.
      • SSL connection must be selected. If Non-SSL connection is selected, the password will be transmitted as plain text as part of the database connection and any SQL statements involving a password will be insecure.
      • After the password is configured, it cannot be changed again until after the migration is complete.
      • The password can consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters ( ~!@#$%^&*()-_=+\|[{}];:,<.>/?). Spaces are not allowed. The password can contain up to three consecutive characters.
    • If Object Status of objects is Abnormal, their Conversion Status is Skip. You can change the status to Convert. If Object Status of objects is Duplicate, these objects are not migrated by default.

  2. Click Next to go to the Conversion Config page.

    • Select a value from the Baseline Template drop-down list.
      • Two templates are preset: default template and maximum compatibility template.
      • After you select a template, the preset values in the template are imported to the configuration item list.
    • Set the configuration items based on the actual conversion scenario.
      • 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.
      • After you import configuration parameters, the configuration status of features is Default. If you edit the configuration of a feature, the configuration status will become Modified.
      • If the custom template of your project is deleted, your project still uses the template configurations, but default value is displayed for Parameter Configuration.
    • When Category is set to Customize template, you can select an existing template or create a template. The template name can contain 5 to 50 characters and can only include letters, numbers, underscores (_), and hyphens (-). It must start with a letter and end with a letter or number.
    • After you select a template, locate a feature and click Edit Configuration in the Operation column to modify the current configuration of the feature. If the target database version and deployment mode in different migration projects are the same, you can apply or modify a template you created in previous projects.

  3. Click Next to go to the Syntax Conversion page.
  4. Click Start to start the conversion. The following information is displayed: object type, the number of total objects, the number of objects converted successfully, the number of objects that failed to be converted, conversion start time, and conversion end time.

    Figure 2 Syntax conversion
    • Click Download Reports, locate the required report, and click Download to download the report to the local PC for analysis.
      • Conversion Error Report: This report contains details about objects that could not be converted to equivalent syntax in the target database.
      • Anonymized Conversion Error Report: This report contains the details about objects, in anonymized form, that could not be converted to equivalent syntax in the target database.
      • Conversion Risk Report: This report contains the details about objects that were converted with risks based on selected configuration options.
      • Anonymized Conversion Risk Report: This report contains details about objects, in anonymized form, that were converted with risks based on the selected configuration options. However, there are function differences after the conversion.
    • Locate an object type that failed to be converted, and click Details in the Operation column to go to the Object Correction page to view details about the object type.

  5. Click Next to go to the Object Correction page.

    Figure 3 Object correction
    • Select object types or objects you want to rerun conversion for and click Rerun Conversion. The SQL modification of other objects is not overwritten

      On the Rerun Conversion page, select the objects you want to rerun conversion, and click Rerun Conversion to perform 4.

    • Batch update: You can click Batch Statement Update to search for and modify objects with the similar issues in batches. For details, see Updating Statements in Batches.
    • Locate the object that failed to be migrated and click View Details in the Operation column. On the displayed page, view the conversion error message and modify the target SQL statements.
    NOTE:
    • If you select a schema to be ignored and click Skip Migration, the Conversion Status or Migration Status changes to Ignore. You can also click Undo Skip to change the status back.
    • If you click Ignore, the migration status of the object changes to Ignore. If you click Undo Skip, the migration status changes to Manual.
    • If there are features commented out in the migration, functions may be affected. You can click Modify to see the details.

  6. Click Next. The Migration & Verification page is displayed. Click Start to start the verification. The migration progress is displayed in a progress bar and as a percentage. When the migration progress reaches 100%, the migration is complete.

    Figure 4 Verification
    • If a message is displayed, indicating that there were errors or risks during migration, the verification will automatically stop.
    • View Empty Stored Procedure: 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.
      • Anonymized full migration report: This report contains migration details, such as statuses, migrated statements, error details for each object, but the original and migrated SQL statements will be anonymized..
    • Locate an object type that failed to be migrated, click Details to return to the object correction page and view details about the object type.

  7. After the migration verification is complete, if any item fails the verification, return to the object correction page. You can modify the items one by one or click Bulk Statement Update to modify them in batches.

    NOTE:

    If no items fail the verification, the Batch Statement Update and Modify buttons on the Object Correction page are unavailable.

Follow-up Operations

  • You can view the conversion success rates and SQL statements. For details, see Viewing Syntax Conversion History and Viewing Migration Project Details.
  • After the migration is complete, you can delete the corresponding database evaluation and object migration project. When the projects are deleted, the database connection information and source database schema information are also deleted. Deleted projects cannot be recovered. Exercise caution when performing this operation.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback