Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: oracle迁入tidb

Has anyone migrated from Oracle to TiDB? Are there any precautions to take?
Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: oracle迁入tidb
Has anyone migrated from Oracle to TiDB? Are there any precautions to take?
I’ve been working on it recently. TiDB does not support custom functions or stored procedures, but other issues are fine. For import and export, you can use CSV files and load them with Lightning, or use some tools for data transfer. The character set conversion from GBK to UTF-8 has no impact.
Oracle stored procedures are not supported; directly use Dumpling for export and import.
If using OGG, you need to be aware of the license issues (the article above didn’t mention this).
Table structure, field conversion, large fields, functions, stored procedures
There is no difference from migrating from ORACLE to MySQL, modifying the character set and table structure conversion, and some large fields are not supported.
The main issues are still the lack of support for incremental updates, special fields, oversized data, and custom fields.
There is a tool that supports heterogeneous data structure conversion from Oracle to MySQL/TiDB:
It was developed by a certain expert within PingCAP and has not been released to the public.
The Navicat tool has a data transfer feature that will work.