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 2023-04-03 GMT+08:00

View PDF

Checking Whether the Collation of the Destination Database Is Correct

Oracle -> MySQL, Oracle -> GaussDB(for MySQL), and Oracle -> DDM Synchronization

**Table 1** Checking whether the collation of the destination database is correct
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

Previous topic: Checking the Database Compatibility Type

Next topic: Checking Whether the Index Name Is Supported

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.