Changing Object Names (Mapping Object Names)

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 Primary/Standby
  • MySQL -> GaussDB Distributed
  • MySQL -> GaussDB(DWS)
  • MySQL -> GaussDB(for MySQL)
  • MySQL -> Kafka
  • MySQL -> PostgreSQL
  • MySQL -> Oracle
  • MariaDB -> MariaDB
  • MariaDB -> MySQL
  • MariaDB -> GaussDB(for MySQL)
  • DDM -> DDM
  • DDM -> Oracle
  • DDM -> GaussDB(DWS)
  • DB2 for LUW -> GaussDB Primary/Standby
  • DB2 for LUW -> GaussDB Distributed
  • DB2 for LUW -> GaussDB(DWS)
  • DDS -> MongoDB
  • Microsoft SQL Server -> GaussDB(DWS)
  • Microsoft SQL Server -> GaussDB Primary/Standby
  • Microsoft SQL Server -> GaussDB Distributed
  • Microsoft SQL Server -> Microsoft SQL Server
  • Microsoft SQL Server -> MySQL
  • Microsoft SQL Server -> PostgreSQL
  • Microsoft SQL Server -> GaussDB(for MySQL)
  • MongoDB -> DDS
  • GaussDB Primary/Standby -> MySQL
  • GaussDB Primary/Standby -> Oracle
  • GaussDB Primary/Standby -> GaussDB Primary/Standby
  • GaussDB Primary/Standby -> GaussDB Distributed
  • GaussDB Distributed -> MySQL
  • GaussDB Distributed -> Oracle
  • GaussDB Distributed -> GaussDB Distributed
  • GaussDB Distributed -> GaussDB Primary/Standby
  • GaussDB(for MySQL) -> MySQL
  • GaussDB(for MySQL) -> GaussDB(DWS)
  • GaussDB(for MySQL) -> GaussDB(for MySQL)
  • Oracle -> MySQL
  • Oracle -> GaussDB(for MySQL)
  • Oracle -> GaussDB(DWS)
  • Oracle -> GaussDB Primary/Standby
  • Oracle -> GaussDB Distributed
  • Oracle -> PostgreSQL
  • Oracle -> DDM
  • PostgreSQL -> PostgreSQL
  • PostgreSQL -> GaussDB(DWS)
  • PostgreSQL -> GaussDB Primary/Standby
  • PostgreSQL -> GaussDB Distributed
  • TiDB -> GaussDB(for MySQL)
• The following data flow scenarios support only table-level mapping:
  • Dynamo -> GeminiDB Dynamo
  • MySQL -> CSS/ES
  • GaussDB(for MySQL) -> CSS/ES
• The following data flow scenarios support only database-level mapping:
  • GaussDB Primary/Standby -> GaussDB(DWS)
  • GaussDB Distributed -> GaussDB(DWS)
• The following data flow types do not support schema mapping for tables of the smallserial, serial, and bigserial types:
  • GaussDB Primary/Standby -> GaussDB Distributed
  • GaussDB Primary/Standby -> GaussDB Primary/Standby
  • GaussDB Distributed -> GaussDB Distributed
  • GaussDB Distributed -> GaussDB Primary/Standby
• The following data flow types support many-to-one object mapping:
  • MySQL -> MySQL
  • MySQL -> GaussDB(for MySQL)
  • MySQL -> GaussDB(DWS)
  • MySQL -> Kafka
  • MySQL -> Oracle
  • GaussDB(for MySQL) -> MySQL
  • GaussDB(for MySQL) -> GaussDB(for MySQL)
  • GaussDB(for MySQL) -> GaussDB(DWS)
  • Oracle -> GaussDB
  • Oracle -> GaussDB(DWS)
  • GaussDB Primary/Standby -> GaussDB(DWS)
  • GaussDB Distributed -> GaussDB(DWS)
  • MySQL->Oracle
  • GaussDB Primary/Standby -> GaussDB Distributed
  • GaussDB Primary/Standby -> GaussDB Primary/Standby
  • GaussDB Distributed -> GaussDB Distributed
  • GaussDB Distributed -> GaussDB Primary/Standby

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.