TiCDC Migrating Data to MySQL 5.0 Version, Unknown Character Set: "utf8mb4"

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: ticdc 迁移数据至mysql5.0版本，unknown character set:“utf8mb4”

| username: TiDBer_GWyrPeql

[TiDB Usage Environment] Production Environment
[TiDB Version] v6.1.0
[Encountered Issue] When syncing data with Ticdc, it prompts unknown character set: “utf8mb4”
[Reproduction Path] tiup ctl:v6.1.0 cdc changefeed create --pd=http://172.16.9.200:2379 --sink-uri=“mysql://root:root@172.16.9.159:3306” --changefeed-id=“upstream-to-downstream” --start-ts=“434217889191428107”
[Issue Phenomenon and Impact]

No Title
No Title965×922 67.8 KB

[Attachments]

  • Relevant logs, configuration files, Grafana monitoring (https://metricstool.pingcap.com/)
  • TiUP Cluster Display information
  • TiUP Cluster Edit config information
  • TiDB-Overview monitoring
  • Corresponding module’s Grafana monitoring (if any, such as BR, TiDB-binlog, TiCDC, etc.)
  • Corresponding module logs (including logs one hour before and after the issue)
2
| username: wuxiangdong | Original post link

MySQL 5.0 does not support utf8mb4.

3
| username: wuxiangdong | Original post link

It seems that Utf8mb4 was only introduced in MySQL 5.6 and 5.7.

4
| username: Hacker007 | Original post link

Such an old version of MySQL, it needs to be upgraded to 5.7.

5
| username: TiDBer_GWyrPeql | Original post link

The issue has been resolved. I’m not sure about the TiDB version, but after using TiDB v4.0.16, versions prior to 6.0 work fine.

6
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.