ER_GTID_NEXT_TYPE_UNDEFINED_GROUP

Overview

When GTID_NEXT is set to a GTID, you must explicitly set it again after a COMMIT or ROLLBACK. If you see this error message in the slave SQL thread, it means that a table in the current transaction is transactional on the master and non-transactional on the slave. In a client connection, it means that you executed SET GTID_NEXT before a transaction and forgot to set GTID_NEXT to a different identifier or to 'AUTOMATIC' after COMMIT or ROLLBACK. Current GTID_NEXT is '%s'

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 1837

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

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

10.3 Enterprise

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

10.3 Community

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

10.2 Enterprise

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

10.2 Community

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

Release Series

History

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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

EXTERNAL REFERENCES