ER_BACKUP_UNKNOWN_STAGE

Overview

In 23.08 ES, 23.07 ES, 10.6 ES, 10.6 CS, 10.5 ES, 10.5 CS, 10.4 ES, 10.4 CS, 10.3 ES, 10.2 ES:

Unknown backup stage: '%s'. Stage should be one of START, FLUSH, BLOCK_DDL, BLOCK_COMMIT or END

In 23.08 ES, 23.07 ES, 10.6 ES, 10.5 ES, 10.4 ES:

Unknown backup stage: '%s'. Stage should be one of START, FLUSH, BLOCK_DDL, BLOCK_COMMIT or END

In 10.3 CS, 10.2 CS:

Not present

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 4149

23.07 Enterprise

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

10.6 Enterprise

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

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

  • Added in MariaDB Community Server 10.4.1 as error number 4149

10.3 Enterprise

  • Added in MariaDB Enterprise Server 10.3.16-1 as error number 4149

10.3 Community

  • Not present.

10.2 Enterprise

  • Added in MariaDB Enterprise Server 10.2.25-1 as error number 4149

10.2 Community

  • Not present.

Release Series

History

23.08 Enterprise

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

23.07 Enterprise

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

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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

EXTERNAL REFERENCES