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

Target Instance Permission Check

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-07-11 15:03:48

Check Details

1. Check whether the user has permission to operate the database. In migration/synchronization/subscription processes, each database type has detailed permission requirements. See corresponding guidance.
2. For the target end being MySQL versions 8.0.26 and later, DTS will check the innodb_strict_mode parameter. It is recommended that innodb_strict_mode be set to OFF during migration/synchronization tasks. If it is not set to OFF, DTS will give a prompt during the pre-verification. For MySQL versions earlier than 8.0.26 or other database types, DTS will modify this parameter at the session level to OFF.
Parameter Description: innodb_strict_mode controls whether the InnoDB storage engine enables strict mode for improper data.
innodb_strict_mode=ON: The InnoDB storage engine will perform strict data validation. If there are syntax errors during operations like CREATE TABLE, ALTER TABLE, and CREATE INDEX, it will throw an error directly.
innodb_strict_mode=OFF: The InnoDB storage engine relaxes data validation. The above syntax errors will not trigger an error, and default syntax will be used instead.
Setting recommendation: If the source database contains improper data, it is recommended that the innodb_strict_mode parameter be set to OFF during migration/synchronization tasks. This will allow data to be synchronized normally to the target.

Fixing Solution

If the user does not have the required permissions, grant the corresponding permissions as specified in the check requirements, then re-run the verification task.

ヘルプとサポート

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

フィードバック