Memory Table Can Cause Errant Transaction In GTID Replication After Slave Restart
(Doc ID 2632668.1)
Last updated on FEBRUARY 04, 2020
Applies to:MySQL Server - Version 5.7 to 8.0 [Release 5.7 to 8.0]
Information in this document applies to any platform.
GTID was generated locally on the slave after the slave database restart.
1. Create a memory table on the master;
Restart the slave database.
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