How to set the value of gtid_purged in case of replication failure in MYSQL Database Service
(Doc ID 2835095.1)
Last updated on JULY 10, 2023
Applies to:
MySQL Database Service - Version N/A to N/AInformation in this document applies to any platform.
Goal
Creating replication channel does not work because of missing gtid transaction
or there can be some possible error as:
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Cannot replicate because the master purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master's binary log expiration period.
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 |