MySQL Enterprise Backup (MEB) Reports An Invalid Binary Log Position; In Some Cases As 18446744073709551615 Or -1
(Doc ID 2043644.1)
Last updated on MARCH 12, 2021
Applies to:MySQL Enterprise Backup - Version 3.6 to 4.0 [Release 3.6 to 4.0]
Information in this document applies to any platform.
When creating a backup with MySQL Enterprise Backup 3.12.3 or earlier or 4.0 where the backup was created in one of the following ways:
- with the --no-locking option
- with the --no-connection option
- with the --connect-if-online option and MySQL being offline
then the binary log position is reported as invalid binary log position such as 18446744073709551615 or -1, but also in some cases what looks like a valid position.
- At the end of the backup phase:
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 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.