Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.
Data Replication Service
Data Replication Service
- What's New
- Function Overview
-
Service Overview
- Infographics
- What Is DRS?
- Supported Databases
- Advantages
- Product Architecture and Function Principles
- Functions and Features
-
Mapping Data Types
- MySQL->PostgreSQL
- MySQL->GaussDB(DWS)
- MySQL->GaussDB
- MySQL->Oracle
- MySQL->CSS/ES
- Oracle->MySQL
- Oracle->GaussDB(for MySQL)
- Oracle->GaussDB
- Oracle->DDM
- Oracle->GaussDB(DWS)
- Oracle->PostgreSQL
- GaussDB(for MySQL)->Oracle
- GaussDB(for MySQL)->CSS/ES
- GaussDB->MySQL
- GaussDB->GaussDB(DWS)
- DB2 for LUW->GaussDB
- DB2 for LUW->GaussDB(DWS)
- PostgreSQL->GaussDB
- PostgreSQL->GaussDB(DWS)
- TiDB->GaussDB(for MySQL)
- Microsoft SQL Server->GaussDB(DWS)
- Microsoft SQL Server->GaussDB
- Specification Description
- Basic Concepts
- Billing
- Security Suggestions
- Accessing DRS
- Permissions Management
- Agency Management
- Security
- Compliance Description
- Related Services
- Change History
- Billing
- Preparations
-
Real-Time Migration
- Migration Overview
- To the Cloud
- Out of the Cloud
-
Task Management
- Creating a Migration Task
- Querying the Migration Progress
- Viewing Migration Logs
- Comparing Migration Items
- Managing Objects
-
Task Life Cycle
- Viewing Task Details
- Editing Migration Task Information
- Modifying Migration Information
- Editing a Migration Task
- Resuming a Migration Task
- Resetting a Migration Task
- Pausing a Migration Task
- Modifying the Flow Control Mode
- Stopping a Migration Task
- Deleting a Migration Task
- Cloning a Migration Task
- Task Statuses
- Tag Management
- Interconnecting with CTS
- Interconnecting with Cloud Eye
- Change History
- Backup Migration
-
Real-Time Synchronization
- Synchronization Overview
- Data Synchronization Topologies
-
To the Cloud
- From MySQL to MySQL
- From MySQL to PostgreSQL
- From MySQL to GaussDB Distributed
- From MySQL to GaussDB Primary/Standby
- From MySQL to GaussDB(DWS)
- From MySQL to GaussDB(for MySQL)
- From PostgreSQL to PostgreSQL
- From PostgreSQL to GaussDB(DWS)
- From PostgreSQL to GaussDB Primary/Standby
- From PostgreSQL to GaussDB Distributed
- From Oracle to MySQL
- From Oracle to GaussDB(for MySQL)
- From Oracle to GaussDB Primary/Standby
- From Oracle to GaussDB Distributed
- From Oracle to DDM
- From Oracle to GaussDB(DWS)
- From Oracle to PostgreSQL
- From DDM to MySQL
- From DDM to GaussDB(DWS)
- From DDM to DDM
- From DB2 for LUW to GaussDB Primary/Standby
- From DB2 for LUW to GaussDB Distributed
- From DB2 for LUW to GaussDB(DWS)
- From TiDB to GaussDB(for MySQL)
- From Microsoft SQL Server to GaussDB(DWS)
- From Microsoft SQL Server to GaussDB Primary/Standby
- From Microsoft SQL Server to GaussDB Distributed
- From Microsoft SQL Server to Microsoft SQL Server
- From MongoDB to DDS
-
Out of the Cloud
- From MySQL to MySQL
- From MySQL to Kafka
- From MySQL to CSS/ES
- From MySQL to Oracle
- From DDM to MySQL
- From DDM to Oracle
- From DDM to Kafka
- From DDS to MongoDB
- From PostgreSQL to Kafka
- From GaussDB Distributed to MySQL
- From GaussDB Distributed to Oracle
- From GaussDB Distributed to GaussDB(DWS)
- From GaussDB Distributed to Kafka
- From GaussDB Distributed to GaussDB Distributed
- From GaussDB Distributed to GaussDB Primary/Standby
- From GaussDB Primary/Standby to MySQL
- From GaussDB Primary/Standby to Oracle
- From GaussDB Primary/Standby to Kafka
- From GaussDB Primary/Standby to GaussDB(DWS)
- From GaussDB Primary/Standby to GaussDB Distributed
- From GaussDB Primary/Standby to GaussDB Primary/Standby
- From GaussDB(for MySQL) to MySQL
- From GaussDB(for MySQL) to GaussDB(DWS)
- From GaussDB(for MySQL) to Kafka
- From GaussDB(for MySQL) to CSS/ES
- From GaussDB(for MySQL) to Oracle
-
Between Self-built Databases
- From MySQL to Kafka
- From MySQL to CSS/ES
- From Oracle to Kafka
- From Oracle to GaussDB Primary/Standby
- From Oracle to GaussDB Distributed
- From PostgreSQL to Kafka
- From GaussDB Primary/Standby to Oracle
- From GaussDB Primary/Standby to Kafka
- From GaussDB Distributed to Oracle
- From GaussDB Distributed to Kafka
-
Task Management
- Creating a Synchronization Task
- Querying the Synchronization Progress
- Viewing Synchronization Logs
- Comparing Synchronization Items
- Managing Objects
-
Task Life Cycle
- Viewing Task Details
- Modifying Task Information
- Modifying Connection Information
- Modifying the Flow Control Mode
- Editing a Synchronization Task
- Resuming a Synchronization Task
- Skipping Data and Resuming a Synchronization Task
- Pausing a Synchronization Task
- Resetting a Synchronization Task
- Skipping a Synchronization Task
- Performing a Primary/Standby Switchover
- Cloning a Synchronization Task
- Changing Specifications
- Unsubscribing from a Yearly/Monthly Task
- Stopping a Synchronization Task
- Deleting a Synchronization Task
- Task Statuses
- Tag Management
- Diagnosis of Abnormal Records
- Interconnecting with CTS
- Interconnecting with Cloud Eye
- Operation Reference in Synchronization Scenarios
- Change History
- Data Subscription
-
Real-Time Disaster Recovery
- DR Overview
-
DR Scenarios
- From MySQL to MySQL (Single-Active DR)
- From MySQL to GaussDB(for MySQL) Primary/Standby (Single-Active DR)
- From DDM to DDM Single-Active DR
- From GaussDB(for MySQL) Primary/Standby to GaussDB(for MySQL) Primary/Standby (Single-Active DR)
- From MySQL to MySQL (Dual-Active DR)
- From GaussDB(for MySQL) Primary/Standby to GaussDB(for MySQL) Primary/Standby (Dual-Active DR)
- Task Management
- Tag Management
- Interconnecting with CTS
- Interconnecting with Cloud Eye
- Change History
-
Best Practices
- Best Practices Summary
- Real-Time Migration
- Backup Migration
-
Real-Time Synchronization
- From Other Cloud PostgreSQL to RDS PostgreSQL
- From PostgreSQL on ECS to RDS PostgreSQL
- From On-Premises PostgreSQL to RDS PostgreSQL
- From RDS MySQL to Kafka
- Change History
- Security White Paper
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- APIs V3.0 (Recommended)
-
APIs V3.0 (Deprecated)
-
Public API Management
- Creating Tasks in Batches
- Testing Connections in Batches
- Testing Connections in Batches (Cluster Mode)
- Modifying Tasks in Batches
- Selecting Database Objects in Batches
- Performing a Batch Pre-Check
- Querying Pre-check Results in Batches
- Setting Flow Control for Tasks
- Obtaining Database Parameters in Batches
- Modifying Database Parameters
- Starting Tasks in Batches
- Resuming or Retrying Tasks in Batches
- Pausing Tasks in Batches
- Stopping or Deleting Tasks in Batches
- Changing the Passwords of the Source and Destination Databases in Batches
- Setting Definers in Batches
- Creating a Comparison Task
- Querying Comparison Results
- Querying Tasks of a Tenant
- Querying Task Details in Batches
- Querying Task Statuses in Batches
- Configuring Exception Notifications
- Querying Available Node Specifications
- Querying Data-level Table Comparison Tasks
- Creating a Data-level Table Comparison Task
- Canceling a Comparison Task
- Immediately Starting a Data-level Table Comparison Task
- Querying the Row Comparison Overview
- Querying Row Comparison Details
- Querying the Value Comparison Overview
- Querying Value Comparison Details
- Querying Value Comparison Differences
- Creating an Object-level Comparison Task
- Querying the Overview of an Object Comparison Task
- Querying Details About an Object Comparison Task
- Exporting the Result File of a Comparison Task
- Downloading the Result File of a Comparison Task
- Real-Time Migration Management
- Real-Time Synchronization Management
- Real-Time Disaster Recovery Management
-
Public API Management
- Application Examples
- Permissions Policies and Supported Actions
- Appendix
- Change History
-
FAQs
-
Product Consulting
- What Are Regions and AZs?
- What Is DRS?
- Can DRS Migrate RDS Primary/Standby Instances?
- What Constraints Does DRS Have for a Source Database?
- What Requirements Does DRS Have for a Destination Database?
- Does DRS Use Concurrency?
- Dose DRS Use Data Compression?
- Does DRS Support Migration Between the Public Cloud and the Dedicated Cloud?
- What Is the Quota?
- Does DRS Support Migration from DB2 for LUW to PostgreSQL?
- Can Microsoft SQL Server Database Synchronize Data with Local Databases in Real Time?
- Does DRS Support Data Replication in a Specified Time Period?
- Does DRS Support Resumable Uploads?
- What Is Single-Active/Dual-Active Disaster Recovery?
- What Are the Differences Between Real-Time Migration, Real-Time DR, and Real-Time Synchronization?
- How Do I Solve the Table Bloat Issue?
- How Do I Select RDS Read Replicas on the DRS Console?
- How Does DRS Affect the Source and Destination Databases?
- Do I Need to Stop Services Running on the Source Database?
- What Is an SMN Topic?
- What Are the Differences Between Primary/Standby and Single-Node Instances for DRS Synchronization Tasks?
- Can DRS Migrates Table Structures Only?
- How Do I Migrate Accounts in MySQL Migration, Synchronization, and DR Tasks and Can I Change Passwords?
- What Factors Affect the DRS Task Speed and How Do I Estimate the Time Required?
- Can I Modify Objects in a DRS Task?
- Does DRS Support Data Synchronization Between Different Databases of the Same DB Instance?
- Which Operations on the Source or Destination Database Affect the DRS Task Status?
- What Are Differences Between Data Subscription and Synchronization from MySQL to Kafka?
-
Network and Security
- What Security Protection Policies Does DRS Have?
- What Can I Do If the Network Is Disconnected During the Migration?
- Which Database Accounts Are Required During Migration?
- How Can I Configure a VPC Security Group to Allow Traffic from an EIP?
- What Can I Do If the Network Connection Between the Replication Instance and Database Is Abnormal?
- How Can the Source and Destination Databases Communicate Across VPCs?
- What Is the EIP Bandwidth of DRS?
- Does DRS Support Cross-Account Cloud Database Migration?
- Permissions Management
-
Real-Time Migration
- When Can I Stop a Migration Task?
- How Do I Maintain the Original Service User Permission System After Definer Is Forcibly Converted During MySQL Migration?
- What Can I Do If the Invoking Permission Problem Occurs After the MySQL Stored Procedure Is Migrated to the Cloud?
- How Do I Ensure that All Services on the Database Are Stopped?
- What Can I Do When Message "can not get agency token" Is Displayed in the Migration Log
- What Do I Do If the Maximum Index Length Has Been Reached During Migration from Oracle to MySQL?
- Why Is the Collation of Heterogeneous or Oracle Databases Converted to utf8mb4_bin After Those Databases Are Migrated to MySQL?
- What Can I Do If MyISAM Tables Are Not Supported by RDS for MySQL?
- What Are the Precautions for Migrating Data from an Earlier Version MySQL to MySQL 8.0?
- What Can I Do When OOM Occurs During the Migration of MongoDB Databases?
- How Do I Disable the Balancer?
- How Do I Export and Import Events and Triggers in Batches?
- How Can I Migrate Databases or Tables Whose Names Contain Uppercase Letters?
- How Do I Delete Orphaned Documents in MongoDB Sharded Clusters?
- Backup Migration
-
Real-Time Synchronization
- Can DRS Sync Tables of Different Schemas to the Same Schema?
- Can Online DDL Tools Be Used for Real-time Synchronization?
- How Do I Delete XStream Outbound Created When XStream Is Enabled?
- Why Do I Use the SCAN IP Address to Connect to an Oracle RAC Cluster?
- How Do I Check Supplemental Logging of the Source Oracle Database?
- Which Specifications Should I Select for My DRS Task to Synchronize Data to GaussDB(DWS)?
- Suggestions on Synchronizing Data to GaussDB(DWS)
- Character Set Compatibility Between Oracle and GaussDB
- Garbled Characters or Synchronization Failure Due to Incompatible Character Sets
- Data Subscription
-
Real-Time Disaster Recovery
- What Are RPO and RTO of DRS Disaster Recovery?
- How Do I Select Active Database 1 and 2 for Dual-Active DR?
- What Is the Meaning of Forward and Backward Subtasks in Dual-Active Disaster Recovery?
- Common Exceptions in Real-Time Disaster Recovery
- Is a Primary/Standby Switchover Triggered Automatically or Manually for DR Tasks?
- Can Real-Time DR Be Performed for Specified Databases?
- Why Does a Real-Time DR Task Not Support Triggers and Events?
- Data-Level Comparison
-
General Operations
- What Can I Do When Information Overlaps on the DRS Console?
- Is the Destination Instance Set to Read-only or Read/Write?
- How Do I Set Global binlog_format=ROW to Take Effect Immediately?
- How Do I Set binlog_row_image=FULL to Take Effect Immediately?
- How Do I Change the Destination Database Password to Meet the Password Policy?
- How Do I Configure the Shard Key for a MongoDB Sharded Cluster?
- Does Bandwidth Expansion Affect the Running DRS Tasks?
- Why Data in MariaDB and SysDB Cannot Be Migrated or Synchronized?
- Constraints and Operation Suggestions on Many-to-One Scenario
- Constraints and Operation Suggestions on One-to-Many Scenario
- Where Can I View DRS Operation Logs?
- Why Is a DRS Task Automatically Stopped?
- How Can I Export a DRS Task List?
- Can a Completed Task Be Restarted?
- What Are the Differences Between Resetting a Task and Recreating a Task?
- Does DRS Support Backward Migration/Synchronization?
- Why Cannot I Select an Existing SMN Topic?
- Can I Change an SMN Topic After a Task Is Created?
- Will Data of DRS Tasks Be Lost After a Primary/Standby Switchover Occurs on the Source MySQL Database?
- What Are the Differences Between All, Tables, and Databases During DRS Object Selection?
- What Do I Do After Changing the Password of the Source or Destination Database?
-
Billing
- Do I Have to Pay For Failed Tasks?
- Do I Have to Pay For Paused Tasks?
- Will DRS Tasks That Are Not Started Be Billed?
- What Will Happen to My Tasks After The Yearly/monthly Subscription Expires?
- Will I Be Charged If I Do Not Delete a Task After It Is Completed?
- Resource Freezing, Release, Deletion, and Unsubscription
- Delay
- Change History
-
Product Consulting
-
Troubleshooting
-
Solutions to Failed Check Items
- Disk Space
-
Database Parameters
- Checking Whether the Source Database Binlog Is Enabled
- Checking Whether the Source Database Binlog Is Row-Based
- Checking Whether the Binlog Retention Period Is Set on the Source Database
- Checking Whether the Source and Destination Database Character Sets Are Consistent
- Checking Whether the Source Database server_id Meets the Incremental Migration Requirements
- Checking Whether the Source and Destination Database Table Names Are Consistent in Case Sensitivity
- Checking Whether the Source Database GTID Is Enabled
- Checking Whether the Source Database Contains Object Names with Non-ASCII Characters
- Checking Whether the Source and Destination Database TIME_ZONE Values Are Consistent
- Checking Whether the COLLATION_SERVER Values of the Source and Destination Databases Are the Same
- Checking Whether the SERVER_UUID Values of the Source and Destination Databases Are the Same
- Checking Whether the SERVER_ID Values of the Source and Destination Databases Are Different
- Checking Whether the Source Database Contains Invalid sql_mode Values
- Checking Whether the SQL_MODE Values of the Source and Destination Databases Are the Same
- Checking Whether the sql_mode Value in the Destination Database Is Not NO_ENGINE_SUBSTITUTION
- Checking Whether the innodb_strict_mode Values of the Source and Destination Databases Are the Same
- Checking Whether the max_wal_senders Value of the Source Database Is Correctly Configured
- Checking Whether the WAL_LEVEL Value in the Source Database Is Correct
- Checking Whether the MAX_REPLICATION_SLOTS Value in the Source Database Is Correct
- Checking Whether the Source Database Is on Standby
- Checking Whether the log_slave_updates Value of the Source Database Is Correctly Configured
- Checking Whether the BLOCK_SIZE Value of the Source Database Is the Same as That of the Destination Database
- Checking Whether the binlog_row_image Value is FULL
- Checking Whether the Transaction Isolation Levels are Consistent
- Checking Whether the lc_monetary Values of the Source and Destination Databases Are the Same
- Checking Whether the Source Database Contains Trigger Names with Non-ASCII Characters
- Checking Whether the Source Database Collections Contain More Than 10 Indexes
- Checking Whether the Source Database Collections Contain TTL Indexes
- Checking Whether log_bin_trust_function_creators Is Set to On in Both the Source and Destination Databases
- Checking Whether GTID Is Enabled for the Source Database
- Checking Whether GTID Is Enabled for the Destination Database
- Checking Whether log_bin_trust_function_creators Is Set to On in the Destination Database
- Checking Whether the Values in the Source Oracle Database Are Out of the Ranges of the MySQL Database
- Checking Whether the max_allowed_packet Value of the Destination Database Is too Small
- Checking Whether the Source Database User Has the Permission to Parse Logs
- Checking Whether the ExpireLogsDays Value Is 0
- Checking Whether the Source Database Character Set Is Supported
- Checking Whether the Length Table and Field Names Is Not Supported
- Checking Whether the Databases and Tables Exist
- Checking Whether the Supplemental Log Level of the Source Database Meets Requirements
- Checking Whether the Length of the Source Database Object Names Exceeds the Limit
- Checking Whether session_replication_role of the Destination Database Is correctly Set
- Checking the Database Compatibility Type
- Checking Whether the Collation of the Destination Database Is Correct
- Checking Whether the Source Database Has the Permission to Parse OGG Logs
- Checking Whether the Index Name Is Supported
- Checking Whether Tables Structures Are Consistent
- Checking Whether Existing Data Meets the Constraints
- Checking the Additional Column of the Destination Database
- Checking Whether Implicit Primary Key Check Is Enabled for the Primary and Standby Databases
- Checking Whether the Source Table Replication Attribute Is Correct
- Checking Whether the Source Database Is on Standby
- Checking Whether the Specified Replication Slot Exists in the Source Database
- Checking Whether the MongoDB Instance Type Matches the Migration Mode
- Checking the Physical Standby Database
- Source DB Instance Statuses
-
Destination DB Instance Statuses
- Checking Whether the Destination Database Is Involved in Another Migration Task
- Checking Whether the Destination Database Has a Read Replica
- Checking Whether the Destination Database Is Read-Only
- Checking Whether the Extensions Are Supported
- Checking Whether Destination Contains the Configured Database
- Checking Whether the Destination DB Instance Is Available
- Checking Whether the Destination Database Is Empty
- Database User Permissions
- Database Versions
- Networks
-
Database Objects
- Checking Whether the Source Database Contains a MyISAM Table
- Checking Whether the Source Database Contains Unsupported Table Field Types
- Checking Whether the Source Database Contains the Functions or Stored Procedures that the Source Database User Is Not Authorized to Migrate
- Checking Whether Objects with the Same Names Exist in the Source Database
- Checking Whether the Source Database Contains Unlogged Tables
- Checking Whether the Names of Views to Be Migrated Are the Same
- Checking Whether the _Id Fields in the Collection of the Source Database Have Indexes
- Checking Whether the Index Length of the Source Database Exceeds the Limit
- Checking Whether the Source Database Tables Use Storage Engines Not Supported by the Destination Database
- Checking Whether the Database Names Mapped to the Destination DB Instance Contain Unsupported Characters
- Checking Whether the Source Database Tables Contain Primary Keys
- Checking Whether the Source Database Contains Triggers or Events
- Checking Whether the Source Database Referenced Roles Pass the Check
- Checking Whether the Source Database Referenced Accounts Pass the Check
- Checking Database Mapping Objects
- Checking Whether Associated Objects Are Selected
- Checking Whether the Specified Objects Exist In the Destination Database
- Checking Whether the Source Table Contains Column Types that Cannot Be Used as Distribution Keys
- Checking Whether the Source Table Contains Unsupported Table Field Types
-
Database Configuration Items
- Checking Whether the Source Database Name Is Valid
- Checking Whether the Source Database Table Name Is Valid
- Checking Whether the Source Database View Name Is Valid
- Checking Whether the Source Database Collection Name Is Valid
- Checking Whether the Shard Key Can Be Obtained from the Source Database
- Checking Whether the Source Database Schema Name Is Valid
- Checking Whether the Maximum Number of Chunks in the Destination Database Is Sufficient
- Checking Whether Archive Logs Are Enabled on the Source Oracle Database
- Checking Whether Supplemental Logging of the Source Oracle Database Meets Requirements
-
Conflicts
- Checking Whether the Names of the Source and Destination Databases Are the Same
- Checking Whether the Same View Names Exist in Both the Source and Destination Databases
- Checking Whether the Destination Database Contains a Non-Empty Collection with the Same Name As the Source Database
- Checking Whether Destination Database Contains the Same Table Names As the Synchronization Objects
- Checking Whether the Destination Database Contains Objects with the Same Name As Those in the Source Database
- Checking Whether Collections in Both the Source and Destination Databases Are Not Capped
-
SSL Connections
- Checking Whether the SSL Connection Is Correctly Configured
- Checking Whether the SSL Connection Is Enabled for the Source Database
- Checking Whether the SSL Certificate of the Source Database Exists
- Checking Whether the SSL Certificate of the Destination Database Exists
- Checking Whether Both the Source and Destination Databases Use SSL
- Object Dependencies
- Source Database Information
-
Failure Cases
- Case Overview
-
Real-Time Migration from MongoDB to DDS
- Full Migration Error: Prematurely reached end of stream
- Full Migration Error: not authorized on riskevaluation to execute command {***}
- Full Migration Error: GC overhead limit exceeded
- Full Migration Error: The background process is unavailable. Maybe it has been killed manually or by the operating system. Please restart the task if possible or wait for restarting by itself within 5 minutes."
- Full Migration Error: Timed out after 60000 ms while waiting to connect
- Full or Incremental Migration Error: Timed out after 60000 ms while waiting to connect
- Full or Incremental Migration Error: Invalid BSON field name XXX
- Incremental Migration Error: Timed out after 60000 ms while waiting for a server that matches com.mongodb.client.internal
- Incremental Migration Error: Command failed with error *** (***):***. The full response is {***}"
-
Real-Time Migration and Synchronization from MySQL to MySQL
- Full Phase Error: Table '%.%' doesn't exist
- Full Phase Error: The background process is unavailable
- Full Phase Error: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
- Full Phase Error: Error writing file '***' (errno: 28 - No space left on device)
- Full Phase Error: The MySQL server is running with the --super-read-only option so it cannot execute this statement
- Full Phase Error: The table 't_diary_mem_font' is full
- Full Phase Error: Unknown column '%s' in 'field list'
- Full Phase Error: Lock wait timeout exceeded; try restarting transaction
- Full Phase Error: Java heap space
- Full Phase Error: Table '%s ' already exists
- Full Phase Error: temp table: %s.%s not exist
- Full Phase Error: failed to create new session
- Full Phase Error: load table: `%s`.`%s` failed
- Full Phase Error: read table=`%s`.`%s` failed
- Full Phase Error: CANNOT UPDATE USER WITH NULL PASSWORD
- Full Phase Error: Access denied for user '***' to database '***'
- Full Phase Error: The MySQL server is running with the --super-read-only option so it cannot execute this statement
- Full Phase Error: Temporary file write failure.
- Full Phase Error: Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys
- Full Phase Error: Unknown database '%s'
- Full Phase Error: Access denied; you need (at least one of) the SUPER privilege(s) for this operation
- Full Phase Error: retry structures failed events and Table '%s.%s' doesn't exist
- Full Phase Error: shard table=`%s`.`%s` failed
- Full Phase Error: Column name 'AUTO_PK_ROW_ID' is reserved.
- Full Phase Error: transfer account failed, can not find password from src DB
- Full Phase Error: Access denied for user %s
- Full or Incremental Phase Error: binlog is not existed
- Full or Incremental Phase Error: Can not read response from server
- Full or Incremental Phase Error: Communications link failure
- Full or Incremental Phase Error: EOF Packet received, master disconnected
- Full or Incremental Phase Error: Extract db create sql failed
- Full or Incremental Phase Error: load table
- Full or Incremental Phase Error: Reached end of input stream
- Full or Incremental Phase Error: Read timed out
- Full or Incremental Phase Error: The background process is unavailable
- Full or Incremental Phase Error: Duplicate entry '%s' for key 'PRIMARY'
- Full or Incremental Phase Error: cause by: Index: %s, Size: %s
- Full or Incremental Phase Error: The offset and file name between src and parser is inconsistency
- Full or Incremental Phase Error: core process is not healthy or crashed
- Full or Incremental Phase Error: table info of table `%s`.`%s` from metadata miss
- Full or Incremental Phase Error: table[%s.%s]record field size for insert/delete dml
- Incremental Phase Error: write table %s.%s failed: Duplicate entry '%s' for key 'PRIMARY'
- Incremental Phase Error: not equals to target db column count
- Incremental Phase Error: The MySQL server is running with the --super-read-only option
- Incremental Phase Error: you need (at least one of) the SUPER privilege(s) for this operation
- Incremental Phase Error: Can't DROP '%s'; check that column/key exists
- Incremental Phase Error: Can't find file: '%s' (errno: 2 - No such file or directory)
- Incremental Phase Error: Data truncation: Data too long for column
- Incremental Phase Error: Failed to read file header from
- Incremental Phase Error: Lock wait timeout exceeded
- Incremental Phase Error: Must seek before attempting to read next event
- Incremental Phase Error: Table '%s' already exists
- Incremental Phase Error: Table '%s' doesn't exist
- Incremental Phase Error: Table %s not found in database
- Incremental Phase Error: source has more columns than target
- Incremental Phase Error: Unknown storage engine
- Incremental Phase Error: Unknown table
- Incremental Phase Error: You have an error in your SQL syntax
- Incremental Phase Error: not illegal for mariaDb gtid position
- Incremental Phase Error: without PK execute failed
- Incremental Phase Error: Deadlock found when trying to get lock
- Incremental Phase Error: current serverUUID not equals to this session
-
Real-time Synchronization from MySQL to GaussDB(DWS)
- Full Synchronization Error: Table %s.%s not found in database
- Full Synchronization Error: column 'database_table' of relation '%s' does not exist
- Full Synchronization Error: value too long for type character varying
- Full Synchronization Error: int1 has not implemented
- Full Synchronization Error: column name 'tid' conflicts with a system column name
- Full Synchronization Error: date/time field value out of range
- Full or Incremental Synchronization Error: service LOGMANAGER failed
- Full or Incremental Synchronization Error: service CAPTURER failed
- Full or Incremental Synchronization Error: ERROR: pooler
- Incremental Synchronization Error: dn_%s_%s: column '%s' contains null values
- Incremental Synchronization Error: source has more columns than target
- Incremental Synchronization Errors: Connection to *.*.*.98:8000 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections
- Incremental Synchronization Error: Table %s not found in target database
- Incremental Synchronization Error: in a read-only transaction
- Incremental Synchronization Error: relation '%s' does not exist
- Incremental Synchronization Error: %s doesn't in the target table
- Incremental Synchronization Error: %s doesn't in the target table
- Incremental Synchronization Error: syntax error at or near
- Incremental Synchronization Error: schema '%s' does not exist
-
Real-Time Synchronization from PostgreSQL to PostgreSQL
- Full Synchronization Error: function uuid_generate_v4() does not exist
- Full Synchronization Error: relation '%s' does not exist
- Full Synchronization Error: GC overhead limit exceeded
- Full Synchronization Error: Java heap space
- Full Synchronization Error: column '%s' of relation '%s' does not exist
- Full Synchronization Error: column '%s' does not exist
- Full Synchronization Error: type 'hstore' does not exist
- Full Synchronization Error: Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections
- Full Synchronization Error: invalid locale name
- Incremental Synchronization Error: Table %s not found in target database
- Incremental Synchronization Error: remaining connection slots are reserved
- Incremental Synchronization Error: PL/pgSQL function %s line %s at SQL statement
- Backup Migration Failed Because Backup Files Cannot Be Found
- Backup Migration Failed Because a Backup Database Cannot Be Found in the Backup Files
-
Solutions to Failed Check Items
- Videos
On this page
Show all
Task Statuses
Updated on 2024-08-23 GMT+08:00
|
Status |
Description |
|---|---|
|
CREATING |
The schema is being created. |
|
CREATE_FAILED |
Creation failed |
|
CONFIGURATION |
Configuring |
|
STARTJOBING |
Starting |
|
WAITING_FOR_START |
The task is being started. |
|
START_JOB_FAILED |
Failed to start one or more tasks. |
|
PAUSING |
The task is being paused. |
|
FULL_TRANSFER_STARTED |
Full migration is in progress, and the DR scenario is initialized. |
|
FULL_TRANSFER_FAILED |
Full migration failed. Initialization failed in the DR scenario. |
|
FULL_TRANSFER_COMPLETE |
Full migration is complete, and the initialization is complete in the DR scenario. |
|
INCRE_TRANSFER_STARTED |
Incremental migration is being performed, and the DR task is in progress. |
|
INCRE_TRANSFER_FAILED |
Incremental migration fails and a DR exception occurs. |
|
RELEASE_RESOURCE_STARTED |
Completing |
|
RELEASE_RESOURCE_FAILED |
Stopping task failed |
|
RELEASE_RESOURCE_COMPLETE |
Completed |
|
CHANGE_JOB_STARTED |
The task is being modified. |
|
CHANGE_JOB_FAILED |
Modifying task failed |
|
CHILD_TRANSFER_STARTING |
The subtask is being started. |
|
CHILD_TRANSFER_STARTED |
The subtask is being migrated. |
|
CHILD_TRANSFER_COMPLETE |
The subtask migration is complete. |
|
CHILD_TRANSFER_FAILED |
Failed to migrate the subtask. |
|
RELEASE_CHILD_TRANSFER_STARTED |
The subtask is being completed. |
|
RELEASE_CHILD_TRANSFER_COMPLETE |
The subtask is complete. |
Parent topic: Appendix
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
