tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements

Advanced Object Check

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-07-08 19:41:52

MySQL/MariaDB/Percona check details

If you select to migrate/sync advanced objects, DTS will verify the following content. You must fix errors to continue the task. For warnings, you can ignore them based on business risk assessment and continue the task.
Error: The target instance parameter log_bin_trust_function_creators must be ON.
Warnings:
The advanced object migration/sync feature conflicts with the database/table renaming feature. After selecting advanced objects, you must cancel database/table renaming.
If you select functions or stored procedures as advanced objects, DTS will check whether user1 corresponding to DEFINER ([DEFINER = user1]) in the source database is the same as the task execution account user2.
If they are the same, do not modify the settings after migration/sync.
If they are different, change the SQL SECURITY attribute of user1 in the target database after migration/sync from DEFINER to INVOKER ([INVOKER = user1]), and set the DEFINER in the target database to the task execution account user2 ([DEFINER = task execution account user2]).
Migration/Sync time of advanced objects:
Stored procedures and functions: They will be migrated/synced during source database export.
Triggers and events: If there are no incremental migration/sync tasks, they will be migrated/synced when the task stops; otherwise, they will be migrated/synced after you click Done, in which case the transition will take a longer time.

Troubleshooting

Modify the log_bin_trust_function_creators parameter.
log_bin_trust_function_creators controls whether to allow users to write stored functions to the binlog. If it is set to OFF, only users with SUPER permissions can write stored function creation operations to the binlog. If it is set to ON, users with no SUPER permissions can also do this.
If an error occurs, troubleshoot as follows:
1. Log in to the source database.
2. Run the following command to modify the log_bin_trust_function_creators parameter:
set global log_bin_trust_function_creators = ON;
3. Run the following command to check whether the parameter modification takes effect:
show variables like '%log_bin_trust_function_creators%';
The system should display a result similar to the following:
mysql> show variables like '%log_bin_trust_function_creators%';
+---------------------------------+-------+
| Variable_name | Value |
+---------------------------------+-------+
| log_bin_trust_function_creators | ON |
4. Run the verification task again.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック