"mysqldump --single-transaction" Executed On A Replica Causes An Errant GTID Set On A Replica; How To Fix GTID_EXECUTED When A Replica Instance Has An Errant GTID Set (Doc ID 2974256.1)

Last updated on APRIL 24, 2024

Applies to:

MySQL Server - Version 5.6 and later
Information in this document applies to any platform.

Goal

Occasionally, a replica may have errant transactions due to various reasons, such as <Bug 35665076>. If a replica has such a GTID set for errant transactions, replication may fail upon reconnect. This document describes how to fix a GTID set on a replica instance.

Solution

	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

Goal

Solution

Stop Replication

Show the Current GTID Set on the Source

Show the Current GTID Set on the Replica

Apply an Edited GTID Set to Replica

Start Replication

References

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

"mysqldump --single-transaction" Executed On A Replica Causes An Errant GTID Set On A Replica; How To Fix GTID_EXECUTED When A Replica Instance Has An Errant GTID Set (Doc ID 2974256.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!