5.7 Replication Errors (1 reply)

After setting up single Source/Replica pair using MySQL 5.7.32, row-based replication, I am encountering the following two errors (1517, 1677) in the Replica's error log; however, there do not appear to be related errors on the Source. Has anyone encountered these and have some guidance as to whether they might be compromising the integrity of the Replica? If I don't ignore these two error codes, replication stops in its tracks. Thanks for any guidance you can provide.

The first error (1517) appears to possibly saying a Query event wasn't possible, so, perhaps this isn't impacting the integrity of the Replica? For the second error (1677), it seems that the table isn't being created on the Replica. I have verified that character set related global variable values are the same for both Source/Replica. The only differences in configuration between the two servers are replication-specific settings.


>>>>>>>>>>>>>>>>

Last_SQL_Errno: 1517

               Last_SQL_Error: Error 'Duplicate partition name p20211022' on query. Default database: 'em'. Query

: 'ALTER TABLE `footable` REORGANIZE PARTITION pMAX INTO (PARTITION p20211022 VALUES LESS THAN (16349472

00), PARTITION pMAX VALUES LESS THAN MAXVALUE)'

 

2021-10-21T15:22:20.770067Z 5 [Note] Slave SQL for channel '': Could not execute Query event. Detailed error: Duplicate partition name p20211022;, Error_code: 1517

>>>>>>

(Error Code 1677)

Last_Error: Column 3 of table 'fooschema.footable' cannot be converted from type 'varchar(765(bytes))' to type 'varchar(255(bytes) latin1)'