tencent cloud

TDSQL-C for MySQL

FAQs

Download
Focus Mode
Font Size
Last updated: 2026-08-28 12:06:37
AI-Translated
This document describes common issues you may encounter when using the traffic replay feature.

What to Do If the Pre-Check Fails

On the pre-check page, the system provides corresponding prompts. You can view the specific failed items and fix them according to the handling suggestions provided by the system. After the fix, you can click Re-check.
Typically, the pre-check fails due to reasons such as: database audit not being enabled on the source instance, insufficient account permissions (requiring a high-privilege account), ports not being opened in the security group, or the target instance not being ready. It is recommended that you meet the preceding conditions in advance to avoid pre-check failure.

How the System Handles Missing Fields in External Log Pre-Checks

If you select an external instance as the source, the system checks the fields in the audit logs. For mandatory fields: timestamp, nsTime, thread_id, execTime, errCode, dbName, and sql, the replay is blocked if any of them is missing. You need to re-export the audit logs containing the complete fields and then run the pre-check again. For missing optional fields, the system issues a warning but does not block the replay process. You can ignore the warning and proceed to the next step.

What to Do If the Operation Fails

Automatic task retry is not supported. If a task goes to the RunningFailed state, you need to submit a ticket to contact technical support for handling.

How Long Does Replay Take?

Typically, replaying one hour of production traffic takes approximately 1 to 1.5 hours. For the exact duration, refer to the actual time taken.

Can a Replay Task Be Terminated Midway?

Yes, you can click Terminate on the task details page. When a task is terminated while running, a partial report is generated and resources are automatically reclaimed. A terminated task cannot be restarted.

Where to Find Tasks Saved as Drafts

You can view tasks on the task list page. A task with the status "Configuring" is a draft. Click Modify to continue editing it.

Why Is the Slow SQL Statement Comparison Not Visible for External Log Sources?

The source instance slow SQL threshold data can be automatically obtained and displayed only when the source instance is TDSQL-C for MySQL. External log sources cannot provide the source instance slow SQL threshold. However, you can still count the number of slow SQL statements on the target end by using the target instance's slow SQL threshold.

Common Error Codes

Error Code
Description
1000 ~ 1099: General Query / Connection Related Errors
1030
Insufficient disk space, corrupted table
1031
Incompatible storage engine operation
1033
Corrupted .frm file or storage engine issue
1037,1038,1041
The memory is insufficient.
1040
The number of connections exceeds the threshold of the database / service.
1047
Unrecognized operation
1048
The field is defined as NOT NULL, but no value is provided during INSERT / UPDATE operations.
1055
This error shares the same origin as error 1140 and is a strict validation under the ONLY_FULL_GROUP_BY mode: a non-aggregated column in the SELECT clause is not included in the GROUP BY clause, and that column has no functional dependency on the grouping columns.
1100 ~ 1199: Table / Index Operation Related Errors
1109
The referenced table alias does not exist (an undefined table alias is used in the SQL statement).
1115
Field compatibility issue (usually related to the MySQL version)
1136
The number of fields specified in the INSERT statement does not match the number of values actually passed in.
1140
MySQL has the ONLY_FULL_GROUP_BY mode enabled (enabled by default). The SELECT statement contains both aggregate functions (MIN/MAX/COUNT) and non-aggregated columns, but the non-aggregated columns are not grouped by GROUP BY. (Related to sql_mode.)
1193
Unknown system variable
1200 ~ 1299: Transaction / Lock Related Errors
1227
Insufficient permissions to perform the current operation.
1248
All tables must have an alias (no alias is specified for a table during multi-table queries / deletions).
1264
Numeric value exceeds the field range (the stored value for a numeric-type field is beyond the upper / lower limit).
1265
Data truncation (the inserted numeric value / string exceeds the defined length of the field or the format is mismatched).
1267
Character set collation mismatch
1292
Column data types are incompatible under the sql_mode strict mode.
1300 ~ 1399: Data Format / Value Related Errors
1305
A non-existent object (table, field, stored procedure, function, trigger, and so on) is referenced.
1364
The field has a default value constraint, but no default value is set (or the default value expression is invalid), which is usually triggered by the sql_mode strict mode.
1366
String encoding is incompatible (the field character set does not support the inserted characters).
Other Error Codes
1406
String length exceeds the field limit (the field cannot store the inserted string).
1525
Time field format issue (sql_mode issue or MySQL version issue)
3024
SQL execution time is exceeded, usually because /+ MAX_EXECUTION_TIME(100) / HINT is set.
3065
When DISTINCT is used for deduplication, the column referenced by ORDER BY is not included in the SELECT list (this is not allowed in MySQL strict mode).
3141
JSON format error (the format of the inserted / updated JSON data is invalid).
8501
Connection / driver error

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback