Memory Table Can Cause Errant Transaction In GTID Replication After Slave Restart
(Doc ID 2632668.1)
Last updated on SEPTEMBER 09, 2021
Applies to:
MySQL Server - Version 5.7 to 8.0 [Release 5.7 to 8.0]Information in this document applies to any platform.
Disclaimer: Starting from v8.0, some terms have been deprecated. Older releases will only use the deprecated terminology, and new releases will only use new terminology. Please see https://dev.mysql.com/doc/mysqld-version-reference/en/ for a complete list of those changes, and in which minor versions it happened.
Symptoms
GTID was generated locally on the replica after the replica database restart.
For example:
1. Create a memory table on the source;
Changes
Restart the replica database.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |