MySQL 5.6.21 replication slave exits unexpectedly when replicating temporal types from 5.5
(Doc ID 1947789.1)
Last updated on APRIL 12, 2021
Applies to:MySQL Server - Version 5.6 to 5.6 [Release 5.6]
Information in this document applies to any platform.
Replicating temporal columns (DATETIME, TIME, TIMESTAMP) with Row-Based Replication (RBR) may cause the server to exit unexpectedly.
A stack trace similar to the following may be observed:
This issue generally occurs after a replication slave is upgraded to MySQL 5.6.21 or earlier.
Handling of temporal types changed in MySQL 5.6, and this issue occurs when the master and slave have differing versions of these types. Generally this is observed when
- Replicating from a master running MySQL 5.5.x to a slave running MySQL <= 5.6.21
- May also occur when the master runs MySQL 5.6 but the table was created on MySQL 5.5 or earlier before the upgrade (in this case, the table still uses the MySQL 5.5 temporal format)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document