My Oracle Support Banner

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.

Symptoms

GTID was generated locally on the slave after the slave database restart.

For example:

1. Create a memory table on the master;

 

Changes

 Restart the slave 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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.