By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Error 'Character set '#255' is not a compiled character set and is not specified mySQL

0

Hi, we've been trying to create a replication between RDS Aurora MySQL to EC2 MySQL We managed to make it worked but after few hours of monitoring and few transactions on the database, we encountered this error "Error 'Character set '#255' is not a compiled character set" when we checked the slave status. We already tried different troubleshooting, tried replicating using new binlog position, modified some of the parameters on both mysql aurora and mysql 5.7 but none of them work. If we connect from a new position the replication will work for a few minutes but after that we will get again the same error. Did someone encounter this before? Any solutions you can provide that we should try? Thank you.

Topics
Migration & ModernizationAnalyticsDatabase
Tags
Amazon Relational Database ServiceDatabaseAmazon AuroraMySQL
Language
English
koyla
asked 7 months ago1023 views
1 Answer
0
Accepted Answer

Hello.

The error message you're encountering, "Error 'Character set '#255' is not a compiled character set," suggests that there might be an issue with character set compatibility between your RDS Aurora MySQL and EC2 MySQL instances. This error typically occurs when the replication process encounters a character set that is not supported or recognized on the receiving end.

You can use the SHOW VARIABLES LIKE 'character_set%'; and SHOW VARIABLES LIKE 'collation%'; commands to check the character set and collation settings on both servers.

Double-check the binary log format and replication settings on both servers. Make sure they are set correctly. The binary log format should be set to ROW or MIXED for better compatibility.

Best regards, Andrii

profile picture
EXPERT
Andrii S
answered 7 months ago
  • koyla
    7 months ago

    Thank you for the answer Andrii, regarding on the setup of both RDS and EC2 mysql, the binary log format is already set to MIXED and gtid_mode is set to ON. I ran this SHOW VARIABLES LIKE 'collation%'; command on both mysql and returns same results while the collation is kinda different. Should I set the same collation on both mysql? or this can be a compatibility issue? Any Idea?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content