ER_MTS_CHANGE_MASTER_CANT_RUN_WITH_GAPS

Overview

CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL

See also: Error Codes for MariaDB Enterprise Server 23.08, in 23.07 ES, in 10.6 ES, 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 23.08, in 23.07 ES, in 10.6 ES, 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

23.08 Enterprise

  • Present starting in MariaDB Enterprise Server 23.08.0 as error number 1802

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0 as error number 1802

10.6 Enterprise

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

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

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

10.3 Enterprise

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

10.3 Community

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

10.2 Enterprise

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

10.2 Community

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

Release Series

History

23.08 Enterprise

  • Present starting in MariaDB Enterprise Server 23.08.0 as error number 1802

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0 as error number 1802

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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

EXTERNAL REFERENCES