ER_ERROR_ON_MASTER

Overview

Query partially completed on the master (error on master: %d) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;. Query:'%s'

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

11.4 Enterprise

  • Not present.

10.6 Enterprise

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

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

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

10.3 Enterprise

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

10.3 Community

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

10.2 Enterprise

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

10.2 Community

  • Added in MariaDB Community Server 10.2.3 as error number 3000

  • Error number changed in MariaDB Community Server 10.2.5 from 3000 to 3001

Release Series

History

11.4 Enterprise

  • Not present.

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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

EXTERNAL REFERENCES