このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。

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
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
Situation Awareness
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
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Scalable File Service Turbo
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
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
Help Center/ Data Replication Service/ Troubleshooting/ Solutions to Failed Check Items/ Conflicts/ Checking Whether the Names of the Source and Destination Databases Are the Same

Checking Whether the Names of the Source and Destination Databases Are the Same

Updated on 2024-11-30 GMT+08:00

MySQL Migration

Table 1 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the names of the source and destination databases are the same.

Failure Cause and Handling Suggestion

Failure cause: This item cannot be checked because the source database fails to be connected.

Handling suggestion: Check whether the source database is connected.

Failure cause: This item cannot be checked because the destination database fails to be connected.

Handling suggestion: Check whether the destination database is connected.

Failure cause: Insufficient user permissions

Handling suggestion: Check whether the database user permissions meet the migration requirements.

Handling suggestion:
  • If you are migrating data to the cloud, determine whether to delete the databases with the same names as the source databases or specify a new destination DB instance based on site requirements.
  • If you are migrating data out of the cloud, determine whether to use the original destination database or specify a new destination DB instance based on site requirements.

Failure cause: During an incremental migration, the source and destination databases cannot have the same names.

Handling suggestion: Determine whether to retain these databases in the destination RDS DB instance or specify another destination RDS DB instance.

Migration from Redis to GeminiDB Redis

Table 2 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the names of the source and destination databases are the same.

Failure Cause and Handling Suggestion

Failure cause: The destination instance cannot contain databases with the same names as those in the source.

Handling suggestion: Determine whether to retain these databases in the destination instance or specify another destination instance.

Oracle -> MySQL/Oracle -> GaussDB(for MySQL) Synchronization

Table 3 Checking Whether the Names of the Source and Destination Databases Are the Same

Check Item

Whether the names of the source and destination databases are the same

Description

The mapping names of the tables to be synchronized in the source databases are the same as the names of the destination database tables.

Failure Cause and Handling Suggestion

Failure cause: Source database names are the same except for letter cases.

Handling suggestion: Change the table name or return to the object selection page and deselect the tables with the same name. Statement for changing the table name:

ALTER TABLE old_table_name RENAME TO new_table_name;

Failure cause: The destination database contains a table to be synchronized. The table name is the same as the mapping name of the table to be synchronized in the source database.

Handling suggestion: Delete the destination database table. Statement for deleting a table:

DROP TABLE table_name;

Oracle -> PostgreSQL Synchronization

Table 4 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

The migration fails when the names of the source and destination databases are different.

Failure Cause and Handling Suggestion

Failure cause: The source and destination databases must have the same names, except that the destination database must use only lowercase letters.

Handling suggestion: Create a database with name in lowercase letters in the destination database.

Failure cause: The names of the objects to be migrated are the same except for letter cases.

Handling suggestion: Select only one database among the databases whose names are the same except for letter cases.

Failure cause: The names of the tables to be migrated are the same except for letter cases.

Handling suggestion: Change table names or do not migrate the tables with the same names.

Failure cause: The names of the tables to be migrated are the same as those in the destination database and use only lowercase letters.

Handling suggestion: Change table names or do not migrate the tables with the same names.

Failure cause: The destination database contains a table to be synchronized. The table name is the same as the mapping name of the table to be synchronized in the source database.

Handling suggestion: Delete the destination database table. Statement for deleting a table:

DROP TABLE table_name;

PostgreSQL > PostgreSQL Synchronization

Table 5 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the source and destination databases have the same names to prevent existing databases from being overwritten. If the source and destination databases have the same name, the migration cannot be performed.

Failure Cause and Handling Suggestion

Failure cause: The destination database names cannot be the same.

Handling suggestion: Change the destination database names to prevent the database from being overwritten.

PostgreSQL to GaussDB(DWS) Synchronization

Table 6 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the source and destination databases have the same names to prevent existing databases from being overwritten. If the source and destination databases have the same name, the migration cannot be performed.

Failure Cause and Handling Suggestion

Failure cause: The destination database names cannot be the same.

Handling suggestion: Change the destination database names to prevent the database from being overwritten.

DDM -> Oracle Synchronization

Table 7 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

To synchronize data from DDM to Oracle, you need to create the corresponding database (user) in the destination database in advance. Otherwise, the synchronization fails.

Failure Cause and Handling Suggestion

Failure cause: Some databases cannot be synchronized because the databases with the same names do not exist in the destination databases.

Handling suggestion: Create these databases or users in the destination database or do not migrate these databases. Statement for creating a user:

CREATE USER user_name IDENTIFIED BY password;

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