ER_GTID_START_FROM_BINLOG_HOLE

Overview

The binlog on the master is missing the GTID %u-%lu requested by the slave (even though a subsequent sequence number does exist), and GTID strict mode is enabled

See also: Error Codes for MariaDB Enterprise Server 10.6, in 10.5 ES, in 10.4 ES, in 10.3 ES, in 10.2 ES, in 10.6 CS, in 10.5 CS, in 10.4 CS, in 10.3 CS, and in 10.2 CS

See also: Error Codes for MariaDB Enterprise Server 10.6, in 10.5 ES, and in 10.4 ES

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1951

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0 as error number 1951

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1951

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0 as error number 1951

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1951

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0 as error number 1951

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1 as error number 1951

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0 as error number 1951

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1 as error number 1951

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0 as error number 1951

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1951

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1951

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1951

EXTERNAL REFERENCES