Help Center/
Data Replication Service/
Troubleshooting/
Solutions to Failed Check Items/
Database Parameters/
Checking Whether the Collation of the Destination Database Is Correct
Updated on 2022-09-21 GMT+08:00
Checking Whether the Collation of the Destination Database Is Correct
Oracle->MySQL, Oracle->GaussDB(for MySQL), and Oracle->DDM Synchronization
|
Check Item |
Whether the collation of the destination database is correct |
|---|---|
|
Description |
The primary key or unique key in the destination database contains a collation ended in _ci. The collation ending in _ci is case insensitive, so an error indicating duplicate keys may be reported during synchronization and cause the synchronization to fail. |
|
Failure Cause and Handling Suggestion |
Failure cause: The destination database collation is not supported. Handling suggestion: Change the destination database collation to a case-sensitive collation (not ending with _ci). |
Parent topic: Database Parameters
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
