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
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 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

Changing Object Names (Mapping Object Names)

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

Data synchronization allows you to synchronize objects (including databases, schemas and tables) in a sources database to the corresponding objects in a destination database. Object name mapping can be used only in the following scenarios:

  • Changing an Object Name: If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one.
  • Many-to-One Synchronization: To synchronize databases, schemas, and tables in many-to-one scenarios, you can use object name mapping.

This section describes how to map objects when configuring a data synchronization task. For details about the mapping relationship, see Viewing Synchronization Mapping Information.

Precautions

  • Objects whose database names or table names contain newline characters cannot be mapped.
  • Object name mapping can be used for the first time you select synchronization objects for a data synchronization task.
  • Object name mapping can be used for the first time you add or delete the synchronization object which is not in a mapping relationship.
  • If the destination DB is a type of PostgreSQL (for example, GaussDB(DWS), GaussDB, or PostgreSQL), the destination schema name cannot start with pg_. Otherwise, the migration fails.
  • The following data flow scenarios support basic mapping:
    • AWS DocumentDB -> DDS
    • Cassandra -> GeminiDB Cassandra
    • MySQL -> MariaDB
    • MySQL -> GaussDB Centralized
    • MySQL -> GaussDB Distributed
    • MySQL -> GaussDB(DWS)
    • MySQL -> TaurusDB
    • MySQL -> Kafka
    • MySQL -> PostgreSQL
    • MySQL -> Oracle
    • MariaDB -> MariaDB
    • MariaDB -> MySQL
    • MariaDB -> TaurusDB
    • DDM -> DDM
    • DDM -> Oracle
    • DDM -> GaussDB(DWS)
    • DDM -> MySQL
    • DB2 for LUW -> GaussDB Centralized
    • DB2 for LUW -> GaussDB Distributed
    • DB2 for LUW -> GaussDB(DWS)
    • DDS -> MongoDB
    • Microsoft SQL Server -> GaussDB(DWS)
    • Microsoft SQL Server -> GaussDB Centralized
    • Microsoft SQL Server -> GaussDB Distributed
    • Microsoft SQL Server -> Microsoft SQL Server
    • Microsoft SQL Server -> MySQL
    • Microsoft SQL Server -> PostgreSQL
    • Microsoft SQL Server -> TaurusDB
    • MongoDB -> DDS
    • GaussDB Centralized -> MySQL
    • GaussDB Centralized -> Oracle
    • GaussDB Centralized -> GaussDB Centralized
    • GaussDB Centralized -> GaussDB Distributed
    • GaussDB Distributed -> MySQL
    • GaussDB Distributed -> Oracle
    • GaussDB Distributed -> GaussDB Distributed
    • GaussDB Distributed -> GaussDB Centralized
    • TaurusDB -> MySQL
    • TaurusDB -> GaussDB(DWS)
    • TaurusDB -> TaurusDB
    • Oracle -> MySQL
    • Oracle -> TaurusDB
    • Oracle -> GaussDB(DWS)
    • Oracle -> GaussDB Centralized
    • Oracle -> GaussDB Distributed
    • Oracle -> PostgreSQL
    • Oracle -> DDM
    • PostgreSQL -> PostgreSQL
    • PostgreSQL -> GaussDB(DWS)
    • PostgreSQL -> GaussDB Centralized
    • PostgreSQL -> GaussDB Distributed
    • TiDB -> TaurusDB
  • The following data flow scenarios support only table-level mapping:
    • Dynamo -> GeminiDB Dynamo
    • MySQL -> CSS/ES
    • TaurusDB -> CSS/ES
  • The following data flow scenarios support only database-level mapping:
    • GaussDB Centralized -> GaussDB(DWS)
    • GaussDB Distributed -> GaussDB(DWS)
  • The following data flow types support schema-level mapping, table-level mapping, and topic-level mapping:
    • GaussDB Centralized - > Kafka
    • GaussDB Distributed -> Kafka
  • The following data flow types do not support schema mapping for tables of the smallserial, serial, and bigserial types:
    • GaussDB Centralized -> GaussDB Distributed
    • GaussDB Centralized -> GaussDB Centralized
    • GaussDB Distributed -> GaussDB Distributed
    • GaussDB Distributed -> GaussDB Centralized
  • The following data flow types support many-to-one object mapping:
    • MySQL -> MySQL
    • MySQL->TaurusDB
    • MySQL -> GaussDB(DWS)
    • MySQL -> Kafka
    • MySQL -> Oracle
    • TaurusDB->MySQL
    • TaurusDB->TaurusDB
    • TaurusDB->GaussDB(DWS)
    • Oracle -> GaussDB
    • Oracle -> GaussDB(DWS)
    • GaussDB Centralized -> GaussDB(DWS)
    • GaussDB Distributed -> GaussDB(DWS)
    • MySQL->Oracle
    • GaussDB Centralized -> GaussDB Distributed
    • GaussDB Centralized -> GaussDB Centralized
    • GaussDB Distributed -> GaussDB Distributed
    • GaussDB Distributed -> GaussDB Centralized

Changing an Object Name

During real-time synchronization, if the names of source databases, schemas, or tables to be synchronized are different from those in the destination, you can map the source names to the destination ones. For example, when synchronizing database A in the source database to database B in the destination database, you need to map database name first.

  1. On the Set Synchronization Task page, select the database that needs to be mapped from the synchronization objects on the right area and click Edit.

    Figure 1 Mapping databases

  2. Change a name.

    In the displayed dialog box, enter a new object name. The new name is the name of the object saved in the destination database.

    Figure 2 Changing a database name
    Figure 3 Changing a schema name
    Figure 4 Changing a table name

  3. Check the result.

    After the name is changed, the name before modification and the new name are displayed. The object name mapping is complete.
    Figure 5 Checking the result

Many-to-One Synchronization

During real-time synchronization, you can use object name mapping to change the names of databases, schemas, and tables to enable many-to-one synchronization.

The following uses a database-level many-to-one synchronization as an example. For schema- and table-level many-to-one scenarios, perform the following similar steps:

  1. On the Set Synchronization Task page, select the target databases that need to be mapped from the synchronization objects on the right area and click Edit one by one.
  2. In the displayed dialog box, enter a given database name. The new database name is the name of the database saved in the destination DB instance.

    For example, change the databases test_16 and auto_nprocess_001 in the source DB instance to the database test_16_new.

    Figure 6 Checking the result

  3. After the database names are changed, the database names before modification and the new database name are displayed. The many-to-one database mapping is complete.
  4. Wait until the task starts and the synchronization is complete. Then, the databases test_16 and auto_nprocess_001 can be synchronized to the database test_16_new.

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