Skip to main content

ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL

This page is part of MariaDB's Enterprise Documentation.

The parent of this page is: Error Codes

Topics on this page:

Overview
CHANGE HISTORY
EXTERNAL REFERENCES

Overview

The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL

See also: Error Codes in 10.6 ES, in 10.6 CS, in 10.5 ES, in 10.5 CS, in 10.4 ES, in 10.4 CS, in 10.3 ES, in 10.3 CS, in 10.2 ES, and in 10.2 CS

CHANGE HISTORY

Release Series	History
10.6 Enterprise	Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1770
10.6 Community	Present starting in MariaDB Community Server 10.6.0 as error number 1770
10.5 Enterprise	Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1770
10.5 Community	Present starting in MariaDB Community Server 10.5.0 as error number 1770
10.4 Enterprise	Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1770
10.4 Community	Present starting in MariaDB Community Server 10.4.0 as error number 1770
10.3 Enterprise	Present starting in MariaDB Enterprise Server 10.3.16-1 as error number 1770
10.3 Community	Present starting in MariaDB Community Server 10.3.0 as error number 1770
10.2 Enterprise	Present starting in MariaDB Enterprise Server 10.2.25-1 as error number 1770
10.2 Community	Present starting in MariaDB Community Server 10.2.0 as error number 1770

EXTERNAL REFERENCES

Information specific to MariaDB SkySQL can be found on the ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL page in the SkySQL Documentation.