MySQL 8.4 Error Reference  /  Server Error Message Reference

Chapter 2 Server Error Message Reference

The MySQL server writes some error messages to its error log, and sends others to client programs.

Example server-side error messages written to the error log: 

2018-10-28T13:01:32.735983Z 0 [Note] [MY-010303] [Server] Skipping
generation of SSL certificates as options related to SSL are specified.

2018-10-02T03:20:39.410387Z 768 [ERROR] [MY-010045] [Server] Event Scheduler:
[evtuser@localhost][myschema.e_daily] Unknown database 'mydb'

Example server-side error message sent to client programs, as displayed by the mysql client: 

mysql> SELECT * FROM no_such_table;
ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist

Each server error message includes an error code, SQLSTATE value, and message string, as described in Error Message Sources and Elements. These elements are available as described in Error Information Interfaces.

In addition to the errors in the following list, the server can also produce error messages that have error codes in the range from 1 to 999. See Chapter 4, Global Error Message Reference

  • Error number: 1002; Symbol: ER_NO; SQLSTATE: HY000

    Message: NO

    Used in the construction of other messages.

  • Error number: 1003; Symbol: ER_YES; SQLSTATE: HY000

    Message: YES

    Used in the construction of other messages.

    Extended EXPLAIN format generates Note messages. ER_YES is used in the Code column for these messages in subsequent SHOW WARNINGS output.

  • Error number: 1004; Symbol: ER_CANT_CREATE_FILE; SQLSTATE: HY000

    Message: Can't create file '%s' (errno: %d - %s)

    Occurs for failure to create or copy a file needed for some operation.

    Possible causes: Permissions problem for source file; destination file already exists but is not writeable.

  • Error number: 1005; Symbol: ER_CANT_CREATE_TABLE; SQLSTATE: HY000

    Message: Can't create table '%s' (errno: %d - %s)

    InnoDB reports this error when a table cannot be created. If the error message refers to error 150, table creation failed because a foreign key constraint was not correctly formed. If the error message refers to error −1, table creation probably failed because the table includes a column name that matched the name of an internal InnoDB table.

  • Error number: 1006; Symbol: ER_CANT_CREATE_DB; SQLSTATE: HY000

    Message: Can't create database '%s' (errno: %d - %s)

  • Error number: 1007; Symbol: ER_DB_CREATE_EXISTS; SQLSTATE: HY000

    Message: Can't create database '%s'; database exists

    An attempt to create a database failed because the database already exists.

    Drop the database first if you really want to replace an existing database, or add an IF NOT EXISTS clause to the CREATE DATABASE statement if to retain an existing database without having the statement produce an error.

  • Error number: 1008; Symbol: ER_DB_DROP_EXISTS; SQLSTATE: HY000

    Message: Can't drop database '%s'; database doesn't exist

  • Error number: 1010; Symbol: ER_DB_DROP_RMDIR; SQLSTATE: HY000

    Message: Error dropping database (can't rmdir '%s', errno: %d - %s)

  • Error number: 1012; Symbol: ER_CANT_FIND_SYSTEM_REC; SQLSTATE: HY000

    Message: Can't read record in system table

    Returned by InnoDB for attempts to access InnoDB INFORMATION_SCHEMA tables when InnoDB is unavailable.

  • Error number: 1013; Symbol: ER_CANT_GET_STAT; SQLSTATE: HY000

    Message: Can't get status of '%s' (errno: %d - %s)

  • Error number: 1015; Symbol: ER_CANT_LOCK; SQLSTATE: HY000

    Message: Can't lock file (errno: %d - %s)

  • Error number: 1016; Symbol: ER_CANT_OPEN_FILE; SQLSTATE: HY000

    Message: Can't open file: '%s' (errno: %d - %s)

    InnoDB reports this error when the table from the InnoDB data files cannot be found.

  • Error number: 1017; Symbol: ER_FILE_NOT_FOUND; SQLSTATE: HY000

    Message: Can't find file: '%s' (errno: %d - %s)

  • Error number: 1018; Symbol: ER_CANT_READ_DIR; SQLSTATE: HY000

    Message: Can't read dir of '%s' (errno: %d - %s)

  • Error number: 1020; Symbol: ER_CHECKREAD; SQLSTATE: HY000

    Message: Record has changed since last read in table '%s'

  • Error number: 1022; Symbol: ER_DUP_KEY; SQLSTATE: 23000

    Message: Can't write; duplicate key in table '%s'

  • Error number: 1024; Symbol: ER_ERROR_ON_READ; SQLSTATE: HY000

    Message: Error reading file '%s' (errno: %d - %s)

  • Error number: 1025; Symbol: ER_ERROR_ON_RENAME; SQLSTATE: HY000

    Message: Error on rename of '%s' to '%s' (errno: %d - %s)

  • Error number: 1026; Symbol: ER_ERROR_ON_WRITE; SQLSTATE: HY000

    Message: Error writing file '%s' (errno: %d - %s)

  • Error number: 1027; Symbol: ER_FILE_USED; SQLSTATE: HY000

    Message: '%s' is locked against change

  • Error number: 1030; Symbol: ER_GET_ERRNO; SQLSTATE: HY000

    Message: Got error %d - '%s' from storage engine

    Check the %d value to see what the OS error means. For example, 28 indicates that you have run out of disk space.

  • Error number: 1031; Symbol: ER_ILLEGAL_HA; SQLSTATE: HY000

    Message: Table storage engine for '%s' doesn't have this option

  • Error number: 1032; Symbol: ER_KEY_NOT_FOUND; SQLSTATE: HY000

    Message: Can't find record in '%s'

  • Error number: 1033; Symbol: ER_NOT_FORM_FILE; SQLSTATE: HY000

    Message: Incorrect information in file: '%s'

  • Error number: 1034; Symbol: ER_NOT_KEYFILE; SQLSTATE: HY000

    Message: Incorrect key file for table '%s'; try to repair it

  • Error number: 1035; Symbol: ER_OLD_KEYFILE; SQLSTATE: HY000

    Message: Old key file for table '%s'; repair it!

  • Error number: 1036; Symbol: ER_OPEN_AS_READONLY; SQLSTATE: HY000

    Message: Table '%s' is read only

  • Error number: 1037; Symbol: ER_OUTOFMEMORY; SQLSTATE: HY001

    Message: Out of memory; restart server and try again (needed %d bytes)

  • Error number: 1038; Symbol: ER_OUT_OF_SORTMEMORY; SQLSTATE: HY001

    Message: Out of sort memory, consider increasing server sort buffer size

  • Error number: 1040; Symbol: ER_CON_COUNT_ERROR; SQLSTATE: 08004

    Message: Too many connections

  • Error number: 1041; Symbol: ER_OUT_OF_RESOURCES; SQLSTATE: HY000

    Message: Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space

  • Error number: 1042; Symbol: ER_BAD_HOST_ERROR; SQLSTATE: 08S01

    Message: Can't get hostname for your address

  • Error number: 1043; Symbol: ER_HANDSHAKE_ERROR; SQLSTATE: 08S01

    Message: Bad handshake

  • Error number: 1044; Symbol: ER_DBACCESS_DENIED_ERROR; SQLSTATE: 42000

    Message: Access denied for user '%s'@'%s' to database '%s'

  • Error number: 1045; Symbol: ER_ACCESS_DENIED_ERROR; SQLSTATE: 28000

    Message: Access denied for user '%s'@'%s' (using password: %s)

  • Error number: 1046; Symbol: ER_NO_DB_ERROR; SQLSTATE: 3D000

    Message: No database selected

  • Error number: 1047; Symbol: ER_UNKNOWN_COM_ERROR; SQLSTATE: 08S01

    Message: Unknown command

  • Error number: 1048; Symbol: ER_BAD_NULL_ERROR; SQLSTATE: 23000

    Message: Column '%s' cannot be null

  • Error number: 1049; Symbol: ER_BAD_DB_ERROR; SQLSTATE: 42000

    Message: Unknown database '%s'

  • Error number: 1050; Symbol: ER_TABLE_EXISTS_ERROR; SQLSTATE: 42S01

    Message: Table '%s' already exists

  • Error number: 1051; Symbol: ER_BAD_TABLE_ERROR; SQLSTATE: 42S02

    Message: Unknown table '%s'

  • Error number: 1052; Symbol: ER_NON_UNIQ_ERROR; SQLSTATE: 23000

    Message: Column '%s' in %s is ambiguous 

    %s = column name
%s = location of column (for example, "field list")

    Likely cause: A column appears in a query without appropriate qualification, such as in a select list or ON clause.

    Examples: 

    mysql> SELECT i FROM t INNER JOIN t AS t2;
ERROR 1052 (23000): Column 'i' in field list is ambiguous

mysql> SELECT * FROM t LEFT JOIN t AS t2 ON i = i;
ERROR 1052 (23000): Column 'i' in on clause is ambiguous

    Resolution:

    • Qualify the column with the appropriate table name: 

      mysql> SELECT t2.i FROM t INNER JOIN t AS t2;

    • Modify the query to avoid the need for qualification: 

      mysql> SELECT * FROM t LEFT JOIN t AS t2 USING (i);

  • Error number: 1053; Symbol: ER_SERVER_SHUTDOWN; SQLSTATE: 08S01

    Message: Server shutdown in progress

  • Error number: 1054; Symbol: ER_BAD_FIELD_ERROR; SQLSTATE: 42S22

    Message: Unknown column '%s' in '%s'

  • Error number: 1055; Symbol: ER_WRONG_FIELD_WITH_GROUP; SQLSTATE: 42000

    Message: '%s' isn't in GROUP BY

  • Error number: 1056; Symbol: ER_WRONG_GROUP_FIELD; SQLSTATE: 42000

    Message: Can't group on '%s'

  • Error number: 1057; Symbol: ER_WRONG_SUM_SELECT; SQLSTATE: 42000

    Message: Statement has sum functions and columns in same statement

  • Error number: 1058; Symbol: ER_WRONG_VALUE_COUNT; SQLSTATE: 21S01

    Message: Column count doesn't match value count

  • Error number: 1059; Symbol: ER_TOO_LONG_IDENT; SQLSTATE: 42000

    Message: Identifier name '%s' is too long

  • Error number: 1060; Symbol: ER_DUP_FIELDNAME; SQLSTATE: 42S21

    Message: Duplicate column name '%s'

  • Error number: 1061; Symbol: ER_DUP_KEYNAME; SQLSTATE: 42000

    Message: Duplicate key name '%s'

  • Error number: 1062; Symbol: ER_DUP_ENTRY; SQLSTATE: 23000

    Message: Duplicate entry '%s' for key %d

    The message returned with this error uses the format string for ER_DUP_ENTRY_WITH_KEY_NAME.

  • Error number: 1063; Symbol: ER_WRONG_FIELD_SPEC; SQLSTATE: 42000

    Message: Incorrect column specifier for column '%s'

  • Error number: 1064; Symbol: ER_PARSE_ERROR; SQLSTATE: 42000

    Message: %s near '%s' at line %d

  • Error number: 1065; Symbol: ER_EMPTY_QUERY; SQLSTATE: 42000

    Message: Query was empty

  • Error number: 1066; Symbol: ER_NONUNIQ_TABLE; SQLSTATE: 42000

    Message: Not unique table/alias: '%s'

  • Error number: 1067; Symbol: ER_INVALID_DEFAULT; SQLSTATE: 42000

    Message: Invalid default value for '%s'

  • Error number: 1068; Symbol: ER_MULTIPLE_PRI_KEY; SQLSTATE: 42000

    Message: Multiple primary key defined

  • Error number: 1069; Symbol: ER_TOO_MANY_KEYS; SQLSTATE: 42000

    Message: Too many keys specified; max %d keys allowed

  • Error number: 1070; Symbol: ER_TOO_MANY_KEY_PARTS; SQLSTATE: 42000

    Message: Too many key parts specified; max %d parts allowed

  • Error number: 1071; Symbol: ER_TOO_LONG_KEY; SQLSTATE: 42000

    Message: Specified key was too long; max key length is %d bytes

  • Error number: 1072; Symbol: ER_KEY_COLUMN_DOES_NOT_EXITS; SQLSTATE: 42000

    Message: Key column '%s' doesn't exist in table

  • Error number: 1073; Symbol: ER_BLOB_USED_AS_KEY; SQLSTATE: 42000

    Message: BLOB column '%s' can't be used in key specification with the used table type

  • Error number: 1074; Symbol: ER_TOO_BIG_FIELDLENGTH; SQLSTATE: 42000

    Message: Column length too big for column '%s' (max = %lu); use BLOB or TEXT instead

  • Error number: 1075; Symbol: ER_WRONG_AUTO_KEY; SQLSTATE: 42000

    Message: Incorrect table definition; there can be only one auto column and it must be defined as a key

  • Error number: 1076; Symbol: ER_READY; SQLSTATE: HY000

    Message: %s: ready for connections. Version: '%s' socket: '%s' port: %d

  • Error number: 1079; Symbol: ER_SHUTDOWN_COMPLETE; SQLSTATE: HY000

    Message: %s: Shutdown complete

  • Error number: 1080; Symbol: ER_FORCING_CLOSE; SQLSTATE: 08S01

    Message: %s: Forcing close of thread %ld user: '%s'

  • Error number: 1081; Symbol: ER_IPSOCK_ERROR; SQLSTATE: 08S01

    Message: Can't create IP socket

  • Error number: 1082; Symbol: ER_NO_SUCH_INDEX; SQLSTATE: 42S12

    Message: Table '%s' has no index like the one used in CREATE INDEX; recreate the table

  • Error number: 1083; Symbol: ER_WRONG_FIELD_TERMINATORS; SQLSTATE: 42000

    Message: Field separator argument is not what is expected; check the manual

  • Error number: 1084; Symbol: ER_BLOBS_AND_NO_TERMINATED; SQLSTATE: 42000

    Message: You can't use fixed rowlength with BLOBs; please use 'fields terminated by'

  • Error number: 1085; Symbol: ER_TEXTFILE_NOT_READABLE; SQLSTATE: HY000

    Message: The file '%s' must be in the database directory or be readable by all

  • Error number: 1086; Symbol: ER_FILE_EXISTS_ERROR; SQLSTATE: HY000

    Message: File '%s' already exists

  • Error number: 1087; Symbol: ER_LOAD_INFO; SQLSTATE: HY000

    Message: Records: %ld Deleted: %ld Skipped: %ld Warnings: %ld

  • Error number: 1088; Symbol: ER_ALTER_INFO; SQLSTATE: HY000

    Message: Records: %ld Duplicates: %ld

  • Error number: 1089; Symbol: ER_WRONG_SUB_KEY; SQLSTATE: HY000

    Message: Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys

  • Error number: 1090; Symbol: ER_CANT_REMOVE_ALL_FIELDS; SQLSTATE: 42000

    Message: You can't delete all columns with ALTER TABLE; use DROP TABLE instead

  • Error number: 1091; Symbol: ER_CANT_DROP_FIELD_OR_KEY; SQLSTATE: 42000

    Message: Can't DROP '%s'; check that column/key exists

  • Error number: 1092; Symbol: ER_INSERT_INFO; SQLSTATE: HY000

    Message: Records: %ld Duplicates: %ld Warnings: %ld

  • Error number: 1093; Symbol: ER_UPDATE_TABLE_USED; SQLSTATE: HY000

    Message: You can't specify target table '%s' for update in FROM clause

    This error occurs for attempts to select from and modify the same table within a single statement. If the select attempt occurs within a derived table, you can avoid this error by setting the derived_merge flag of the optimizer_switch system variable to force the subquery to be materialized into a temporary table, which effectively causes it to be a different table from the one modified. See Optimizing Derived Tables, View References, and Common Table Expressions with Merging or Materialization.

  • Error number: 1094; Symbol: ER_NO_SUCH_THREAD; SQLSTATE: HY000

    Message: Unknown thread id: %lu

  • Error number: 1095; Symbol: ER_KILL_DENIED_ERROR; SQLSTATE: HY000

    Message: You are not owner of thread %lu

  • Error number: 1096; Symbol: ER_NO_TABLES_USED; SQLSTATE: HY000

    Message: No tables used

  • Error number: 1097; Symbol: ER_TOO_BIG_SET; SQLSTATE: HY000

    Message: Too many strings for column %s and SET

  • Error number: 1098; Symbol: ER_NO_UNIQUE_LOGFILE; SQLSTATE: HY000

    Message: Can't generate a unique log-filename %s.(1-999)

  • Error number: 1099; Symbol: ER_TABLE_NOT_LOCKED_FOR_WRITE; SQLSTATE: HY000

    Message: Table '%s' was locked with a READ lock and can't be updated

  • Error number: 1100; Symbol: ER_TABLE_NOT_LOCKED; SQLSTATE: HY000

    Message: Table '%s' was not locked with LOCK TABLES

  • Error number: 1101; Symbol: ER_BLOB_CANT_HAVE_DEFAULT; SQLSTATE: 42000

    Message: BLOB, TEXT, GEOMETRY or JSON column '%s' can't have a default value

  • Error number: 1102; Symbol: ER_WRONG_DB_NAME; SQLSTATE: 42000

    Message: Incorrect database name '%s'

  • Error number: 1103; Symbol: ER_WRONG_TABLE_NAME; SQLSTATE: 42000

    Message: Incorrect table name '%s'

  • Error number: 1104; Symbol: ER_TOO_BIG_SELECT; SQLSTATE: 42000

    Message: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay

  • Error number: 1105; Symbol: ER_UNKNOWN_ERROR; SQLSTATE: HY000

    Message: Unknown error

  • Error number: 1106; Symbol: ER_UNKNOWN_PROCEDURE; SQLSTATE: 42000

    Message: Unknown procedure '%s'

  • Error number: 1107; Symbol: ER_WRONG_PARAMCOUNT_TO_PROCEDURE; SQLSTATE: 42000

    Message: Incorrect parameter count to procedure '%s'

  • Error number: 1108; Symbol: ER_WRONG_PARAMETERS_TO_PROCEDURE; SQLSTATE: HY000

    Message: Incorrect parameters to procedure '%s'

  • Error number: 1109; Symbol: ER_UNKNOWN_TABLE; SQLSTATE: 42S02

    Message: Unknown table '%s' in %s

  • Error number: 1110; Symbol: ER_FIELD_SPECIFIED_TWICE; SQLSTATE: 42000

    Message: Column '%s' specified twice

  • Error number: 1111; Symbol: ER_INVALID_GROUP_FUNC_USE; SQLSTATE: HY000

    Message: Invalid use of group function

  • Error number: 1112; Symbol: ER_UNSUPPORTED_EXTENSION; SQLSTATE: 42000

    Message: Table '%s' uses an extension that doesn't exist in this MySQL version

  • Error number: 1113; Symbol: ER_TABLE_MUST_HAVE_COLUMNS; SQLSTATE: 42000

    Message: A table must have at least 1 column

  • Error number: 1114; Symbol: ER_RECORD_FILE_FULL; SQLSTATE: HY000

    Message: The table '%s' is full

    InnoDB reports this error when the system tablespace runs out of free space. Reconfigure the system tablespace to add a new data file.

  • Error number: 1115; Symbol: ER_UNKNOWN_CHARACTER_SET; SQLSTATE: 42000

    Message: Unknown character set: '%s'

  • Error number: 1116; Symbol: ER_TOO_MANY_TABLES; SQLSTATE: HY000

    Message: Too many tables; MySQL can only use %d tables in a join

  • Error number: 1117; Symbol: ER_TOO_MANY_FIELDS; SQLSTATE: HY000

    Message: Too many columns

  • Error number: 1118; Symbol: ER_TOO_BIG_ROWSIZE; SQLSTATE: 42000

    Message: Row size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

  • Error number: 1119; Symbol: ER_STACK_OVERRUN; SQLSTATE: HY000

    Message: Thread stack overrun: Used: %ld of a %ld stack. Use 'mysqld --thread_stack=#' to specify a bigger stack if needed

  • Error number: 1120; Symbol: ER_WRONG_OUTER_JOIN_UNUSED; SQLSTATE: 42000

    Message: Cross dependency found in OUTER JOIN; examine your ON conditions

  • Error number: 1121; Symbol: ER_NULL_COLUMN_IN_INDEX; SQLSTATE: 42000

    Message: Table handler doesn't support NULL in given index. Please change column '%s' to be NOT NULL or use another handler

  • Error number: 1122; Symbol: ER_CANT_FIND_UDF; SQLSTATE: HY000

    Message: Can't load function '%s'

  • Error number: 1123; Symbol: ER_CANT_INITIALIZE_UDF; SQLSTATE: HY000

    Message: Can't initialize function '%s'; %s

  • Error number: 1124; Symbol: ER_UDF_NO_PATHS; SQLSTATE: HY000

    Message: No paths allowed for shared library

  • Error number: 1125; Symbol: ER_UDF_EXISTS; SQLSTATE: HY000

    Message: Function '%s' already exists

  • Error number: 1126; Symbol: ER_CANT_OPEN_LIBRARY; SQLSTATE: HY000

    Message: Can't open shared library '%s' (errno: %d %s)

  • Error number: 1127; Symbol: ER_CANT_FIND_DL_ENTRY; SQLSTATE: HY000

    Message: Can't find symbol '%s' in library

  • Error number: 1128; Symbol: ER_FUNCTION_NOT_DEFINED; SQLSTATE: HY000

    Message: Function '%s' is not defined

  • Error number: 1129; Symbol: ER_HOST_IS_BLOCKED; SQLSTATE: HY000

    Message: Host '%s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'

  • Error number: 1130; Symbol: ER_HOST_NOT_PRIVILEGED; SQLSTATE: HY000

    Message: Host '%s' is not allowed to connect to this MySQL server

  • Error number: 1131; Symbol: ER_PASSWORD_ANONYMOUS_USER; SQLSTATE: 42000

    Message: You are using MySQL as an anonymous user and anonymous users are not allowed to change passwords

  • Error number: 1132; Symbol: ER_PASSWORD_NOT_ALLOWED; SQLSTATE: 42000

    Message: You must have privileges to update tables in the mysql database to be able to change passwords for others

  • Error number: 1133; Symbol: ER_PASSWORD_NO_MATCH; SQLSTATE: 42000

    Message: Can't find any matching row in the user table

  • Error number: 1134; Symbol: ER_UPDATE_INFO; SQLSTATE: HY000

    Message: Rows matched: %ld Changed: %ld Warnings: %ld

  • Error number: 1135; Symbol: ER_CANT_CREATE_THREAD; SQLSTATE: HY000

    Message: Can't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug

  • Error number: 1136; Symbol: ER_WRONG_VALUE_COUNT_ON_ROW; SQLSTATE: 21S01

    Message: Column count doesn't match value count at row %ld

  • Error number: 1137; Symbol: ER_CANT_REOPEN_TABLE; SQLSTATE: HY000

    Message: Can't reopen table: '%s'

  • Error number: 1138; Symbol: ER_INVALID_USE_OF_NULL; SQLSTATE: 22004

    Message: Invalid use of NULL value

  • Error number: 1139; Symbol: ER_REGEXP_ERROR; SQLSTATE: 42000

    Message: Got error '%s' from regexp

  • Error number: 1140; Symbol: ER_MIX_OF_GROUP_FUNC_AND_FIELDS; SQLSTATE: 42000

    Message: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause

  • Error number: 1141; Symbol: ER_NONEXISTING_GRANT; SQLSTATE: 42000

    Message: There is no such grant defined for user '%s' on host '%s'

  • Error number: 1142; Symbol: ER_TABLEACCESS_DENIED_ERROR; SQLSTATE: 42000

    Message: %s command denied to user '%s'@'%s' for table '%s'

  • Error number: 1143; Symbol: ER_COLUMNACCESS_DENIED_ERROR; SQLSTATE: 42000

    Message: %s command denied to user '%s'@'%s' for column '%s' in table '%s'

  • Error number: 1144; Symbol: ER_ILLEGAL_GRANT_FOR_TABLE; SQLSTATE: 42000

    Message: Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used

  • Error number: 1145; Symbol: ER_GRANT_WRONG_HOST_OR_USER; SQLSTATE: 42000

    Message: The host or user argument to GRANT is too long

  • Error number: 1146; Symbol: ER_NO_SUCH_TABLE; SQLSTATE: 42S02

    Message: Table '%s.%s' doesn't exist

  • Error number: 1147; Symbol: ER_NONEXISTING_TABLE_GRANT; SQLSTATE: 42000

    Message: There is no such grant defined for user '%s' on host '%s' on table '%s'

  • Error number: 1148; Symbol: ER_NOT_ALLOWED_COMMAND; SQLSTATE: 42000

    Message: The used command is not allowed with this MySQL version

  • Error number: 1149; Symbol: ER_SYNTAX_ERROR; SQLSTATE: 42000

    Message: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use

  • Error number: 1152; Symbol: ER_ABORTING_CONNECTION; SQLSTATE: 08S01

    Message: Aborted connection %ld to db: '%s' user: '%s' (%s)

  • Error number: 1153; Symbol: ER_NET_PACKET_TOO_LARGE; SQLSTATE: 08S01

    Message: Got a packet bigger than 'max_allowed_packet' bytes

  • Error number: 1154; Symbol: ER_NET_READ_ERROR_FROM_PIPE; SQLSTATE: 08S01

    Message: Got a read error from the connection pipe

  • Error number: 1155; Symbol: ER_NET_FCNTL_ERROR; SQLSTATE: 08S01

    Message: Got an error from fcntl()

  • Error number: 1156; Symbol: ER_NET_PACKETS_OUT_OF_ORDER; SQLSTATE: 08S01

    Message: Got packets out of order

  • Error number: 1157; Symbol: ER_NET_UNCOMPRESS_ERROR; SQLSTATE: 08S01

    Message: Couldn't uncompress communication packet

  • Error number: 1158; Symbol: ER_NET_READ_ERROR; SQLSTATE: 08S01

    Message: Got an error reading communication packets

  • Error number: 1159; Symbol: ER_NET_READ_INTERRUPTED; SQLSTATE: 08S01

    Message: Got timeout reading communication packets

  • Error number: 1160; Symbol: ER_NET_ERROR_ON_WRITE; SQLSTATE: 08S01

    Message: Got an error writing communication packets

  • Error number: 1161; Symbol: ER_NET_WRITE_INTERRUPTED; SQLSTATE: 08S01

    Message: Got timeout writing communication packets

  • Error number: 1162; Symbol: ER_TOO_LONG_STRING; SQLSTATE: 42000

    Message: Result string is longer than 'max_allowed_packet' bytes

  • Error number: 1163; Symbol: ER_TABLE_CANT_HANDLE_BLOB; SQLSTATE: 42000

    Message: The used table type doesn't support BLOB/TEXT columns

  • Error number: 1164; Symbol: ER_TABLE_CANT_HANDLE_AUTO_INCREMENT; SQLSTATE: 42000

    Message: The used table type doesn't support AUTO_INCREMENT columns

  • Error number: 1166; Symbol: ER_WRONG_COLUMN_NAME; SQLSTATE: 42000

    Message: Incorrect column name '%s'

  • Error number: 1167; Symbol: ER_WRONG_KEY_COLUMN; SQLSTATE: 42000

    Message: The used storage engine can't index column '%s'

  • Error number: 1168; Symbol: ER_WRONG_MRG_TABLE; SQLSTATE: HY000

    Message: Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist

  • Error number: 1169; Symbol: ER_DUP_UNIQUE; SQLSTATE: 23000

    Message: Can't write, because of unique constraint, to table '%s'

  • Error number: 1170; Symbol: ER_BLOB_KEY_WITHOUT_LENGTH; SQLSTATE: 42000

    Message: BLOB/TEXT column '%s' used in key specification without a key length

  • Error number: 1171; Symbol: ER_PRIMARY_CANT_HAVE_NULL; SQLSTATE: 42000

    Message: All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead

  • Error number: 1172; Symbol: ER_TOO_MANY_ROWS; SQLSTATE: 42000

    Message: Result consisted of more than one row

  • Error number: 1173; Symbol: ER_REQUIRES_PRIMARY_KEY; SQLSTATE: 42000

    Message: This table type requires a primary key

  • Error number: 1175; Symbol: ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE; SQLSTATE: HY000

    Message: You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %s

  • Error number: 1176; Symbol: ER_KEY_DOES_NOT_EXITS; SQLSTATE: 42000

    Message: Key '%s' doesn't exist in table '%s'

  • Error number: 1177; Symbol: ER_CHECK_NO_SUCH_TABLE; SQLSTATE: 42000

    Message: Can't open table

  • Error number: 1178; Symbol: ER_CHECK_NOT_IMPLEMENTED; SQLSTATE: 42000

    Message: The storage engine for the table doesn't support %s

  • Error number: 1179; Symbol: ER_CANT_DO_THIS_DURING_AN_TRANSACTION; SQLSTATE: 25000

    Message: You are not allowed to execute this command in a transaction

  • Error number: 1180; Symbol: ER_ERROR_DURING_COMMIT; SQLSTATE: HY000

    Message: Got error %d - '%s' during COMMIT

  • Error number: 1181; Symbol: ER_ERROR_DURING_ROLLBACK; SQLSTATE: HY000

    Message: Got error %d - '%s' during ROLLBACK

  • Error number: 1182; Symbol: ER_ERROR_DURING_FLUSH_LOGS; SQLSTATE: HY000

    Message: Got error %d during FLUSH_LOGS

  • Error number: 1184; Symbol: ER_NEW_ABORTING_CONNECTION; SQLSTATE: 08S01

    Message: Aborted connection %u to db: '%s' user: '%s' host: '%s' (%s)

  • Error number: 1188; Symbol: ER_SOURCE; SQLSTATE: HY000

    Message: Error from source: '%s'

  • Error number: 1189; Symbol: ER_SOURCE_NET_READ; SQLSTATE: 08S01

    Message: Net error reading from source

  • Error number: 1190; Symbol: ER_SOURCE_NET_WRITE; SQLSTATE: 08S01

    Message: Net error writing to source

  • Error number: 1191; Symbol: ER_FT_MATCHING_KEY_NOT_FOUND; SQLSTATE: HY000

    Message: Can't find FULLTEXT index matching the column list

  • Error number: 1192; Symbol: ER_LOCK_OR_ACTIVE_TRANSACTION; SQLSTATE: HY000

    Message: Can't execute the given command because you have active locked tables or an active transaction

  • Error number: 1193; Symbol: ER_UNKNOWN_SYSTEM_VARIABLE; SQLSTATE: HY000

    Message: Unknown system variable '%s'

  • Error number: 1194; Symbol: ER_CRASHED_ON_USAGE; SQLSTATE: HY000

    Message: Table '%s' is marked as crashed and should be repaired

  • Error number: 1195; Symbol: ER_CRASHED_ON_REPAIR; SQLSTATE: HY000

    Message: Table '%s' is marked as crashed and last (automatic?) repair failed

  • Error number: 1196; Symbol: ER_WARNING_NOT_COMPLETE_ROLLBACK; SQLSTATE: HY000

    Message: Some non-transactional changed tables couldn't be rolled back

  • Error number: 1197; Symbol: ER_TRANS_CACHE_FULL; SQLSTATE: HY000

    Message: Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again

  • Error number: 1199; Symbol: ER_REPLICA_NOT_RUNNING; SQLSTATE: HY000

    Message: This operation requires a running replica; configure replica and do START REPLICA

  • Error number: 1200; Symbol: ER_BAD_REPLICA; SQLSTATE: HY000

    Message: The server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TO

  • Error number: 1201; Symbol: ER_CONNECTION_METADATA; SQLSTATE: HY000

    Message: Could not initialize connection metadata structure; more error messages can be found in the MySQL error log

  • Error number: 1202; Symbol: ER_REPLICA_THREAD; SQLSTATE: HY000

    Message: Could not create replica thread; check system resources

  • Error number: 1203; Symbol: ER_TOO_MANY_USER_CONNECTIONS; SQLSTATE: 42000

    Message: User %s already has more than 'max_user_connections' active connections

  • Error number: 1204; Symbol: ER_SET_CONSTANTS_ONLY; SQLSTATE: HY000

    Message: You may only use constant expressions with SET

  • Error number: 1205; Symbol: ER_LOCK_WAIT_TIMEOUT; SQLSTATE: HY000

    Message: Lock wait timeout exceeded; try restarting transaction

    InnoDB reports this error when lock wait timeout expires. The statement that waited too long was rolled back (not the entire transaction). You can increase the value of the innodb_lock_wait_timeout configuration option if SQL statements should wait longer for other transactions to complete, or decrease it if too many long-running transactions are causing locking problems and reducing concurrency on a busy system.

  • Error number: 1206; Symbol: ER_LOCK_TABLE_FULL; SQLSTATE: HY000

    Message: The total number of locks exceeds the lock table size

    InnoDB reports this error when the total number of locks exceeds the amount of memory devoted to managing locks. To avoid this error, increase the value of innodb_buffer_pool_size. Within an individual application, a workaround may be to break a large operation into smaller pieces. For example, if the error occurs for a large INSERT, perform several smaller INSERT operations.

  • Error number: 1207; Symbol: ER_READ_ONLY_TRANSACTION; SQLSTATE: 25000

    Message: Update locks cannot be acquired during a READ UNCOMMITTED transaction

  • Error number: 1210; Symbol: ER_WRONG_ARGUMENTS; SQLSTATE: HY000

    Message: Incorrect arguments to %s

  • Error number: 1211; Symbol: ER_NO_PERMISSION_TO_CREATE_USER; SQLSTATE: 42000

    Message: '%s'@'%s' is not allowed to create new users

  • Error number: 1213; Symbol: ER_LOCK_DEADLOCK; SQLSTATE: 40001

    Message: Deadlock found when trying to get lock; try restarting transaction

    InnoDB reports this error when a transaction encounters a deadlock and is automatically rolled back so that your application can take corrective action. To recover from this error, run all the operations in this transaction again. A deadlock occurs when requests for locks arrive in inconsistent order between transactions. The transaction that was rolled back released all its locks, and the other transaction can now get all the locks it requested. Thus, when you re-run the transaction that was rolled back, it might have to wait for other transactions to complete, but typically the deadlock does not recur. If you encounter frequent deadlocks, make the sequence of locking operations (LOCK TABLES, SELECT ... FOR UPDATE, and so on) consistent between the different transactions or applications that experience the issue. See Deadlocks in InnoDB for details.

  • Error number: 1214; Symbol: ER_TABLE_CANT_HANDLE_FT; SQLSTATE: HY000

    Message: The used table type doesn't support FULLTEXT indexes

  • Error number: 1215; Symbol: ER_CANNOT_ADD_FOREIGN; SQLSTATE: HY000

    Message: Cannot add foreign key constraint

  • Error number: 1216; Symbol: ER_NO_REFERENCED_ROW; SQLSTATE: 23000

    Message: Cannot add or update a child row: a foreign key constraint fails

    InnoDB reports this error when you try to add a row but there is no parent row, and a foreign key constraint fails. Add the parent row first.

  • Error number: 1217; Symbol: ER_ROW_IS_REFERENCED; SQLSTATE: 23000

    Message: Cannot delete or update a parent row: a foreign key constraint fails

    InnoDB reports this error when you try to delete a parent row that has children, and a foreign key constraint fails. Delete the children first.

  • Error number: 1218; Symbol: ER_CONNECT_TO_SOURCE; SQLSTATE: 08S01

    Message: Error connecting to source: %s

  • Error number: 1220; Symbol: ER_ERROR_WHEN_EXECUTING_COMMAND; SQLSTATE: HY000

    Message: Error when executing command %s: %s

  • Error number: 1221; Symbol: ER_WRONG_USAGE; SQLSTATE: HY000

    Message: Incorrect usage of %s and %s

  • Error number: 1222; Symbol: ER_WRONG_NUMBER_OF_COLUMNS_IN_SELECT; SQLSTATE: 21000

    Message: The used SELECT statements have a different number of columns

  • Error number: 1223; Symbol: ER_CANT_UPDATE_WITH_READLOCK; SQLSTATE: HY000

    Message: Can't execute the query because you have a conflicting read lock

  • Error number: 1224; Symbol: ER_MIXING_NOT_ALLOWED; SQLSTATE: HY000

    Message: Mixing of transactional and non-transactional tables is disabled

  • Error number: 1225; Symbol: ER_DUP_ARGUMENT; SQLSTATE: HY000

    Message: Option '%s' used twice in statement

  • Error number: 1226; Symbol: ER_USER_LIMIT_REACHED; SQLSTATE: 42000

    Message: User '%s' has exceeded the '%s' resource (current value: %ld)

  • Error number: 1227; Symbol: ER_SPECIFIC_ACCESS_DENIED_ERROR; SQLSTATE: 42000

    Message: Access denied; you need (at least one of) the %s privilege(s) for this operation

  • Error number: 1228; Symbol: ER_LOCAL_VARIABLE; SQLSTATE: HY000

    Message: Variable '%s' is a SESSION variable and can't be used with SET GLOBAL

  • Error number: 1229; Symbol: ER_GLOBAL_VARIABLE; SQLSTATE: HY000

    Message: Variable '%s' is a GLOBAL variable and should be set with SET GLOBAL

  • Error number: 1230; Symbol: ER_NO_DEFAULT; SQLSTATE: 42000

    Message: Variable '%s' doesn't have a default value

  • Error number: 1231; Symbol: ER_WRONG_VALUE_FOR_VAR; SQLSTATE: 42000

    Message: Variable '%s' can't be set to the value of '%s'

  • Error number: 1232; Symbol: ER_WRONG_TYPE_FOR_VAR; SQLSTATE: 42000

    Message: Incorrect argument type to variable '%s'

  • Error number: 1233; Symbol: ER_VAR_CANT_BE_READ; SQLSTATE: HY000

    Message: Variable '%s' can only be set, not read

  • Error number: 1234; Symbol: ER_CANT_USE_OPTION_HERE; SQLSTATE: 42000

    Message: Incorrect usage/placement of '%s'

  • Error number: 1235; Symbol: ER_NOT_SUPPORTED_YET; SQLSTATE: 42000

    Message: This version of MySQL doesn't yet support '%s'

  • Error number: 1236; Symbol: ER_SOURCE_FATAL_ERROR_READING_BINLOG; SQLSTATE: HY000

    Message: Got fatal error %d from source when reading data from binary log: '%s'

  • Error number: 1237; Symbol: ER_REPLICA_IGNORED_TABLE; SQLSTATE: HY000

    Message: Replica SQL thread ignored the query because of replicate-*-table rules

  • Error number: 1238; Symbol: ER_INCORRECT_GLOBAL_LOCAL_VAR; SQLSTATE: HY000

    Message: Variable '%s' is a %s variable

  • Error number: 1239; Symbol: ER_WRONG_FK_DEF; SQLSTATE: 42000

    Message: Incorrect foreign key definition for '%s': %s

  • Error number: 1240; Symbol: ER_KEY_REF_DO_NOT_MATCH_TABLE_REF; SQLSTATE: HY000

    Message: Key reference and table reference don't match

  • Error number: 1241; Symbol: ER_OPERAND_COLUMNS; SQLSTATE: 21000

    Message: Operand should contain %d column(s)

  • Error number: 1242; Symbol: ER_SUBQUERY_NO_1_ROW; SQLSTATE: 21000

    Message: Subquery returns more than 1 row

  • Error number: 1243; Symbol: ER_UNKNOWN_STMT_HANDLER; SQLSTATE: HY000

    Message: Unknown prepared statement handler (%.*s) given to %s

  • Error number: 1244; Symbol: ER_CORRUPT_HELP_DB; SQLSTATE: HY000

    Message: Help database is corrupt or does not exist

  • Error number: 1246; Symbol: ER_AUTO_CONVERT; SQLSTATE: HY000

    Message: Converting column '%s' from %s to %s

  • Error number: 1247; Symbol: ER_ILLEGAL_REFERENCE; SQLSTATE: 42S22

    Message: Reference '%s' not supported (%s)

  • Error number: 1248; Symbol: ER_DERIVED_MUST_HAVE_ALIAS; SQLSTATE: 42000

    Message: Every derived table must have its own alias

  • Error number: 1249; Symbol: ER_SELECT_REDUCED; SQLSTATE: 01000

    Message: Select %u was reduced during optimization

  • Error number: 1250; Symbol: ER_TABLENAME_NOT_ALLOWED_HERE; SQLSTATE: 42000

    Message: Table '%s' from one of the SELECTs cannot be used in %s

  • Error number: 1251; Symbol: ER_NOT_SUPPORTED_AUTH_MODE; SQLSTATE: 08004

    Message: Client does not support authentication protocol requested by server; consider upgrading MySQL client

  • Error number: 1252; Symbol: ER_SPATIAL_CANT_HAVE_NULL; SQLSTATE: 42000

    Message: All parts of a SPATIAL index must be NOT NULL

  • Error number: 1253; Symbol: ER_COLLATION_CHARSET_MISMATCH; SQLSTATE: 42000

    Message: COLLATION '%s' is not valid for CHARACTER SET '%s'

  • Error number: 1256; Symbol: ER_TOO_BIG_FOR_UNCOMPRESS; SQLSTATE: HY000

    Message: Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)

  • Error number: 1257; Symbol: ER_ZLIB_Z_MEM_ERROR; SQLSTATE: HY000

    Message: ZLIB: Not enough memory

  • Error number: 1258; Symbol: ER_ZLIB_Z_BUF_ERROR; SQLSTATE: HY000

    Message: ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)

  • Error number: 1259; Symbol: ER_ZLIB_Z_DATA_ERROR; SQLSTATE: HY000

    Message: ZLIB: Input data corrupted

  • Error number: 1260; Symbol: ER_CUT_VALUE_GROUP_CONCAT; SQLSTATE: HY000

    Message: Row %u was cut by GROUP_CONCAT()

  • Error number: 1261; Symbol: ER_WARN_TOO_FEW_RECORDS; SQLSTATE: 01000

    Message: Row %ld doesn't contain data for all columns

  • Error number: 1262; Symbol: ER_WARN_TOO_MANY_RECORDS; SQLSTATE: 01000

    Message: Row %ld was truncated; it contained more data than there were input columns

  • Error number: 1263; Symbol: ER_WARN_NULL_TO_NOTNULL; SQLSTATE: 22004

    Message: Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld

  • Error number: 1264; Symbol: ER_WARN_DATA_OUT_OF_RANGE; SQLSTATE: 22003

    Message: Out of range value for column '%s' at row %ld

  • Error number: 1265; Symbol: WARN_DATA_TRUNCATED; SQLSTATE: 01000

    Message: Data truncated for column '%s' at row %ld

  • Error number: 1266; Symbol: ER_WARN_USING_OTHER_HANDLER; SQLSTATE: HY000

    Message: Using storage engine %s for table '%s'

  • Error number: 1267; Symbol: ER_CANT_AGGREGATE_2COLLATIONS; SQLSTATE: HY000

    Message: Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'

  • Error number: 1269; Symbol: ER_REVOKE_GRANTS; SQLSTATE: HY000

    Message: Can't revoke all privileges for one or more of the requested users

  • Error number: 1270; Symbol: ER_CANT_AGGREGATE_3COLLATIONS; SQLSTATE: HY000

    Message: Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'

  • Error number: 1271; Symbol: ER_CANT_AGGREGATE_NCOLLATIONS; SQLSTATE: HY000

    Message: Illegal mix of collations for operation '%s'

  • Error number: 1272; Symbol: ER_VARIABLE_IS_NOT_STRUCT; SQLSTATE: HY000

    Message: Variable '%s' is not a variable component (can't be used as XXXX.variable_name)

  • Error number: 1273; Symbol: ER_UNKNOWN_COLLATION; SQLSTATE: HY000

    Message: Unknown collation: '%s'

  • Error number: 1274; Symbol: ER_REPLICA_IGNORED_SSL_PARAMS; SQLSTATE: HY000

    Message: SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is started

  • Error number: 1276; Symbol: ER_WARN_FIELD_RESOLVED; SQLSTATE: HY000

    Message: Field or reference '%s%s%s%s%s' of SELECT #%d was resolved in SELECT #%d

  • Error number: 1277; Symbol: ER_BAD_REPLICA_UNTIL_COND; SQLSTATE: HY000

    Message: Incorrect parameter or combination of parameters for START REPLICA UNTIL

  • Error number: 1278; Symbol: ER_MISSING_SKIP_REPLICA; SQLSTATE: HY000

    Message: It is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restart

  • Error number: 1279; Symbol: ER_UNTIL_COND_IGNORED; SQLSTATE: HY000

    Message: SQL thread is not to be started so UNTIL options are ignored

  • Error number: 1280; Symbol: ER_WRONG_NAME_FOR_INDEX; SQLSTATE: 42000

    Message: Incorrect index name '%s'

  • Error number: 1281; Symbol: ER_WRONG_NAME_FOR_CATALOG; SQLSTATE: 42000

    Message: Incorrect catalog name '%s'

  • Error number: 1283; Symbol: ER_BAD_FT_COLUMN; SQLSTATE: HY000

    Message: Column '%s' cannot be part of FULLTEXT index

  • Error number: 1284; Symbol: ER_UNKNOWN_KEY_CACHE; SQLSTATE: HY000

    Message: Unknown key cache '%s'

  • Error number: 1285; Symbol: ER_WARN_HOSTNAME_WONT_WORK; SQLSTATE: HY000

    Message: MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work

  • Error number: 1286; Symbol: ER_UNKNOWN_STORAGE_ENGINE; SQLSTATE: 42000

    Message: Unknown storage engine '%s'

  • Error number: 1287; Symbol: ER_WARN_DEPRECATED_SYNTAX; SQLSTATE: HY000

    Message: '%s' is deprecated and will be removed in a future release. Please use %s instead

  • Error number: 1288; Symbol: ER_NON_UPDATABLE_TABLE; SQLSTATE: HY000

    Message: The target table %s of the %s is not updatable

  • Error number: 1289; Symbol: ER_FEATURE_DISABLED; SQLSTATE: HY000

    Message: The '%s' feature is disabled; you need MySQL built with '%s' to have it working

  • Error number: 1290; Symbol: ER_OPTION_PREVENTS_STATEMENT; SQLSTATE: HY000

    Message: The MySQL server is running with the %s option so it cannot execute this statement

  • Error number: 1291; Symbol: ER_DUPLICATED_VALUE_IN_TYPE; SQLSTATE: HY000

    Message: Column '%s' has duplicated value '%s' in %s

  • Error number: 1292; Symbol: ER_TRUNCATED_WRONG_VALUE; SQLSTATE: 22007

    Message: Truncated incorrect %s value: '%s'

  • Error number: 1294; Symbol: ER_INVALID_ON_UPDATE; SQLSTATE: HY000

    Message: Invalid ON UPDATE clause for '%s' column

  • Error number: 1295; Symbol: ER_UNSUPPORTED_PS; SQLSTATE: HY000

    Message: This command is not supported in the prepared statement protocol yet

  • Error number: 1296; Symbol: ER_GET_ERRMSG; SQLSTATE: HY000

    Message: Got error %d '%s' from %s

  • Error number: 1297; Symbol: ER_GET_TEMPORARY_ERRMSG; SQLSTATE: HY000

    Message: Got temporary error %d '%s' from %s

  • Error number: 1298; Symbol: ER_UNKNOWN_TIME_ZONE; SQLSTATE: HY000

    Message: Unknown or incorrect time zone: '%s'

  • Error number: 1299; Symbol: ER_WARN_INVALID_TIMESTAMP; SQLSTATE: HY000

    Message: Invalid TIMESTAMP value in column '%s' at row %ld

  • Error number: 1300; Symbol: ER_INVALID_CHARACTER_STRING; SQLSTATE: HY000

    Message: Invalid %s character string: '%s'

  • Error number: 1301; Symbol: ER_WARN_ALLOWED_PACKET_OVERFLOWED; SQLSTATE: HY000

    Message: Result of %s() was larger than max_allowed_packet (%ld) - truncated

  • Error number: 1302; Symbol: ER_CONFLICTING_DECLARATIONS; SQLSTATE: HY000

    Message: Conflicting declarations: '%s%s' and '%s%s'

  • Error number: 1303; Symbol: ER_SP_NO_RECURSIVE_CREATE; SQLSTATE: 2F003

    Message: Can't create a %s from within another stored routine

  • Error number: 1304; Symbol: ER_SP_ALREADY_EXISTS; SQLSTATE: 42000

    Message: %s %s already exists

  • Error number: 1305; Symbol: ER_SP_DOES_NOT_EXIST; SQLSTATE: 42000

    Message: %s %s does not exist

  • Error number: 1306; Symbol: ER_SP_DROP_FAILED; SQLSTATE: HY000

    Message: Failed to DROP %s %s

  • Error number: 1307; Symbol: ER_SP_STORE_FAILED; SQLSTATE: HY000

    Message: Failed to CREATE %s %s

  • Error number: 1308; Symbol: ER_SP_LILABEL_MISMATCH; SQLSTATE: 42000

    Message: %s with no matching label: %s

  • Error number: 1309; Symbol: ER_SP_LABEL_REDEFINE; SQLSTATE: 42000

    Message: Redefining label %s

  • Error number: 1310; Symbol: ER_SP_LABEL_MISMATCH; SQLSTATE: 42000

    Message: End-label %s without match

  • Error number: 1311; Symbol: ER_SP_UNINIT_VAR; SQLSTATE: 01000

    Message: Referring to uninitialized variable %s

  • Error number: 1312; Symbol: ER_SP_BADSELECT; SQLSTATE: 0A000

    Message: PROCEDURE %s can't return a result set in the given context

  • Error number: 1313; Symbol: ER_SP_BADRETURN; SQLSTATE: 42000

    Message: RETURN is only allowed in a FUNCTION

  • Error number: 1314; Symbol: ER_SP_BADSTATEMENT; SQLSTATE: 0A000

    Message: %s is not allowed in stored procedures

  • Error number: 1315; Symbol: ER_UPDATE_LOG_DEPRECATED_IGNORED; SQLSTATE: 42000

    Message: The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.

  • Error number: 1316; Symbol: ER_UPDATE_LOG_DEPRECATED_TRANSLATED; SQLSTATE: 42000

    Message: The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.

  • Error number: 1317; Symbol: ER_QUERY_INTERRUPTED; SQLSTATE: 70100

    Message: Query execution was interrupted

  • Error number: 1318; Symbol: ER_SP_WRONG_NO_OF_ARGS; SQLSTATE: 42000

    Message: Incorrect number of arguments for %s %s; expected %u, got %u

  • Error number: 1319; Symbol: ER_SP_COND_MISMATCH; SQLSTATE: 42000

    Message: Undefined CONDITION: %s

  • Error number: 1320; Symbol: ER_SP_NORETURN; SQLSTATE: 42000

    Message: No RETURN found in FUNCTION %s

  • Error number: 1321; Symbol: ER_SP_NORETURNEND; SQLSTATE: 2F005

    Message: FUNCTION %s ended without RETURN

  • Error number: 1322; Symbol: ER_SP_BAD_CURSOR_QUERY; SQLSTATE: 42000

    Message: Cursor statement must be a SELECT

  • Error number: 1323; Symbol: ER_SP_BAD_CURSOR_SELECT; SQLSTATE: 42000

    Message: Cursor SELECT must not have INTO

  • Error number: 1324; Symbol: ER_SP_CURSOR_MISMATCH; SQLSTATE: 42000

    Message: Undefined CURSOR: %s

  • Error number: 1325; Symbol: ER_SP_CURSOR_ALREADY_OPEN; SQLSTATE: 24000

    Message: Cursor is already open

  • Error number: 1326; Symbol: ER_SP_CURSOR_NOT_OPEN; SQLSTATE: 24000

    Message: Cursor is not open

  • Error number: 1327; Symbol: ER_SP_UNDECLARED_VAR; SQLSTATE: 42000

    Message: Undeclared variable: %s

  • Error number: 1328; Symbol: ER_SP_WRONG_NO_OF_FETCH_ARGS; SQLSTATE: HY000

    Message: Incorrect number of FETCH variables

  • Error number: 1329; Symbol: ER_SP_FETCH_NO_DATA; SQLSTATE: 02000

    Message: No data - zero rows fetched, selected, or processed

  • Error number: 1330; Symbol: ER_SP_DUP_PARAM; SQLSTATE: 42000

    Message: Duplicate parameter: %s

  • Error number: 1331; Symbol: ER_SP_DUP_VAR; SQLSTATE: 42000

    Message: Duplicate variable: %s

  • Error number: 1332; Symbol: ER_SP_DUP_COND; SQLSTATE: 42000

    Message: Duplicate condition: %s

  • Error number: 1333; Symbol: ER_SP_DUP_CURS; SQLSTATE: 42000

    Message: Duplicate cursor: %s

  • Error number: 1334; Symbol: ER_SP_CANT_ALTER; SQLSTATE: HY000

    Message: Failed to ALTER %s %s

  • Error number: 1335; Symbol: ER_SP_SUBSELECT_NYI; SQLSTATE: 0A000

    Message: Subquery value not supported

  • Error number: 1336; Symbol: ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG; SQLSTATE: 0A000

    Message: %s is not allowed in stored function or trigger

  • Error number: 1337; Symbol: ER_SP_VARCOND_AFTER_CURSHNDLR; SQLSTATE: 42000

    Message: Variable or condition declaration after cursor or handler declaration

  • Error number: 1338; Symbol: ER_SP_CURSOR_AFTER_HANDLER; SQLSTATE: 42000

    Message: Cursor declaration after handler declaration

  • Error number: 1339; Symbol: ER_SP_CASE_NOT_FOUND; SQLSTATE: 20000

    Message: Case not found for CASE statement

  • Error number: 1340; Symbol: ER_FPARSER_TOO_BIG_FILE; SQLSTATE: HY000

    Message: Configuration file '%s' is too big

  • Error number: 1341; Symbol: ER_FPARSER_BAD_HEADER; SQLSTATE: HY000

    Message: Malformed file type header in file '%s'

  • Error number: 1342; Symbol: ER_FPARSER_EOF_IN_COMMENT; SQLSTATE: HY000

    Message: Unexpected end of file while parsing comment '%s'

  • Error number: 1343; Symbol: ER_FPARSER_ERROR_IN_PARAMETER; SQLSTATE: HY000

    Message: Error while parsing parameter '%s' (line: '%s')

  • Error number: 1344; Symbol: ER_FPARSER_EOF_IN_UNKNOWN_PARAMETER; SQLSTATE: HY000

    Message: Unexpected end of file while skipping unknown parameter '%s'

  • Error number: 1345; Symbol: ER_VIEW_NO_EXPLAIN; SQLSTATE: HY000

    Message: EXPLAIN/SHOW can not be issued; lacking privileges for underlying table

  • Error number: 1347; Symbol: ER_WRONG_OBJECT; SQLSTATE: HY000

    Message: '%s.%s' is not %s

    The named object is incorrect for the type of operation attempted on it. It must be an object of the named type. Example: HANDLER OPEN requires a base table, not a view. It fails if attempted on an INFORMATION_SCHEMA table that is implemented as a view on data dictionary tables.

  • Error number: 1348; Symbol: ER_NONUPDATEABLE_COLUMN; SQLSTATE: HY000

    Message: Column '%s' is not updatable

  • Error number: 1350; Symbol: ER_VIEW_SELECT_CLAUSE; SQLSTATE: HY000

    Message: View's SELECT contains a '%s' clause

  • Error number: 1351; Symbol: ER_VIEW_SELECT_VARIABLE; SQLSTATE: HY000

    Message: View's SELECT contains a variable or parameter

  • Error number: 1352; Symbol: ER_VIEW_SELECT_TMPTABLE; SQLSTATE: HY000

    Message: View's SELECT refers to a temporary table '%s'

  • Error number: 1353; Symbol: ER_VIEW_WRONG_LIST; SQLSTATE: HY000

    Message: In definition of view, derived table or common table expression, SELECT list and column names list have different column counts

  • Error number: 1354; Symbol: ER_WARN_VIEW_MERGE; SQLSTATE: HY000

    Message: View merge algorithm can't be used here for now (assumed undefined algorithm)

  • Error number: 1355; Symbol: ER_WARN_VIEW_WITHOUT_KEY; SQLSTATE: HY000

    Message: View being updated does not have complete key of underlying table in it

  • Error number: 1356; Symbol: ER_VIEW_INVALID; SQLSTATE: HY000

    Message: View '%s.%s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them

  • Error number: 1357; Symbol: ER_SP_NO_DROP_SP; SQLSTATE: HY000

    Message: Can't drop or alter a %s from within another stored routine

  • Error number: 1359; Symbol: ER_TRG_ALREADY_EXISTS; SQLSTATE: HY000

    Message: Trigger already exists

  • Error number: 1360; Symbol: ER_TRG_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Trigger does not exist

  • Error number: 1361; Symbol: ER_TRG_ON_VIEW_OR_TEMP_TABLE; SQLSTATE: HY000

    Message: Trigger's '%s' is view or temporary table

  • Error number: 1362; Symbol: ER_TRG_CANT_CHANGE_ROW; SQLSTATE: HY000

    Message: Updating of %s row is not allowed in %strigger

  • Error number: 1363; Symbol: ER_TRG_NO_SUCH_ROW_IN_TRG; SQLSTATE: HY000

    Message: There is no %s row in %s trigger

  • Error number: 1364; Symbol: ER_NO_DEFAULT_FOR_FIELD; SQLSTATE: HY000

    Message: Field '%s' doesn't have a default value

  • Error number: 1365; Symbol: ER_DIVISION_BY_ZERO; SQLSTATE: 22012

    Message: Division by 0

  • Error number: 1366; Symbol: ER_TRUNCATED_WRONG_VALUE_FOR_FIELD; SQLSTATE: HY000

    Message: Incorrect %s value: '%s' for column '%s' at row %ld

  • Error number: 1367; Symbol: ER_ILLEGAL_VALUE_FOR_TYPE; SQLSTATE: 22007

    Message: Illegal %s '%s' value found during parsing

  • Error number: 1368; Symbol: ER_VIEW_NONUPD_CHECK; SQLSTATE: HY000

    Message: CHECK OPTION on non-updatable view '%s.%s'

  • Error number: 1369; Symbol: ER_VIEW_CHECK_FAILED; SQLSTATE: HY000

    Message: CHECK OPTION failed '%s.%s'

  • Error number: 1370; Symbol: ER_PROCACCESS_DENIED_ERROR; SQLSTATE: 42000

    Message: %s command denied to user '%s'@'%s' for routine '%s'

  • Error number: 1371; Symbol: ER_RELAY_LOG_FAIL; SQLSTATE: HY000

    Message: Failed purging old relay logs: %s

  • Error number: 1373; Symbol: ER_UNKNOWN_TARGET_BINLOG; SQLSTATE: HY000

    Message: Target log not found in binlog index

  • Error number: 1374; Symbol: ER_IO_ERR_LOG_INDEX_READ; SQLSTATE: HY000

    Message: I/O error reading log index file

  • Error number: 1375; Symbol: ER_BINLOG_PURGE_PROHIBITED; SQLSTATE: HY000

    Message: Server configuration does not permit binlog purge

  • Error number: 1376; Symbol: ER_FSEEK_FAIL; SQLSTATE: HY000

    Message: Failed on fseek()

  • Error number: 1377; Symbol: ER_BINLOG_PURGE_FATAL_ERR; SQLSTATE: HY000

    Message: Fatal error during log purge

  • Error number: 1378; Symbol: ER_LOG_IN_USE; SQLSTATE: HY000

    Message: A purgeable log is in use, will not purge

  • Error number: 1379; Symbol: ER_LOG_PURGE_UNKNOWN_ERR; SQLSTATE: HY000

    Message: Unknown error during log purge

  • Error number: 1380; Symbol: ER_RELAY_LOG_INIT; SQLSTATE: HY000

    Message: Failed initializing relay log position: %s

  • Error number: 1381; Symbol: ER_NO_BINARY_LOGGING; SQLSTATE: HY000

    Message: You are not using binary logging

  • Error number: 1382; Symbol: ER_RESERVED_SYNTAX; SQLSTATE: HY000

    Message: The '%s' syntax is reserved for purposes internal to the MySQL server

  • Error number: 1390; Symbol: ER_PS_MANY_PARAM; SQLSTATE: HY000

    Message: Prepared statement contains too many placeholders

  • Error number: 1391; Symbol: ER_KEY_PART_0; SQLSTATE: HY000

    Message: Key part '%s' length cannot be 0

  • Error number: 1392; Symbol: ER_VIEW_CHECKSUM; SQLSTATE: HY000

    Message: View text checksum failed

  • Error number: 1393; Symbol: ER_VIEW_MULTIUPDATE; SQLSTATE: HY000

    Message: Can not modify more than one base table through a join view '%s.%s'

  • Error number: 1394; Symbol: ER_VIEW_NO_INSERT_FIELD_LIST; SQLSTATE: HY000

    Message: Can not insert into join view '%s.%s' without fields list

  • Error number: 1395; Symbol: ER_VIEW_DELETE_MERGE_VIEW; SQLSTATE: HY000

    Message: Can not delete from join view '%s.%s'

  • Error number: 1396; Symbol: ER_CANNOT_USER; SQLSTATE: HY000

    Message: Operation %s failed for %s

  • Error number: 1397; Symbol: ER_XAER_NOTA; SQLSTATE: XAE04

    Message: XAER_NOTA: Unknown XID

  • Error number: 1398; Symbol: ER_XAER_INVAL; SQLSTATE: XAE05

    Message: XAER_INVAL: Invalid arguments (or unsupported command)

  • Error number: 1399; Symbol: ER_XAER_RMFAIL; SQLSTATE: XAE07

    Message: XAER_RMFAIL: The command cannot be executed when global transaction is in the %s state

  • Error number: 1400; Symbol: ER_XAER_OUTSIDE; SQLSTATE: XAE09

    Message: XAER_OUTSIDE: Some work is done outside global transaction

  • Error number: 1401; Symbol: ER_XAER_RMERR; SQLSTATE: XAE03

    Message: XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency

  • Error number: 1402; Symbol: ER_XA_RBROLLBACK; SQLSTATE: XA100

    Message: XA_RBROLLBACK: Transaction branch was rolled back

  • Error number: 1403; Symbol: ER_NONEXISTING_PROC_GRANT; SQLSTATE: 42000

    Message: There is no such grant defined for user '%s' on host '%s' on routine '%s'

  • Error number: 1404; Symbol: ER_PROC_AUTO_GRANT_FAIL; SQLSTATE: HY000

    Message: Failed to grant EXECUTE and ALTER ROUTINE privileges

  • Error number: 1405; Symbol: ER_PROC_AUTO_REVOKE_FAIL; SQLSTATE: HY000

    Message: Failed to revoke all privileges to dropped routine

  • Error number: 1406; Symbol: ER_DATA_TOO_LONG; SQLSTATE: 22001

    Message: Data too long for column '%s' at row %ld

  • Error number: 1407; Symbol: ER_SP_BAD_SQLSTATE; SQLSTATE: 42000

    Message: Bad SQLSTATE: '%s'

  • Error number: 1408; Symbol: ER_STARTUP; SQLSTATE: HY000

    Message: %s: ready for connections. Version: '%s' socket: '%s' port: %d %s

  • Error number: 1409; Symbol: ER_LOAD_FROM_FIXED_SIZE_ROWS_TO_VAR; SQLSTATE: HY000

    Message: Can't load value from file with fixed size rows to variable

  • Error number: 1410; Symbol: ER_CANT_CREATE_USER_WITH_GRANT; SQLSTATE: 42000

    Message: You are not allowed to create a user with GRANT

  • Error number: 1411; Symbol: ER_WRONG_VALUE_FOR_TYPE; SQLSTATE: HY000

    Message: Incorrect %s value: '%s' for function %s

  • Error number: 1412; Symbol: ER_TABLE_DEF_CHANGED; SQLSTATE: HY000

    Message: Table definition has changed, please retry transaction

  • Error number: 1413; Symbol: ER_SP_DUP_HANDLER; SQLSTATE: 42000

    Message: Duplicate handler declared in the same block

  • Error number: 1414; Symbol: ER_SP_NOT_VAR_ARG; SQLSTATE: 42000

    Message: OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger

  • Error number: 1415; Symbol: ER_SP_NO_RETSET; SQLSTATE: 0A000

    Message: Not allowed to return a result set from a %s

  • Error number: 1416; Symbol: ER_CANT_CREATE_GEOMETRY_OBJECT; SQLSTATE: 22003

    Message: Cannot get geometry object from data you send to the GEOMETRY field

  • Error number: 1418; Symbol: ER_BINLOG_UNSAFE_ROUTINE; SQLSTATE: HY000

    Message: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)

  • Error number: 1419; Symbol: ER_BINLOG_CREATE_ROUTINE_NEED_SUPER; SQLSTATE: HY000

    Message: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)

  • Error number: 1421; Symbol: ER_STMT_HAS_NO_OPEN_CURSOR; SQLSTATE: HY000

    Message: The statement (%lu) has no open cursor.

  • Error number: 1422; Symbol: ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG; SQLSTATE: HY000

    Message: Explicit or implicit commit is not allowed in stored function or trigger.

  • Error number: 1423; Symbol: ER_NO_DEFAULT_FOR_VIEW_FIELD; SQLSTATE: HY000

    Message: Field of view '%s.%s' underlying table doesn't have a default value

  • Error number: 1424; Symbol: ER_SP_NO_RECURSION; SQLSTATE: HY000

    Message: Recursive stored functions and triggers are not allowed.

  • Error number: 1425; Symbol: ER_TOO_BIG_SCALE; SQLSTATE: 42000

    Message: Too big scale %d specified for column '%s'. Maximum is %lu.

  • Error number: 1426; Symbol: ER_TOO_BIG_PRECISION; SQLSTATE: 42000

    Message: Too-big precision %d specified for '%s'. Maximum is %lu.

  • Error number: 1427; Symbol: ER_M_BIGGER_THAN_D; SQLSTATE: 42000

    Message: For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%s').

  • Error number: 1428; Symbol: ER_WRONG_LOCK_OF_SYSTEM_TABLE; SQLSTATE: HY000

    Message: You can't combine write-locking of system tables with other tables or lock types

  • Error number: 1429; Symbol: ER_CONNECT_TO_FOREIGN_DATA_SOURCE; SQLSTATE: HY000

    Message: Unable to connect to foreign data source: %s

  • Error number: 1430; Symbol: ER_QUERY_ON_FOREIGN_DATA_SOURCE; SQLSTATE: HY000

    Message: There was a problem processing the query on the foreign data source. Data source error: %s

  • Error number: 1431; Symbol: ER_FOREIGN_DATA_SOURCE_DOESNT_EXIST; SQLSTATE: HY000

    Message: The foreign data source you are trying to reference does not exist. Data source error: %s

  • Error number: 1432; Symbol: ER_FOREIGN_DATA_STRING_INVALID_CANT_CREATE; SQLSTATE: HY000

    Message: Can't create federated table. The data source connection string '%s' is not in the correct format

  • Error number: 1433; Symbol: ER_FOREIGN_DATA_STRING_INVALID; SQLSTATE: HY000

    Message: The data source connection string '%s' is not in the correct format

  • Error number: 1435; Symbol: ER_TRG_IN_WRONG_SCHEMA; SQLSTATE: HY000

    Message: Trigger in wrong schema

  • Error number: 1436; Symbol: ER_STACK_OVERRUN_NEED_MORE; SQLSTATE: HY000

    Message: Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack.

  • Error number: 1437; Symbol: ER_TOO_LONG_BODY; SQLSTATE: 42000

    Message: Routine body for '%s' is too long

  • Error number: 1438; Symbol: ER_WARN_CANT_DROP_DEFAULT_KEYCACHE; SQLSTATE: HY000

    Message: Cannot drop default keycache

  • Error number: 1439; Symbol: ER_TOO_BIG_DISPLAYWIDTH; SQLSTATE: 42000

    Message: Display width out of range for column '%s' (max = %lu)

  • Error number: 1440; Symbol: ER_XAER_DUPID; SQLSTATE: XAE08

    Message: XAER_DUPID: The XID already exists

  • Error number: 1441; Symbol: ER_DATETIME_FUNCTION_OVERFLOW; SQLSTATE: 22008

    Message: Datetime function: %s field overflow

  • Error number: 1442; Symbol: ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG; SQLSTATE: HY000

    Message: Can't update table '%s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.

  • Error number: 1443; Symbol: ER_VIEW_PREVENT_UPDATE; SQLSTATE: HY000

    Message: The definition of table '%s' prevents operation %s on table '%s'.

  • Error number: 1444; Symbol: ER_PS_NO_RECURSION; SQLSTATE: HY000

    Message: The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive manner

  • Error number: 1445; Symbol: ER_SP_CANT_SET_AUTOCOMMIT; SQLSTATE: HY000

    Message: Not allowed to set autocommit from a stored function or trigger

  • Error number: 1447; Symbol: ER_VIEW_FRM_NO_USER; SQLSTATE: HY000

    Message: View '%s'.'%s' has no definer information (old table format). Current user is used as definer. Please recreate the view!

  • Error number: 1448; Symbol: ER_VIEW_OTHER_USER; SQLSTATE: HY000

    Message: You need the SUPER privilege for creation view with '%s'@'%s' definer

  • Error number: 1449; Symbol: ER_NO_SUCH_USER; SQLSTATE: HY000

    Message: The user specified as a definer ('%s'@'%s') does not exist

  • Error number: 1450; Symbol: ER_FORBID_SCHEMA_CHANGE; SQLSTATE: HY000

    Message: Changing schema from '%s' to '%s' is not allowed.

  • Error number: 1451; Symbol: ER_ROW_IS_REFERENCED_2; SQLSTATE: 23000

    Message: Cannot delete or update a parent row: a foreign key constraint fails%s

    InnoDB reports this error when you try to delete a parent row that has children, and a foreign key constraint fails. Delete the children first.

  • Error number: 1452; Symbol: ER_NO_REFERENCED_ROW_2; SQLSTATE: 23000

    Message: Cannot add or update a child row: a foreign key constraint fails%s

    InnoDB reports this error when you try to add a row but there is no parent row, and a foreign key constraint fails. Add the parent row first.

  • Error number: 1453; Symbol: ER_SP_BAD_VAR_SHADOW; SQLSTATE: 42000

    Message: Variable '%s' must be quoted with `...`, or renamed

  • Error number: 1454; Symbol: ER_TRG_NO_DEFINER; SQLSTATE: HY000

    Message: No definer attribute for trigger '%s'.'%s'. It's disallowed to create trigger without definer.

  • Error number: 1455; Symbol: ER_OLD_FILE_FORMAT; SQLSTATE: HY000

    Message: '%s' has an old format, you should re-create the '%s' object(s)

  • Error number: 1456; Symbol: ER_SP_RECURSION_LIMIT; SQLSTATE: HY000

    Message: Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %s

  • Error number: 1458; Symbol: ER_SP_WRONG_NAME; SQLSTATE: 42000

    Message: Incorrect routine name '%s'

  • Error number: 1459; Symbol: ER_TABLE_NEEDS_UPGRADE; SQLSTATE: HY000

    Message: Table upgrade required. Please do "REPAIR TABLE `%s`" or dump/reload to fix it!

  • Error number: 1460; Symbol: ER_SP_NO_AGGREGATE; SQLSTATE: 42000

    Message: AGGREGATE is not supported for stored functions

  • Error number: 1461; Symbol: ER_MAX_PREPARED_STMT_COUNT_REACHED; SQLSTATE: 42000

    Message: Can't create more than max_prepared_stmt_count statements (current value: %lu)

  • Error number: 1462; Symbol: ER_VIEW_RECURSIVE; SQLSTATE: HY000

    Message: `%s`.`%s` contains view recursion

  • Error number: 1463; Symbol: ER_NON_GROUPING_FIELD_USED; SQLSTATE: 42000

    Message: Non-grouping field '%s' is used in %s clause

  • Error number: 1464; Symbol: ER_TABLE_CANT_HANDLE_SPKEYS; SQLSTATE: HY000

    Message: The used table type doesn't support SPATIAL indexes

  • Error number: 1465; Symbol: ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA; SQLSTATE: HY000

    Message: Triggers can not be created on system tables

  • Error number: 1466; Symbol: ER_REMOVED_SPACES; SQLSTATE: HY000

    Message: Leading spaces are removed from name '%s'

  • Error number: 1467; Symbol: ER_AUTOINC_READ_FAILED; SQLSTATE: HY000

    Message: Failed to read auto-increment value from storage engine

  • Error number: 1468; Symbol: ER_USERNAME; SQLSTATE: HY000

    Message: user name

  • Error number: 1469; Symbol: ER_HOSTNAME; SQLSTATE: HY000

    Message: host name

  • Error number: 1470; Symbol: ER_WRONG_STRING_LENGTH; SQLSTATE: HY000

    Message: String '%s' is too long for %s (should be no longer than %d)

  • Error number: 1471; Symbol: ER_NON_INSERTABLE_TABLE; SQLSTATE: HY000

    Message: The target table %s of the %s is not insertable-into

  • Error number: 1472; Symbol: ER_ADMIN_WRONG_MRG_TABLE; SQLSTATE: HY000

    Message: Table '%s' is differently defined or of non-MyISAM type or doesn't exist

  • Error number: 1473; Symbol: ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT; SQLSTATE: HY000

    Message: Too high level of nesting for select

  • Error number: 1474; Symbol: ER_NAME_BECOMES_EMPTY; SQLSTATE: HY000

    Message: Name '%s' has become ''

  • Error number: 1475; Symbol: ER_AMBIGUOUS_FIELD_TERM; SQLSTATE: HY000

    Message: First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY

  • Error number: 1476; Symbol: ER_FOREIGN_SERVER_EXISTS; SQLSTATE: HY000

    Message: The foreign server, %s, you are trying to create already exists.

  • Error number: 1477; Symbol: ER_FOREIGN_SERVER_DOESNT_EXIST; SQLSTATE: HY000

    Message: The foreign server name you are trying to reference does not exist. Data source error: %s

  • Error number: 1478; Symbol: ER_ILLEGAL_HA_CREATE_OPTION; SQLSTATE: HY000

    Message: Table storage engine '%s' does not support the create option '%s'

  • Error number: 1479; Symbol: ER_PARTITION_REQUIRES_VALUES_ERROR; SQLSTATE: HY000

    Message: Syntax error: %s PARTITIONING requires definition of VALUES %s for each partition

  • Error number: 1480; Symbol: ER_PARTITION_WRONG_VALUES_ERROR; SQLSTATE: HY000

    Message: Only %s PARTITIONING can use VALUES %s in partition definition

  • Error number: 1481; Symbol: ER_PARTITION_MAXVALUE_ERROR; SQLSTATE: HY000

    Message: MAXVALUE can only be used in last partition definition

  • Error number: 1484; Symbol: ER_PARTITION_WRONG_NO_PART_ERROR; SQLSTATE: HY000

    Message: Wrong number of partitions defined, mismatch with previous setting

  • Error number: 1485; Symbol: ER_PARTITION_WRONG_NO_SUBPART_ERROR; SQLSTATE: HY000

    Message: Wrong number of subpartitions defined, mismatch with previous setting

  • Error number: 1486; Symbol: ER_WRONG_EXPR_IN_PARTITION_FUNC_ERROR; SQLSTATE: HY000

    Message: Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed

  • Error number: 1488; Symbol: ER_FIELD_NOT_FOUND_PART_ERROR; SQLSTATE: HY000

    Message: Field in list of fields for partition function not found in table

  • Error number: 1490; Symbol: ER_INCONSISTENT_PARTITION_INFO_ERROR; SQLSTATE: HY000

    Message: The partition info in the frm file is not consistent with what can be written into the frm file

  • Error number: 1491; Symbol: ER_PARTITION_FUNC_NOT_ALLOWED_ERROR; SQLSTATE: HY000

    Message: The %s function returns the wrong type

  • Error number: 1492; Symbol: ER_PARTITIONS_MUST_BE_DEFINED_ERROR; SQLSTATE: HY000

    Message: For %s partitions each partition must be defined

  • Error number: 1493; Symbol: ER_RANGE_NOT_INCREASING_ERROR; SQLSTATE: HY000

    Message: VALUES LESS THAN value must be strictly increasing for each partition

  • Error number: 1494; Symbol: ER_INCONSISTENT_TYPE_OF_FUNCTIONS_ERROR; SQLSTATE: HY000

    Message: VALUES value must be of same type as partition function

  • Error number: 1495; Symbol: ER_MULTIPLE_DEF_CONST_IN_LIST_PART_ERROR; SQLSTATE: HY000

    Message: Multiple definition of same constant in list partitioning

  • Error number: 1496; Symbol: ER_PARTITION_ENTRY_ERROR; SQLSTATE: HY000

    Message: Partitioning can not be used stand-alone in query

  • Error number: 1497; Symbol: ER_MIX_HANDLER_ERROR; SQLSTATE: HY000

    Message: The mix of handlers in the partitions is not allowed in this version of MySQL

  • Error number: 1498; Symbol: ER_PARTITION_NOT_DEFINED_ERROR; SQLSTATE: HY000

    Message: For the partitioned engine it is necessary to define all %s

  • Error number: 1499; Symbol: ER_TOO_MANY_PARTITIONS_ERROR; SQLSTATE: HY000

    Message: Too many partitions (including subpartitions) were defined

  • Error number: 1500; Symbol: ER_SUBPARTITION_ERROR; SQLSTATE: HY000

    Message: It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning

  • Error number: 1501; Symbol: ER_CANT_CREATE_HANDLER_FILE; SQLSTATE: HY000

    Message: Failed to create specific handler file

  • Error number: 1502; Symbol: ER_BLOB_FIELD_IN_PART_FUNC_ERROR; SQLSTATE: HY000

    Message: A BLOB field is not allowed in partition function

  • Error number: 1503; Symbol: ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF; SQLSTATE: HY000

    Message: A %s must include all columns in the table's partitioning function (prefixed columns are not considered).

  • Error number: 1504; Symbol: ER_NO_PARTS_ERROR; SQLSTATE: HY000

    Message: Number of %s = 0 is not an allowed value

  • Error number: 1505; Symbol: ER_PARTITION_MGMT_ON_NONPARTITIONED; SQLSTATE: HY000

    Message: Partition management on a not partitioned table is not possible

  • Error number: 1506; Symbol: ER_FOREIGN_KEY_ON_PARTITIONED; SQLSTATE: HY000

    Message: Foreign keys are not yet supported in conjunction with partitioning

  • Error number: 1507; Symbol: ER_DROP_PARTITION_NON_EXISTENT; SQLSTATE: HY000

    Message: Error in list of partitions to %s

  • Error number: 1508; Symbol: ER_DROP_LAST_PARTITION; SQLSTATE: HY000

    Message: Cannot remove all partitions, use DROP TABLE instead

  • Error number: 1509; Symbol: ER_COALESCE_ONLY_ON_HASH_PARTITION; SQLSTATE: HY000

    Message: COALESCE PARTITION can only be used on HASH/KEY partitions

  • Error number: 1510; Symbol: ER_REORG_HASH_ONLY_ON_SAME_NO; SQLSTATE: HY000

    Message: REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers

  • Error number: 1511; Symbol: ER_REORG_NO_PARAM_ERROR; SQLSTATE: HY000

    Message: REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs

  • Error number: 1512; Symbol: ER_ONLY_ON_RANGE_LIST_PARTITION; SQLSTATE: HY000

    Message: %s PARTITION can only be used on RANGE/LIST partitions

  • Error number: 1513; Symbol: ER_ADD_PARTITION_SUBPART_ERROR; SQLSTATE: HY000

    Message: Trying to Add partition(s) with wrong number of subpartitions

  • Error number: 1514; Symbol: ER_ADD_PARTITION_NO_NEW_PARTITION; SQLSTATE: HY000

    Message: At least one partition must be added

  • Error number: 1515; Symbol: ER_COALESCE_PARTITION_NO_PARTITION; SQLSTATE: HY000

    Message: At least one partition must be coalesced

  • Error number: 1516; Symbol: ER_REORG_PARTITION_NOT_EXIST; SQLSTATE: HY000

    Message: More partitions to reorganize than there are partitions

  • Error number: 1517; Symbol: ER_SAME_NAME_PARTITION; SQLSTATE: HY000

    Message: Duplicate partition name %s

  • Error number: 1518; Symbol: ER_NO_BINLOG_ERROR; SQLSTATE: HY000

    Message: It is not allowed to shut off binlog on this command

  • Error number: 1519; Symbol: ER_CONSECUTIVE_REORG_PARTITIONS; SQLSTATE: HY000

    Message: When reorganizing a set of partitions they must be in consecutive order

  • Error number: 1520; Symbol: ER_REORG_OUTSIDE_RANGE; SQLSTATE: HY000

    Message: Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range

  • Error number: 1521; Symbol: ER_PARTITION_FUNCTION_FAILURE; SQLSTATE: HY000

    Message: Partition function not supported in this version for this handler

  • Error number: 1523; Symbol: ER_LIMITED_PART_RANGE; SQLSTATE: HY000

    Message: The %s handler only supports 32 bit integers in VALUES

  • Error number: 1524; Symbol: ER_PLUGIN_IS_NOT_LOADED; SQLSTATE: HY000

    Message: Plugin '%s' is not loaded

  • Error number: 1525; Symbol: ER_WRONG_VALUE; SQLSTATE: HY000

    Message: Incorrect %s value: '%s'

  • Error number: 1526; Symbol: ER_NO_PARTITION_FOR_GIVEN_VALUE; SQLSTATE: HY000

    Message: Table has no partition for value %s

  • Error number: 1527; Symbol: ER_FILEGROUP_OPTION_ONLY_ONCE; SQLSTATE: HY000

    Message: It is not allowed to specify %s more than once

  • Error number: 1528; Symbol: ER_CREATE_FILEGROUP_FAILED; SQLSTATE: HY000

    Message: Failed to create %s

  • Error number: 1529; Symbol: ER_DROP_FILEGROUP_FAILED; SQLSTATE: HY000

    Message: Failed to drop %s

  • Error number: 1530; Symbol: ER_TABLESPACE_AUTO_EXTEND_ERROR; SQLSTATE: HY000

    Message: The handler doesn't support autoextend of tablespaces

  • Error number: 1531; Symbol: ER_WRONG_SIZE_NUMBER; SQLSTATE: HY000

    Message: A size parameter was incorrectly specified, either number or on the form 10M

  • Error number: 1532; Symbol: ER_SIZE_OVERFLOW_ERROR; SQLSTATE: HY000

    Message: The size number was correct but we don't allow the digit part to be more than 2 billion

  • Error number: 1533; Symbol: ER_ALTER_FILEGROUP_FAILED; SQLSTATE: HY000

    Message: Failed to alter: %s

  • Error number: 1534; Symbol: ER_BINLOG_ROW_LOGGING_FAILED; SQLSTATE: HY000

    Message: Writing one row to the row-based binary log failed

  • Error number: 1537; Symbol: ER_EVENT_ALREADY_EXISTS; SQLSTATE: HY000

    Message: Event '%s' already exists

  • Error number: 1539; Symbol: ER_EVENT_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Unknown event '%s'

  • Error number: 1542; Symbol: ER_EVENT_INTERVAL_NOT_POSITIVE_OR_TOO_BIG; SQLSTATE: HY000

    Message: INTERVAL is either not positive or too big

  • Error number: 1543; Symbol: ER_EVENT_ENDS_BEFORE_STARTS; SQLSTATE: HY000

    Message: ENDS is either invalid or before STARTS

  • Error number: 1544; Symbol: ER_EVENT_EXEC_TIME_IN_THE_PAST; SQLSTATE: HY000

    Message: Event execution time is in the past. Event has been disabled

  • Error number: 1551; Symbol: ER_EVENT_SAME_NAME; SQLSTATE: HY000

    Message: Same old and new event name

  • Error number: 1553; Symbol: ER_DROP_INDEX_FK; SQLSTATE: HY000

    Message: Cannot drop index '%s': needed in a foreign key constraint

    InnoDB reports this error when you attempt to drop the last index that can enforce a particular referential constraint.

    For optimal performance with DML statements, InnoDB requires an index to exist on foreign key columns, so that UPDATE and DELETE operations on a parent table can easily check whether corresponding rows exist in the child table. MySQL creates or drops such indexes automatically when needed, as a side-effect of CREATE TABLE, CREATE INDEX, and ALTER TABLE statements.

    When you drop an index, InnoDB checks if the index is used for checking a foreign key constraint. It is still OK to drop the index if there is another index that can be used to enforce the same constraint. InnoDB prevents you from dropping the last index that can enforce a particular referential constraint.

  • Error number: 1554; Symbol: ER_WARN_DEPRECATED_SYNTAX_WITH_VER; SQLSTATE: HY000

    Message: The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead

  • Error number: 1556; Symbol: ER_CANT_LOCK_LOG_TABLE; SQLSTATE: HY000

    Message: You can't use locks with log tables.

  • Error number: 1557; Symbol: ER_FOREIGN_DUPLICATE_KEY_OLD_UNUSED; SQLSTATE: 23000

    Message: Upholding foreign key constraints for table '%s', entry '%s', key %d would lead to a duplicate entry

  • Error number: 1558; Symbol: ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE; SQLSTATE: HY000

    Message: The column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.

  • Error number: 1560; Symbol: ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT; SQLSTATE: HY000

    Message: Cannot change the binary logging format inside a stored function or trigger

  • Error number: 1562; Symbol: ER_PARTITION_NO_TEMPORARY; SQLSTATE: HY000

    Message: Cannot create temporary table with partitions

  • Error number: 1563; Symbol: ER_PARTITION_CONST_DOMAIN_ERROR; SQLSTATE: HY000

    Message: Partition constant is out of partition function domain

  • Error number: 1564; Symbol: ER_PARTITION_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: This partition function is not allowed

  • Error number: 1566; Symbol: ER_NULL_IN_VALUES_LESS_THAN; SQLSTATE: HY000

    Message: Not allowed to use NULL value in VALUES LESS THAN

  • Error number: 1567; Symbol: ER_WRONG_PARTITION_NAME; SQLSTATE: HY000

    Message: Incorrect partition name

  • Error number: 1568; Symbol: ER_CANT_CHANGE_TX_CHARACTERISTICS; SQLSTATE: 25001

    Message: Transaction characteristics can't be changed while a transaction is in progress

  • Error number: 1569; Symbol: ER_DUP_ENTRY_AUTOINCREMENT_CASE; SQLSTATE: HY000

    Message: ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%s' for key '%s'

  • Error number: 1571; Symbol: ER_EVENT_SET_VAR_ERROR; SQLSTATE: HY000

    Message: Error during starting/stopping of the scheduler. Error code %u

  • Error number: 1572; Symbol: ER_PARTITION_MERGE_ERROR; SQLSTATE: HY000

    Message: Engine cannot be used in partitioned tables

  • Error number: 1575; Symbol: ER_BASE64_DECODE_ERROR; SQLSTATE: HY000

    Message: Decoding of base64 string failed

  • Error number: 1576; Symbol: ER_EVENT_RECURSION_FORBIDDEN; SQLSTATE: HY000

    Message: Recursion of EVENT DDL statements is forbidden when body is present

  • Error number: 1578; Symbol: ER_ONLY_INTEGERS_ALLOWED; SQLSTATE: HY000

    Message: Only integers allowed as number here

  • Error number: 1579; Symbol: ER_UNSUPORTED_LOG_ENGINE; SQLSTATE: HY000

    Message: This storage engine cannot be used for log tables

  • Error number: 1580; Symbol: ER_BAD_LOG_STATEMENT; SQLSTATE: HY000

    Message: You cannot '%s' a log table if logging is enabled

  • Error number: 1581; Symbol: ER_CANT_RENAME_LOG_TABLE; SQLSTATE: HY000

    Message: Cannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'

  • Error number: 1582; Symbol: ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT; SQLSTATE: 42000

    Message: Incorrect parameter count in the call to native function '%s'

  • Error number: 1583; Symbol: ER_WRONG_PARAMETERS_TO_NATIVE_FCT; SQLSTATE: 42000

    Message: Incorrect parameters in the call to native function '%s'

  • Error number: 1584; Symbol: ER_WRONG_PARAMETERS_TO_STORED_FCT; SQLSTATE: 42000

    Message: Incorrect parameters in the call to stored function %s

  • Error number: 1585; Symbol: ER_NATIVE_FCT_NAME_COLLISION; SQLSTATE: HY000

    Message: This function '%s' has the same name as a native function

  • Error number: 1586; Symbol: ER_DUP_ENTRY_WITH_KEY_NAME; SQLSTATE: 23000

    Message: Duplicate entry '%s' for key '%s'

    The format string for this error is also used with ER_DUP_ENTRY.

  • Error number: 1587; Symbol: ER_BINLOG_PURGE_EMFILE; SQLSTATE: HY000

    Message: Too many files opened, please execute the command again

  • Error number: 1588; Symbol: ER_EVENT_CANNOT_CREATE_IN_THE_PAST; SQLSTATE: HY000

    Message: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.

  • Error number: 1589; Symbol: ER_EVENT_CANNOT_ALTER_IN_THE_PAST; SQLSTATE: HY000

    Message: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.

  • Error number: 1591; Symbol: ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT; SQLSTATE: HY000

    Message: Table has no partition for some existing values

  • Error number: 1592; Symbol: ER_BINLOG_UNSAFE_STATEMENT; SQLSTATE: HY000

    Message: Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s

  • Error number: 1593; Symbol: ER_BINLOG_FATAL_ERROR; SQLSTATE: HY000

    Message: Fatal error: %s

  • Error number: 1598; Symbol: ER_BINLOG_LOGGING_IMPOSSIBLE; SQLSTATE: HY000

    Message: Binary logging not possible. Message: %s

  • Error number: 1599; Symbol: ER_VIEW_NO_CREATION_CTX; SQLSTATE: HY000

    Message: View `%s`.`%s` has no creation context

  • Error number: 1600; Symbol: ER_VIEW_INVALID_CREATION_CTX; SQLSTATE: HY000

    Message: Creation context of view `%s`.`%s' is invalid

  • Error number: 1602; Symbol: ER_TRG_CORRUPTED_FILE; SQLSTATE: HY000

    Message: Corrupted TRG file for table `%s`.`%s`

  • Error number: 1603; Symbol: ER_TRG_NO_CREATION_CTX; SQLSTATE: HY000

    Message: Triggers for table `%s`.`%s` have no creation context

  • Error number: 1604; Symbol: ER_TRG_INVALID_CREATION_CTX; SQLSTATE: HY000

    Message: Trigger creation context of table `%s`.`%s` is invalid

  • Error number: 1605; Symbol: ER_EVENT_INVALID_CREATION_CTX; SQLSTATE: HY000

    Message: Creation context of event `%s`.`%s` is invalid

  • Error number: 1606; Symbol: ER_TRG_CANT_OPEN_TABLE; SQLSTATE: HY000

    Message: Cannot open table for trigger `%s`.`%s`

  • Error number: 1609; Symbol: ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT; SQLSTATE: HY000

    Message: The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.

  • Error number: 1610; Symbol: ER_REPLICA_CORRUPT_EVENT; SQLSTATE: HY000

    Message: Corrupted replication event was detected

  • Error number: 1612; Symbol: ER_LOG_PURGE_NO_FILE; SQLSTATE: HY000

    Message: Being purged log %s was not found

  • Error number: 1613; Symbol: ER_XA_RBTIMEOUT; SQLSTATE: XA106

    Message: XA_RBTIMEOUT: Transaction branch was rolled back: took too long

  • Error number: 1614; Symbol: ER_XA_RBDEADLOCK; SQLSTATE: XA102

    Message: XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected

  • Error number: 1615; Symbol: ER_NEED_REPREPARE; SQLSTATE: HY000

    Message: Prepared statement needs to be re-prepared

  • Error number: 1617; Symbol: WARN_NO_CONNECTION_METADATA; SQLSTATE: HY000

    Message: The connection metadata structure does not exist

  • Error number: 1618; Symbol: WARN_OPTION_IGNORED; SQLSTATE: HY000

    Message: <%s> option ignored

  • Error number: 1619; Symbol: ER_PLUGIN_DELETE_BUILTIN; SQLSTATE: HY000

    Message: Built-in plugins cannot be deleted

  • Error number: 1620; Symbol: WARN_PLUGIN_BUSY; SQLSTATE: HY000

    Message: Plugin is busy and will be uninstalled on shutdown

  • Error number: 1621; Symbol: ER_VARIABLE_IS_READONLY; SQLSTATE: HY000

    Message: %s variable '%s' is read-only. Use SET %s to assign the value

  • Error number: 1622; Symbol: ER_WARN_ENGINE_TRANSACTION_ROLLBACK; SQLSTATE: HY000

    Message: Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted

  • Error number: 1624; Symbol: ER_REPLICA_HEARTBEAT_VALUE_OUT_OF_RANGE; SQLSTATE: HY000

    Message: The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).

  • Error number: 1625; Symbol: ER_NDB_REPLICATION_SCHEMA_ERROR; SQLSTATE: HY000

    Message: Bad schema for mysql.ndb_replication table. Message: %s

  • Error number: 1626; Symbol: ER_CONFLICT_FN_PARSE_ERROR; SQLSTATE: HY000

    Message: Error in parsing conflict function. Message: %s

  • Error number: 1627; Symbol: ER_EXCEPTIONS_WRITE_ERROR; SQLSTATE: HY000

    Message: Write to exceptions table failed. Message: %s

  • Error number: 1628; Symbol: ER_TOO_LONG_TABLE_COMMENT; SQLSTATE: HY000

    Message: Comment for table '%s' is too long (max = %lu)

  • Error number: 1629; Symbol: ER_TOO_LONG_FIELD_COMMENT; SQLSTATE: HY000

    Message: The maximum supported character limit for the field, '%s', has been exceeded (max = %lu)

  • Error number: 1630; Symbol: ER_FUNC_INEXISTENT_NAME_COLLISION; SQLSTATE: 42000

    Message: FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual

  • Error number: 1631; Symbol: ER_DATABASE_NAME; SQLSTATE: HY000

    Message: Database

  • Error number: 1632; Symbol: ER_TABLE_NAME; SQLSTATE: HY000

    Message: Table

  • Error number: 1633; Symbol: ER_PARTITION_NAME; SQLSTATE: HY000

    Message: Partition

  • Error number: 1634; Symbol: ER_SUBPARTITION_NAME; SQLSTATE: HY000

    Message: Subpartition

  • Error number: 1635; Symbol: ER_TEMPORARY_NAME; SQLSTATE: HY000

    Message: Temporary

  • Error number: 1636; Symbol: ER_RENAMED_NAME; SQLSTATE: HY000

    Message: Renamed

  • Error number: 1637; Symbol: ER_TOO_MANY_CONCURRENT_TRXS; SQLSTATE: HY000

    Message: Too many active concurrent transactions

  • Error number: 1638; Symbol: WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED; SQLSTATE: HY000

    Message: Non-ASCII separator arguments are not fully supported

  • Error number: 1639; Symbol: ER_DEBUG_SYNC_TIMEOUT; SQLSTATE: HY000

    Message: debug sync point wait timed out

  • Error number: 1640; Symbol: ER_DEBUG_SYNC_HIT_LIMIT; SQLSTATE: HY000

    Message: debug sync point hit limit reached

  • Error number: 1641; Symbol: ER_DUP_SIGNAL_SET; SQLSTATE: 42000

    Message: Duplicate condition information item '%s'

  • Error number: 1642; Symbol: ER_SIGNAL_WARN; SQLSTATE: 01000

    Message: Unhandled user-defined warning condition

  • Error number: 1643; Symbol: ER_SIGNAL_NOT_FOUND; SQLSTATE: 02000

    Message: Unhandled user-defined not found condition

  • Error number: 1644; Symbol: ER_SIGNAL_EXCEPTION; SQLSTATE: HY000

    Message: Unhandled user-defined exception condition

  • Error number: 1645; Symbol: ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER; SQLSTATE: 0K000

    Message: RESIGNAL when handler not active

  • Error number: 1646; Symbol: ER_SIGNAL_BAD_CONDITION_TYPE; SQLSTATE: HY000

    Message: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE

  • Error number: 1647; Symbol: WARN_COND_ITEM_TRUNCATED; SQLSTATE: HY000

    Message: Data truncated for condition item '%s'

  • Error number: 1648; Symbol: ER_COND_ITEM_TOO_LONG; SQLSTATE: HY000

    Message: Data too long for condition item '%s'

  • Error number: 1649; Symbol: ER_UNKNOWN_LOCALE; SQLSTATE: HY000

    Message: Unknown locale: '%s'

  • Error number: 1650; Symbol: ER_REPLICA_IGNORE_SERVER_IDS; SQLSTATE: HY000

    Message: The requested server id %d clashes with the replica startup option --replicate-same-server-id

  • Error number: 1652; Symbol: ER_SAME_NAME_PARTITION_FIELD; SQLSTATE: HY000

    Message: Duplicate partition field name '%s'

  • Error number: 1653; Symbol: ER_PARTITION_COLUMN_LIST_ERROR; SQLSTATE: HY000

    Message: Inconsistency in usage of column lists for partitioning

  • Error number: 1654; Symbol: ER_WRONG_TYPE_COLUMN_VALUE_ERROR; SQLSTATE: HY000

    Message: Partition column values of incorrect type

  • Error number: 1655; Symbol: ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR; SQLSTATE: HY000

    Message: Too many fields in '%s'

  • Error number: 1656; Symbol: ER_MAXVALUE_IN_VALUES_IN; SQLSTATE: HY000

    Message: Cannot use MAXVALUE as value in VALUES IN

  • Error number: 1657; Symbol: ER_TOO_MANY_VALUES_ERROR; SQLSTATE: HY000

    Message: Cannot have more than one value for this type of %s partitioning

  • Error number: 1658; Symbol: ER_ROW_SINGLE_PARTITION_FIELD_ERROR; SQLSTATE: HY000

    Message: Row expressions in VALUES IN only allowed for multi-field column partitioning

  • Error number: 1659; Symbol: ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD; SQLSTATE: HY000

    Message: Field '%s' is of a not allowed type for this type of partitioning

  • Error number: 1660; Symbol: ER_PARTITION_FIELDS_TOO_LONG; SQLSTATE: HY000

    Message: The total length of the partitioning fields is too large

  • Error number: 1661; Symbol: ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.

  • Error number: 1662; Symbol: ER_BINLOG_ROW_MODE_AND_STMT_ENGINE; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.

  • Error number: 1663; Symbol: ER_BINLOG_UNSAFE_AND_STMT_ENGINE; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s

  • Error number: 1664; Symbol: ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.

  • Error number: 1665; Symbol: ER_BINLOG_STMT_MODE_AND_ROW_ENGINE; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s

  • Error number: 1666; Symbol: ER_BINLOG_ROW_INJECTION_AND_STMT_MODE; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.

  • Error number: 1667; Symbol: ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.

  • Error number: 1668; Symbol: ER_BINLOG_UNSAFE_LIMIT; SQLSTATE: HY000

    Message: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.

  • Error number: 1670; Symbol: ER_BINLOG_UNSAFE_SYSTEM_TABLE; SQLSTATE: HY000

    Message: The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.

  • Error number: 1671; Symbol: ER_BINLOG_UNSAFE_AUTOINC_COLUMNS; SQLSTATE: HY000

    Message: Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.

  • Error number: 1672; Symbol: ER_BINLOG_UNSAFE_UDF; SQLSTATE: HY000

    Message: Statement is unsafe because it uses a UDF which may not return the same value on the replica.

  • Error number: 1673; Symbol: ER_BINLOG_UNSAFE_SYSTEM_VARIABLE; SQLSTATE: HY000

    Message: Statement is unsafe because it uses a system variable that may have a different value on the replica.

  • Error number: 1674; Symbol: ER_BINLOG_UNSAFE_SYSTEM_FUNCTION; SQLSTATE: HY000

    Message: Statement is unsafe because it uses a system function that may return a different value on the replica.

  • Error number: 1675; Symbol: ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS; SQLSTATE: HY000

    Message: Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.

  • Error number: 1676; Symbol: ER_MESSAGE_AND_STATEMENT; SQLSTATE: HY000

    Message: %s Statement: %s

  • Error number: 1678; Symbol: ER_REPLICA_CANT_CREATE_CONVERSION; SQLSTATE: HY000

    Message: Can't create conversion table for table '%s.%s'

  • Error number: 1679; Symbol: ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT; SQLSTATE: HY000

    Message: Cannot modify @@session.binlog_format inside a transaction

  • Error number: 1680; Symbol: ER_PATH_LENGTH; SQLSTATE: HY000

    Message: The path specified for %s is too long.

  • Error number: 1681; Symbol: ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT; SQLSTATE: HY000

    Message: '%s' is deprecated and will be removed in a future release.

  • Error number: 1682; Symbol: ER_WRONG_NATIVE_TABLE_STRUCTURE; SQLSTATE: HY000

    Message: Native table '%s'.'%s' has the wrong structure

  • Error number: 1683; Symbol: ER_WRONG_PERFSCHEMA_USAGE; SQLSTATE: HY000

    Message: Invalid performance_schema usage.

  • Error number: 1684; Symbol: ER_WARN_I_S_SKIPPED_TABLE; SQLSTATE: HY000

    Message: Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement

  • Error number: 1685; Symbol: ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT; SQLSTATE: HY000

    Message: Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction

  • Error number: 1686; Symbol: ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT; SQLSTATE: HY000

    Message: Cannot change the binlog direct flag inside a stored function or trigger

  • Error number: 1687; Symbol: ER_SPATIAL_MUST_HAVE_GEOM_COL; SQLSTATE: 42000

    Message: A SPATIAL index may only contain a geometrical type column

  • Error number: 1688; Symbol: ER_TOO_LONG_INDEX_COMMENT; SQLSTATE: HY000

    Message: Comment for index '%s' is too long (max = %lu)

  • Error number: 1689; Symbol: ER_LOCK_ABORTED; SQLSTATE: HY000

    Message: Wait on a lock was aborted due to a pending exclusive lock

  • Error number: 1690; Symbol: ER_DATA_OUT_OF_RANGE; SQLSTATE: 22003

    Message: %s value is out of range in '%s'

  • Error number: 1692; Symbol: ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE; SQLSTATE: HY000

    Message: Mixing self-logging and non-self-logging engines in a statement is unsafe.

  • Error number: 1693; Symbol: ER_BINLOG_UNSAFE_MIXED_STATEMENT; SQLSTATE: HY000

    Message: Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.

  • Error number: 1694; Symbol: ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN; SQLSTATE: HY000

    Message: Cannot modify @@session.sql_log_bin inside a transaction

  • Error number: 1695; Symbol: ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN; SQLSTATE: HY000

    Message: Cannot change the sql_log_bin inside a stored function or trigger

  • Error number: 1696; Symbol: ER_FAILED_READ_FROM_PAR_FILE; SQLSTATE: HY000

    Message: Failed to read from the .par file

  • Error number: 1697; Symbol: ER_VALUES_IS_NOT_INT_TYPE_ERROR; SQLSTATE: HY000

    Message: VALUES value for partition '%s' must have type INT

  • Error number: 1698; Symbol: ER_ACCESS_DENIED_NO_PASSWORD_ERROR; SQLSTATE: 28000

    Message: Access denied for user '%s'@'%s'

  • Error number: 1701; Symbol: ER_TRUNCATE_ILLEGAL_FK; SQLSTATE: 42000

    Message: Cannot truncate a table referenced in a foreign key constraint (%s)

  • Error number: 1702; Symbol: ER_PLUGIN_IS_PERMANENT; SQLSTATE: HY000

    Message: Plugin '%s' is force_plus_permanent and can not be unloaded

  • Error number: 1703; Symbol: ER_REPLICA_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN; SQLSTATE: HY000

    Message: The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.

  • Error number: 1704; Symbol: ER_REPLICA_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX; SQLSTATE: HY000

    Message: The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.

  • Error number: 1705; Symbol: ER_STMT_CACHE_FULL; SQLSTATE: HY000

    Message: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again

  • Error number: 1706; Symbol: ER_MULTI_UPDATE_KEY_CONFLICT; SQLSTATE: HY000

    Message: Primary key/partition key update is not allowed since the table is updated both as '%s' and '%s'.

  • Error number: 1707; Symbol: ER_TABLE_NEEDS_REBUILD; SQLSTATE: HY000

    Message: Table rebuild required. Please do "ALTER TABLE `%s` FORCE" or dump/reload to fix it!

  • Error number: 1708; Symbol: WARN_OPTION_BELOW_LIMIT; SQLSTATE: HY000

    Message: The value of '%s' should be no less than the value of '%s'

  • Error number: 1709; Symbol: ER_INDEX_COLUMN_TOO_LONG; SQLSTATE: HY000

    Message: Index column size too large. The maximum column size is %lu bytes.

  • Error number: 1710; Symbol: ER_ERROR_IN_TRIGGER_BODY; SQLSTATE: HY000

    Message: Trigger '%s' has an error in its body: '%s'

  • Error number: 1711; Symbol: ER_ERROR_IN_UNKNOWN_TRIGGER_BODY; SQLSTATE: HY000

    Message: Unknown trigger has an error in its body: '%s'

  • Error number: 1712; Symbol: ER_INDEX_CORRUPT; SQLSTATE: HY000

    Message: Index %s is corrupted

  • Error number: 1713; Symbol: ER_UNDO_RECORD_TOO_BIG; SQLSTATE: HY000

    Message: Undo log record is too big.

  • Error number: 1714; Symbol: ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT; SQLSTATE: HY000

    Message: INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1715; Symbol: ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE; SQLSTATE: HY000

    Message: INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1716; Symbol: ER_BINLOG_UNSAFE_REPLACE_SELECT; SQLSTATE: HY000

    Message: REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1717; Symbol: ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT; SQLSTATE: HY000

    Message: CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1718; Symbol: ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT; SQLSTATE: HY000

    Message: CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1719; Symbol: ER_BINLOG_UNSAFE_UPDATE_IGNORE; SQLSTATE: HY000

    Message: UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1720; Symbol: ER_PLUGIN_NO_UNINSTALL; SQLSTATE: HY000

    Message: Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.

  • Error number: 1721; Symbol: ER_PLUGIN_NO_INSTALL; SQLSTATE: HY000

    Message: Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.

  • Error number: 1722; Symbol: ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT; SQLSTATE: HY000

    Message: Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1723; Symbol: ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC; SQLSTATE: HY000

    Message: CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.

  • Error number: 1724; Symbol: ER_BINLOG_UNSAFE_INSERT_TWO_KEYS; SQLSTATE: HY000

    Message: INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe

  • Error number: 1725; Symbol: ER_TABLE_IN_FK_CHECK; SQLSTATE: HY000

    Message: Table is being used in foreign key check.

  • Error number: 1726; Symbol: ER_UNSUPPORTED_ENGINE; SQLSTATE: HY000

    Message: Storage engine '%s' does not support system tables. [%s.%s]

  • Error number: 1727; Symbol: ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST; SQLSTATE: HY000

    Message: INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.

  • Error number: 1728; Symbol: ER_CANNOT_LOAD_FROM_TABLE_V2; SQLSTATE: HY000

    Message: Cannot load from %s.%s. The table is probably corrupted

  • Error number: 1729; Symbol: ER_SOURCE_DELAY_VALUE_OUT_OF_RANGE; SQLSTATE: HY000

    Message: The requested value %s for the source delay exceeds the maximum %u

  • Error number: 1730; Symbol: ER_ONLY_FD_AND_RBR_EVENTS_ALLOWED_IN_BINLOG_STATEMENT; SQLSTATE: HY000

    Message: Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)

  • Error number: 1731; Symbol: ER_PARTITION_EXCHANGE_DIFFERENT_OPTION; SQLSTATE: HY000

    Message: Non matching attribute '%s' between partition and table

  • Error number: 1732; Symbol: ER_PARTITION_EXCHANGE_PART_TABLE; SQLSTATE: HY000

    Message: Table to exchange with partition is partitioned: '%s'

  • Error number: 1733; Symbol: ER_PARTITION_EXCHANGE_TEMP_TABLE; SQLSTATE: HY000

    Message: Table to exchange with partition is temporary: '%s'

  • Error number: 1734; Symbol: ER_PARTITION_INSTEAD_OF_SUBPARTITION; SQLSTATE: HY000

    Message: Subpartitioned table, use subpartition instead of partition

  • Error number: 1735; Symbol: ER_UNKNOWN_PARTITION; SQLSTATE: HY000

    Message: Unknown partition '%s' in table '%s'

  • Error number: 1736; Symbol: ER_TABLES_DIFFERENT_METADATA; SQLSTATE: HY000

    Message: Tables have different definitions

  • Error number: 1737; Symbol: ER_ROW_DOES_NOT_MATCH_PARTITION; SQLSTATE: HY000

    Message: Found a row that does not match the partition

  • Error number: 1738; Symbol: ER_BINLOG_CACHE_SIZE_GREATER_THAN_MAX; SQLSTATE: HY000

    Message: Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.

  • Error number: 1739; Symbol: ER_WARN_INDEX_NOT_APPLICABLE; SQLSTATE: HY000

    Message: Cannot use %s access on index '%s' due to type or collation conversion on field '%s'

  • Error number: 1740; Symbol: ER_PARTITION_EXCHANGE_FOREIGN_KEY; SQLSTATE: HY000

    Message: Table to exchange with partition has foreign key references: '%s'

  • Error number: 1742; Symbol: ER_RPL_INFO_DATA_TOO_LONG; SQLSTATE: HY000

    Message: Data for column '%s' too long

  • Error number: 1745; Symbol: ER_BINLOG_STMT_CACHE_SIZE_GREATER_THAN_MAX; SQLSTATE: HY000

    Message: Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.

  • Error number: 1746; Symbol: ER_CANT_UPDATE_TABLE_IN_CREATE_TABLE_SELECT; SQLSTATE: HY000

    Message: Can't update table '%s' while '%s' is being created.

  • Error number: 1747; Symbol: ER_PARTITION_CLAUSE_ON_NONPARTITIONED; SQLSTATE: HY000

    Message: PARTITION () clause on non partitioned table

  • Error number: 1748; Symbol: ER_ROW_DOES_NOT_MATCH_GIVEN_PARTITION_SET; SQLSTATE: HY000

    Message: Found a row not matching the given partition set

  • Error number: 1750; Symbol: ER_CHANGE_RPL_INFO_REPOSITORY_FAILURE; SQLSTATE: HY000

    Message: Failure while changing the type of replication repository: %s.

  • Error number: 1751; Symbol: ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_CREATED_TEMP_TABLE; SQLSTATE: HY000

    Message: The creation of some temporary tables could not be rolled back.

  • Error number: 1752; Symbol: ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_DROPPED_TEMP_TABLE; SQLSTATE: HY000

    Message: Some temporary tables were dropped, but these operations could not be rolled back.

  • Error number: 1753; Symbol: ER_MTA_FEATURE_IS_NOT_SUPPORTED; SQLSTATE: HY000

    Message: %s is not supported in multi-threaded replica mode. %s

  • Error number: 1754; Symbol: ER_MTA_UPDATED_DBS_GREATER_MAX; SQLSTATE: HY000

    Message: The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.

  • Error number: 1755; Symbol: ER_MTA_CANT_PARALLEL; SQLSTATE: HY000

    Message: Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.

  • Error number: 1756; Symbol: ER_MTA_INCONSISTENT_DATA; SQLSTATE: HY000

    Message: %s

  • Error number: 1757; Symbol: ER_FULLTEXT_NOT_SUPPORTED_WITH_PARTITIONING; SQLSTATE: HY000

    Message: FULLTEXT index is not supported for partitioned tables.

  • Error number: 1758; Symbol: ER_DA_INVALID_CONDITION_NUMBER; SQLSTATE: 35000

    Message: Invalid condition number

  • Error number: 1759; Symbol: ER_INSECURE_PLAIN_TEXT; SQLSTATE: HY000

    Message: Sending passwords in plain text without SSL/TLS is extremely insecure.

  • Error number: 1760; Symbol: ER_INSECURE_CHANGE_SOURCE; SQLSTATE: HY000

    Message: Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.

  • Error number: 1761; Symbol: ER_FOREIGN_DUPLICATE_KEY_WITH_CHILD_INFO; SQLSTATE: 23000

    Message: Foreign key constraint for table '%s', record '%s' would lead to a duplicate entry in table '%s', key '%s'

  • Error number: 1762; Symbol: ER_FOREIGN_DUPLICATE_KEY_WITHOUT_CHILD_INFO; SQLSTATE: 23000

    Message: Foreign key constraint for table '%s', record '%s' would lead to a duplicate entry in a child table

  • Error number: 1763; Symbol: ER_SQLTHREAD_WITH_SECURE_REPLICA; SQLSTATE: HY000

    Message: Setting authentication options is not possible when only the Replica SQL Thread is being started.

  • Error number: 1764; Symbol: ER_TABLE_HAS_NO_FT; SQLSTATE: HY000

    Message: The table does not have FULLTEXT index to support this query

  • Error number: 1765; Symbol: ER_VARIABLE_NOT_SETTABLE_IN_SF_OR_TRIGGER; SQLSTATE: HY000

    Message: The system variable %s cannot be set in stored functions or triggers.

  • Error number: 1766; Symbol: ER_VARIABLE_NOT_SETTABLE_IN_TRANSACTION; SQLSTATE: HY000

    Message: The system variable %s cannot be set when there is an ongoing transaction.

  • Error number: 1769; Symbol: ER_SET_STATEMENT_CANNOT_INVOKE_FUNCTION; SQLSTATE: HY000

    Message: The statement 'SET %s' cannot invoke a stored function.

  • Error number: 1770; Symbol: ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL; SQLSTATE: HY000

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

  • Error number: 1772; Symbol: ER_MALFORMED_GTID_SET_SPECIFICATION; SQLSTATE: HY000

    Message: Malformed GTID set specification '%s'.

  • Error number: 1773; Symbol: ER_MALFORMED_GTID_SET_ENCODING; SQLSTATE: HY000

    Message: Malformed GTID set encoding.

  • Error number: 1774; Symbol: ER_MALFORMED_GTID_SPECIFICATION; SQLSTATE: HY000

    Message: Malformed GTID specification '%s'.

  • Error number: 1775; Symbol: ER_GNO_EXHAUSTED; SQLSTATE: HY000

    Message: Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.

  • Error number: 1776; Symbol: ER_BAD_REPLICA_AUTO_POSITION; SQLSTATE: HY000

    Message: Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.

  • Error number: 1777; Symbol: ER_AUTO_POSITION_REQUIRES_GTID_MODE_NOT_OFF; SQLSTATE: HY000

    Message: CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.

  • Error number: 1778; Symbol: ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET; SQLSTATE: HY000

    Message: Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.

  • Error number: 1779; Symbol: ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON; SQLSTATE: HY000

    Message: GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.

  • Error number: 1781; Symbol: ER_CANT_SET_GTID_NEXT_TO_GTID_WHEN_GTID_MODE_IS_OFF; SQLSTATE: HY000

    Message: @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.

  • Error number: 1782; Symbol: ER_CANT_SET_GTID_NEXT_TO_ANONYMOUS_WHEN_GTID_MODE_IS_ON; SQLSTATE: HY000

    Message: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.

  • Error number: 1783; Symbol: ER_CANT_SET_GTID_NEXT_LIST_TO_NON_NULL_WHEN_GTID_MODE_IS_OFF; SQLSTATE: HY000

    Message: @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.

  • Error number: 1785; Symbol: ER_GTID_UNSAFE_NON_TRANSACTIONAL_TABLE; SQLSTATE: HY000

    Message: Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

  • Error number: 1786; Symbol: ER_GTID_UNSAFE_CREATE_SELECT; SQLSTATE: HY000

    Message: Statement violates GTID consistency: CREATE TABLE ... SELECT.

  • Error number: 1788; Symbol: ER_GTID_MODE_CAN_ONLY_CHANGE_ONE_STEP_AT_A_TIME; SQLSTATE: HY000

    Message: The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.

  • Error number: 1789; Symbol: ER_SOURCE_HAS_PURGED_REQUIRED_GTIDS; SQLSTATE: HY000

    Message: Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s

  • Error number: 1790; Symbol: ER_CANT_SET_GTID_NEXT_WHEN_OWNING_GTID; SQLSTATE: HY000

    Message: @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.

  • Error number: 1791; Symbol: ER_UNKNOWN_EXPLAIN_FORMAT; SQLSTATE: HY000

    Message: Unknown EXPLAIN format name: '%s'

  • Error number: 1792; Symbol: ER_CANT_EXECUTE_IN_READ_ONLY_TRANSACTION; SQLSTATE: 25006

    Message: Cannot execute statement in a READ ONLY transaction.

  • Error number: 1793; Symbol: ER_TOO_LONG_TABLE_PARTITION_COMMENT; SQLSTATE: HY000

    Message: Comment for table partition '%s' is too long (max = %lu)

  • Error number: 1794; Symbol: ER_REPLICA_CONFIGURATION; SQLSTATE: HY000

    Message: Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.

  • Error number: 1795; Symbol: ER_INNODB_FT_LIMIT; SQLSTATE: HY000

    Message: InnoDB presently supports one FULLTEXT index creation at a time

  • Error number: 1796; Symbol: ER_INNODB_NO_FT_TEMP_TABLE; SQLSTATE: HY000

    Message: Cannot create FULLTEXT index on temporary InnoDB table

  • Error number: 1797; Symbol: ER_INNODB_FT_WRONG_DOCID_COLUMN; SQLSTATE: HY000

    Message: Column '%s' is of wrong type for an InnoDB FULLTEXT index

  • Error number: 1798; Symbol: ER_INNODB_FT_WRONG_DOCID_INDEX; SQLSTATE: HY000

    Message: Index '%s' is of wrong type for an InnoDB FULLTEXT index

  • Error number: 1799; Symbol: ER_INNODB_ONLINE_LOG_TOO_BIG; SQLSTATE: HY000

    Message: Creating index '%s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.

  • Error number: 1800; Symbol: ER_UNKNOWN_ALTER_ALGORITHM; SQLSTATE: HY000

    Message: Unknown ALGORITHM '%s'

  • Error number: 1801; Symbol: ER_UNKNOWN_ALTER_LOCK; SQLSTATE: HY000

    Message: Unknown LOCK type '%s'

  • Error number: 1802; Symbol: ER_MTA_CHANGE_SOURCE_CANT_RUN_WITH_GAPS; SQLSTATE: HY000

    Message: CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.

  • Error number: 1803; Symbol: ER_MTA_RECOVERY_FAILURE; SQLSTATE: HY000

    Message: Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.

  • Error number: 1804; Symbol: ER_MTA_RESET_WORKERS; SQLSTATE: HY000

    Message: Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.

  • Error number: 1805; Symbol: ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2; SQLSTATE: HY000

    Message: Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted

  • Error number: 1806; Symbol: ER_REPLICA_SILENT_RETRY_TRANSACTION; SQLSTATE: HY000

    Message: Replica must silently retry current transaction

  • Error number: 1807; Symbol: ER_DISCARD_FK_CHECKS_RUNNING; SQLSTATE: HY000

    Message: There is a foreign key check running on table '%s'. Cannot discard the table.

  • Error number: 1808; Symbol: ER_TABLE_SCHEMA_MISMATCH; SQLSTATE: HY000

    Message: Schema mismatch (%s)

  • Error number: 1809; Symbol: ER_TABLE_IN_SYSTEM_TABLESPACE; SQLSTATE: HY000

    Message: Table '%s' in system tablespace

  • Error number: 1810; Symbol: ER_IO_READ_ERROR; SQLSTATE: HY000

    Message: IO Read error: (%lu, %s) %s

  • Error number: 1811; Symbol: ER_IO_WRITE_ERROR; SQLSTATE: HY000

    Message: IO Write error: (%lu, %s) %s

  • Error number: 1812; Symbol: ER_TABLESPACE_MISSING; SQLSTATE: HY000

    Message: Tablespace is missing for table %s.

  • Error number: 1813; Symbol: ER_TABLESPACE_EXISTS; SQLSTATE: HY000

    Message: Tablespace '%s' exists.

  • Error number: 1814; Symbol: ER_TABLESPACE_DISCARDED; SQLSTATE: HY000

    Message: Tablespace is discarded for table, '%s'

  • Error number: 1815; Symbol: ER_INTERNAL_ERROR; SQLSTATE: HY000

    Message: Internal error: %s

  • Error number: 1816; Symbol: ER_INNODB_IMPORT_ERROR; SQLSTATE: HY000

    Message: ALTER TABLE %s IMPORT TABLESPACE failed with error %lu : '%s'

  • Error number: 1817; Symbol: ER_INNODB_INDEX_CORRUPT; SQLSTATE: HY000

    Message: Index corrupt: %s

  • Error number: 1818; Symbol: ER_INVALID_YEAR_COLUMN_LENGTH; SQLSTATE: HY000

    Message: Invalid display width. Use YEAR instead.

  • Error number: 1819; Symbol: ER_NOT_VALID_PASSWORD; SQLSTATE: HY000

    Message: Your password does not satisfy the current policy requirements

  • Error number: 1820; Symbol: ER_MUST_CHANGE_PASSWORD; SQLSTATE: HY000

    Message: You must reset your password using ALTER USER statement before executing this statement.

  • Error number: 1821; Symbol: ER_FK_NO_INDEX_CHILD; SQLSTATE: HY000

    Message: Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'

  • Error number: 1822; Symbol: ER_FK_NO_INDEX_PARENT; SQLSTATE: HY000

    Message: Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'

  • Error number: 1823; Symbol: ER_FK_FAIL_ADD_SYSTEM; SQLSTATE: HY000

    Message: Failed to add the foreign key constraint '%s' to system tables

  • Error number: 1824; Symbol: ER_FK_CANNOT_OPEN_PARENT; SQLSTATE: HY000

    Message: Failed to open the referenced table '%s'

  • Error number: 1825; Symbol: ER_FK_INCORRECT_OPTION; SQLSTATE: HY000

    Message: Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'

  • Error number: 1826; Symbol: ER_FK_DUP_NAME; SQLSTATE: HY000

    Message: Duplicate foreign key constraint name '%s'

  • Error number: 1827; Symbol: ER_PASSWORD_FORMAT; SQLSTATE: HY000

    Message: The password hash doesn't have the expected format.

  • Error number: 1828; Symbol: ER_FK_COLUMN_CANNOT_DROP; SQLSTATE: HY000

    Message: Cannot drop column '%s': needed in a foreign key constraint '%s'

  • Error number: 1829; Symbol: ER_FK_COLUMN_CANNOT_DROP_CHILD; SQLSTATE: HY000

    Message: Cannot drop column '%s': needed in a foreign key constraint '%s' of table '%s'

  • Error number: 1830; Symbol: ER_FK_COLUMN_NOT_NULL; SQLSTATE: HY000

    Message: Column '%s' cannot be NOT NULL: needed in a foreign key constraint '%s' SET NULL

  • Error number: 1831; Symbol: ER_DUP_INDEX; SQLSTATE: HY000

    Message: Duplicate index '%s' defined on the table '%s.%s'. This is deprecated and will be disallowed in a future release.

  • Error number: 1832; Symbol: ER_FK_COLUMN_CANNOT_CHANGE; SQLSTATE: HY000

    Message: Cannot change column '%s': used in a foreign key constraint '%s'

  • Error number: 1833; Symbol: ER_FK_COLUMN_CANNOT_CHANGE_CHILD; SQLSTATE: HY000

    Message: Cannot change column '%s': used in a foreign key constraint '%s' of table '%s'

  • Error number: 1835; Symbol: ER_MALFORMED_PACKET; SQLSTATE: HY000

    Message: Malformed communication packet.

  • Error number: 1836; Symbol: ER_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Running in read-only mode

  • Error number: 1837; Symbol: ER_GTID_NEXT_TYPE_UNDEFINED_GTID; SQLSTATE: HY000

    Message: When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.

  • Error number: 1838; Symbol: ER_VARIABLE_NOT_SETTABLE_IN_SP; SQLSTATE: HY000

    Message: The system variable %s cannot be set in stored procedures.

  • Error number: 1840; Symbol: ER_CANT_SET_GTID_PURGED_WHEN_GTID_EXECUTED_IS_NOT_EMPTY; SQLSTATE: HY000

    Message: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.

  • Error number: 1841; Symbol: ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY; SQLSTATE: HY000

    Message: @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).

  • Error number: 1842; Symbol: ER_GTID_PURGED_WAS_CHANGED; SQLSTATE: HY000

    Message: @@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.

  • Error number: 1843; Symbol: ER_GTID_EXECUTED_WAS_CHANGED; SQLSTATE: HY000

    Message: @@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.

  • Error number: 1844; Symbol: ER_BINLOG_STMT_MODE_AND_NO_REPL_TABLES; SQLSTATE: HY000

    Message: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.

  • Error number: 1845; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED; SQLSTATE: 0A000

    Message: %s is not supported for this operation. Try %s.

  • Error number: 1846; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON; SQLSTATE: 0A000

    Message: %s is not supported. Reason: %s. Try %s.

  • Error number: 1847; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY; SQLSTATE: HY000

    Message: COPY algorithm requires a lock

  • Error number: 1848; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION; SQLSTATE: HY000

    Message: Partition specific operations do not yet support LOCK/ALGORITHM

  • Error number: 1849; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME; SQLSTATE: HY000

    Message: Columns participating in a foreign key are renamed

  • Error number: 1850; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE; SQLSTATE: HY000

    Message: Cannot change column type INPLACE

  • Error number: 1851; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK; SQLSTATE: HY000

    Message: Adding foreign keys needs foreign_key_checks=OFF

  • Error number: 1853; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK; SQLSTATE: HY000

    Message: Dropping a primary key is not allowed without also adding a new primary key

  • Error number: 1854; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC; SQLSTATE: HY000

    Message: Adding an auto-increment column requires a lock

  • Error number: 1855; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS; SQLSTATE: HY000

    Message: Cannot replace hidden FTS_DOC_ID with a user-visible one

  • Error number: 1856; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS; SQLSTATE: HY000

    Message: Cannot drop or rename FTS_DOC_ID

  • Error number: 1857; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FTS; SQLSTATE: HY000

    Message: Fulltext index creation requires a lock

  • Error number: 1859; Symbol: ER_DUP_UNKNOWN_IN_INDEX; SQLSTATE: 23000

    Message: Duplicate entry for key '%s'

  • Error number: 1860; Symbol: ER_IDENT_CAUSES_TOO_LONG_PATH; SQLSTATE: HY000

    Message: Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.

  • Error number: 1861; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL; SQLSTATE: HY000

    Message: cannot silently convert NULL values, as required in this SQL_MODE

  • Error number: 1862; Symbol: ER_MUST_CHANGE_PASSWORD_LOGIN; SQLSTATE: HY000

    Message: Your password has expired. To log in you must change it using a client that supports expired passwords.

  • Error number: 1863; Symbol: ER_ROW_IN_WRONG_PARTITION; SQLSTATE: HY000

    Message: Found a row in wrong partition %s

  • Error number: 1864; Symbol: ER_MTA_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX; SQLSTATE: HY000

    Message: Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.

  • Error number: 1866; Symbol: ER_BINLOG_LOGICAL_CORRUPTION; SQLSTATE: HY000

    Message: The binary log file '%s' is logically corrupted: %s

  • Error number: 1867; Symbol: ER_WARN_PURGE_LOG_IN_USE; SQLSTATE: HY000

    Message: file %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.

  • Error number: 1868; Symbol: ER_WARN_PURGE_LOG_IS_ACTIVE; SQLSTATE: HY000

    Message: file %s was not purged because it is the active log file.

  • Error number: 1869; Symbol: ER_AUTO_INCREMENT_CONFLICT; SQLSTATE: HY000

    Message: Auto-increment value in UPDATE conflicts with internally generated values

  • Error number: 1870; Symbol: WARN_ON_BLOCKHOLE_IN_RBR; SQLSTATE: HY000

    Message: Row events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%s'

  • Error number: 1871; Symbol: ER_REPLICA_CM_INIT_REPOSITORY; SQLSTATE: HY000

    Message: Replica failed to initialize connection metadata structure from the repository

  • Error number: 1872; Symbol: ER_REPLICA_AM_INIT_REPOSITORY; SQLSTATE: HY000

    Message: Replica failed to initialize applier metadata structure from the repository

  • Error number: 1873; Symbol: ER_ACCESS_DENIED_CHANGE_USER_ERROR; SQLSTATE: 28000

    Message: Access denied trying to change to user '%s'@'%s' (using password: %s). Disconnecting.

  • Error number: 1874; Symbol: ER_INNODB_READ_ONLY; SQLSTATE: HY000

    Message: InnoDB is in read only mode.

  • Error number: 1875; Symbol: ER_STOP_REPLICA_SQL_THREAD_TIMEOUT; SQLSTATE: HY000

    Message: STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.

  • Error number: 1876; Symbol: ER_STOP_REPLICA_IO_THREAD_TIMEOUT; SQLSTATE: HY000

    Message: STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.

  • Error number: 1877; Symbol: ER_TABLE_CORRUPT; SQLSTATE: HY000

    Message: Operation cannot be performed. The table '%s.%s' is missing, corrupt or contains bad data.

  • Error number: 1878; Symbol: ER_TEMP_FILE_WRITE_FAILURE; SQLSTATE: HY000

    Message: Temporary file write failure.

  • Error number: 1879; Symbol: ER_INNODB_FT_AUX_NOT_HEX_ID; SQLSTATE: HY000

    Message: Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.

  • Error number: 1880; Symbol: ER_OLD_TEMPORALS_UPGRADED; SQLSTATE: HY000

    Message: TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.

  • Error number: 1881; Symbol: ER_INNODB_FORCED_RECOVERY; SQLSTATE: HY000

    Message: Operation not allowed when innodb_force_recovery > 0.

  • Error number: 1882; Symbol: ER_AES_INVALID_IV; SQLSTATE: HY000

    Message: The initialization vector supplied to %s is too short. Must be at least %d bytes long

  • Error number: 1883; Symbol: ER_PLUGIN_CANNOT_BE_UNINSTALLED; SQLSTATE: HY000

    Message: Plugin '%s' cannot be uninstalled now. %s

  • Error number: 1884; Symbol: ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_ASSIGNED_GTID; SQLSTATE: HY000

    Message: Cannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.

  • Error number: 1885; Symbol: ER_REPLICA_HAS_MORE_GTIDS_THAN_SOURCE; SQLSTATE: HY000

    Message: Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.

  • Error number: 1886; Symbol: ER_MISSING_KEY; SQLSTATE: HY000

    Message: The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.

  • Error number: 1887; Symbol: WARN_NAMED_PIPE_ACCESS_EVERYONE; SQLSTATE: HY000

    Message: Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.

  • Error number: 3000; Symbol: ER_FILE_CORRUPT; SQLSTATE: HY000

    Message: File %s is corrupted

  • Error number: 3001; Symbol: ER_ERROR_ON_SOURCE; SQLSTATE: HY000

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

  • Error number: 3003; Symbol: ER_STORAGE_ENGINE_NOT_LOADED; SQLSTATE: HY000

    Message: Storage engine for table '%s'.'%s' is not loaded.

  • Error number: 3004; Symbol: ER_GET_STACKED_DA_WITHOUT_ACTIVE_HANDLER; SQLSTATE: 0Z002

    Message: GET STACKED DIAGNOSTICS when handler not active

  • Error number: 3005; Symbol: ER_WARN_LEGACY_SYNTAX_CONVERTED; SQLSTATE: HY000

    Message: %s is no longer supported. The statement was converted to %s.

  • Error number: 3006; Symbol: ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN; SQLSTATE: HY000

    Message: Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.

  • Error number: 3007; Symbol: ER_CANNOT_DISCARD_TEMPORARY_TABLE; SQLSTATE: HY000

    Message: Cannot DISCARD/IMPORT tablespace associated with temporary table

  • Error number: 3008; Symbol: ER_FK_DEPTH_EXCEEDED; SQLSTATE: HY000

    Message: Foreign key cascade delete/update exceeds max depth of %d.

  • Error number: 3009; Symbol: ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2; SQLSTATE: HY000

    Message: The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.

  • Error number: 3010; Symbol: ER_WARN_TRIGGER_DOESNT_HAVE_CREATED; SQLSTATE: HY000

    Message: Trigger %s.%s.%s does not have CREATED attribute.

  • Error number: 3011; Symbol: ER_REFERENCED_TRG_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Referenced trigger '%s' for the given action time and event type does not exist.

  • Error number: 3012; Symbol: ER_EXPLAIN_NOT_SUPPORTED; SQLSTATE: HY000

    Message: EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE

  • Error number: 3013; Symbol: ER_INVALID_FIELD_SIZE; SQLSTATE: HY000

    Message: Invalid size for column '%s'.

  • Error number: 3014; Symbol: ER_MISSING_HA_CREATE_OPTION; SQLSTATE: HY000

    Message: Table storage engine '%s' found required create option missing

  • Error number: 3015; Symbol: ER_ENGINE_OUT_OF_MEMORY; SQLSTATE: HY000

    Message: Out of memory in storage engine '%s'.

  • Error number: 3016; Symbol: ER_PASSWORD_EXPIRE_ANONYMOUS_USER; SQLSTATE: HY000

    Message: The password for anonymous user cannot be expired.

  • Error number: 3017; Symbol: ER_REPLICA_SQL_THREAD_MUST_STOP; SQLSTATE: HY000

    Message: This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD first

  • Error number: 3018; Symbol: ER_NO_FT_MATERIALIZED_SUBQUERY; SQLSTATE: HY000

    Message: Cannot create FULLTEXT index on materialized subquery

  • Error number: 3019; Symbol: ER_INNODB_UNDO_LOG_FULL; SQLSTATE: HY000

    Message: Undo Log error: %s

  • Error number: 3020; Symbol: ER_INVALID_ARGUMENT_FOR_LOGARITHM; SQLSTATE: 2201E

    Message: Invalid argument for logarithm

  • Error number: 3021; Symbol: ER_REPLICA_CHANNEL_IO_THREAD_MUST_STOP; SQLSTATE: HY000

    Message: This operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.

  • Error number: 3022; Symbol: ER_WARN_OPEN_TEMP_TABLES_MUST_BE_ZERO; SQLSTATE: HY000

    Message: This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.

  • Error number: 3023; Symbol: ER_WARN_ONLY_SOURCE_LOG_FILE_NO_POS; SQLSTATE: HY000

    Message: CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.

  • Error number: 3024; Symbol: ER_QUERY_TIMEOUT; SQLSTATE: HY000

    Message: Query execution was interrupted, maximum statement execution time exceeded

  • Error number: 3025; Symbol: ER_NON_RO_SELECT_DISABLE_TIMER; SQLSTATE: HY000

    Message: Select is not a read only statement, disabling timer

  • Error number: 3026; Symbol: ER_DUP_LIST_ENTRY; SQLSTATE: HY000

    Message: Duplicate entry '%s'.

  • Error number: 3028; Symbol: ER_AGGREGATE_ORDER_FOR_UNION; SQLSTATE: HY000

    Message: Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECT

  • Error number: 3029; Symbol: ER_AGGREGATE_ORDER_NON_AGG_QUERY; SQLSTATE: HY000

    Message: Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query

  • Error number: 3030; Symbol: ER_REPLICA_WORKER_STOPPED_PREVIOUS_THD_ERROR; SQLSTATE: HY000

    Message: Replica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.

  • Error number: 3031; Symbol: ER_DONT_SUPPORT_REPLICA_PRESERVE_COMMIT_ORDER; SQLSTATE: HY000

    Message: replica_preserve_commit_order is not supported %s.

  • Error number: 3032; Symbol: ER_SERVER_OFFLINE_MODE; SQLSTATE: HY000

    Message: The server is currently in offline mode

  • Error number: 3033; Symbol: ER_GIS_DIFFERENT_SRIDS; SQLSTATE: HY000

    Message: Binary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.

    Geometry values passed as arguments to spatial functions must have the same SRID value.

  • Error number: 3034; Symbol: ER_GIS_UNSUPPORTED_ARGUMENT; SQLSTATE: HY000

    Message: Calling geometry function %s with unsupported types of arguments.

    A spatial function was called with a combination of argument types that the function does not support.

  • Error number: 3035; Symbol: ER_GIS_UNKNOWN_ERROR; SQLSTATE: HY000

    Message: Unknown GIS error occurred in function %s.

  • Error number: 3036; Symbol: ER_GIS_UNKNOWN_EXCEPTION; SQLSTATE: HY000

    Message: Unknown exception caught in GIS function %s.

  • Error number: 3037; Symbol: ER_GIS_INVALID_DATA; SQLSTATE: 22023

    Message: Invalid GIS data provided to function %s.

    A spatial function was called with an argument not recognized as a valid geometry value.

  • Error number: 3038; Symbol: ER_BOOST_GEOMETRY_EMPTY_INPUT_EXCEPTION; SQLSTATE: HY000

    Message: The geometry has no data in function %s.

  • Error number: 3039; Symbol: ER_BOOST_GEOMETRY_CENTROID_EXCEPTION; SQLSTATE: HY000

    Message: Unable to calculate centroid because geometry is empty in function %s.

  • Error number: 3040; Symbol: ER_BOOST_GEOMETRY_OVERLAY_INVALID_INPUT_EXCEPTION; SQLSTATE: HY000

    Message: Geometry overlay calculation error: geometry data is invalid in function %s.

  • Error number: 3041; Symbol: ER_BOOST_GEOMETRY_TURN_INFO_EXCEPTION; SQLSTATE: HY000

    Message: Geometry turn info calculation error: geometry data is invalid in function %s.

  • Error number: 3042; Symbol: ER_BOOST_GEOMETRY_SELF_INTERSECTION_POINT_EXCEPTION; SQLSTATE: HY000

    Message: Analysis procedures of intersection points interrupted unexpectedly in function %s.

  • Error number: 3043; Symbol: ER_BOOST_GEOMETRY_UNKNOWN_EXCEPTION; SQLSTATE: HY000

    Message: Unknown exception thrown in function %s.

  • Error number: 3044; Symbol: ER_STD_BAD_ALLOC_ERROR; SQLSTATE: HY000

    Message: Memory allocation error: %s in function %s.

  • Error number: 3045; Symbol: ER_STD_DOMAIN_ERROR; SQLSTATE: HY000

    Message: Domain error: %s in function %s.

  • Error number: 3046; Symbol: ER_STD_LENGTH_ERROR; SQLSTATE: HY000

    Message: Length error: %s in function %s.

  • Error number: 3047; Symbol: ER_STD_INVALID_ARGUMENT; SQLSTATE: HY000

    Message: Invalid argument error: %s in function %s.

  • Error number: 3048; Symbol: ER_STD_OUT_OF_RANGE_ERROR; SQLSTATE: HY000

    Message: Out of range error: %s in function %s.

  • Error number: 3049; Symbol: ER_STD_OVERFLOW_ERROR; SQLSTATE: HY000

    Message: Overflow error: %s in function %s.

  • Error number: 3050; Symbol: ER_STD_RANGE_ERROR; SQLSTATE: HY000

    Message: Range error: %s in function %s.

  • Error number: 3051; Symbol: ER_STD_UNDERFLOW_ERROR; SQLSTATE: HY000

    Message: Underflow error: %s in function %s.

  • Error number: 3052; Symbol: ER_STD_LOGIC_ERROR; SQLSTATE: HY000

    Message: Logic error: %s in function %s.

  • Error number: 3053; Symbol: ER_STD_RUNTIME_ERROR; SQLSTATE: HY000

    Message: Runtime error: %s in function %s.

  • Error number: 3054; Symbol: ER_STD_UNKNOWN_EXCEPTION; SQLSTATE: HY000

    Message: Unknown exception: %s in function %s.

  • Error number: 3055; Symbol: ER_GIS_DATA_WRONG_ENDIANESS; SQLSTATE: HY000

    Message: Geometry byte string must be little endian.

  • Error number: 3056; Symbol: ER_CHANGE_SOURCE_PASSWORD_LENGTH; SQLSTATE: HY000

    Message: The password provided for the replication user exceeds the maximum length of 32 characters

  • Error number: 3057; Symbol: ER_USER_LOCK_WRONG_NAME; SQLSTATE: 42000

    Message: Incorrect user-level lock name '%s'. The name is empty, NULL, or can not be expressed in the current character-set.

  • Error number: 3058; Symbol: ER_USER_LOCK_DEADLOCK; SQLSTATE: HY000

    Message: Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.

    This error is returned when the metdata locking subsystem detects a deadlock for an attempt to acquire a named lock with GET_LOCK.

  • Error number: 3059; Symbol: ER_REPLACE_INACCESSIBLE_ROWS; SQLSTATE: HY000

    Message: REPLACE cannot be executed as it requires deleting rows that are not in the view

  • Error number: 3060; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_GIS; SQLSTATE: HY000

    Message: Do not support online operation on table with GIS index

  • Error number: 3061; Symbol: ER_ILLEGAL_USER_VAR; SQLSTATE: 42000

    Message: User variable name '%s' is illegal

  • Error number: 3062; Symbol: ER_GTID_MODE_OFF; SQLSTATE: HY000

    Message: Cannot %s when GTID_MODE = OFF.

  • Error number: 3064; Symbol: ER_INCORRECT_TYPE; SQLSTATE: HY000

    Message: Incorrect type for argument %s in function %s.

  • Error number: 3065; Symbol: ER_FIELD_IN_ORDER_NOT_SELECT; SQLSTATE: HY000

    Message: Expression #%u of ORDER BY clause is not in SELECT list, references column '%s' which is not in SELECT list; this is incompatible with %s

  • Error number: 3066; Symbol: ER_AGGREGATE_IN_ORDER_NOT_SELECT; SQLSTATE: HY000

    Message: Expression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %s

  • Error number: 3067; Symbol: ER_INVALID_RPL_WILD_TABLE_FILTER_PATTERN; SQLSTATE: HY000

    Message: Supplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'

  • Error number: 3068; Symbol: ER_NET_OK_PACKET_TOO_LARGE; SQLSTATE: 08S01

    Message: OK packet too large

  • Error number: 3069; Symbol: ER_INVALID_JSON_DATA; SQLSTATE: HY000

    Message: Invalid JSON data provided to function %s: %s

  • Error number: 3070; Symbol: ER_INVALID_GEOJSON_MISSING_MEMBER; SQLSTATE: HY000

    Message: Invalid GeoJSON data provided to function %s: Missing required member '%s'

  • Error number: 3071; Symbol: ER_INVALID_GEOJSON_WRONG_TYPE; SQLSTATE: HY000

    Message: Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'

  • Error number: 3072; Symbol: ER_INVALID_GEOJSON_UNSPECIFIED; SQLSTATE: HY000

    Message: Invalid GeoJSON data provided to function %s

  • Error number: 3073; Symbol: ER_DIMENSION_UNSUPPORTED; SQLSTATE: HY000

    Message: Unsupported number of coordinate dimensions in function %s: Found %u, expected %u

  • Error number: 3074; Symbol: ER_REPLICA_CHANNEL_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Replica channel '%s' does not exist.

  • Error number: 3076; Symbol: ER_REPLICA_CHANNEL_NAME_INVALID_OR_TOO_LONG; SQLSTATE: HY000

    Message: Couldn't create channel: Channel name is either invalid or too long.

  • Error number: 3077; Symbol: ER_REPLICA_NEW_CHANNEL_WRONG_REPOSITORY; SQLSTATE: HY000

    Message: To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.

  • Error number: 3079; Symbol: ER_REPLICA_MULTIPLE_CHANNELS_CMD; SQLSTATE: HY000

    Message: Multiple channels exist on the replica. Please provide channel name as an argument.

  • Error number: 3080; Symbol: ER_REPLICA_MAX_CHANNELS_EXCEEDED; SQLSTATE: HY000

    Message: Maximum number of replication channels allowed exceeded.

  • Error number: 3081; Symbol: ER_REPLICA_CHANNEL_MUST_STOP; SQLSTATE: HY000

    Message: This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' first

  • Error number: 3082; Symbol: ER_REPLICA_CHANNEL_NOT_RUNNING; SQLSTATE: HY000

    Message: This operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'

  • Error number: 3083; Symbol: ER_REPLICA_CHANNEL_WAS_RUNNING; SQLSTATE: HY000

    Message: Replication thread(s) for channel '%s' are already runnning.

  • Error number: 3084; Symbol: ER_REPLICA_CHANNEL_WAS_NOT_RUNNING; SQLSTATE: HY000

    Message: Replication thread(s) for channel '%s' are already stopped.

  • Error number: 3085; Symbol: ER_REPLICA_CHANNEL_SQL_THREAD_MUST_STOP; SQLSTATE: HY000

    Message: This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.

  • Error number: 3086; Symbol: ER_REPLICA_CHANNEL_SQL_SKIP_COUNTER; SQLSTATE: HY000

    Message: When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.

  • Error number: 3087; Symbol: ER_WRONG_FIELD_WITH_GROUP_V2; SQLSTATE: HY000

    Message: Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by

  • Error number: 3088; Symbol: ER_MIX_OF_GROUP_FUNC_AND_FIELDS_V2; SQLSTATE: HY000

    Message: In aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%s'; this is incompatible with sql_mode=only_full_group_by

  • Error number: 3089; Symbol: ER_WARN_DEPRECATED_SYSVAR_UPDATE; SQLSTATE: HY000

    Message: Updating '%s' is deprecated. It will be made read-only in a future release.

  • Error number: 3090; Symbol: ER_WARN_DEPRECATED_SQLMODE; SQLSTATE: HY000

    Message: Changing sql mode '%s' is deprecated. It will be removed in a future release.

  • Error number: 3091; Symbol: ER_CANNOT_LOG_PARTIAL_DROP_DATABASE_WITH_GTID; SQLSTATE: HY000

    Message: DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %s; (2) SET GTID_NEXT='%s'; (3) DROP DATABASE `%s`.

  • Error number: 3092; Symbol: ER_GROUP_REPLICATION_CONFIGURATION; SQLSTATE: HY000

    Message: The server is not configured properly to be an active member of the group. Please see more details on error log.

  • Error number: 3093; Symbol: ER_GROUP_REPLICATION_RUNNING; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed since the group is already running.

  • Error number: 3094; Symbol: ER_GROUP_REPLICATION_APPLIER_INIT_ERROR; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed as the applier module failed to start.

  • Error number: 3095; Symbol: ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT; SQLSTATE: HY000

    Message: The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.

  • Error number: 3096; Symbol: ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERROR; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.

  • Error number: 3097; Symbol: ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed as there was an error when joining the communication group.

  • Error number: 3098; Symbol: ER_BEFORE_DML_VALIDATION_ERROR; SQLSTATE: HY000

    Message: The table does not comply with the requirements by an external plugin.

  • Error number: 3099; Symbol: ER_PREVENTS_VARIABLE_WITHOUT_RBR; SQLSTATE: HY000

    Message: Cannot change the value of variable %s without binary log format as ROW.

  • Error number: 3100; Symbol: ER_RUN_HOOK_ERROR; SQLSTATE: HY000

    Message: Error on observer while running replication hook '%s'.

  • Error number: 3101; Symbol: ER_TRANSACTION_ROLLBACK_DURING_COMMIT; SQLSTATE: 40000

    Message: Plugin instructed the server to rollback the current transaction.

    When using Group Replication, this means that a transaction failed the group certification process, due to one or more members detecting a potential conflict, and was thus rolled back. See Group Replication.

  • Error number: 3102; Symbol: ER_GENERATED_COLUMN_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: Expression of generated column '%s' contains a disallowed function.

  • Error number: 3103; Symbol: ER_UNSUPPORTED_ALTER_INPLACE_ON_VIRTUAL_COLUMN; SQLSTATE: HY000

    Message: INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actions

  • Error number: 3104; Symbol: ER_WRONG_FK_OPTION_FOR_GENERATED_COLUMN; SQLSTATE: HY000

    Message: Cannot define foreign key with %s clause on a generated column.

  • Error number: 3105; Symbol: ER_NON_DEFAULT_VALUE_FOR_GENERATED_COLUMN; SQLSTATE: HY000

    Message: The value specified for generated column '%s' in table '%s' is not allowed.

  • Error number: 3106; Symbol: ER_UNSUPPORTED_ACTION_ON_GENERATED_COLUMN; SQLSTATE: HY000

    Message: '%s' is not supported for generated columns.

  • Error number: 3107; Symbol: ER_GENERATED_COLUMN_NON_PRIOR; SQLSTATE: HY000

    Message: Generated column can refer only to generated columns defined prior to it.

    To address this issue, change the table definition to define each generated column later than any generated columns to which it refers.

  • Error number: 3108; Symbol: ER_DEPENDENT_BY_GENERATED_COLUMN; SQLSTATE: HY000

    Message: Column '%s' has a generated column dependency.

    You cannot drop or rename a generated column if another column refers to it. You must either drop those columns as well, or redefine them not to refer to the generated column.

  • Error number: 3109; Symbol: ER_GENERATED_COLUMN_REF_AUTO_INC; SQLSTATE: HY000

    Message: Generated column '%s' cannot refer to auto-increment column.

  • Error number: 3110; Symbol: ER_FEATURE_NOT_AVAILABLE; SQLSTATE: HY000

    Message: The '%s' feature is not available; you need to remove '%s' or use MySQL built with '%s'

  • Error number: 3111; Symbol: ER_CANT_SET_GTID_MODE; SQLSTATE: HY000

    Message: SET @@GLOBAL.GTID_MODE = %s is not allowed because %s.

  • Error number: 3112; Symbol: ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF; SQLSTATE: HY000

    Message: The replication receiver thread%s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.

  • Error number: 3116; Symbol: ER_CANT_ENFORCE_GTID_CONSISTENCY_WITH_ONGOING_GTID_VIOLATING_TX; SQLSTATE: HY000

    Message: Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.

    ER_CANT_SET_ENFORCE_GTID_CONSISTENCY_ON_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS was renamed to ER_CANT_ENFORCE_GTID_CONSISTENCY_WITH_ONGOING_GTID_VIOLATING_TX.

  • Error number: 3117; Symbol: ER_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TX; SQLSTATE: HY000

    Message: There are ongoing transactions that violate GTID consistency.

    ER_SET_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS was renamed to ER_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TX.

  • Error number: 3118; Symbol: ER_ACCOUNT_HAS_BEEN_LOCKED; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s'. Account is locked.

    The account was locked with CREATE USER ... ACCOUNT LOCK or ALTER USER ... ACCOUNT LOCK. An administrator can unlock it with ALTER USER ... ACCOUNT UNLOCK.

  • Error number: 3119; Symbol: ER_WRONG_TABLESPACE_NAME; SQLSTATE: 42000

    Message: Incorrect tablespace name `%s`

  • Error number: 3120; Symbol: ER_TABLESPACE_IS_NOT_EMPTY; SQLSTATE: HY000

    Message: Tablespace `%s` is not empty.

  • Error number: 3121; Symbol: ER_WRONG_FILE_NAME; SQLSTATE: HY000

    Message: Incorrect File Name '%s'.

  • Error number: 3122; Symbol: ER_BOOST_GEOMETRY_INCONSISTENT_TURNS_EXCEPTION; SQLSTATE: HY000

    Message: Inconsistent intersection points.

  • Error number: 3123; Symbol: ER_WARN_OPTIMIZER_HINT_SYNTAX_ERROR; SQLSTATE: HY000

    Message: Optimizer hint syntax error

  • Error number: 3124; Symbol: ER_WARN_BAD_MAX_EXECUTION_TIME; SQLSTATE: HY000

    Message: Unsupported MAX_EXECUTION_TIME

  • Error number: 3125; Symbol: ER_WARN_UNSUPPORTED_MAX_EXECUTION_TIME; SQLSTATE: HY000

    Message: MAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements only

    The MAX_EXECUTION_TIME optimizer hint is supported only for SELECT statements.

  • Error number: 3126; Symbol: ER_WARN_CONFLICTING_HINT; SQLSTATE: HY000

    Message: Hint %s is ignored as conflicting/duplicated

  • Error number: 3127; Symbol: ER_WARN_UNKNOWN_QB_NAME; SQLSTATE: HY000

    Message: Query block name %s is not found for %s hint

  • Error number: 3128; Symbol: ER_UNRESOLVED_HINT_NAME; SQLSTATE: HY000

    Message: Unresolved name %s for %s hint

  • Error number: 3129; Symbol: ER_WARN_ON_MODIFYING_GTID_EXECUTED_TABLE; SQLSTATE: HY000

    Message: Please do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.

  • Error number: 3130; Symbol: ER_PLUGGABLE_PROTOCOL_COMMAND_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Command not supported by pluggable protocols

  • Error number: 3131; Symbol: ER_LOCKING_SERVICE_WRONG_NAME; SQLSTATE: 42000

    Message: Incorrect locking service lock name '%s'.

    A locking service name was specified as NULL, the empty string, or a string longer than 64 characters. Namespace and lock names must be non-NULL, nonempty, and no more than 64 characters long.

  • Error number: 3132; Symbol: ER_LOCKING_SERVICE_DEADLOCK; SQLSTATE: HY000

    Message: Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.

  • Error number: 3133; Symbol: ER_LOCKING_SERVICE_TIMEOUT; SQLSTATE: HY000

    Message: Service lock wait timeout exceeded.

  • Error number: 3134; Symbol: ER_GIS_MAX_POINTS_IN_GEOMETRY_OVERFLOWED; SQLSTATE: HY000

    Message: Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.

  • Error number: 3135; Symbol: ER_SQL_MODE_MERGED; SQLSTATE: HY000

    Message: 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.

  • Error number: 3136; Symbol: ER_VTOKEN_PLUGIN_TOKEN_MISMATCH; SQLSTATE: HY000

    Message: Version token mismatch for %.*s. Correct value %.*s

    The client has set its version_tokens_session system variable to the list of tokens it requires the server to match, but the server token list has at least one matching token name that has a value different from what the client requires. See Version Tokens.

  • Error number: 3137; Symbol: ER_VTOKEN_PLUGIN_TOKEN_NOT_FOUND; SQLSTATE: HY000

    Message: Version token %.*s not found.

    The client has set its version_tokens_session system variable to the list of tokens it requires the server to match, but the server token list is missing at least one of those tokens. See Version Tokens.

  • Error number: 3138; Symbol: ER_CANT_SET_VARIABLE_WHEN_OWNING_GTID; SQLSTATE: HY000

    Message: Variable %s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.

  • Error number: 3139; Symbol: ER_REPLICA_CHANNEL_OPERATION_NOT_ALLOWED; SQLSTATE: HY000

    Message: %s cannot be performed on channel '%s'.

  • Error number: 3140; Symbol: ER_INVALID_JSON_TEXT; SQLSTATE: 22032

    Message: Invalid JSON text: "%s" at position %u in value for column '%s'.

  • Error number: 3141; Symbol: ER_INVALID_JSON_TEXT_IN_PARAM; SQLSTATE: 22032

    Message: Invalid JSON text in argument %u to function %s: "%s" at position %u.%s

  • Error number: 3142; Symbol: ER_INVALID_JSON_BINARY_DATA; SQLSTATE: HY000

    Message: The JSON binary value contains invalid data.

  • Error number: 3143; Symbol: ER_INVALID_JSON_PATH; SQLSTATE: 42000

    Message: Invalid JSON path expression. The error is around character position %u.%s

  • Error number: 3144; Symbol: ER_INVALID_JSON_CHARSET; SQLSTATE: 22032

    Message: Cannot create a JSON value from a string with CHARACTER SET '%s'.

  • Error number: 3145; Symbol: ER_INVALID_JSON_CHARSET_IN_FUNCTION; SQLSTATE: 22032

    Message: Invalid JSON character data provided to function %s: '%s'; utf8 is required.

  • Error number: 3146; Symbol: ER_INVALID_TYPE_FOR_JSON; SQLSTATE: 22032

    Message: Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.

  • Error number: 3147; Symbol: ER_INVALID_CAST_TO_JSON; SQLSTATE: 22032

    Message: Cannot CAST value to JSON.

  • Error number: 3148; Symbol: ER_INVALID_JSON_PATH_CHARSET; SQLSTATE: 42000

    Message: A path expression must be encoded in the utf8 character set. The path expression '%s' is encoded in character set '%s'.

  • Error number: 3149; Symbol: ER_INVALID_JSON_PATH_WILDCARD; SQLSTATE: 42000

    Message: In this situation, path expressions may not contain the * and ** tokens or an array range.

  • Error number: 3150; Symbol: ER_JSON_VALUE_TOO_BIG; SQLSTATE: 22032

    Message: The JSON value is too big to be stored in a JSON column.

  • Error number: 3151; Symbol: ER_JSON_KEY_TOO_BIG; SQLSTATE: 22032

    Message: The JSON object contains a key name that is too long.

  • Error number: 3152; Symbol: ER_JSON_USED_AS_KEY; SQLSTATE: 42000

    Message: JSON column '%s' supports indexing only via generated columns on a specified JSON path.

  • Error number: 3153; Symbol: ER_JSON_VACUOUS_PATH; SQLSTATE: 42000

    Message: The path expression '$' is not allowed in this context.

  • Error number: 3154; Symbol: ER_JSON_BAD_ONE_OR_ALL_ARG; SQLSTATE: 42000

    Message: The oneOrAll argument to %s may take these values: 'one' or 'all'.

  • Error number: 3155; Symbol: ER_NUMERIC_JSON_VALUE_OUT_OF_RANGE; SQLSTATE: 22003

    Message: Out of range JSON value for CAST to %s%s from column %s at row %ld

  • Error number: 3156; Symbol: ER_INVALID_JSON_VALUE_FOR_CAST; SQLSTATE: 22018

    Message: Invalid JSON value for CAST to %s%s from column %s at row %ld

  • Error number: 3157; Symbol: ER_JSON_DOCUMENT_TOO_DEEP; SQLSTATE: 22032

    Message: The JSON document exceeds the maximum depth.

  • Error number: 3158; Symbol: ER_JSON_DOCUMENT_NULL_KEY; SQLSTATE: 22032

    Message: JSON documents may not contain NULL member names.

  • Error number: 3159; Symbol: ER_SECURE_TRANSPORT_REQUIRED; SQLSTATE: HY000

    Message: Connections using insecure transport are prohibited while --require_secure_transport=ON.

    With the require_secure_transport system variable, clients can connect only using secure transports. Qualifying connections are those using SSL, a Unix socket file, or shared memory.

  • Error number: 3160; Symbol: ER_NO_SECURE_TRANSPORTS_CONFIGURED; SQLSTATE: HY000

    Message: No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.

    The require_secure_transport system variable cannot be enabled if the server does not support at least one secure transport. Configure the server with the required SSL keys/certificates to enable SSL connections, or enable the shared_memory system variable to enable shared-memory connections.

  • Error number: 3161; Symbol: ER_DISABLED_STORAGE_ENGINE; SQLSTATE: HY000

    Message: Storage engine %s is disabled (Table creation is disallowed).

    An attempt was made to create a table or tablespace using a storage engine listed in the value of the disabled_storage_engines system variable, or to change an existing table or tablespace to such an engine. Choose a different storage engine.

  • Error number: 3162; Symbol: ER_USER_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Authorization ID %s does not exist.

  • Error number: 3163; Symbol: ER_USER_ALREADY_EXISTS; SQLSTATE: HY000

    Message: Authorization ID %s already exists.

  • Error number: 3164; Symbol: ER_AUDIT_API_ABORT; SQLSTATE: HY000

    Message: Aborted by Audit API ('%s';%d).

    This error indicates that an audit plugin terminated execution of an event. The message typically indicates the event subclass name and a numeric status value.

  • Error number: 3165; Symbol: ER_INVALID_JSON_PATH_ARRAY_CELL; SQLSTATE: 42000

    Message: A path expression is not a path to a cell in an array.

  • Error number: 3166; Symbol: ER_BUFPOOL_RESIZE_INPROGRESS; SQLSTATE: HY000

    Message: Another buffer pool resize is already in progress.

  • Error number: 3167; Symbol: ER_FEATURE_DISABLED_SEE_DOC; SQLSTATE: HY000

    Message: The '%s' feature is disabled; see the documentation for '%s'

  • Error number: 3168; Symbol: ER_SERVER_ISNT_AVAILABLE; SQLSTATE: HY000

    Message: Server isn't available

  • Error number: 3169; Symbol: ER_SESSION_WAS_KILLED; SQLSTATE: HY000

    Message: Session was killed

  • Error number: 3170; Symbol: ER_CAPACITY_EXCEEDED; SQLSTATE: HY000

    Message: Memory capacity of %llu bytes for '%s' exceeded. %s

  • Error number: 3171; Symbol: ER_CAPACITY_EXCEEDED_IN_RANGE_OPTIMIZER; SQLSTATE: HY000

    Message: Range optimization was not done for this query.

  • Error number: 3173; Symbol: ER_CANT_WAIT_FOR_EXECUTED_GTID_SET_WHILE_OWNING_A_GTID; SQLSTATE: HY000

    Message: The client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.

  • Error number: 3174; Symbol: ER_CANNOT_ADD_FOREIGN_BASE_COL_VIRTUAL; SQLSTATE: HY000

    Message: Cannot add foreign key on the base column of indexed virtual column.

  • Error number: 3175; Symbol: ER_CANNOT_CREATE_VIRTUAL_INDEX_CONSTRAINT; SQLSTATE: HY000

    Message: Cannot create index on virtual column whose base column has foreign constraint.

  • Error number: 3176; Symbol: ER_ERROR_ON_MODIFYING_GTID_EXECUTED_TABLE; SQLSTATE: HY000

    Message: Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.

  • Error number: 3177; Symbol: ER_LOCK_REFUSED_BY_ENGINE; SQLSTATE: HY000

    Message: Lock acquisition refused by storage engine.

  • Error number: 3178; Symbol: ER_UNSUPPORTED_ALTER_ONLINE_ON_VIRTUAL_COLUMN; SQLSTATE: HY000

    Message: ADD COLUMN col...VIRTUAL, ADD INDEX(col)

  • Error number: 3179; Symbol: ER_MASTER_KEY_ROTATION_NOT_SUPPORTED_BY_SE; SQLSTATE: HY000

    Message: Master key rotation is not supported by storage engine.

  • Error number: 3181; Symbol: ER_MASTER_KEY_ROTATION_BINLOG_FAILED; SQLSTATE: HY000

    Message: Write to binlog failed. However, master key rotation has been completed successfully.

  • Error number: 3182; Symbol: ER_MASTER_KEY_ROTATION_SE_UNAVAILABLE; SQLSTATE: HY000

    Message: Storage engine is not available.

  • Error number: 3183; Symbol: ER_TABLESPACE_CANNOT_ENCRYPT; SQLSTATE: HY000

    Message: This tablespace can't be encrypted.

  • Error number: 3184; Symbol: ER_INVALID_ENCRYPTION_OPTION; SQLSTATE: HY000

    Message: Invalid encryption option.

  • Error number: 3185; Symbol: ER_CANNOT_FIND_KEY_IN_KEYRING; SQLSTATE: HY000

    Message: Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.

  • Error number: 3186; Symbol: ER_CAPACITY_EXCEEDED_IN_PARSER; SQLSTATE: HY000

    Message: Parser bailed out for this query.

  • Error number: 3187; Symbol: ER_UNSUPPORTED_ALTER_ENCRYPTION_INPLACE; SQLSTATE: HY000

    Message: Cannot alter encryption attribute by inplace algorithm.

  • Error number: 3188; Symbol: ER_KEYRING_UDF_KEYRING_SERVICE_ERROR; SQLSTATE: HY000

    Message: Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.

  • Error number: 3189; Symbol: ER_USER_COLUMN_OLD_LENGTH; SQLSTATE: HY000

    Message: It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.

  • Error number: 3190; Symbol: ER_CANT_RESET_SOURCE; SQLSTATE: HY000

    Message: RESET BINARY LOGS AND GTIDS is not allowed because %s.

  • Error number: 3191; Symbol: ER_GROUP_REPLICATION_MAX_GROUP_SIZE; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed since the group already has 9 members.

  • Error number: 3192; Symbol: ER_CANNOT_ADD_FOREIGN_BASE_COL_STORED; SQLSTATE: HY000

    Message: Cannot add foreign key on the base column of stored column.

  • Error number: 3193; Symbol: ER_TABLE_REFERENCED; SQLSTATE: HY000

    Message: Cannot complete the operation because table is referenced by another connection.

  • Error number: 3197; Symbol: ER_XA_RETRY; SQLSTATE: HY000

    Message: The resource manager is not able to commit the transaction branch at this time. Please retry later.

  • Error number: 3198; Symbol: ER_KEYRING_AWS_UDF_AWS_KMS_ERROR; SQLSTATE: HY000

    Message: Function %s failed due to: %s.

  • Error number: 3199; Symbol: ER_BINLOG_UNSAFE_XA; SQLSTATE: HY000

    Message: Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.

  • Error number: 3200; Symbol: ER_UDF_ERROR; SQLSTATE: HY000

    Message: %s UDF failed; %s

  • Error number: 3201; Symbol: ER_KEYRING_MIGRATION_FAILURE; SQLSTATE: HY000

    Message: Can not perform keyring migration : %s

  • Error number: 3202; Symbol: ER_KEYRING_ACCESS_DENIED_ERROR; SQLSTATE: 42000

    Message: Access denied; you need %s privileges for this operation

  • Error number: 3203; Symbol: ER_KEYRING_MIGRATION_STATUS; SQLSTATE: HY000

    Message: Keyring migration %s.

  • Error number: 3218; Symbol: ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_VALUE; SQLSTATE: HY000

    Message: Invalid "max_array_length" argument value.

  • Error number: 3231; Symbol: ER_WRITE_SET_EXCEEDS_LIMIT; SQLSTATE: HY000

    Message: The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.

  • Error number: 3235; Symbol: ER_AES_INVALID_KDF_NAME; SQLSTATE: HY000

    Message: KDF method name is not valid. Please use hkdf or pbkdf2_hmac method name

  • Error number: 3236; Symbol: ER_AES_INVALID_KDF_ITERATIONS; SQLSTATE: HY000

    Message: For KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535

  • Error number: 3237; Symbol: WARN_AES_KEY_SIZE; SQLSTATE: HY000

    Message: AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.

  • Error number: 3238; Symbol: ER_AES_INVALID_KDF_OPTION_SIZE; SQLSTATE: HY000

    Message: KDF option size is invalid, please provide valid size < %d bytes and not NULL

  • Error number: 3500; Symbol: ER_UNSUPPORT_COMPRESSED_TEMPORARY_TABLE; SQLSTATE: HY000

    Message: CREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.

  • Error number: 3501; Symbol: ER_ACL_OPERATION_FAILED; SQLSTATE: HY000

    Message: The ACL operation failed due to the following error from SE: errcode %d - %s

  • Error number: 3502; Symbol: ER_UNSUPPORTED_INDEX_ALGORITHM; SQLSTATE: HY000

    Message: This storage engine does not support the %s index algorithm, storage engine default was used instead.

  • Error number: 3503; Symbol: ER_NO_SUCH_DB; SQLSTATE: 42Y07

    Message: Database '%s' doesn't exist

  • Error number: 3504; Symbol: ER_TOO_BIG_ENUM; SQLSTATE: HY000

    Message: Too many enumeration values for column %s.

  • Error number: 3505; Symbol: ER_TOO_LONG_SET_ENUM_VALUE; SQLSTATE: HY000

    Message: Too long enumeration/set value for column %s.

  • Error number: 3506; Symbol: ER_INVALID_DD_OBJECT; SQLSTATE: HY000

    Message: %s dictionary object is invalid. (%s)

  • Error number: 3507; Symbol: ER_UPDATING_DD_TABLE; SQLSTATE: HY000

    Message: Failed to update %s dictionary object.

  • Error number: 3508; Symbol: ER_INVALID_DD_OBJECT_ID; SQLSTATE: HY000

    Message: Dictionary object id (%lu) does not exist.

  • Error number: 3509; Symbol: ER_INVALID_DD_OBJECT_NAME; SQLSTATE: HY000

    Message: Dictionary object name '%s' is invalid. (%s)

  • Error number: 3510; Symbol: ER_TABLESPACE_MISSING_WITH_NAME; SQLSTATE: HY000

    Message: Tablespace %s doesn't exist.

  • Error number: 3511; Symbol: ER_TOO_LONG_ROUTINE_COMMENT; SQLSTATE: HY000

    Message: Comment for routine '%s' is too long (max = %lu)

  • Error number: 3512; Symbol: ER_SP_LOAD_FAILED; SQLSTATE: HY000

    Message: Failed to load routine '%s'.

  • Error number: 3513; Symbol: ER_INVALID_BITWISE_OPERANDS_SIZE; SQLSTATE: HY000

    Message: Binary operands of bitwise operators must be of equal length

  • Error number: 3514; Symbol: ER_INVALID_BITWISE_AGGREGATE_OPERANDS_SIZE; SQLSTATE: HY000

    Message: Aggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() function

  • Error number: 3515; Symbol: ER_WARN_UNSUPPORTED_HINT; SQLSTATE: HY000

    Message: Hints aren't supported in %s

  • Error number: 3516; Symbol: ER_UNEXPECTED_GEOMETRY_TYPE; SQLSTATE: 22S01

    Message: %s value is a geometry of unexpected type %s in %s.

  • Error number: 3517; Symbol: ER_SRS_PARSE_ERROR; SQLSTATE: SR002

    Message: Can't parse the spatial reference system definition of SRID %u.

  • Error number: 3518; Symbol: ER_SRS_PROJ_PARAMETER_MISSING; SQLSTATE: SR003

    Message: The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.

  • Error number: 3519; Symbol: ER_WARN_SRS_NOT_FOUND; SQLSTATE: 01000

    Message: There's no spatial reference system with SRID %u.

  • Error number: 3520; Symbol: ER_SRS_NOT_CARTESIAN; SQLSTATE: 22S00

    Message: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.

  • Error number: 3521; Symbol: ER_SRS_NOT_CARTESIAN_UNDEFINED; SQLSTATE: SR001

    Message: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.

  • Error number: 3522; Symbol: ER_PK_INDEX_CANT_BE_INVISIBLE; SQLSTATE: HY000

    Message: A primary key index cannot be invisible

  • Error number: 3523; Symbol: ER_UNKNOWN_AUTHID; SQLSTATE: HY000

    Message: Unknown authorization ID `%s`@`%s`

  • Error number: 3524; Symbol: ER_FAILED_ROLE_GRANT; SQLSTATE: HY000

    Message: Failed to grant %s` to %s

  • Error number: 3525; Symbol: ER_OPEN_ROLE_TABLES; SQLSTATE: HY000

    Message: Failed to open the security system tables

  • Error number: 3526; Symbol: ER_FAILED_DEFAULT_ROLES; SQLSTATE: HY000

    Message: Failed to set default roles

  • Error number: 3527; Symbol: ER_COMPONENTS_NO_SCHEME; SQLSTATE: HY000

    Message: Cannot find schema in specified URN: '%s'.

  • Error number: 3528; Symbol: ER_COMPONENTS_NO_SCHEME_SERVICE; SQLSTATE: HY000

    Message: Cannot acquire scheme load service implementation for schema '%s' in specified URN: '%s'.

  • Error number: 3529; Symbol: ER_COMPONENTS_CANT_LOAD; SQLSTATE: HY000

    Message: Cannot load component from specified URN: '%s'.

  • Error number: 3530; Symbol: ER_ROLE_NOT_GRANTED; SQLSTATE: HY000

    Message: `%s`@`%s` is not granted to `%s`@`%s`

  • Error number: 3531; Symbol: ER_FAILED_REVOKE_ROLE; SQLSTATE: HY000

    Message: Could not revoke role from `%s`@`%s`

  • Error number: 3532; Symbol: ER_RENAME_ROLE; SQLSTATE: HY000

    Message: Renaming of a role identifier is forbidden

  • Error number: 3533; Symbol: ER_COMPONENTS_CANT_ACQUIRE_SERVICE_IMPLEMENTATION; SQLSTATE: HY000

    Message: Cannot acquire specified service implementation: '%s'.

  • Error number: 3534; Symbol: ER_COMPONENTS_CANT_SATISFY_DEPENDENCY; SQLSTATE: HY000

    Message: Cannot satisfy dependency for service '%s' required by component '%s'.

  • Error number: 3535; Symbol: ER_COMPONENTS_LOAD_CANT_REGISTER_SERVICE_IMPLEMENTATION; SQLSTATE: HY000

    Message: Cannot register service implementation '%s' provided by component '%s'.

  • Error number: 3536; Symbol: ER_COMPONENTS_LOAD_CANT_INITIALIZE; SQLSTATE: HY000

    Message: Initialization method provided by component '%s' failed.

  • Error number: 3537; Symbol: ER_COMPONENTS_UNLOAD_NOT_LOADED; SQLSTATE: HY000

    Message: Component specified by URN '%s' to unload has not been loaded before.

  • Error number: 3538; Symbol: ER_COMPONENTS_UNLOAD_CANT_DEINITIALIZE; SQLSTATE: HY000

    Message: De-initialization method provided by component '%s' failed.

  • Error number: 3539; Symbol: ER_COMPONENTS_CANT_RELEASE_SERVICE; SQLSTATE: HY000

    Message: Release of previously acquired service implementation failed.

  • Error number: 3540; Symbol: ER_COMPONENTS_UNLOAD_CANT_UNREGISTER_SERVICE; SQLSTATE: HY000

    Message: Unregistration of service implementation '%s' provided by component '%s' failed during unloading of the component.

  • Error number: 3541; Symbol: ER_COMPONENTS_CANT_UNLOAD; SQLSTATE: HY000

    Message: Cannot unload component from specified URN: '%s'.

  • Error number: 3542; Symbol: ER_WARN_UNLOAD_THE_NOT_PERSISTED; SQLSTATE: HY000

    Message: The Persistent Dynamic Loader was used to unload a component '%s', but it was not used to load that component before.

  • Error number: 3543; Symbol: ER_COMPONENT_TABLE_INCORRECT; SQLSTATE: HY000

    Message: The mysql.component table is missing or has an incorrect definition.

  • Error number: 3544; Symbol: ER_COMPONENT_MANIPULATE_ROW_FAILED; SQLSTATE: HY000

    Message: Failed to manipulate component '%s' persistence data. Error code %d from storage engine.

  • Error number: 3545; Symbol: ER_COMPONENTS_UNLOAD_DUPLICATE_IN_GROUP; SQLSTATE: HY000

    Message: The component with specified URN: '%s' was specified in group more than once.

  • Error number: 3546; Symbol: ER_CANT_SET_GTID_PURGED_DUE_SETS_CONSTRAINTS; SQLSTATE: HY000

    Message: @@GLOBAL.GTID_PURGED cannot be changed: %s

  • Error number: 3547; Symbol: ER_CANNOT_LOCK_USER_MANAGEMENT_CACHES; SQLSTATE: HY000

    Message: Can not lock user management caches for processing.

  • Error number: 3548; Symbol: ER_SRS_NOT_FOUND; SQLSTATE: SR001

    Message: There's no spatial reference system with SRID %u.

  • Error number: 3549; Symbol: ER_VARIABLE_NOT_PERSISTED; SQLSTATE: HY000

    Message: Variables cannot be persisted. Please retry.

  • Error number: 3550; Symbol: ER_IS_QUERY_INVALID_CLAUSE; SQLSTATE: HY000

    Message: Information schema queries do not support the '%s' clause.

  • Error number: 3551; Symbol: ER_UNABLE_TO_STORE_STATISTICS; SQLSTATE: HY000

    Message: Unable to store dynamic %s statistics into data dictionary.

  • Error number: 3552; Symbol: ER_NO_SYSTEM_SCHEMA_ACCESS; SQLSTATE: HY000

    Message: Access to system schema '%s' is rejected.

  • Error number: 3553; Symbol: ER_NO_SYSTEM_TABLESPACE_ACCESS; SQLSTATE: HY000

    Message: Access to system tablespace '%s' is rejected.

  • Error number: 3554; Symbol: ER_NO_SYSTEM_TABLE_ACCESS; SQLSTATE: HY000

    Message: Access to %s '%s.%s' is rejected.

  • Error number: 3555; Symbol: ER_NO_SYSTEM_TABLE_ACCESS_FOR_DICTIONARY_TABLE; SQLSTATE: HY000

    Message: data dictionary table

  • Error number: 3556; Symbol: ER_NO_SYSTEM_TABLE_ACCESS_FOR_SYSTEM_TABLE; SQLSTATE: HY000

    Message: system table

  • Error number: 3557; Symbol: ER_NO_SYSTEM_TABLE_ACCESS_FOR_TABLE; SQLSTATE: HY000

    Message: table

  • Error number: 3558; Symbol: ER_INVALID_OPTION_KEY; SQLSTATE: 22023

    Message: Invalid option key '%s' in function %s.

  • Error number: 3559; Symbol: ER_INVALID_OPTION_VALUE; SQLSTATE: 22023

    Message: Invalid value '%s' for option '%s' in function '%s'.

  • Error number: 3560; Symbol: ER_INVALID_OPTION_KEY_VALUE_PAIR; SQLSTATE: 22023

    Message: The string '%s' is not a valid key %c value pair in function %s.

  • Error number: 3561; Symbol: ER_INVALID_OPTION_START_CHARACTER; SQLSTATE: 22023

    Message: The options argument in function %s starts with the invalid character '%c'.

  • Error number: 3562; Symbol: ER_INVALID_OPTION_END_CHARACTER; SQLSTATE: 22023

    Message: The options argument in function %s ends with the invalid character '%c'.

  • Error number: 3563; Symbol: ER_INVALID_OPTION_CHARACTERS; SQLSTATE: 22023

    Message: The options argument in function %s contains the invalid character sequence '%s'.

  • Error number: 3564; Symbol: ER_DUPLICATE_OPTION_KEY; SQLSTATE: 22023

    Message: Duplicate option key '%s' in funtion '%s'.

  • Error number: 3565; Symbol: ER_WARN_SRS_NOT_FOUND_AXIS_ORDER; SQLSTATE: 01000

    Message: There's no spatial reference system with SRID %u. The axis order is unknown.

  • Error number: 3566; Symbol: ER_NO_ACCESS_TO_NATIVE_FCT; SQLSTATE: HY000

    Message: Access to native function '%s' is rejected.

  • Error number: 3567; Symbol: ER_RESET_SOURCE_TO_VALUE_OUT_OF_RANGE; SQLSTATE: HY000

    Message: The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.

  • Error number: 3568; Symbol: ER_UNRESOLVED_TABLE_LOCK; SQLSTATE: HY000

    Message: Unresolved table name %s in locking clause.

  • Error number: 3569; Symbol: ER_DUPLICATE_TABLE_LOCK; SQLSTATE: HY000

    Message: Table %s appears in multiple locking clauses.

  • Error number: 3570; Symbol: ER_BINLOG_UNSAFE_SKIP_LOCKED; SQLSTATE: HY000

    Message: Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.

  • Error number: 3571; Symbol: ER_BINLOG_UNSAFE_NOWAIT; SQLSTATE: HY000

    Message: Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.

  • Error number: 3572; Symbol: ER_LOCK_NOWAIT; SQLSTATE: HY000

    Message: Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.

  • Error number: 3573; Symbol: ER_CTE_RECURSIVE_REQUIRES_UNION; SQLSTATE: HY000

    Message: Recursive Common Table Expression '%s' should contain a UNION

  • Error number: 3574; Symbol: ER_CTE_RECURSIVE_REQUIRES_NONRECURSIVE_FIRST; SQLSTATE: HY000

    Message: Recursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive ones

  • Error number: 3575; Symbol: ER_CTE_RECURSIVE_FORBIDS_AGGREGATION; SQLSTATE: HY000

    Message: Recursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query block

  • Error number: 3576; Symbol: ER_CTE_RECURSIVE_FORBIDDEN_JOIN_ORDER; SQLSTATE: HY000

    Message: In recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hints

  • Error number: 3577; Symbol: ER_CTE_RECURSIVE_REQUIRES_SINGLE_REFERENCE; SQLSTATE: HY000

    Message: In recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery

  • Error number: 3578; Symbol: ER_SWITCH_TMP_ENGINE; SQLSTATE: HY000

    Message: '%s' requires @@internal_tmp_disk_storage_engine=InnoDB

  • Error number: 3579; Symbol: ER_WINDOW_NO_SUCH_WINDOW; SQLSTATE: HY000

    Message: Window name '%s' is not defined.

  • Error number: 3580; Symbol: ER_WINDOW_CIRCULARITY_IN_WINDOW_GRAPH; SQLSTATE: HY000

    Message: There is a circularity in the window dependency graph.

  • Error number: 3581; Symbol: ER_WINDOW_NO_CHILD_PARTITIONING; SQLSTATE: HY000

    Message: A window which depends on another cannot define partitioning.

  • Error number: 3582; Symbol: ER_WINDOW_NO_INHERIT_FRAME; SQLSTATE: HY000

    Message: Window '%s' has a frame definition, so cannot be referenced by another window.

  • Error number: 3583; Symbol: ER_WINDOW_NO_REDEFINE_ORDER_BY; SQLSTATE: HY000

    Message: Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.

  • Error number: 3584; Symbol: ER_WINDOW_FRAME_START_ILLEGAL; SQLSTATE: HY000

    Message: Window '%s': frame start cannot be UNBOUNDED FOLLOWING.

  • Error number: 3585; Symbol: ER_WINDOW_FRAME_END_ILLEGAL; SQLSTATE: HY000

    Message: Window '%s': frame end cannot be UNBOUNDED PRECEDING.

  • Error number: 3586; Symbol: ER_WINDOW_FRAME_ILLEGAL; SQLSTATE: HY000

    Message: Window '%s': frame start or end is negative, NULL or of non-integral type

  • Error number: 3587; Symbol: ER_WINDOW_RANGE_FRAME_ORDER_TYPE; SQLSTATE: HY000

    Message: Window '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal type

  • Error number: 3588; Symbol: ER_WINDOW_RANGE_FRAME_TEMPORAL_TYPE; SQLSTATE: HY000

    Message: Window '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.

  • Error number: 3589; Symbol: ER_WINDOW_RANGE_FRAME_NUMERIC_TYPE; SQLSTATE: HY000

    Message: Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.

  • Error number: 3590; Symbol: ER_WINDOW_RANGE_BOUND_NOT_CONSTANT; SQLSTATE: HY000

    Message: Window '%s' has a non-constant frame bound.

  • Error number: 3591; Symbol: ER_WINDOW_DUPLICATE_NAME; SQLSTATE: HY000

    Message: Window '%s' is defined twice.

  • Error number: 3592; Symbol: ER_WINDOW_ILLEGAL_ORDER_BY; SQLSTATE: HY000

    Message: Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.

  • Error number: 3593; Symbol: ER_WINDOW_INVALID_WINDOW_FUNC_USE; SQLSTATE: HY000

    Message: You cannot use the window function '%s' in this context.'

  • Error number: 3594; Symbol: ER_WINDOW_INVALID_WINDOW_FUNC_ALIAS_USE; SQLSTATE: HY000

    Message: You cannot use the alias '%s' of an expression containing a window function in this context.'

  • Error number: 3595; Symbol: ER_WINDOW_NESTED_WINDOW_FUNC_USE_IN_WINDOW_SPEC; SQLSTATE: HY000

    Message: You cannot nest a window function in the specification of window '%s'.

  • Error number: 3596; Symbol: ER_WINDOW_ROWS_INTERVAL_USE; SQLSTATE: HY000

    Message: Window '%s': INTERVAL can only be used with RANGE frames.

  • Error number: 3597; Symbol: ER_WINDOW_NO_GROUP_ORDER_UNUSED; SQLSTATE: HY000

    Message: ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BY

  • Error number: 3598; Symbol: ER_WINDOW_EXPLAIN_JSON; SQLSTATE: HY000

    Message: To get information about window functions use EXPLAIN FORMAT=JSON

  • Error number: 3599; Symbol: ER_WINDOW_FUNCTION_IGNORES_FRAME; SQLSTATE: HY000

    Message: Window function '%s' ignores the frame clause of window '%s' and aggregates over the whole partition

  • Error number: 3600; Symbol: ER_WL9236_NOW_UNUSED; SQLSTATE: HY000

    Message: Windowing requires @@internal_tmp_mem_storage_engine=TempTable.

  • Error number: 3601; Symbol: ER_INVALID_NO_OF_ARGS; SQLSTATE: HY000

    Message: Too many arguments for function %s: %lu; maximum allowed is %s.

  • Error number: 3602; Symbol: ER_FIELD_IN_GROUPING_NOT_GROUP_BY; SQLSTATE: HY000

    Message: Argument #%u of GROUPING function is not in GROUP BY

  • Error number: 3603; Symbol: ER_TOO_LONG_TABLESPACE_COMMENT; SQLSTATE: HY000

    Message: Comment for tablespace '%s' is too long (max = %lu)

  • Error number: 3604; Symbol: ER_ENGINE_CANT_DROP_TABLE; SQLSTATE: HY000

    Message: Storage engine can't drop table '%s'

  • Error number: 3605; Symbol: ER_ENGINE_CANT_DROP_MISSING_TABLE; SQLSTATE: HY000

    Message: Storage engine can't drop table '%s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.

  • Error number: 3606; Symbol: ER_TABLESPACE_DUP_FILENAME; SQLSTATE: HY000

    Message: Duplicate file name for tablespace '%s'

  • Error number: 3607; Symbol: ER_DB_DROP_RMDIR2; SQLSTATE: HY000

    Message: Problem while dropping database. Can't remove database directory (%s). Please remove it manually.

  • Error number: 3608; Symbol: ER_IMP_NO_FILES_MATCHED; SQLSTATE: HY000

    Message: No SDI files matched the pattern '%s'

  • Error number: 3609; Symbol: ER_IMP_SCHEMA_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Schema '%s', referenced in SDI, does not exist.

  • Error number: 3610; Symbol: ER_IMP_TABLE_ALREADY_EXISTS; SQLSTATE: HY000

    Message: Table '%s.%s', referenced in SDI, already exists.

  • Error number: 3611; Symbol: ER_IMP_INCOMPATIBLE_MYSQLD_VERSION; SQLSTATE: HY000

    Message: Imported mysqld_version (%llu) is not compatible with current (%llu)

  • Error number: 3612; Symbol: ER_IMP_INCOMPATIBLE_DD_VERSION; SQLSTATE: HY000

    Message: Imported dd version (%u) is not compatible with current (%u)

  • Error number: 3613; Symbol: ER_IMP_INCOMPATIBLE_SDI_VERSION; SQLSTATE: HY000

    Message: Imported sdi version (%llu) is not compatible with current (%llu)

  • Error number: 3614; Symbol: ER_WARN_INVALID_HINT; SQLSTATE: HY000

    Message: Invalid number of arguments for hint %s

  • Error number: 3615; Symbol: ER_VAR_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Variable %s does not exist in persisted config file

  • Error number: 3616; Symbol: ER_LONGITUDE_OUT_OF_RANGE; SQLSTATE: 22S02

    Message: Longitude %f is out of range in function %s. It must be within (%f, %f].

  • Error number: 3617; Symbol: ER_LATITUDE_OUT_OF_RANGE; SQLSTATE: 22S03

    Message: Latitude %f is out of range in function %s. It must be within [%f, %f].

  • Error number: 3618; Symbol: ER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS; SQLSTATE: 22S00

    Message: %s(%s) has not been implemented for geographic spatial reference systems.

  • Error number: 3619; Symbol: ER_ILLEGAL_PRIVILEGE_LEVEL; SQLSTATE: HY000

    Message: Illegal privilege level specified for %s

  • Error number: 3620; Symbol: ER_NO_SYSTEM_VIEW_ACCESS; SQLSTATE: HY000

    Message: Access to system view INFORMATION_SCHEMA.'%s' is rejected.

  • Error number: 3621; Symbol: ER_COMPONENT_FILTER_FLABBERGASTED; SQLSTATE: HY000

    Message: The log-filter component "%s" got confused at "%s" ...

  • Error number: 3622; Symbol: ER_PART_EXPR_TOO_LONG; SQLSTATE: HY000

    Message: Partitioning expression is too long.

  • Error number: 3623; Symbol: ER_UDF_DROP_DYNAMICALLY_REGISTERED; SQLSTATE: HY000

    Message: DROP FUNCTION can't drop a dynamically registered user defined function

  • Error number: 3624; Symbol: ER_UNABLE_TO_STORE_COLUMN_STATISTICS; SQLSTATE: HY000

    Message: Unable to store column statistics for column '%s' in table '%s'.'%s'

  • Error number: 3625; Symbol: ER_UNABLE_TO_UPDATE_COLUMN_STATISTICS; SQLSTATE: HY000

    Message: Unable to update column statistics for column '%s' in table '%s'.'%s'

  • Error number: 3626; Symbol: ER_UNABLE_TO_DROP_COLUMN_STATISTICS; SQLSTATE: HY000

    Message: Unable to remove column statistics for column '%s' in table '%s'.'%s'

  • Error number: 3627; Symbol: ER_UNABLE_TO_BUILD_HISTOGRAM; SQLSTATE: HY000

    Message: Unable to build histogram statistics for column '%s' in table '%s'.'%s'

  • Error number: 3628; Symbol: ER_MANDATORY_ROLE; SQLSTATE: HY000

    Message: The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.

  • Error number: 3629; Symbol: ER_MISSING_TABLESPACE_FILE; SQLSTATE: HY000

    Message: Tablespace '%s' does not have a file named '%s'

  • Error number: 3630; Symbol: ER_PERSIST_ONLY_ACCESS_DENIED_ERROR; SQLSTATE: 42000

    Message: Access denied; you need %s privileges for this operation

  • Error number: 3631; Symbol: ER_CMD_NEED_SUPER; SQLSTATE: HY000

    Message: You need the SUPER privilege for command '%s'

  • Error number: 3632; Symbol: ER_PATH_IN_DATADIR; SQLSTATE: HY000

    Message: Path is within the current data directory '%s'

  • Error number: 3633; Symbol: ER_CLONE_DDL_IN_PROGRESS; SQLSTATE: HY000

    Message: Concurrent DDL is performed during clone operation. Please try again.

  • Error number: 3634; Symbol: ER_CLONE_TOO_MANY_CONCURRENT_CLONES; SQLSTATE: HY000

    Message: Too many concurrent clone operations. Maximum allowed - %d.

  • Error number: 3635; Symbol: ER_APPLIER_LOG_EVENT_VALIDATION_ERROR; SQLSTATE: HY000

    Message: The table in transaction %s does not comply with the requirements by an external plugin.

  • Error number: 3636; Symbol: ER_CTE_MAX_RECURSION_DEPTH; SQLSTATE: HY000

    Message: Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.

  • Error number: 3637; Symbol: ER_NOT_HINT_UPDATABLE_VARIABLE; SQLSTATE: HY000

    Message: Variable %s cannot be set using SET_VAR hint.

  • Error number: 3638; Symbol: ER_CREDENTIALS_CONTRADICT_TO_HISTORY; SQLSTATE: HY000

    Message: Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policy

  • Error number: 3639; Symbol: ER_WARNING_PASSWORD_HISTORY_CLAUSES_VOID; SQLSTATE: HY000

    Message: Non-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password history

  • Error number: 3640; Symbol: ER_CLIENT_DOES_NOT_SUPPORT; SQLSTATE: HY000

    Message: The client doesn't support %s

  • Error number: 3641; Symbol: ER_I_S_SKIPPED_TABLESPACE; SQLSTATE: HY000

    Message: Tablespace '%s' was skipped since its definition is being modified by concurrent DDL statement

  • Error number: 3642; Symbol: ER_TABLESPACE_ENGINE_MISMATCH; SQLSTATE: HY000

    Message: Engine '%s' does not match stored engine '%s' for tablespace '%s'

  • Error number: 3643; Symbol: ER_WRONG_SRID_FOR_COLUMN; SQLSTATE: HY000

    Message: The SRID of the geometry does not match the SRID of the column '%s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.

  • Error number: 3644; Symbol: ER_CANNOT_ALTER_SRID_DUE_TO_INDEX; SQLSTATE: HY000

    Message: The SRID specification on the column '%s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.

  • Error number: 3645; Symbol: ER_WARN_BINLOG_PARTIAL_UPDATES_DISABLED; SQLSTATE: HY000

    Message: When %s, the option binlog_row_value_options=%s will be ignored and updates will be written in full format to binary log.

  • Error number: 3647; Symbol: ER_WARN_BINLOG_PARTIAL_UPDATES_SUGGESTS_PARTIAL_IMAGES; SQLSTATE: HY000

    Message: When %s, the option binlog_row_value_options=%s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.

  • Error number: 3648; Symbol: ER_COULD_NOT_APPLY_JSON_DIFF; SQLSTATE: HY000

    Message: Could not apply JSON diff in table %.*s, column %s.

  • Error number: 3649; Symbol: ER_CORRUPTED_JSON_DIFF; SQLSTATE: HY000

    Message: Corrupted JSON diff for table %.*s, column %s.

  • Error number: 3650; Symbol: ER_RESOURCE_GROUP_EXISTS; SQLSTATE: HY000

    Message: Resource Group '%s' exists

  • Error number: 3651; Symbol: ER_RESOURCE_GROUP_NOT_EXISTS; SQLSTATE: HY000

    Message: Resource Group '%s' does not exist.

  • Error number: 3652; Symbol: ER_INVALID_VCPU_ID; SQLSTATE: HY000

    Message: Invalid cpu id %u

  • Error number: 3653; Symbol: ER_INVALID_VCPU_RANGE; SQLSTATE: HY000

    Message: Invalid VCPU range %u-%u

  • Error number: 3654; Symbol: ER_INVALID_THREAD_PRIORITY; SQLSTATE: HY000

    Message: Invalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].

  • Error number: 3655; Symbol: ER_DISALLOWED_OPERATION; SQLSTATE: HY000

    Message: %s operation is disallowed on %s

  • Error number: 3656; Symbol: ER_RESOURCE_GROUP_BUSY; SQLSTATE: HY000

    Message: Resource group %s is busy.

  • Error number: 3657; Symbol: ER_RESOURCE_GROUP_DISABLED; SQLSTATE: HY000

    Message: Resource group %s is disabled.

  • Error number: 3658; Symbol: ER_FEATURE_UNSUPPORTED; SQLSTATE: HY000

    Message: Feature %s is unsupported (%s).

  • Error number: 3659; Symbol: ER_ATTRIBUTE_IGNORED; SQLSTATE: HY000

    Message: Attribute %s is ignored (%s).

  • Error number: 3660; Symbol: ER_INVALID_THREAD_ID; SQLSTATE: HY000

    Message: Invalid thread id (%llu).

  • Error number: 3661; Symbol: ER_RESOURCE_GROUP_BIND_FAILED; SQLSTATE: HY000

    Message: Unable to bind resource group %s with thread id (%llu).(%s).

  • Error number: 3662; Symbol: ER_INVALID_USE_OF_FORCE_OPTION; SQLSTATE: HY000

    Message: Option FORCE invalid as DISABLE option is not specified.

  • Error number: 3663; Symbol: ER_GROUP_REPLICATION_COMMAND_FAILURE; SQLSTATE: HY000

    Message: The %s command encountered a failure. %s

  • Error number: 3664; Symbol: ER_SDI_OPERATION_FAILED; SQLSTATE: HY000

    Message: Failed to %s SDI '%s.%s' in tablespace '%s'.

  • Error number: 3665; Symbol: ER_MISSING_JSON_TABLE_VALUE; SQLSTATE: 22035

    Message: Missing value for JSON_TABLE column '%s'

  • Error number: 3666; Symbol: ER_WRONG_JSON_TABLE_VALUE; SQLSTATE: 2203F

    Message: Can't store an array or an object in the scalar JSON_TABLE column '%s'

  • Error number: 3667; Symbol: ER_TF_MUST_HAVE_ALIAS; SQLSTATE: 42000

    Message: Every table function must have an alias

  • Error number: 3668; Symbol: ER_TF_FORBIDDEN_JOIN_TYPE; SQLSTATE: HY000

    Message: INNER or LEFT JOIN must be used for LATERAL references made by '%s'

  • Error number: 3669; Symbol: ER_JT_VALUE_OUT_OF_RANGE; SQLSTATE: 22003

    Message: Value is out of range for JSON_TABLE's column '%s'

  • Error number: 3670; Symbol: ER_JT_MAX_NESTED_PATH; SQLSTATE: 42000

    Message: More than supported %u NESTED PATHs were found in JSON_TABLE '%s'

  • Error number: 3671; Symbol: ER_PASSWORD_EXPIRATION_NOT_SUPPORTED_BY_AUTH_METHOD; SQLSTATE: HY000

    Message: The selected authentication method %.*s does not support password expiration

  • Error number: 3672; Symbol: ER_INVALID_GEOJSON_CRS_NOT_TOP_LEVEL; SQLSTATE: HY000

    Message: Invalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.

  • Error number: 3673; Symbol: ER_BAD_NULL_ERROR_NOT_IGNORED; SQLSTATE: 23000

    Message: Column '%s' cannot be null

  • Error number: 3674; Symbol: WARN_USELESS_SPATIAL_INDEX; SQLSTATE: HY000

    Message: The spatial index on column '%s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.

  • Error number: 3675; Symbol: ER_DISK_FULL_NOWAIT; SQLSTATE: HY000

    Message: Create table/tablespace '%s' failed, as disk is full

  • Error number: 3676; Symbol: ER_PARSE_ERROR_IN_DIGEST_FN; SQLSTATE: HY000

    Message: Could not parse argument to digest function: "%s".

  • Error number: 3677; Symbol: ER_UNDISCLOSED_PARSE_ERROR_IN_DIGEST_FN; SQLSTATE: HY000

    Message: Could not parse argument to digest function.

  • Error number: 3678; Symbol: ER_SCHEMA_DIR_EXISTS; SQLSTATE: HY000

    Message: Schema directory '%s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).

  • Error number: 3679; Symbol: ER_SCHEMA_DIR_MISSING; SQLSTATE: HY000

    Message: Schema directory '%s' does not exist

  • Error number: 3680; Symbol: ER_SCHEMA_DIR_CREATE_FAILED; SQLSTATE: HY000

    Message: Failed to create schema directory '%s' (errno: %d - %s)

  • Error number: 3681; Symbol: ER_SCHEMA_DIR_UNKNOWN; SQLSTATE: HY000

    Message: Schema '%s' does not exist, but schema directory '%s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).

  • Error number: 3682; Symbol: ER_ONLY_IMPLEMENTED_FOR_SRID_0_AND_4326; SQLSTATE: 22S00

    Message: Function %s is only defined for SRID 0 and SRID 4326.

  • Error number: 3684; Symbol: ER_REGEXP_BUFFER_OVERFLOW; SQLSTATE: HY000

    Message: The result string is larger than the result buffer.

  • Error number: 3685; Symbol: ER_REGEXP_ILLEGAL_ARGUMENT; SQLSTATE: HY000

    Message: Illegal argument to a regular expression.

  • Error number: 3686; Symbol: ER_REGEXP_INDEX_OUTOFBOUNDS_ERROR; SQLSTATE: HY000

    Message: Index out of bounds in regular expression search.

  • Error number: 3687; Symbol: ER_REGEXP_INTERNAL_ERROR; SQLSTATE: HY000

    Message: Internal error in the regular expression library.

  • Error number: 3688; Symbol: ER_REGEXP_RULE_SYNTAX; SQLSTATE: HY000

    Message: Syntax error in regular expression on line %u, character %u.

  • Error number: 3689; Symbol: ER_REGEXP_BAD_ESCAPE_SEQUENCE; SQLSTATE: HY000

    Message: Unrecognized escape sequence in regular expression.

  • Error number: 3690; Symbol: ER_REGEXP_UNIMPLEMENTED; SQLSTATE: HY000

    Message: The regular expression contains a feature that is not implemented in this library version.

  • Error number: 3691; Symbol: ER_REGEXP_MISMATCHED_PAREN; SQLSTATE: HY000

    Message: Mismatched parenthesis in regular expression.

  • Error number: 3692; Symbol: ER_REGEXP_BAD_INTERVAL; SQLSTATE: HY000

    Message: Incorrect description of a {min,max} interval.

  • Error number: 3693; Symbol: ER_REGEXP_MAX_LT_MIN; SQLSTATE: HY000

    Message: The maximum is less than the minumum in a {min,max} interval.

  • Error number: 3694; Symbol: ER_REGEXP_INVALID_BACK_REF; SQLSTATE: HY000

    Message: Invalid back-reference in regular expression.

  • Error number: 3695; Symbol: ER_REGEXP_LOOK_BEHIND_LIMIT; SQLSTATE: HY000

    Message: The look-behind assertion exceeds the limit in regular expression.

  • Error number: 3696; Symbol: ER_REGEXP_MISSING_CLOSE_BRACKET; SQLSTATE: HY000

    Message: The regular expression contains an unclosed bracket expression.

  • Error number: 3697; Symbol: ER_REGEXP_INVALID_RANGE; SQLSTATE: HY000

    Message: The regular expression contains an [x-y] character range where x comes after y.

  • Error number: 3698; Symbol: ER_REGEXP_STACK_OVERFLOW; SQLSTATE: HY000

    Message: Overflow in the regular expression backtrack stack.

  • Error number: 3699; Symbol: ER_REGEXP_TIME_OUT; SQLSTATE: HY000

    Message: Timeout exceeded in regular expression match.

  • Error number: 3700; Symbol: ER_REGEXP_PATTERN_TOO_BIG; SQLSTATE: HY000

    Message: The regular expression pattern exceeds limits on size or complexity.

  • Error number: 3701; Symbol: ER_CANT_SET_ERROR_LOG_SERVICE; SQLSTATE: HY000

    Message: Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.

  • Error number: 3702; Symbol: ER_EMPTY_PIPELINE_FOR_ERROR_LOG_SERVICE; SQLSTATE: HY000

    Message: Setting an empty %s pipeline disables error logging!

  • Error number: 3703; Symbol: ER_COMPONENT_FILTER_DIAGNOSTICS; SQLSTATE: HY000

    Message: filter %s: %s

  • Error number: 3704; Symbol: ER_NOT_IMPLEMENTED_FOR_CARTESIAN_SRS; SQLSTATE: 22S00

    Message: %s(%s) has not been implemented for Cartesian spatial reference systems.

  • Error number: 3705; Symbol: ER_NOT_IMPLEMENTED_FOR_PROJECTED_SRS; SQLSTATE: 22S00

    Message: %s(%s) has not been implemented for projected spatial reference systems.

  • Error number: 3706; Symbol: ER_NONPOSITIVE_RADIUS; SQLSTATE: 22003

    Message: Invalid radius provided to function %s: Radius must be greater than zero.

  • Error number: 3707; Symbol: ER_RESTART_SERVER_FAILED; SQLSTATE: HY000

    Message: Restart server failed (%s).

  • Error number: 3708; Symbol: ER_SRS_MISSING_MANDATORY_ATTRIBUTE; SQLSTATE: SR006

    Message: Missing mandatory attribute %s.

  • Error number: 3709; Symbol: ER_SRS_MULTIPLE_ATTRIBUTE_DEFINITIONS; SQLSTATE: SR006

    Message: Multiple definitions of attribute %s.

  • Error number: 3710; Symbol: ER_SRS_NAME_CANT_BE_EMPTY_OR_WHITESPACE; SQLSTATE: SR006

    Message: The spatial reference system name can't be an empty string or start or end with whitespace.

  • Error number: 3711; Symbol: ER_SRS_ORGANIZATION_CANT_BE_EMPTY_OR_WHITESPACE; SQLSTATE: SR006

    Message: The organization name can't be an empty string or start or end with whitespace.

  • Error number: 3712; Symbol: ER_SRS_ID_ALREADY_EXISTS; SQLSTATE: SR004

    Message: There is already a spatial reference system with SRID %u.

  • Error number: 3713; Symbol: ER_WARN_SRS_ID_ALREADY_EXISTS; SQLSTATE: 01S00

    Message: There is already a spatial reference system with SRID %u.

  • Error number: 3714; Symbol: ER_CANT_MODIFY_SRID_0; SQLSTATE: SR000

    Message: SRID 0 is not modifiable.

  • Error number: 3715; Symbol: ER_WARN_RESERVED_SRID_RANGE; SQLSTATE: 01S01

    Message: The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.

  • Error number: 3716; Symbol: ER_CANT_MODIFY_SRS_USED_BY_COLUMN; SQLSTATE: SR005

    Message: Can't modify SRID %u. There is at least one column depending on it.

  • Error number: 3717; Symbol: ER_SRS_INVALID_CHARACTER_IN_ATTRIBUTE; SQLSTATE: SR006

    Message: Invalid character in attribute %s.

  • Error number: 3718; Symbol: ER_SRS_ATTRIBUTE_STRING_TOO_LONG; SQLSTATE: SR006

    Message: Attribute %s is too long. The maximum length is %u characters.

  • Error number: 3719; Symbol: ER_DEPRECATED_UTF8_ALIAS; SQLSTATE: HY000

    Message: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.

  • Error number: 3720; Symbol: ER_DEPRECATED_NATIONAL; SQLSTATE: HY000

    Message: NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.

  • Error number: 3721; Symbol: ER_INVALID_DEFAULT_UTF8MB4_COLLATION; SQLSTATE: HY000

    Message: Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected

  • Error number: 3722; Symbol: ER_UNABLE_TO_COLLECT_LOG_STATUS; SQLSTATE: HY000

    Message: Unable to collect information for column '%s': %s.

  • Error number: 3723; Symbol: ER_RESERVED_TABLESPACE_NAME; SQLSTATE: HY000

    Message: The table '%s' may not be created in the reserved tablespace '%s'.

  • Error number: 3724; Symbol: ER_UNABLE_TO_SET_OPTION; SQLSTATE: HY000

    Message: This option cannot be set %s.

  • Error number: 3725; Symbol: ER_REPLICA_POSSIBLY_DIVERGED_AFTER_DDL; SQLSTATE: HY000

    Message: A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.

  • Error number: 3726; Symbol: ER_SRS_NOT_GEOGRAPHIC; SQLSTATE: 22S00

    Message: Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.

  • Error number: 3727; Symbol: ER_POLYGON_TOO_LARGE; SQLSTATE: 22023

    Message: Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.

  • Error number: 3728; Symbol: ER_SPATIAL_UNIQUE_INDEX; SQLSTATE: HY000

    Message: Spatial indexes can't be primary or unique indexes.

  • Error number: 3729; Symbol: ER_INDEX_TYPE_NOT_SUPPORTED_FOR_SPATIAL_INDEX; SQLSTATE: HY000

    Message: The index type %s is not supported for spatial indexes.

  • Error number: 3730; Symbol: ER_FK_CANNOT_DROP_PARENT; SQLSTATE: HY000

    Message: Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.

  • Error number: 3731; Symbol: ER_GEOMETRY_PARAM_LONGITUDE_OUT_OF_RANGE; SQLSTATE: 22S02

    Message: A parameter of function %s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].

  • Error number: 3732; Symbol: ER_GEOMETRY_PARAM_LATITUDE_OUT_OF_RANGE; SQLSTATE: 22S03

    Message: A parameter of function %s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].

  • Error number: 3733; Symbol: ER_FK_CANNOT_USE_VIRTUAL_COLUMN; SQLSTATE: HY000

    Message: Foreign key '%s' uses virtual column '%s' which is not supported.

  • Error number: 3734; Symbol: ER_FK_NO_COLUMN_PARENT; SQLSTATE: HY000

    Message: Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'

  • Error number: 3735; Symbol: ER_CANT_SET_ERROR_SUPPRESSION_LIST; SQLSTATE: HY000

    Message: %s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.

  • Error number: 3736; Symbol: ER_SRS_GEOGCS_INVALID_AXES; SQLSTATE: SR002

    Message: The spatial reference system definition for SRID %u specifies invalid geographic axes '%s' and '%s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.

  • Error number: 3737; Symbol: ER_SRS_INVALID_SEMI_MAJOR_AXIS; SQLSTATE: SR002

    Message: The length of the semi-major axis must be a positive number.

  • Error number: 3738; Symbol: ER_SRS_INVALID_INVERSE_FLATTENING; SQLSTATE: SR002

    Message: The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.

  • Error number: 3739; Symbol: ER_SRS_INVALID_ANGULAR_UNIT; SQLSTATE: SR002

    Message: The angular unit conversion factor must be a positive number.

  • Error number: 3740; Symbol: ER_SRS_INVALID_PRIME_MERIDIAN; SQLSTATE: SR002

    Message: The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.

  • Error number: 3741; Symbol: ER_TRANSFORM_SOURCE_SRS_NOT_SUPPORTED; SQLSTATE: 22S00

    Message: Transformation from SRID %u is not supported.

  • Error number: 3742; Symbol: ER_TRANSFORM_TARGET_SRS_NOT_SUPPORTED; SQLSTATE: 22S00

    Message: Transformation to SRID %u is not supported.

  • Error number: 3743; Symbol: ER_TRANSFORM_SOURCE_SRS_MISSING_TOWGS84; SQLSTATE: 22S00

    Message: Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.

  • Error number: 3744; Symbol: ER_TRANSFORM_TARGET_SRS_MISSING_TOWGS84; SQLSTATE: 22S00

    Message: Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.

  • Error number: 3745; Symbol: ER_TEMP_TABLE_PREVENTS_SWITCH_SESSION_BINLOG_FORMAT; SQLSTATE: HY000

    Message: Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.

  • Error number: 3746; Symbol: ER_TEMP_TABLE_PREVENTS_SWITCH_GLOBAL_BINLOG_FORMAT; SQLSTATE: HY000

    Message: Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try again

  • Error number: 3747; Symbol: ER_RUNNING_APPLIER_PREVENTS_SWITCH_GLOBAL_BINLOG_FORMAT; SQLSTATE: HY000

    Message: Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.

  • Error number: 3748; Symbol: ER_CLIENT_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRX_IN_SBR; SQLSTATE: HY000

    Message: Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.

  • Error number: 3750; Symbol: ER_TABLE_WITHOUT_PK; SQLSTATE: HY000

    Message: Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.

  • Error number: 3751; Symbol: ER_WARN_DATA_TRUNCATED_FUNCTIONAL_INDEX; SQLSTATE: 01000

    Message: Data truncated for functional index '%s' at row %ld

  • Error number: 3752; Symbol: ER_WARN_DATA_OUT_OF_RANGE_FUNCTIONAL_INDEX; SQLSTATE: 22003

    Message: Value is out of range for functional index '%s' at row %ld

  • Error number: 3753; Symbol: ER_FUNCTIONAL_INDEX_ON_JSON_OR_GEOMETRY_FUNCTION; SQLSTATE: 42000

    Message: Cannot create a functional index on a function that returns a JSON or GEOMETRY value.

  • Error number: 3754; Symbol: ER_FUNCTIONAL_INDEX_REF_AUTO_INCREMENT; SQLSTATE: HY000

    Message: Functional index '%s' cannot refer to an auto-increment column.

  • Error number: 3755; Symbol: ER_CANNOT_DROP_COLUMN_FUNCTIONAL_INDEX; SQLSTATE: HY000

    Message: Cannot drop column '%s' because it is used by a functional index. In order to drop the column, you must remove the functional index.

  • Error number: 3756; Symbol: ER_FUNCTIONAL_INDEX_PRIMARY_KEY; SQLSTATE: HY000

    Message: The primary key cannot be a functional index

  • Error number: 3757; Symbol: ER_FUNCTIONAL_INDEX_ON_LOB; SQLSTATE: HY000

    Message: Cannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.

  • Error number: 3758; Symbol: ER_FUNCTIONAL_INDEX_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: Expression of functional index '%s' contains a disallowed function.

  • Error number: 3759; Symbol: ER_FULLTEXT_FUNCTIONAL_INDEX; SQLSTATE: HY000

    Message: Fulltext functional index is not supported.

  • Error number: 3760; Symbol: ER_SPATIAL_FUNCTIONAL_INDEX; SQLSTATE: HY000

    Message: Spatial functional index is not supported.

  • Error number: 3761; Symbol: ER_WRONG_KEY_COLUMN_FUNCTIONAL_INDEX; SQLSTATE: HY000

    Message: The used storage engine cannot index the expression '%s'.

  • Error number: 3762; Symbol: ER_FUNCTIONAL_INDEX_ON_FIELD; SQLSTATE: HY000

    Message: Functional index on a column is not supported. Consider using a regular index instead.

  • Error number: 3763; Symbol: ER_GENERATED_COLUMN_NAMED_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: Expression of generated column '%s' contains a disallowed function: %s.

  • Error number: 3764; Symbol: ER_GENERATED_COLUMN_ROW_VALUE; SQLSTATE: HY000

    Message: Expression of generated column '%s' cannot refer to a row value.

  • Error number: 3765; Symbol: ER_GENERATED_COLUMN_VARIABLES; SQLSTATE: HY000

    Message: Expression of generated column '%s' cannot refer user or system variables.

  • Error number: 3766; Symbol: ER_DEPENDENT_BY_DEFAULT_GENERATED_VALUE; SQLSTATE: HY000

    Message: Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.

  • Error number: 3767; Symbol: ER_DEFAULT_VAL_GENERATED_NON_PRIOR; SQLSTATE: HY000

    Message: Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.

  • Error number: 3768; Symbol: ER_DEFAULT_VAL_GENERATED_REF_AUTO_INC; SQLSTATE: HY000

    Message: Default value expression of column '%s' cannot refer to an auto-increment column.

  • Error number: 3769; Symbol: ER_DEFAULT_VAL_GENERATED_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: Default value expression of column '%s' contains a disallowed function.

  • Error number: 3770; Symbol: ER_DEFAULT_VAL_GENERATED_NAMED_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: Default value expression of column '%s' contains a disallowed function: %s.

  • Error number: 3771; Symbol: ER_DEFAULT_VAL_GENERATED_ROW_VALUE; SQLSTATE: HY000

    Message: Default value expression of column '%s' cannot refer to a row value.

  • Error number: 3772; Symbol: ER_DEFAULT_VAL_GENERATED_VARIABLES; SQLSTATE: HY000

    Message: Default value expression of column '%s' cannot refer user or system variables.

  • Error number: 3773; Symbol: ER_DEFAULT_AS_VAL_GENERATED; SQLSTATE: HY000

    Message: DEFAULT function cannot be used with default value expressions

  • Error number: 3774; Symbol: ER_UNSUPPORTED_ACTION_ON_DEFAULT_VAL_GENERATED; SQLSTATE: HY000

    Message: '%s' is not supported for default value expressions.

  • Error number: 3775; Symbol: ER_GTID_UNSAFE_ALTER_ADD_COL_WITH_DEFAULT_EXPRESSION; SQLSTATE: HY000

    Message: Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.

  • Error number: 3776; Symbol: ER_FK_CANNOT_CHANGE_ENGINE; SQLSTATE: HY000

    Message: Cannot change table's storage engine because the table participates in a foreign key constraint.

  • Error number: 3777; Symbol: ER_WARN_DEPRECATED_USER_SET_EXPR; SQLSTATE: HY000

    Message: Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.

  • Error number: 3778; Symbol: ER_WARN_DEPRECATED_UTF8MB3_COLLATION; SQLSTATE: HY000

    Message: '%s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.

  • Error number: 3779; Symbol: ER_WARN_DEPRECATED_NESTED_COMMENT_SYNTAX; SQLSTATE: HY000

    Message: Nested comment syntax is deprecated and will be removed in a future release.

  • Error number: 3780; Symbol: ER_FK_INCOMPATIBLE_COLUMNS; SQLSTATE: HY000

    Message: Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.

  • Error number: 3781; Symbol: ER_GR_HOLD_WAIT_TIMEOUT; SQLSTATE: HY000

    Message: Timeout exceeded for held statement while new Group Replication primary member is applying backlog.

  • Error number: 3782; Symbol: ER_GR_HOLD_KILLED; SQLSTATE: HY000

    Message: Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.

  • Error number: 3783; Symbol: ER_GR_HOLD_MEMBER_STATUS_ERROR; SQLSTATE: HY000

    Message: Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.

  • Error number: 3784; Symbol: ER_RPL_ENCRYPTION_FAILED_TO_FETCH_KEY; SQLSTATE: HY000

    Message: Failed to fetch key from keyring, please check if keyring is loaded.

  • Error number: 3785; Symbol: ER_RPL_ENCRYPTION_KEY_NOT_FOUND; SQLSTATE: HY000

    Message: Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.

  • Error number: 3786; Symbol: ER_RPL_ENCRYPTION_KEYRING_INVALID_KEY; SQLSTATE: HY000

    Message: Fetched an invalid key from keyring.

  • Error number: 3787; Symbol: ER_RPL_ENCRYPTION_HEADER_ERROR; SQLSTATE: HY000

    Message: Error reading a replication log encryption header: %s.

  • Error number: 3788; Symbol: ER_RPL_ENCRYPTION_FAILED_TO_ROTATE_LOGS; SQLSTATE: HY000

    Message: Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.

  • Error number: 3789; Symbol: ER_RPL_ENCRYPTION_KEY_EXISTS_UNEXPECTED; SQLSTATE: HY000

    Message: Key %s exists unexpected.

  • Error number: 3790; Symbol: ER_RPL_ENCRYPTION_FAILED_TO_GENERATE_KEY; SQLSTATE: HY000

    Message: Failed to generate key, please check if keyring is loaded.

  • Error number: 3791; Symbol: ER_RPL_ENCRYPTION_FAILED_TO_STORE_KEY; SQLSTATE: HY000

    Message: Failed to store key, please check if keyring is loaded.

  • Error number: 3792; Symbol: ER_RPL_ENCRYPTION_FAILED_TO_REMOVE_KEY; SQLSTATE: HY000

    Message: Failed to remove key, please check if keyring is loaded.

  • Error number: 3793; Symbol: ER_RPL_ENCRYPTION_UNABLE_TO_CHANGE_OPTION; SQLSTATE: HY000

    Message: Failed to change binlog_encryption value. %s.

  • Error number: 3794; Symbol: ER_RPL_ENCRYPTION_MASTER_KEY_RECOVERY_FAILED; SQLSTATE: HY000

    Message: Unable to recover binlog encryption master key, please check if keyring is loaded.

  • Error number: 3795; Symbol: ER_SLOW_LOG_MODE_IGNORED_WHEN_NOT_LOGGING_TO_FILE; SQLSTATE: HY000

    Message: slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.

  • Error number: 3796; Symbol: ER_GRP_TRX_CONSISTENCY_NOT_ALLOWED; SQLSTATE: HY000

    Message: The option group_replication_consistency cannot be used on the current member state.

  • Error number: 3797; Symbol: ER_GRP_TRX_CONSISTENCY_BEFORE; SQLSTATE: HY000

    Message: Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.

  • Error number: 3798; Symbol: ER_GRP_TRX_CONSISTENCY_AFTER_ON_TRX_BEGIN; SQLSTATE: HY000

    Message: Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.

  • Error number: 3799; Symbol: ER_GRP_TRX_CONSISTENCY_BEGIN_NOT_ALLOWED; SQLSTATE: HY000

    Message: The Group Replication plugin is stopping, therefore new transactions are not allowed to start.

  • Error number: 3800; Symbol: ER_FUNCTIONAL_INDEX_ROW_VALUE_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: Expression of functional index '%s' cannot refer to a row value.

  • Error number: 3801; Symbol: ER_RPL_ENCRYPTION_FAILED_TO_ENCRYPT; SQLSTATE: HY000

    Message: Failed to encrypt content to write into binlog file: %s.

  • Error number: 3802; Symbol: ER_PAGE_TRACKING_NOT_STARTED; SQLSTATE: HY000

    Message: Page Tracking is not started yet.

  • Error number: 3803; Symbol: ER_PAGE_TRACKING_RANGE_NOT_TRACKED; SQLSTATE: HY000

    Message: Tracking was not enabled for the LSN range specified

  • Error number: 3804; Symbol: ER_PAGE_TRACKING_CANNOT_PURGE; SQLSTATE: HY000

    Message: Cannot purge data when concurrent clone is in progress. Try later.

  • Error number: 3805; Symbol: ER_RPL_ENCRYPTION_CANNOT_ROTATE_BINLOG_MASTER_KEY; SQLSTATE: HY000

    Message: Cannot rotate binary log master key when 'binlog-encryption' is off.

  • Error number: 3806; Symbol: ER_BINLOG_MASTER_KEY_RECOVERY_OUT_OF_COMBINATION; SQLSTATE: HY000

    Message: Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.

  • Error number: 3807; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_OPERATE_KEY; SQLSTATE: HY000

    Message: Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.

  • Error number: 3808; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_ROTATE_LOGS; SQLSTATE: HY000

    Message: Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.

  • Error number: 3809; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_REENCRYPT_LOG; SQLSTATE: HY000

    Message: %s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.

  • Error number: 3810; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_UNUSED_KEYS; SQLSTATE: HY000

    Message: Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.

  • Error number: 3811; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_AUX_KEY; SQLSTATE: HY000

    Message: Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.

  • Error number: 3812; Symbol: ER_NON_BOOLEAN_EXPR_FOR_CHECK_CONSTRAINT; SQLSTATE: HY000

    Message: An expression of non-boolean type specified to a check constraint '%s'.

  • Error number: 3813; Symbol: ER_COLUMN_CHECK_CONSTRAINT_REFERENCES_OTHER_COLUMN; SQLSTATE: HY000

    Message: Column check constraint '%s' references other column.

  • Error number: 3814; Symbol: ER_CHECK_CONSTRAINT_NAMED_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: An expression of a check constraint '%s' contains disallowed function: %s.

  • Error number: 3815; Symbol: ER_CHECK_CONSTRAINT_FUNCTION_IS_NOT_ALLOWED; SQLSTATE: HY000

    Message: An expression of a check constraint '%s' contains disallowed function.

  • Error number: 3816; Symbol: ER_CHECK_CONSTRAINT_VARIABLES; SQLSTATE: HY000

    Message: An expression of a check constraint '%s' cannot refer to a user or system variable.

  • Error number: 3817; Symbol: ER_CHECK_CONSTRAINT_ROW_VALUE; SQLSTATE: HY000

    Message: Check constraint '%s' cannot refer to a row value.

  • Error number: 3818; Symbol: ER_CHECK_CONSTRAINT_REFERS_AUTO_INCREMENT_COLUMN; SQLSTATE: HY000

    Message: Check constraint '%s' cannot refer to an auto-increment column.

  • Error number: 3819; Symbol: ER_CHECK_CONSTRAINT_VIOLATED; SQLSTATE: HY000

    Message: Check constraint '%s' is violated.

  • Error number: 3820; Symbol: ER_CHECK_CONSTRAINT_REFERS_UNKNOWN_COLUMN; SQLSTATE: HY000

    Message: Check constraint '%s' refers to non-existing column '%s'.

  • Error number: 3821; Symbol: ER_CHECK_CONSTRAINT_NOT_FOUND; SQLSTATE: HY000

    Message: Check constraint '%s' is not found in the table.

  • Error number: 3822; Symbol: ER_CHECK_CONSTRAINT_DUP_NAME; SQLSTATE: HY000

    Message: Duplicate check constraint name '%s'.

  • Error number: 3823; Symbol: ER_CHECK_CONSTRAINT_CLAUSE_USING_FK_REFER_ACTION_COLUMN; SQLSTATE: HY000

    Message: Column '%s' cannot be used in a check constraint '%s': needed in a foreign key constraint '%s' referential action.

  • Error number: 3824; Symbol: WARN_UNENCRYPTED_TABLE_IN_ENCRYPTED_DB; SQLSTATE: HY000

    Message: Creating an unencrypted table in a database with default encryption enabled.

  • Error number: 3825; Symbol: ER_INVALID_ENCRYPTION_REQUEST; SQLSTATE: HY000

    Message: Request to create %s table while using an %s tablespace.

  • Error number: 3826; Symbol: ER_CANNOT_SET_TABLE_ENCRYPTION; SQLSTATE: HY000

    Message: Table encryption differ from its database default encryption, and user doesn't have enough privilege.

  • Error number: 3827; Symbol: ER_CANNOT_SET_DATABASE_ENCRYPTION; SQLSTATE: HY000

    Message: Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.

  • Error number: 3828; Symbol: ER_CANNOT_SET_TABLESPACE_ENCRYPTION; SQLSTATE: HY000

    Message: Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.

  • Error number: 3829; Symbol: ER_TABLESPACE_CANNOT_BE_ENCRYPTED; SQLSTATE: HY000

    Message: This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.

  • Error number: 3830; Symbol: ER_TABLESPACE_CANNOT_BE_DECRYPTED; SQLSTATE: HY000

    Message: This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.

  • Error number: 3831; Symbol: ER_TABLESPACE_TYPE_UNKNOWN; SQLSTATE: HY000

    Message: Cannot determine the type of the tablespace named '%s'.

  • Error number: 3832; Symbol: ER_TARGET_TABLESPACE_UNENCRYPTED; SQLSTATE: HY000

    Message: Source tablespace is encrypted but target tablespace is not.

  • Error number: 3833; Symbol: ER_CANNOT_USE_ENCRYPTION_CLAUSE; SQLSTATE: HY000

    Message: ENCRYPTION clause is not valid for %s tablespace.

  • Error number: 3834; Symbol: ER_INVALID_MULTIPLE_CLAUSES; SQLSTATE: HY000

    Message: Multiple %s clauses

  • Error number: 3835; Symbol: ER_UNSUPPORTED_USE_OF_GRANT_AS; SQLSTATE: HY000

    Message: GRANT ... AS is currently supported only for global privileges.

  • Error number: 3836; Symbol: ER_UKNOWN_AUTH_ID_OR_ACCESS_DENIED_FOR_GRANT_AS; SQLSTATE: HY000

    Message: Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.

  • Error number: 3837; Symbol: ER_DEPENDENT_BY_FUNCTIONAL_INDEX; SQLSTATE: HY000

    Message: Column '%s' has a functional index dependency and cannot be dropped or renamed.

  • Error number: 3838; Symbol: ER_PLUGIN_NOT_EARLY; SQLSTATE: HY000

    Message: Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.

  • Error number: 3839; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_START_SUBDIR_PATH; SQLSTATE: HY000

    Message: Redo log archiving start prohibits path name in 'subdir' argument

  • Error number: 3840; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_START_TIMEOUT; SQLSTATE: HY000

    Message: Redo log archiving start timed out

  • Error number: 3841; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_DIRS_INVALID; SQLSTATE: HY000

    Message: Server variable 'innodb_redo_log_archive_dirs' is NULL or empty

  • Error number: 3842; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_LABEL_NOT_FOUND; SQLSTATE: HY000

    Message: Label '%s' not found in server variable 'innodb_redo_log_archive_dirs'

  • Error number: 3843; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_DIR_EMPTY; SQLSTATE: HY000

    Message: Directory is empty after label '%s' in server variable 'innodb_redo_log_archive_dirs'

  • Error number: 3844; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_NO_SUCH_DIR; SQLSTATE: HY000

    Message: Redo log archive directory '%s' does not exist or is not a directory

  • Error number: 3845; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_DIR_CLASH; SQLSTATE: HY000

    Message: Redo log archive directory '%s' is in, under, or over server directory '%s' - '%s'

  • Error number: 3846; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_DIR_PERMISSIONS; SQLSTATE: HY000

    Message: Redo log archive directory '%s' is accessible to all OS users

  • Error number: 3847; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_FILE_CREATE; SQLSTATE: HY000

    Message: Cannot create redo log archive file '%s' (OS errno: %d - %s)

  • Error number: 3848; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_ACTIVE; SQLSTATE: HY000

    Message: Redo log archiving has been started on '%s' - Call innodb_redo_log_archive_stop() first

  • Error number: 3849; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_INACTIVE; SQLSTATE: HY000

    Message: Redo log archiving is not active

  • Error number: 3850; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_FAILED; SQLSTATE: HY000

    Message: Redo log archiving failed: %s

  • Error number: 3851; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_SESSION; SQLSTATE: HY000

    Message: Redo log archiving has not been started by this session

  • Error number: 3852; Symbol: ER_STD_REGEX_ERROR; SQLSTATE: HY000

    Message: Regex error: %s in function %s.

  • Error number: 3853; Symbol: ER_INVALID_JSON_TYPE; SQLSTATE: 22032

    Message: Invalid JSON type in argument %u to function %s; an %s is required.

  • Error number: 3854; Symbol: ER_CANNOT_CONVERT_STRING; SQLSTATE: HY000

    Message: Cannot convert string '%s' from %s to %s

  • Error number: 3855; Symbol: ER_DEPENDENT_BY_PARTITION_FUNC; SQLSTATE: HY000

    Message: Column '%s' has a partitioning function dependency and cannot be dropped or renamed.

  • Error number: 3856; Symbol: ER_WARN_DEPRECATED_FLOAT_AUTO_INCREMENT; SQLSTATE: HY000

    Message: AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%s'.

  • Error number: 3857; Symbol: ER_RPL_CANT_STOP_REPLICA_WHILE_LOCKED_BACKUP; SQLSTATE: HY000

    Message: Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.

  • Error number: 3858; Symbol: ER_WARN_DEPRECATED_FLOAT_DIGITS; SQLSTATE: HY000

    Message: Specifying number of digits for floating point data types is deprecated and will be removed in a future release.

  • Error number: 3859; Symbol: ER_WARN_DEPRECATED_FLOAT_UNSIGNED; SQLSTATE: HY000

    Message: UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.

  • Error number: 3860; Symbol: ER_WARN_DEPRECATED_INTEGER_DISPLAY_WIDTH; SQLSTATE: HY000

    Message: Integer display width is deprecated and will be removed in a future release.

  • Error number: 3861; Symbol: ER_WARN_DEPRECATED_ZEROFILL; SQLSTATE: HY000

    Message: The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.

  • Error number: 3862; Symbol: ER_CLONE_DONOR; SQLSTATE: HY000

    Message: Clone Donor Error: %s.

  • Error number: 3863; Symbol: ER_CLONE_PROTOCOL; SQLSTATE: HY000

    Message: Clone received unexpected response from Donor : %s.

  • Error number: 3864; Symbol: ER_CLONE_DONOR_VERSION; SQLSTATE: HY000

    Message: Clone Donor MySQL version: %s is different from Recipient MySQL version %s.

  • Error number: 3865; Symbol: ER_CLONE_OS; SQLSTATE: HY000

    Message: Clone Donor OS: %s is different from Recipient OS: %s.

  • Error number: 3866; Symbol: ER_CLONE_PLATFORM; SQLSTATE: HY000

    Message: Clone Donor platform: %s is different from Recipient platform: %s.

  • Error number: 3867; Symbol: ER_CLONE_CHARSET; SQLSTATE: HY000

    Message: Clone Donor collation: %s is unavailable in Recipient.

  • Error number: 3868; Symbol: ER_CLONE_CONFIG; SQLSTATE: HY000

    Message: Clone Configuration %s: Donor value: %s is different from Recipient value: %s.

  • Error number: 3869; Symbol: ER_CLONE_SYS_CONFIG; SQLSTATE: HY000

    Message: Clone system configuration: %s

  • Error number: 3870; Symbol: ER_CLONE_PLUGIN_MATCH; SQLSTATE: HY000

    Message: Clone Donor plugin %s is not active in Recipient.

  • Error number: 3871; Symbol: ER_CLONE_LOOPBACK; SQLSTATE: HY000

    Message: Clone cannot use loop back connection while cloning into current data directory.

  • Error number: 3872; Symbol: ER_CLONE_ENCRYPTION; SQLSTATE: HY000

    Message: Clone needs SSL connection for encrypted table.

  • Error number: 3873; Symbol: ER_CLONE_DISK_SPACE; SQLSTATE: HY000

    Message: Clone estimated database size is %s. Available space %s is not enough.

  • Error number: 3874; Symbol: ER_CLONE_IN_PROGRESS; SQLSTATE: HY000

    Message: Concurrent clone in progress. Please try after clone is complete.

  • Error number: 3875; Symbol: ER_CLONE_DISALLOWED; SQLSTATE: HY000

    Message: The clone operation cannot be executed when %s.

  • Error number: 3876; Symbol: ER_CANNOT_GRANT_ROLES_TO_ANONYMOUS_USER; SQLSTATE: HY000

    Message: Cannot grant roles to an anonymous user.

  • Error number: 3877; Symbol: ER_SECONDARY_ENGINE_PLUGIN; SQLSTATE: HY000

    Message: %s

  • Error number: 3878; Symbol: ER_SECOND_PASSWORD_CANNOT_BE_EMPTY; SQLSTATE: HY000

    Message: Empty password can not be retained as second password for user '%s'@'%s'.

  • Error number: 3879; Symbol: ER_DB_ACCESS_DENIED; SQLSTATE: HY000

    Message: Access denied for AuthId `%s`@`%s` to database '%s'.

  • Error number: 3880; Symbol: ER_DA_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES; SQLSTATE: HY000

    Message: Cannot set mandatory_roles: AuthId `%s`@`%s` has '%s' privilege.

  • Error number: 3881; Symbol: ER_DA_RPL_GTID_TABLE_CANNOT_OPEN; SQLSTATE: HY000

    Message: Gtid table is not ready to be used. Table '%s.%s' cannot be opened.

  • Error number: 3882; Symbol: ER_GEOMETRY_IN_UNKNOWN_LENGTH_UNIT; SQLSTATE: SU001

    Message: The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.

  • Error number: 3883; Symbol: ER_DA_PLUGIN_INSTALL_ERROR; SQLSTATE: HY000

    Message: Error installing plugin '%s': %s

  • Error number: 3884; Symbol: ER_NO_SESSION_TEMP; SQLSTATE: HY000

    Message: Storage engine could not allocate temporary tablespace for this session.

  • Error number: 3885; Symbol: ER_DA_UNKNOWN_ERROR_NUMBER; SQLSTATE: HY000

    Message: Got unknown error: %d

  • Error number: 3886; Symbol: ER_COLUMN_CHANGE_SIZE; SQLSTATE: HY000

    Message: Could not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.

  • Error number: 3887; Symbol: ER_REGEXP_INVALID_CAPTURE_GROUP_NAME; SQLSTATE: HY000

    Message: A capture group has an invalid name.

  • Error number: 3888; Symbol: ER_DA_SSL_LIBRARY_ERROR; SQLSTATE: HY000

    Message: Failed to set up SSL because of the following SSL library error: %s

  • Error number: 3889; Symbol: ER_SECONDARY_ENGINE; SQLSTATE: HY000

    Message: Secondary engine operation failed. %s.

  • Error number: 3890; Symbol: ER_SECONDARY_ENGINE_DDL; SQLSTATE: HY000

    Message: You cannot perform DDLs on a table that has a secondary engine defined.

  • Error number: 3891; Symbol: ER_INCORRECT_CURRENT_PASSWORD; SQLSTATE: HY000

    Message: Incorrect current password. Specify the correct password which has to be replaced.

  • Error number: 3892; Symbol: ER_MISSING_CURRENT_PASSWORD; SQLSTATE: HY000

    Message: Current password needs to be specified in the REPLACE clause in order to change it.

  • Error number: 3893; Symbol: ER_CURRENT_PASSWORD_NOT_REQUIRED; SQLSTATE: HY000

    Message: Do not specify the current password while changing it for other users.

  • Error number: 3894; Symbol: ER_PASSWORD_CANNOT_BE_RETAINED_ON_PLUGIN_CHANGE; SQLSTATE: HY000

    Message: Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.

  • Error number: 3895; Symbol: ER_CURRENT_PASSWORD_CANNOT_BE_RETAINED; SQLSTATE: HY000

    Message: Current password can not be retained for user '%s'@'%s' because new password is empty.

  • Error number: 3896; Symbol: ER_PARTIAL_REVOKES_EXIST; SQLSTATE: HY000

    Message: At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.

  • Error number: 3897; Symbol: ER_CANNOT_GRANT_SYSTEM_PRIV_TO_MANDATORY_ROLE; SQLSTATE: HY000

    Message: AuthId `%s`@`%s` is set as mandatory_roles. Cannot grant the '%s' privilege.

  • Error number: 3898; Symbol: ER_XA_REPLICATION_FILTERS; SQLSTATE: HY000

    Message: The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.

  • Error number: 3899; Symbol: ER_UNSUPPORTED_SQL_MODE; SQLSTATE: HY000

    Message: sql_mode=0x%08x is not supported.

  • Error number: 3900; Symbol: ER_REGEXP_INVALID_FLAG; SQLSTATE: HY000

    Message: Invalid match mode flag in regular expression.

  • Error number: 3901; Symbol: ER_PARTIAL_REVOKE_AND_DB_GRANT_BOTH_EXISTS; SQLSTATE: HY000

    Message: '%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.

  • Error number: 3902; Symbol: ER_UNIT_NOT_FOUND; SQLSTATE: SU001

    Message: There's no unit of measure named '%s'.

  • Error number: 3903; Symbol: ER_INVALID_JSON_VALUE_FOR_FUNC_INDEX; SQLSTATE: 22018

    Message: Invalid JSON value for CAST for functional index '%s'.

  • Error number: 3904; Symbol: ER_JSON_VALUE_OUT_OF_RANGE_FOR_FUNC_INDEX; SQLSTATE: 22003

    Message: Out of range JSON value for CAST for functional index '%s'.

  • Error number: 3905; Symbol: ER_EXCEEDED_MV_KEYS_NUM; SQLSTATE: HY000

    Message: Exceeded max number of values per record for multi-valued index '%s' by %u value(s).

  • Error number: 3906; Symbol: ER_EXCEEDED_MV_KEYS_SPACE; SQLSTATE: HY000

    Message: Exceeded max total length of values per record for multi-valued index '%s' by %u bytes.

  • Error number: 3907; Symbol: ER_FUNCTIONAL_INDEX_DATA_IS_TOO_LONG; SQLSTATE: 22001

    Message: Data too long for functional index '%s'.

  • Error number: 3908; Symbol: ER_WRONG_MVI_VALUE; SQLSTATE: HY000

    Message: Cannot store an array or an object in a scalar key part of the index '%s'.

  • Error number: 3909; Symbol: ER_WARN_FUNC_INDEX_NOT_APPLICABLE; SQLSTATE: HY000

    Message: Cannot use functional index '%s' due to type or collation conversion.

  • Error number: 3910; Symbol: ER_GRP_RPL_UDF_ERROR; SQLSTATE: HY000

    Message: The function '%s' failed. %s

  • Error number: 3911; Symbol: ER_UPDATE_GTID_PURGED_WITH_GR; SQLSTATE: HY000

    Message: Cannot update GTID_PURGED with the Group Replication plugin running

  • Error number: 3912; Symbol: ER_GROUPING_ON_TIMESTAMP_IN_DST; SQLSTATE: HY000

    Message: Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.

  • Error number: 3913; Symbol: ER_TABLE_NAME_CAUSES_TOO_LONG_PATH; SQLSTATE: HY000

    Message: Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.

  • Error number: 3914; Symbol: ER_AUDIT_LOG_INSUFFICIENT_PRIVILEGE; SQLSTATE: HY000

    Message: Request ignored for '%s'@'%s'. Role needed to perform operation: '%s'

  • Error number: 3916; Symbol: ER_DA_GRP_RPL_STARTED_AUTO_REJOIN; SQLSTATE: HY000

    Message: Started auto-rejoin procedure attempt %lu of %lu

  • Error number: 3917; Symbol: ER_SYSVAR_CHANGE_DURING_QUERY; SQLSTATE: HY000

    Message: A plugin was loaded or unloaded during a query, a system variable table was changed.

  • Error number: 3918; Symbol: ER_GLOBSTAT_CHANGE_DURING_QUERY; SQLSTATE: HY000

    Message: A plugin was loaded or unloaded during a query, a global status variable was changed.

  • Error number: 3919; Symbol: ER_GRP_RPL_MESSAGE_SERVICE_INIT_FAILURE; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed to start its message service.

  • Error number: 3920; Symbol: ER_CHANGE_SOURCE_WRONG_COMPRESSION_ALGORITHM_CLIENT; SQLSTATE: HY000

    Message: Invalid SOURCE_COMPRESSION_ALGORITHMS '%s' for channel '%s'.

  • Error number: 3921; Symbol: ER_CHANGE_SOURCE_WRONG_COMPRESSION_LEVEL_CLIENT; SQLSTATE: HY000

    Message: Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%s'.

  • Error number: 3922; Symbol: ER_WRONG_COMPRESSION_ALGORITHM_CLIENT; SQLSTATE: HY000

    Message: Invalid compression algorithm '%s'.

  • Error number: 3923; Symbol: ER_WRONG_COMPRESSION_LEVEL_CLIENT; SQLSTATE: HY000

    Message: Invalid zstd compression level for algorithm '%s'.

  • Error number: 3924; Symbol: ER_CHANGE_SOURCE_WRONG_COMPRESSION_ALGORITHM_LIST_CLIENT; SQLSTATE: HY000

    Message: Specified compression algorithm list '%s' exceeds total count of 3 for channel '%s'.

  • Error number: 3925; Symbol: ER_CLIENT_PRIVILEGE_CHECKS_USER_CANNOT_BE_ANONYMOUS; SQLSTATE: HY000

    Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to ``@`%s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.

  • Error number: 3926; Symbol: ER_CLIENT_PRIVILEGE_CHECKS_USER_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this is not an existing user.

  • Error number: 3927; Symbol: ER_CLIENT_PRIVILEGE_CHECKS_USER_CORRUPT; SQLSTATE: HY000

    Message: Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.

  • Error number: 3928; Symbol: ER_CLIENT_PRIVILEGE_CHECKS_USER_NEEDS_RPL_APPLIER_PRIV; SQLSTATE: HY000

    Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this user does not have REPLICATION_APPLIER privilege.

  • Error number: 3929; Symbol: ER_WARN_DA_PRIVILEGE_NOT_REGISTERED; SQLSTATE: HY000

    Message: Dynamic privilege '%s' is not registered with the server.

  • Error number: 3930; Symbol: ER_CLIENT_KEYRING_UDF_KEY_INVALID; SQLSTATE: HY000

    Message: Function '%s' failed because key is invalid.

  • Error number: 3931; Symbol: ER_CLIENT_KEYRING_UDF_KEY_TYPE_INVALID; SQLSTATE: HY000

    Message: Function '%s' failed because key type is invalid.

  • Error number: 3932; Symbol: ER_CLIENT_KEYRING_UDF_KEY_TOO_LONG; SQLSTATE: HY000

    Message: Function '%s' failed because key length is too long.

  • Error number: 3933; Symbol: ER_CLIENT_KEYRING_UDF_KEY_TYPE_TOO_LONG; SQLSTATE: HY000

    Message: Function '%s' failed because key type is too long.

  • Error number: 3934; Symbol: ER_JSON_SCHEMA_VALIDATION_ERROR_WITH_DETAILED_REPORT; SQLSTATE: HY000

    Message: %s.

  • Error number: 3935; Symbol: ER_DA_UDF_INVALID_CHARSET_SPECIFIED; SQLSTATE: HY000

    Message: Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.

  • Error number: 3936; Symbol: ER_DA_UDF_INVALID_CHARSET; SQLSTATE: HY000

    Message: Invalid character set '%s' was specified. It must be a character set name as supported by server.

  • Error number: 3937; Symbol: ER_DA_UDF_INVALID_COLLATION; SQLSTATE: HY000

    Message: Invalid collation '%s' was specified. It must be a collation name as supported by server.

  • Error number: 3938; Symbol: ER_DA_UDF_INVALID_EXTENSION_ARGUMENT_TYPE; SQLSTATE: HY000

    Message: Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.

  • Error number: 3939; Symbol: ER_MULTIPLE_CONSTRAINTS_WITH_SAME_NAME; SQLSTATE: HY000

    Message: Table has multiple constraints with the name '%s'. Please use constraint specific '%s' clause.

  • Error number: 3940; Symbol: ER_CONSTRAINT_NOT_FOUND; SQLSTATE: HY000

    Message: Constraint '%s' does not exist.

  • Error number: 3941; Symbol: ER_ALTER_CONSTRAINT_ENFORCEMENT_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Altering constraint enforcement is not supported for the constraint '%s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.

  • Error number: 3942; Symbol: ER_TABLE_VALUE_CONSTRUCTOR_MUST_HAVE_COLUMNS; SQLSTATE: HY000

    Message: Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.

  • Error number: 3943; Symbol: ER_TABLE_VALUE_CONSTRUCTOR_CANNOT_HAVE_DEFAULT; SQLSTATE: HY000

    Message: A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.

  • Error number: 3944; Symbol: ER_CLIENT_QUERY_FAILURE_INVALID_NON_ROW_FORMAT; SQLSTATE: HY000

    Message: The query does not comply with variable require_row_format restrictions.

  • Error number: 3945; Symbol: ER_REQUIRE_ROW_FORMAT_INVALID_VALUE; SQLSTATE: HY000

    Message: The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.

  • Error number: 3946; Symbol: ER_FAILED_TO_DETERMINE_IF_ROLE_IS_MANDATORY; SQLSTATE: HY000

    Message: Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatory

  • Error number: 3947; Symbol: ER_FAILED_TO_FETCH_MANDATORY_ROLE_LIST; SQLSTATE: HY000

    Message: Failed to acquire lock on user management service, unable to fetch mandatory role list

  • Error number: 3948; Symbol: ER_CLIENT_LOCAL_FILES_DISABLED; SQLSTATE: 42000

    Message: Loading local data is disabled; this must be enabled on both the client and server sides

  • Error number: 3949; Symbol: ER_IMP_INCOMPATIBLE_CFG_VERSION; SQLSTATE: HY000

    Message: Failed to import %s because the CFG file version (%u) is not compatible with the current version (%u)

  • Error number: 3950; Symbol: ER_DA_OOM; SQLSTATE: HY000

    Message: Out of memory

  • Error number: 3951; Symbol: ER_DA_UDF_INVALID_ARGUMENT_TO_SET_CHARSET; SQLSTATE: HY000

    Message: Character set can be set only for the UDF argument type STRING.

  • Error number: 3952; Symbol: ER_DA_UDF_INVALID_RETURN_TYPE_TO_SET_CHARSET; SQLSTATE: HY000

    Message: Character set can be set only for the UDF RETURN type STRING.

  • Error number: 3953; Symbol: ER_MULTIPLE_INTO_CLAUSES; SQLSTATE: HY000

    Message: Multiple INTO clauses in one query block.

  • Error number: 3954; Symbol: ER_MISPLACED_INTO; SQLSTATE: HY000

    Message: Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.

  • Error number: 3955; Symbol: ER_USER_ACCESS_DENIED_FOR_USER_ACCOUNT_BLOCKED_BY_PASSWORD_LOCK; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.

  • Error number: 3956; Symbol: ER_WARN_DEPRECATED_YEAR_UNSIGNED; SQLSTATE: HY000

    Message: UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.

  • Error number: 3957; Symbol: ER_CLONE_NETWORK_PACKET; SQLSTATE: HY000

    Message: Clone needs max_allowed_packet value to be %u or more. Current value is %u

  • Error number: 3958; Symbol: ER_SDI_OPERATION_FAILED_MISSING_RECORD; SQLSTATE: HY000

    Message: Failed to %s sdi for %s.%s in %s due to missing record.

  • Error number: 3959; Symbol: ER_DEPENDENT_BY_CHECK_CONSTRAINT; SQLSTATE: HY000

    Message: Check constraint '%s' uses column '%s', hence column cannot be dropped or renamed.

  • Error number: 3960; Symbol: ER_GRP_OPERATION_NOT_ALLOWED_GR_MUST_STOP; SQLSTATE: HY000

    Message: This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION first

  • Error number: 3961; Symbol: ER_WARN_DEPRECATED_JSON_TABLE_ON_ERROR_ON_EMPTY; SQLSTATE: HY000

    Message: Specifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.

  • Error number: 3962; Symbol: ER_WARN_DEPRECATED_INNER_INTO; SQLSTATE: HY000

    Message: The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.

  • Error number: 3963; Symbol: ER_WARN_DEPRECATED_VALUES_FUNCTION_ALWAYS_NULL; SQLSTATE: HY000

    Message: The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.

  • Error number: 3964; Symbol: ER_WARN_DEPRECATED_SQL_CALC_FOUND_ROWS; SQLSTATE: HY000

    Message: SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.

  • Error number: 3965; Symbol: ER_WARN_DEPRECATED_FOUND_ROWS; SQLSTATE: HY000

    Message: FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.

  • Error number: 3966; Symbol: ER_MISSING_JSON_VALUE; SQLSTATE: 22035

    Message: No value was found by '%s' on the specified path.

  • Error number: 3967; Symbol: ER_MULTIPLE_JSON_VALUES; SQLSTATE: 22034

    Message: More than one value was found by '%s' on the specified path.

  • Error number: 3968; Symbol: ER_HOSTNAME_TOO_LONG; SQLSTATE: HY000

    Message: Hostname cannot be longer than %d characters.

  • Error number: 3970; Symbol: ER_GROUP_REPLICATION_USER_EMPTY_MSG; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.

  • Error number: 3971; Symbol: ER_GROUP_REPLICATION_USER_MANDATORY_MSG; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.

  • Error number: 3972; Symbol: ER_GROUP_REPLICATION_PASSWORD_LENGTH; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.

  • Error number: 3973; Symbol: ER_SUBQUERY_TRANSFORM_REJECTED; SQLSTATE: HY000

    Message: Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' on.

  • Error number: 3974; Symbol: ER_DA_GRP_RPL_RECOVERY_ENDPOINT_FORMAT; SQLSTATE: HY000

    Message: Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port).

  • Error number: 3975; Symbol: ER_DA_GRP_RPL_RECOVERY_ENDPOINT_INVALID; SQLSTATE: HY000

    Message: The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.

  • Error number: 3976; Symbol: ER_WRONG_VALUE_FOR_VAR_PLUS_ACTIONABLE_PART; SQLSTATE: HY000

    Message: Variable '%s' cannot be set to the value of '%s'. %s

  • Error number: 3977; Symbol: ER_STATEMENT_NOT_ALLOWED_AFTER_START_TRANSACTION; SQLSTATE: HY000

    Message: Only BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.

  • Error number: 3978; Symbol: ER_FOREIGN_KEY_WITH_ATOMIC_CREATE_SELECT; SQLSTATE: HY000

    Message: Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.

  • Error number: 3979; Symbol: ER_NOT_ALLOWED_WITH_START_TRANSACTION; SQLSTATE: HY000

    Message: START TRANSACTION clause cannot be used %s

  • Error number: 3980; Symbol: ER_INVALID_JSON_ATTRIBUTE; SQLSTATE: HY000

    Message: Invalid json attribute, error: "%s" at pos %u: '%s'

  • Error number: 3981; Symbol: ER_ENGINE_ATTRIBUTE_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Storage engine '%s' does not support ENGINE_ATTRIBUTE.

  • Error number: 3982; Symbol: ER_INVALID_USER_ATTRIBUTE_JSON; SQLSTATE: HY000

    Message: The user attribute must be a valid JSON object

  • Error number: 3983; Symbol: ER_INNODB_REDO_DISABLED; SQLSTATE: HY000

    Message: Cannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCE

  • Error number: 3984; Symbol: ER_INNODB_REDO_ARCHIVING_ENABLED; SQLSTATE: HY000

    Message: Cannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()

  • Error number: 3985; Symbol: ER_MDL_OUT_OF_RESOURCES; SQLSTATE: HY000

    Message: Not enough resources to complete lock request.

  • Error number: 3986; Symbol: ER_IMPLICIT_COMPARISON_FOR_JSON; SQLSTATE: HY000

    Message: Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNING

  • Error number: 3987; Symbol: ER_FUNCTION_DOES_NOT_SUPPORT_CHARACTER_SET; SQLSTATE: HY000

    Message: The function %s does not support the character set '%s'.

  • Error number: 3988; Symbol: ER_IMPOSSIBLE_STRING_CONVERSION; SQLSTATE: HY000

    Message: Conversion from collation %s into %s impossible for %s

  • Error number: 3989; Symbol: ER_SCHEMA_READ_ONLY; SQLSTATE: HY000

    Message: Schema '%s' is in read only mode.

  • Error number: 3990; Symbol: ER_RPL_ASYNC_RECONNECT_GTID_MODE_OFF; SQLSTATE: HY000

    Message: Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.

  • Error number: 3991; Symbol: ER_RPL_ASYNC_RECONNECT_AUTO_POSITION_OFF; SQLSTATE: HY000

    Message: Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.

  • Error number: 3992; Symbol: ER_DISABLE_GTID_MODE_REQUIRES_ASYNC_RECONNECT_OFF; SQLSTATE: HY000

    Message: The @@GLOBAL.GTID_MODE = %s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.

  • Error number: 3993; Symbol: ER_DISABLE_AUTO_POSITION_REQUIRES_ASYNC_RECONNECT_OFF; SQLSTATE: HY000

    Message: CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.

  • Error number: 3994; Symbol: ER_INVALID_PARAMETER_USE; SQLSTATE: HY000

    Message: Invalid use of parameters in '%s'

  • Error number: 3995; Symbol: ER_CHARACTER_SET_MISMATCH; SQLSTATE: HY000

    Message: Character set '%s' cannot be used in conjunction with '%s' in call to %s.

  • Error number: 3996; Symbol: ER_WARN_VAR_VALUE_CHANGE_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Changing %s not supported on this platform. Falling back to the default.

  • Error number: 3997; Symbol: ER_INVALID_TIME_ZONE_INTERVAL; SQLSTATE: HY000

    Message: Invalid time zone interval: '%s'

  • Error number: 3998; Symbol: ER_INVALID_CAST; SQLSTATE: HY000

    Message: Cannot cast value to %s.

  • Error number: 3999; Symbol: ER_HYPERGRAPH_NOT_SUPPORTED_YET; SQLSTATE: 42000

    Message: The hypergraph optimizer does not yet support '%s'

  • Error number: 4001; Symbol: ER_DA_NO_ERROR_LOG_PARSER_CONFIGURED; SQLSTATE: HY000

    Message: None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.

  • Error number: 4002; Symbol: ER_DA_ERROR_LOG_TABLE_DISABLED; SQLSTATE: HY000

    Message: None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.

  • Error number: 4003; Symbol: ER_DA_ERROR_LOG_MULTIPLE_FILTERS; SQLSTATE: HY000

    Message: @@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.

  • Error number: 4004; Symbol: ER_DA_CANT_OPEN_ERROR_LOG; SQLSTATE: HY000

    Message: Could not open file '%s' for error logging%s%s

  • Error number: 4005; Symbol: ER_USER_REFERENCED_AS_DEFINER; SQLSTATE: HY000

    Message: User %s is referenced as a definer account in %s.

  • Error number: 4006; Symbol: ER_CANNOT_USER_REFERENCED_AS_DEFINER; SQLSTATE: HY000

    Message: Operation %s failed for %s as it is referenced as a definer account in %s.

  • Error number: 4007; Symbol: ER_REGEX_NUMBER_TOO_BIG; SQLSTATE: HY000

    Message: Decimal number in regular expression is too large.

  • Error number: 4008; Symbol: ER_SPVAR_NONINTEGER_TYPE; SQLSTATE: HY000

    Message: The variable "%s" has a non-integer based type

  • Error number: 4009; Symbol: WARN_UNSUPPORTED_ACL_TABLES_READ; SQLSTATE: HY000

    Message: Reads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.

  • Error number: 4010; Symbol: ER_BINLOG_UNSAFE_ACL_TABLE_READ_IN_DML_DDL; SQLSTATE: HY000

    Message: The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.

  • Error number: 4011; Symbol: ER_STOP_REPLICA_MONITOR_IO_THREAD_TIMEOUT; SQLSTATE: HY000

    Message: STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.

  • Error number: 4012; Symbol: ER_STARTING_REPLICA_MONITOR_IO_THREAD; SQLSTATE: HY000

    Message: The Replica Monitor thread failed to start.

  • Error number: 4013; Symbol: ER_CANT_USE_ANONYMOUS_TO_GTID_WITH_GTID_MODE_NOT_ON; SQLSTATE: HY000

    Message: Replication cannot start%s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.

  • Error number: 4014; Symbol: ER_CANT_COMBINE_ANONYMOUS_TO_GTID_AND_AUTOPOSITION; SQLSTATE: HY000

    Message: The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.

  • Error number: 4015; Symbol: ER_ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS_REQUIRES_GTID_MODE_ON; SQLSTATE: HY000

    Message: CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.

  • Error number: 4016; Symbol: ER_SQL_REPLICA_SKIP_COUNTER_USED_WITH_GTID_MODE_ON; SQLSTATE: HY000

    Message: The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.

  • Error number: 4017; Symbol: ER_USING_ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS_AS_LOCAL_OR_UUID; SQLSTATE: HY000

    Message: Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.

  • Error number: 4019; Symbol: ER_CANT_SET_SQL_AFTER_OR_BEFORE_GTIDS_WITH_ANONYMOUS_TO_GTID; SQLSTATE: HY000

    Message: The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.

  • Error number: 4020; Symbol: ER_ANONYMOUS_TO_GTID_UUID_SAME_AS_GROUP_NAME; SQLSTATE: HY000

    Message: Replication '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_name

  • Error number: 4021; Symbol: ER_CANT_USE_SAME_UUID_AS_GROUP_NAME; SQLSTATE: HY000

    Message: CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.

  • Error number: 4022; Symbol: ER_GRP_RPL_RECOVERY_CHANNEL_STILL_RUNNING; SQLSTATE: HY000

    Message: The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.

  • Error number: 4023; Symbol: ER_INNODB_INVALID_AUTOEXTEND_SIZE_VALUE; SQLSTATE: HY000

    Message: AUTOEXTEND_SIZE should be a multiple of %uM

  • Error number: 4024; Symbol: ER_INNODB_INCOMPATIBLE_WITH_TABLESPACE; SQLSTATE: HY000

    Message: InnoDB: "%s" not allowed with general tablespaces

  • Error number: 4025; Symbol: ER_INNODB_AUTOEXTEND_SIZE_OUT_OF_RANGE; SQLSTATE: HY000

    Message: AUTOEXTEND_SIZE value should be between %uM and %uM

  • Error number: 4026; Symbol: ER_CANNOT_USE_AUTOEXTEND_SIZE_CLAUSE; SQLSTATE: HY000

    Message: AUTOEXTEND_SIZE clause is not valid for %s tablespace.

  • Error number: 4027; Symbol: ER_ROLE_GRANTED_TO_ITSELF; SQLSTATE: HY000

    Message: User account %s is directly or indirectly granted to the role %s. The GRANT would create a loop

  • Error number: 4028; Symbol: ER_TABLE_MUST_HAVE_A_VISIBLE_COLUMN; SQLSTATE: HY000

    Message: A table must have at least one visible column.

  • Error number: 4029; Symbol: ER_INNODB_COMPRESSION_FAILURE; SQLSTATE: HY000

    Message: Compression failed with the following error : %s

  • Error number: 4030; Symbol: ER_WARN_ASYNC_CONN_FAILOVER_NETWORK_NAMESPACE; SQLSTATE: HY000

    Message: The parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.

  • Error number: 4031; Symbol: ER_CLIENT_INTERACTION_TIMEOUT; SQLSTATE: HY000

    Message: The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.

  • Error number: 4032; Symbol: ER_INVALID_CAST_TO_GEOMETRY; SQLSTATE: 22S01

    Message: Invalid cast from %s to %s.

  • Error number: 4033; Symbol: ER_INVALID_CAST_POLYGON_RING_DIRECTION; SQLSTATE: 22S04

    Message: Invalid cast from %s to %s. A polygon ring is in the wrong direction.

  • Error number: 4034; Symbol: ER_GIS_DIFFERENT_SRIDS_AGGREGATION; SQLSTATE: 22S05

    Message: Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.

  • Error number: 4035; Symbol: ER_RELOAD_KEYRING_FAILURE; SQLSTATE: HY000

    Message: Keyring reload failed. Please check error log for more details.

  • Error number: 4036; Symbol: ER_SDI_GET_KEYS_INVALID_TABLESPACE; SQLSTATE: HY000

    Message: Tablespace '%s' is invalid for SDI operations.

  • Error number: 4037; Symbol: ER_CHANGE_RPL_SRC_WRONG_COMPRESSION_ALGORITHM_SIZE; SQLSTATE: HY000

    Message: Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%s'.

  • Error number: 4039; Symbol: ER_CANT_USE_SAME_UUID_AS_VIEW_CHANGE_UUID; SQLSTATE: HY000

    Message: CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.

  • Error number: 4040; Symbol: ER_ANONYMOUS_TO_GTID_UUID_SAME_AS_VIEW_CHANGE_UUID; SQLSTATE: HY000

    Message: Replication '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuid

  • Error number: 4041; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_FAIL_GET_VARIABLE; SQLSTATE: HY000

    Message: Unable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.

  • Error number: 4042; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_AND_PRUNE_SECONDS; SQLSTATE: HY000

    Message: Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignored

  • Error number: 4043; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_CLOSE_TO_ROTATE_ON_SIZE; SQLSTATE: HY000

    Message: audit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.

  • Error number: 4044; Symbol: ER_KERBEROS_CREATE_USER; SQLSTATE: HY000

    Message: Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.

  • Error number: 4045; Symbol: ER_INSTALL_PLUGIN_CONFLICT_CLIENT; SQLSTATE: HY000

    Message: Cannot install the %s plugin when the %s plugin is installed.

  • Error number: 4046; Symbol: ER_DA_ERROR_LOG_COMPONENT_FLUSH_FAILED; SQLSTATE: HY000

    Message: %d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.

  • Error number: 4047; Symbol: ER_WARN_SQL_AFTER_MTS_GAPS_GAP_NOT_CALCULATED; SQLSTATE: HY000

    Message: The until clause SQL_AFTER_MTS_GAPS is being used for channel '%s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.

  • Error number: 4048; Symbol: ER_INVALID_ASSIGNMENT_TARGET; SQLSTATE: 42000

    Message: Invalid target for assignment in INSERT or UPDATE statement '%s'.

  • Error number: 4049; Symbol: ER_OPERATION_NOT_ALLOWED_ON_GR_SECONDARY; SQLSTATE: HY000

    Message: This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.

  • Error number: 4050; Symbol: ER_GRP_RPL_FAILOVER_CHANNEL_STATUS_PROPAGATION; SQLSTATE: HY000

    Message: Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.

  • Error number: 4051; Symbol: ER_WARN_AUDIT_LOG_FORMAT_UNIX_TIMESTAMP_ONLY_WHEN_JSON; SQLSTATE: HY000

    Message: audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.

  • Error number: 4052; Symbol: ER_INVALID_MFA_PLUGIN_SPECIFIED; SQLSTATE: HY000

    Message: Invalid plugin "%s" specified as %d factor during "%s".

  • Error number: 4053; Symbol: ER_IDENTIFIED_BY_UNSUPPORTED; SQLSTATE: HY000

    Message: IDENTIFIED BY clause during "%s" not supported for plugin "%s".

  • Error number: 4054; Symbol: ER_INVALID_PLUGIN_FOR_REGISTRATION; SQLSTATE: HY000

    Message: This operation is not supported for plugin "%s".

  • Error number: 4055; Symbol: ER_PLUGIN_REQUIRES_REGISTRATION; SQLSTATE: HY000

    Message: Authentication plugin requires registration. Please refer ALTER USER syntax or set --register-factor command line option to do registration.

  • Error number: 4056; Symbol: ER_MFA_METHOD_EXISTS; SQLSTATE: HY000

    Message: %d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.

  • Error number: 4057; Symbol: ER_MFA_METHOD_NOT_EXISTS; SQLSTATE: HY000

    Message: %d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.

  • Error number: 4058; Symbol: ER_AUTHENTICATION_POLICY_MISMATCH; SQLSTATE: HY000

    Message: %d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.

  • Error number: 4059; Symbol: ER_PLUGIN_REGISTRATION_DONE; SQLSTATE: HY000

    Message: The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.

  • Error number: 4060; Symbol: ER_INVALID_USER_FOR_REGISTRATION; SQLSTATE: HY000

    Message: The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.

  • Error number: 4061; Symbol: ER_USER_REGISTRATION_FAILED; SQLSTATE: HY000

    Message: Authentication plugin's registration failed.

  • Error number: 4062; Symbol: ER_MFA_METHODS_INVALID_ORDER; SQLSTATE: HY000

    Message: %d factor authentication method should be added before %d factor authentication method.

  • Error number: 4063; Symbol: ER_MFA_METHODS_IDENTICAL; SQLSTATE: HY000

    Message: Authentication factor should be different.

  • Error number: 4064; Symbol: ER_INVALID_MFA_OPERATIONS_FOR_PASSWORDLESS_USER; SQLSTATE: HY000

    Message: The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.

  • Error number: 4065; Symbol: ER_CHANGE_REPLICATION_SOURCE_NO_OPTIONS_FOR_GTID_ONLY; SQLSTATE: HY000

    Message: GTID_ONLY cannot be enabled for replication channel '%s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.

  • Error number: 4066; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_REQ_ROW_FORMAT_WITH_GTID_ONLY; SQLSTATE: HY000

    Message: REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%s' when GTID_ONLY=1.

  • Error number: 4067; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_AUTO_POSITION_WITH_GTID_ONLY; SQLSTATE: HY000

    Message: SOURCE_AUTO_POSITION cannot be disabled for replication channel '%s' when GTID_ONLY=1.

  • Error number: 4068; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_GTID_ONLY_WITHOUT_POSITIONS; SQLSTATE: HY000

    Message: When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.

  • Error number: 4069; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_AUTO_POS_WITHOUT_POSITIONS; SQLSTATE: HY000

    Message: When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.

  • Error number: 4070; Symbol: ER_CHANGE_REP_SOURCE_GR_CHANNEL_WITH_GTID_MODE_NOT_ON; SQLSTATE: HY000

    Message: When configuring a group replication channel you must do it when GTID_MODE = ON.

  • Error number: 4071; Symbol: ER_CANT_USE_GTID_ONLY_WITH_GTID_MODE_NOT_ON; SQLSTATE: HY000

    Message: Replication cannot start%s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.

  • Error number: 4072; Symbol: ER_WARN_C_DISABLE_GTID_ONLY_WITH_SOURCE_AUTO_POS_INVALID_POS; SQLSTATE: HY000

    Message: The replication positions relative to the source may be out-of-date on channel '%s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.

  • Error number: 4073; Symbol: ER_DA_SSL_FIPS_MODE_ERROR; SQLSTATE: HY000

    Message: SSL fips mode error: %s

  • Error number: 4074; Symbol: ER_VALUE_OUT_OF_RANGE; SQLSTATE: HY000

    Message: %s=%llu is outside the valid range [%llu,%llu]. %llu will be used.

  • Error number: 4075; Symbol: ER_FULLTEXT_WITH_ROLLUP; SQLSTATE: HY000

    Message: MATCH does not support ROLLUP columns.

  • Error number: 4076; Symbol: ER_REGEXP_MISSING_RESOURCE; SQLSTATE: HY000

    Message: Missing locale resource in regular expression library.

  • Error number: 4077; Symbol: ER_WARN_REGEXP_USING_DEFAULT; SQLSTATE: HY000

    Message: Regular expression library used default (root) locale.

  • Error number: 4078; Symbol: ER_REGEXP_MISSING_FILE; SQLSTATE: HY000

    Message: Missing data file in regular expression library.

  • Error number: 4079; Symbol: ER_WARN_DEPRECATED_COLLATION; SQLSTATE: HY000

    Message: '%s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.

  • Error number: 4080; Symbol: ER_CONCURRENT_PROCEDURE_USAGE; SQLSTATE: HY000

    Message: The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.

  • Error number: 4081; Symbol: ER_DA_GLOBAL_CONN_LIMIT; SQLSTATE: HY000

    Message: Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.

  • Error number: 4082; Symbol: ER_DA_CONN_LIMIT; SQLSTATE: HY000

    Message: Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.

  • Error number: 4083; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE_INSTANT; SQLSTATE: HY000

    Message: Need to rebuild the table to change column type

  • Error number: 4084; Symbol: ER_WARN_SF_UDF_NAME_COLLISION; SQLSTATE: HY000

    Message: This function '%s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.

  • Error number: 4085; Symbol: ER_CANNOT_PURGE_BINLOG_WITH_BACKUP_LOCK; SQLSTATE: HY000

    Message: Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.

  • Error number: 4086; Symbol: ER_TOO_MANY_WINDOWS; SQLSTATE: HY000

    Message: Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.

  • Error number: 4087; Symbol: ER_MYSQLBACKUP_CLIENT_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: 4088; Symbol: ER_COMMENT_CONTAINS_INVALID_STRING; SQLSTATE: HY000

    Message: Comment for %s '%s' contains an invalid %s character string: '%s'.

  • Error number: 4089; Symbol: ER_DEFINITION_CONTAINS_INVALID_STRING; SQLSTATE: HY000

    Message: Definition of %s '%s.%s' contains an invalid %s character string: '%s'.

  • Error number: 4090; Symbol: ER_CANT_EXECUTE_COMMAND_WITH_ASSIGNED_GTID_NEXT; SQLSTATE: HY000

    Message: Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.

  • Error number: 4091; Symbol: ER_XA_TEMP_TABLE; SQLSTATE: HY000

    Message: XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ON

  • Error number: 4092; Symbol: ER_INNODB_MAX_ROW_VERSION; SQLSTATE: HY000

    Message: Maximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.

  • Error number: 4094; Symbol: ER_OPERATION_NOT_ALLOWED_WHILE_PRIMARY_CHANGE_IS_RUNNING; SQLSTATE: HY000

    Message: All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.

  • Error number: 4095; Symbol: ER_WARN_DEPRECATED_DATETIME_DELIMITER; SQLSTATE: HY000

    Message: Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.

  • Error number: 4096; Symbol: ER_WARN_DEPRECATED_SUPERFLUOUS_DELIMITER; SQLSTATE: HY000

    Message: Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.

  • Error number: 4097; Symbol: ER_CANNOT_PERSIST_SENSITIVE_VARIABLES; SQLSTATE: HY000

    Message: Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.

  • Error number: 4098; Symbol: ER_WARN_CANNOT_SECURELY_PERSIST_SENSITIVE_VARIABLES; SQLSTATE: HY000

    Message: SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.

  • Error number: 4099; Symbol: ER_WARN_TRG_ALREADY_EXISTS; SQLSTATE: HY000

    Message: Trigger '%s' already exists on the table '%s'.'%s'.

  • Error number: 4100; Symbol: ER_IF_NOT_EXISTS_UNSUPPORTED_TRG_EXISTS_ON_DIFFERENT_TABLE; SQLSTATE: HY000

    Message: Trigger '%s'.'%s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.

  • Error number: 4101; Symbol: ER_IF_NOT_EXISTS_UNSUPPORTED_UDF_NATIVE_FCT_NAME_COLLISION; SQLSTATE: HY000

    Message: This function '%s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.

  • Error number: 4102; Symbol: ER_SET_PASSWORD_AUTH_PLUGIN_ERROR; SQLSTATE: HY000

    Message: SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.

  • Error number: 4105; Symbol: ER_SRS_INVALID_LATITUDE_OF_ORIGIN; SQLSTATE: SR002

    Message: Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.

  • Error number: 4106; Symbol: ER_SRS_INVALID_LONGITUDE_OF_ORIGIN; SQLSTATE: SR002

    Message: Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.

  • Error number: 4107; Symbol: ER_SRS_UNUSED_PROJ_PARAMETER_PRESENT; SQLSTATE: SR002

    Message: The spatial reference system definition for SRID %u contains unused projection parameter "%s".

  • Error number: 4108; Symbol: ER_GIPK_COLUMN_EXISTS; SQLSTATE: HY000

    Message: Failed to generate invisible primary key. Column 'my_row_id' already exists.

  • Error number: 4109; Symbol: ER_GIPK_FAILED_AUTOINC_COLUMN_EXISTS; SQLSTATE: HY000

    Message: Failed to generate invisible primary key. Auto-increment column already exists.

  • Error number: 4110; Symbol: ER_GIPK_COLUMN_ALTER_NOT_ALLOWED; SQLSTATE: HY000

    Message: Altering generated invisible primary key column 'my_row_id' is not allowed.

  • Error number: 4111; Symbol: ER_DROP_PK_COLUMN_TO_DROP_GIPK; SQLSTATE: HY000

    Message: Please drop primary key column to be able to drop generated invisible primary key.

  • Error number: 4112; Symbol: ER_CREATE_SELECT_WITH_GIPK_DISALLOWED_IN_SBR; SQLSTATE: HY000

    Message: Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.

  • Error number: 4114; Symbol: ER_CTE_RECURSIVE_NOT_UNION; SQLSTATE: HY000

    Message: Recursive table reference in EXCEPT or INTERSECT operand is not allowed.

  • Error number: 4115; Symbol: ER_COMMAND_BACKEND_FAILED_TO_FETCH_SECURITY_CTX; SQLSTATE: HY000

    Message: Error when trying to fetch information from security context object, when trying to connect the server.

  • Error number: 4116; Symbol: ER_COMMAND_SERVICE_BACKEND_FAILED; SQLSTATE: HY000

    Message: Error in command service backend interface, because of : "%s"

  • Error number: 4117; Symbol: ER_CLIENT_FILE_PRIVILEGE_FOR_REPLICATION_CHECKS; SQLSTATE: HY000

    Message: The PRIVILEGE_CHECKS_USER for channel '%s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.

  • Error number: 4118; Symbol: ER_GROUP_REPLICATION_FORCE_MEMBERS_COMMAND_FAILURE; SQLSTATE: HY000

    Message: The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %s

  • Error number: 4119; Symbol: ER_WARN_DEPRECATED_IDENT; SQLSTATE: HY000

    Message: Using %s as unquoted identifier is deprecated, please use quotes or rename the identifier.

  • Error number: 4120; Symbol: ER_INTERSECT_ALL_MAX_DUPLICATES_EXCEEDED; SQLSTATE: HY000

    Message: Max number of duplicate rows in INTERSECT ALL exceeded.

  • Error number: 4121; Symbol: ER_TP_QUERY_THRS_PER_GRP_EXCEEDS_TXN_THR_LIMIT; SQLSTATE: HY000

    Message: Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per group

  • Error number: 4122; Symbol: ER_BAD_TIMESTAMP_FORMAT; SQLSTATE: HY000

    Message: Invalid timestamp format in %s udf

  • Error number: 4123; Symbol: ER_SHAPE_PRIDICTION_UDF; SQLSTATE: HY000

    Message: SHAPE_PREDICTION UDF %s got error because of %s.

  • Error number: 4124; Symbol: ER_SRS_INVALID_HEIGHT; SQLSTATE: SR002

    Message: Height parameter must be non negative.

  • Error number: 4125; Symbol: ER_SRS_INVALID_SCALING; SQLSTATE: SR002

    Message: Scaling parameter must be non negative.

  • Error number: 4126; Symbol: ER_SRS_INVALID_ZONE_WIDTH; SQLSTATE: SR002

    Message: Zone width parameter must be an integer between 1-60.

  • Error number: 4127; Symbol: ER_SRS_INVALID_LATITUDE_POLAR_STERE_VAR_A; SQLSTATE: SR002

    Message: Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).

  • Error number: 4128; Symbol: ER_WARN_DEPRECATED_CLIENT_NO_SCHEMA_OPTION; SQLSTATE: HY000

    Message: The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.

  • Error number: 4129; Symbol: ER_TABLE_NOT_EMPTY; SQLSTATE: HY000

    Message: Table '%s' is not empty.

  • Error number: 4130; Symbol: ER_TABLE_NO_PRIMARY_KEY; SQLSTATE: HY000

    Message: Table '%s' has no primary key.

  • Error number: 4131; Symbol: ER_TABLE_IN_SHARED_TABLESPACE; SQLSTATE: HY000

    Message: Table '%s' is in a shared tablespace.

  • Error number: 4132; Symbol: ER_INDEX_OTHER_THAN_PK; SQLSTATE: HY000

    Message: Table '%s' has indexes other than primary key.

  • Error number: 4133; Symbol: ER_LOAD_BULK_DATA_UNSORTED; SQLSTATE: HY000

    Message: [IN PRIMARY KEY ORDER] specified but data not sorted: '%s'

  • Error number: 4134; Symbol: ER_BULK_EXECUTOR_ERROR; SQLSTATE: HY000

    Message: Bulk executor error: %s

  • Error number: 4135; Symbol: ER_BULK_READER_LIBCURL_INIT_FAILED; SQLSTATE: HY000

    Message: Bulk reader failed to initialize libcurl

  • Error number: 4136; Symbol: ER_BULK_READER_LIBCURL_ERROR; SQLSTATE: HY000

    Message: Bulk reader got libcurl error: %s

  • Error number: 4137; Symbol: ER_BULK_READER_SERVER_ERROR; SQLSTATE: HY000

    Message: Bulk reader got error response from server: %ld

  • Error number: 4138; Symbol: ER_BULK_READER_COMMUNICATION_ERROR; SQLSTATE: HY000

    Message: Bulk reader got error in communication with source server, check the error log for additional details.

  • Error number: 4139; Symbol: ER_BULK_LOAD_DATA_FAILED; SQLSTATE: HY000

    Message: Bulk loader failed in Innodb storage engine, check the error log for additional details.

  • Error number: 4140; Symbol: ER_BULK_LOADER_COLUMN_TOO_BIG_FOR_LEFTOVER_BUFFER; SQLSTATE: HY000

    Message: CSV column too big for leftover buffer.

  • Error number: 4141; Symbol: ER_BULK_LOADER_COMPONENT_ERROR; SQLSTATE: HY000

    Message: Bulk loader component error: %s

  • Error number: 4142; Symbol: ER_BULK_LOADER_FILE_CONTAINS_LESS_LINES_THAN_IGNORE_CLAUSE; SQLSTATE: HY000

    Message: The first file being loaded contained less lines than the ignore clause

  • Error number: 4143; Symbol: ER_BULK_PARSER_MISSING_ENCLOSED_BY; SQLSTATE: HY000

    Message: Missing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.

  • Error number: 4144; Symbol: ER_BULK_PARSER_ROW_BUFFER_MAX_TOTAL_COLS_EXCEEDED; SQLSTATE: HY000

    Message: The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.

  • Error number: 4145; Symbol: ER_BULK_PARSER_COPY_BUFFER_SIZE_EXCEEDED; SQLSTATE: HY000

    Message: The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.

  • Error number: 4146; Symbol: ER_BULK_PARSER_UNEXPECTED_END_OF_INPUT; SQLSTATE: HY000

    Message: Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.

  • Error number: 4147; Symbol: ER_BULK_PARSER_UNEXPECTED_ROW_TERMINATOR; SQLSTATE: HY000

    Message: Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.

  • Error number: 4148; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_ENDING_ENCLOSED_BY; SQLSTATE: HY000

    Message: Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.

  • Error number: 4149; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_NULL_ESCAPE; SQLSTATE: HY000

    Message: Unexpected characters after NULL escape (\\N) found at row %ld in file '%s'.

  • Error number: 4150; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_COLUMN_TERMINATOR; SQLSTATE: HY000

    Message: Unexpected characters after column terminator found at row %ld in file '%s'.

  • Error number: 4151; Symbol: ER_BULK_PARSER_INCOMPLETE_ESCAPE_SEQUENCE; SQLSTATE: HY000

    Message: Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.

  • Error number: 4152; Symbol: ER_LOAD_BULK_DATA_FAILED; SQLSTATE: HY000

    Message: LOAD BULK DATA into table '%s' failed: %s

  • Error number: 4153; Symbol: ER_LOAD_BULK_DATA_WRONG_VALUE_FOR_FIELD; SQLSTATE: HY000

    Message: Incorrect %s value: '%s' for column '%s' at row %ld in file '%s'

  • Error number: 4154; Symbol: ER_LOAD_BULK_DATA_WARN_NULL_TO_NOTNULL; SQLSTATE: HY000

    Message: NULL supplied to NOT NULL column '%s' at row %ld in file '%s'

  • Error number: 4155; Symbol: ER_REQUIRE_TABLE_PRIMARY_KEY_CHECK_GENERATE_WITH_GR; SQLSTATE: HY000

    Message: On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.

  • Error number: 4156; Symbol: ER_CANT_CHANGE_SYS_VAR_IN_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Cannot change the '%s' system variable in read-only mode.

  • Error number: 4157; Symbol: ER_INNODB_INSTANT_ADD_DROP_NOT_SUPPORTED_MAX_SIZE; SQLSTATE: HY000

    Message: Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.

  • Error number: 4158; Symbol: ER_INNODB_INSTANT_ADD_NOT_SUPPORTED_MAX_FIELDS; SQLSTATE: HY000

    Message: Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.

  • Error number: 4159; Symbol: ER_CANT_SET_PERSISTED; SQLSTATE: HY000

    Message: Failed to set persisted options.

  • Error number: 4160; Symbol: ER_INSTALL_COMPONENT_SET_NULL_VALUE; SQLSTATE: HY000

    Message: The value supplied for %s in the SET list cannot be null

  • Error number: 4161; Symbol: ER_INSTALL_COMPONENT_SET_UNUSED_VALUE; SQLSTATE: HY000

    Message: The assignment of %s in SET doesn't match any of the variables registered by the component(s)

  • Error number: 4162; Symbol: ER_WARN_DEPRECATED_USER_DEFINED_COLLATIONS; SQLSTATE: HY000

    Message: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.

  • Error number: 4163; Symbol: ER_USER_LOCK_OVERLONG_NAME; SQLSTATE: 42000

    Message: User-level lock name '%s' should not exceed %d characters.

  • Error number: 4164; Symbol: ER_WARN_NO_SPACE_VERSION_COMMENT; SQLSTATE: HY000

    Message: Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.

  • Error number: 4165; Symbol: ER_VALIDATE_PASSWORD_INSUFFICIENT_CHANGED_CHARACTERS; SQLSTATE: HY000

    Message: The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.

  • Error number: 4166; Symbol: ER_WARN_DEPRECATED_WITH_NOTE; SQLSTATE: HY000

    Message: '%s' is deprecated and will be removed in a future release. %s

  • Error number: 6000; Symbol: ER_LANGUAGE_COMPONENT; SQLSTATE: HY000

    Message: %s

  • Error number: 6001; Symbol: ER_LANGUAGE_COMPONENT_NOT_AVAILABLE; SQLSTATE: HY000

    Message: Language component: Not available.

  • Error number: 6002; Symbol: ER_LANGUAGE_COMPONENT_UNSUPPORTED_LANGUAGE; SQLSTATE: HY000

    Message: Language component: Unsupported language '%s'

  • Error number: 6003; Symbol: ER_LANGUAGE_COMPONENT_CANNOT_UNINSTALL; SQLSTATE: HY000

    Message: Language component: Cannot uninstall due to connected sessions. Please disconnect all sessions and try again.

  • Error number: 6004; Symbol: ER_SP_NO_ALTER_LANGUAGE; SQLSTATE: HY000

    Message: Altering the language of an existing routine is not possible.

  • Error number: 6006; Symbol: ER_EXPLAIN_INTO_IMPLICIT_FORMAT_NOT_SUPPORTED; SQLSTATE: 0A000

    Message: EXPLAIN INTO does not support implicit FORMAT.

  • Error number: 6007; Symbol: ER_EXPLAIN_INTO_FORMAT_NOT_SUPPORTED; SQLSTATE: 0A000

    Message: EXPLAIN INTO does not support FORMAT=%s.

  • Error number: 6008; Symbol: ER_NULL_CANT_BE_PERSISTED_FOR_READONLY; SQLSTATE: HY000

    Message: Trying to persist a NULL into a variable '%s' that's settable only on command line is not supported

  • Error number: 6009; Symbol: ER_EXPLAIN_INTO_FOR_CONNECTION_NOT_SUPPORTED; SQLSTATE: 0A000

    Message: EXPLAIN FOR CONNECTION does not support the INTO clause.

  • Error number: 6010; Symbol: ER_INNODB_IMPORT_WRONG_DROPPED_ENUM_LENGTH; SQLSTATE: HY000

    Message: Enum element name length %lu, is invalid for column %s

  • Error number: 6011; Symbol: ER_INNODB_IMPORT_WRONG_NUMBER_OF_INDEXES_ZERO; SQLSTATE: HY000

    Message: Number of indexes in meta-data file is 0

  • Error number: 6012; Symbol: ER_INNODB_IMPORT_WRONG_NUMBER_OF_INDEXES_TOO_HIGH; SQLSTATE: HY000

    Message: Number of indexes in meta-data file is too high: %llu

  • Error number: 6013; Symbol: ER_INNODB_IMPORT_DROP_COL_METADATA_MISMATCH; SQLSTATE: HY000

    Message: DD metadata for INSTANT DROP column %s in target table doesn't match with CFG.

  • Error number: 6014; Symbol: ER_INNODB_IMPORT_ENUM_NULL_TERMINATOR_MISSING; SQLSTATE: HY000

    Message: Enum/Set element name missing null terminator for column '%s'

  • Error number: 6015; Symbol: ER_SIMULATED_INJECTION_ERROR; SQLSTATE: HY000

    Message: %s %s %zu.

  • Error number: 6016; Symbol: ER_WARN_DEPRECATED_DYNAMIC_PRIV_IN_GRANT; SQLSTATE: HY000

    Message: The privilege '%s' is deprecated.

  • Error number: 6017; Symbol: ER_BULK_MULTI_READER_OPEN_FILE_FAILED; SQLSTATE: HY000

    Message: Bulk Multi Reader: Failed to open file

  • Error number: 6018; Symbol: ER_BULK_MULTI_READER_READ_FILE_FAILED; SQLSTATE: HY000

    Message: Bulk Multi Reader: Failed to read file

  • Error number: 6019; Symbol: ER_BULK_MERGE_INVALID_CHUNK; SQLSTATE: HY000

    Message: Bulk Merge Loader: Invalid Chunk

  • Error number: 6020; Symbol: ER_BULK_MERGE_NOT_ALL_CHUNKS_CONSUMED; SQLSTATE: HY000

    Message: Bulk Merge Loader: Not all chunks consumed

  • Error number: 6021; Symbol: ER_BULK_WRITER_LIBCURL_INIT_FAILED; SQLSTATE: HY000

    Message: Bulk writer failed to initialize libcurl

  • Error number: 6022; Symbol: ER_BULK_WRITER_LIBCURL_ERROR; SQLSTATE: HY000

    Message: Bulk writer got libcurl error: %s

  • Error number: 6023; Symbol: ER_BULK_SORTING_LOADER_WRITE; SQLSTATE: HY000

    Message: Bulk Sorting Loader: Failed to write data to temporary file

  • Error number: 6024; Symbol: ER_BULK_SORTING_LOADER_WAIT; SQLSTATE: HY000

    Message: Bulk Sorting Loader: Interrupted while waiting

  • Error number: 6025; Symbol: ER_BULK_READER_OPEN_FILE_FAILED; SQLSTATE: HY000

    Message: Bulk Reader: Failed to access file %s

  • Error number: 6026; Symbol: ER_BULK_LOAD_TABLE_HAS_INSTANT_COLS; SQLSTATE: HY000

    Message: Bulk Loader: Table '%s' has instantly added/dropped columns. Please TRUNCATE TABLE and retry.

  • Error number: 6027; Symbol: ER_BULK_LOAD_RESOURCE; SQLSTATE: HY000

    Message: Bulk Loader: Not enough memory available. Memory needed for loading %s data: %s for %u threads, %s with minimal configuration. Total configured memory is %s, Available memory is %s.

  • Error number: 6028; Symbol: ER_BULK_LOAD_SECONDARY_ENGINE; SQLSTATE: HY000

    Message: LOAD DATA with BULK Algorithm is not supported on a table with secondary engine.

  • Error number: 6029; Symbol: ER_BULK_READER_ERROR; SQLSTATE: HY000

    Message: Bulk reader error: %s

  • Error number: 6030; Symbol: ER_BULK_READER_FILE_DOESNT_EXIST; SQLSTATE: HY000

    Message: File not found, check whether it exists: %s

  • Error number: 6031; Symbol: ER_BULK_READER_COULDNT_RESOLVE_HOST; SQLSTATE: HY000

    Message: Couldn't resolve host: %s

  • Error number: 6032; Symbol: ER_START_REPLICA_CHANNEL_INVALID_CONFIGURATION; SQLSTATE: HY000

    Message: Cannot start replication channel '%s' because %s.

  • Error number: 6033; Symbol: ER_CANNOT_EXECUTE_IN_PRIMARY; SQLSTATE: HY000

    Message: '%s' is not supported

  • Error number: 6034; Symbol: ER_TOO_MANY_GROUP_BY_MODIFIER_BRANCHES; SQLSTATE: HY000

    Message: '%s' is supported with maximum %d elements in the GROUP BY list

  • Error number: 6035; Symbol: ER_WARN_DEPRECATED_ENGINE_SYNTAX_NO_REPLACEMENT; SQLSTATE: HY000

    Message: '%s' for '%s' storage engine is deprecated and will be removed in a future release.

  • Error number: 6036; Symbol: ER_QUALIFY_WITHOUT_WINDOW_FUNCTION; SQLSTATE: HY000

    Message: QUALIFY clause cannot be used without a window function.

  • Error number: 6037; Symbol: ER_SUPPORTED_ONLY_WITH_HYPERGRAPH; SQLSTATE: HY000

    Message: '%s' can be used only if the hypergraph optimizer is enabled.

  • Error number: 6038; Symbol: ER_SPECIFIC_ACCESS_DENIED; SQLSTATE: HY000

    Message: Access denied; you need %s privilege(s) for this operation

  • Error number: 6039; Symbol: ER_CANT_SET_GTID_NEXT_TO_AUTOMATIC_TAGGED_WHEN_GTID_MODE_IS_OFF; SQLSTATE: HY000

    Message: @@SESSION.GTID_NEXT cannot be set to AUTOMATIC:<TAG> when @@GLOBAL.GTID_MODE = OFF or OFF_PERMISSIVE

  • Error number: 6040; Symbol: ER_GTID_NEXT_TAG_GTID_MODE_OFF; SQLSTATE: HY000

    Message: @@SESSION.GTID_NEXT cannot be set to UUID:TAG:NUMBER when @@GLOBAL.GTID_MODE = OFF.

  • Error number: 6041; Symbol: ER_LH_COL_NOT_NULLABLE; SQLSTATE: HY000

    Message: Column %d of %s : Column contains null but it is not nullable.

  • Error number: 6042; Symbol: ER_LH_WARN_COL_MISSING_NOT_NULLABLE; SQLSTATE: HY000

    Message: Column %d of %s : Column is missing, but it is not nullable and no explicit default value is provided.

  • Error number: 6043; Symbol: ER_LH_COL_IS_EMPTY; SQLSTATE: HY000

    Message: Column %d of %s : Column is empty.

  • Error number: 6044; Symbol: ER_LH_COL_IS_EMPTY_WARN; SQLSTATE: HY000

    Message: Column %d of %s : Column is empty, setting default value.

  • Error number: 6045; Symbol: ER_LH_BAD_VALUE; SQLSTATE: HY000

    Message: Column %d of %s : Invalid %s value.

  • Error number: 6046; Symbol: ER_LH_DECIMAL_UNKNOWN_ERR; SQLSTATE: HY000

    Message: Column %d of %s : Unknown error while parsing decimal.

  • Error number: 6047; Symbol: ER_LH_DECIMAL_OOM_ERR; SQLSTATE: HY000

    Message: Column %d of %s : Out of memory loading decimal.

  • Error number: 6048; Symbol: ER_LH_WARN_DECIMAL_ROUNDING; SQLSTATE: HY000

    Message: Column %d of %s : Fraction exceeds schema, rounding value.

  • Error number: 6049; Symbol: ER_LH_DECIMAL_PRECISION_EXCEEDS_SCHEMA; SQLSTATE: HY000

    Message: Column %d of %s : decimal precision exceeds schema.

  • Error number: 6050; Symbol: ER_LH_EXCEEDS_MIN; SQLSTATE: HY000

    Message: Column %d of %s : %s exceeds min.

  • Error number: 6051; Symbol: ER_LH_EXCEEDS_MAX; SQLSTATE: HY000

    Message: Column %d of %s : %s exceeds max.

  • Error number: 6052; Symbol: ER_LH_WARN_EXCEEDS_MIN_TRUNCATING; SQLSTATE: HY000

    Message: Column %d of %s : %s exceeds min, setting to min value possible.

  • Error number: 6053; Symbol: ER_LH_WARN_EXCEEDS_MAX_TRUNCATING; SQLSTATE: HY000

    Message: Column %d of %s : %s exceeds max, setting to max value possible.

  • Error number: 6054; Symbol: ER_LH_REAL_IS_NAN; SQLSTATE: HY000

    Message: Column %d of %s : Real value is NaN.

  • Error number: 6055; Symbol: ER_LH_OUT_OF_RANGE; SQLSTATE: HY000

    Message: Column %d of %s : %s value is out of range.

  • Error number: 6056; Symbol: ER_LH_DATETIME_FORMAT; SQLSTATE: HY000

    Message: Column %d of %s : Error while applying %s.

  • Error number: 6057; Symbol: ER_LH_WARN_TRUNCATED; SQLSTATE: HY000

    Message: Column %d of %s : %s value was truncated.

  • Error number: 6058; Symbol: ER_LH_CANNOT_CONVERT_STRING; SQLSTATE: HY000

    Message: Column %d of %s : Cannot convert string %s.

  • Error number: 6059; Symbol: ER_LH_RESOURCE_PRINCIPAL_ERR; SQLSTATE: HY000

    Message: Resource principal error.

  • Error number: 6060; Symbol: ER_LH_AWS_AUTH_ERR; SQLSTATE: HY000

    Message: AWS authentication error.

  • Error number: 6061; Symbol: ER_LH_CSV_PARSING_ERR; SQLSTATE: HY000

    Message: %s:%lu: Parsing error found. %s.

  • Error number: 6062; Symbol: ER_LH_COLUMN_MISMATCH_ERR; SQLSTATE: HY000

    Message: %s: Mismatch in the number of columns. Expected %u, found %u.

  • Error number: 6063; Symbol: ER_LH_COLUMN_MAX_ERR; SQLSTATE: HY000

    Message: %s: More than %u column(s) found.

  • Error number: 6064; Symbol: ER_LH_CHARSET_UNSUPPORTED; SQLSTATE: HY000

    Message: Column %d in %s: Charset is not supported.

  • Error number: 6065; Symbol: ER_LH_PARQUET_DECIMAL_CONVERSION_ERR; SQLSTATE: HY000

    Message: Column %d in %s: Decimal conversion error.

  • Error number: 6066; Symbol: ER_LH_STRING_TOO_LONG; SQLSTATE: HY000

    Message: Column %d in %s: String is too long.

  • Error number: 6067; Symbol: ER_LH_RESOURCE_PRINCIPAL_BUCKET_ERR; SQLSTATE: HY000

    Message: Resource Principal endpoint is not configured. Cannot access following buckets: %s.

  • Error number: 6068; Symbol: ER_LH_NO_FILES_FOUND; SQLSTATE: HY000

    Message: No files found corresponding to the following data locations: %s.

  • Error number: 6069; Symbol: ER_LH_EMPTY_FILE; SQLSTATE: HY000

    Message: File %s is empty.

  • Error number: 6070; Symbol: ER_LH_DUPLICATE_FILE; SQLSTATE: HY000

    Message: File %s was not processed (duplicate).

  • Error number: 6071; Symbol: ER_LH_AVRO_SCHEMA_DEPTH_EXCEEDS_MAX; SQLSTATE: HY000

    Message: File %s: Avro schema depth exceeds max allowed depth.

  • Error number: 6072; Symbol: ER_LH_AVRO_HEADER_MISMATCH; SQLSTATE: HY000

    Message: File %s: Header does not match other files.

  • Error number: 6073; Symbol: ER_LH_AVRO_ENUM_CANNOT_CONVERT_CHARSET; SQLSTATE: HY000

    Message: File %s: Enum symbol can't convert to column charset.

  • Error number: 6074; Symbol: ER_LH_AVRO_ENUM_MISMATCH; SQLSTATE: HY000

    Message: File %s: Enum symbols are not the same, or are not in the same order.

  • Error number: 6075; Symbol: ER_LH_AVRO_TYPE_CANNOT_CONVERT; SQLSTATE: HY000

    Message: Column %d in %s: Avro value of physical type %.*s logical type %.*s cannot be converted to mysql type %s.

  • Error number: 6076; Symbol: ER_LH_AVRO_FILE_ENDS_UNEXPECTEDLY; SQLSTATE: HY000

    Message: File %.*s: Ends unexpectedly.

  • Error number: 6077; Symbol: ER_LH_AVRO_FILE_DATA_CORRUPT; SQLSTATE: HY000

    Message: File %.*s: File data might be corrupt.

  • Error number: 6078; Symbol: ER_LH_AVRO_INVALID_UNION; SQLSTATE: HY000

    Message: Column %d in %s: Invalid union encountered. Unions are only supported to represent nullable columns. One of the two types of the union must be null.

  • Error number: 6079; Symbol: ER_LH_AVRO_INVALID_BLOCK_SIZE; SQLSTATE: HY000

    Message: File %.*s: Invalid avro block size.

  • Error number: 6080; Symbol: ER_LH_AVRO_INVALID_BLOCK_RECORD_COUNT; SQLSTATE: HY000

    Message: File %.*s: Invalid Avro block record count.

  • Error number: 6081; Symbol: ER_LH_FORMAT_HEADER_NO_MAGIC_BYTES; SQLSTATE: HY000

    Message: File %.*s: Cannot locate %s specific metadata. Either the file is corrupted or this is not an %s file.

  • Error number: 6082; Symbol: ER_LH_AVRO_HEADER_METADATA_ERR; SQLSTATE: HY000

    Message: File %.*s: Could not process Avro header metadata. The metadata is corrupted or invalid.

  • Error number: 6083; Symbol: ER_LH_AVRO_HEADER_NO_SCHEMA; SQLSTATE: HY000

    Message: File %.*s: No schema in Avro header metadata.

  • Error number: 6084; Symbol: ER_LH_AVRO_NO_CODEC_IN_HEADER; SQLSTATE: HY000

    Message: File %.*s: No codec in Avro header metadata.

  • Error number: 6085; Symbol: ER_LH_AVRO_INVALID_NAME_IN_SCHEMA; SQLSTATE: HY000

    Message: File %.*s: Invalid name in Avro schema.

  • Error number: 6086; Symbol: ER_LH_AVRO_DECODING_ERR; SQLSTATE: HY000

    Message: File %.*s: Error decoding Avro %.*s. %s

  • Error number: 6087; Symbol: ER_LH_PARQUET_NON_UTF8_FILE_ENC; SQLSTATE: HY000

    Message: Column %d in %s: String with non-utf8 file encoding.

  • Error number: 6088; Symbol: ER_LH_PARQUET_SCHEMA_MISMATCH; SQLSTATE: HY000

    Message: Difference in schema among Parquet files.

  • Error number: 6089; Symbol: ER_LH_PARQUET_ROW_GROUP_SIZE_EXCEEDS_MAX; SQLSTATE: HY000

    Message: File %s: Size of row group %ld is larger than maximum allowed size (%d).

  • Error number: 6090; Symbol: ER_LH_PARQUET_CANNOT_LOCATE_OFFSET; SQLSTATE: HY000

    Message: File %s: Cannot locate offset of row group %ld in metadata.

  • Error number: 6091; Symbol: ER_LH_PARQUET_TYPE_CANNOT_CONVERT; SQLSTATE: HY000

    Message: Column %d in parquet table cannot be converted to mysql format.

  • Error number: 6092; Symbol: ER_LH_PARQUET_CANNOT_LOCATE_SCHEMA; SQLSTATE: HY000

    Message: Cannot locate schema in %s.

  • Error number: 6093; Symbol: ER_LH_INFER_SCHEMA_MISMATCH; SQLSTATE: HY000

    Message: Found files with mismatched schemas.

  • Error number: 6094; Symbol: ER_LH_OOM; SQLSTATE: HY000

    Message: Insufficient memory.

  • Error number: 6095; Symbol: ER_LH_WARN_INFER_SKIPPED_LINES; SQLSTATE: HY000

    Message: Skipped %lu line(s) due to mismatched num of cols.

  • Error number: 6096; Symbol: ER_LH_WARN_INFER_SKIPPED_FILES; SQLSTATE: HY000

    Message: Skipped %lu file(s) due to mismatched num of cols.

  • Error number: 6097; Symbol: ER_LH_INFER_FILE_HAS_NO_DATA; SQLSTATE: HY000

    Message: File %s is skipped because it has no valid data. File is either empty or all rows are skipped.

  • Error number: 6098; Symbol: ER_LH_INFER_NO_DATA; SQLSTATE: HY000

    Message: No valid data found for processing.

  • Error number: 6099; Symbol: ER_LH_INFER_NO_FILES; SQLSTATE: HY000

    Message: No valid files found for processing.

  • Error number: 6100; Symbol: ER_LH_WARN_INFER_USE_DEFAULT_COL_NAMES; SQLSTATE: HY000

    Message: Used default column names for column index(s) %s as they are %s.

  • Error number: 6101; Symbol: ER_LH_PARQUET_CANNOT_READ_HEADER; SQLSTATE: HY000

    Message: File %s: Unable to read Parquet header.

  • Error number: 6102; Symbol: ER_LH_INFER_WARN_GOT_EXCEPTION; SQLSTATE: HY000

    Message: Got an exception while trying to process file task.

  • Error number: 6103; Symbol: ER_LH_AVRO_CANNOT_PARSE_HEADER; SQLSTATE: HY000

    Message: File %.*s: Could not parse avro header. Probably corrupted avro file.

  • Error number: 6104; Symbol: ER_LH_PARQUET_CANT_OPEN_FILE; SQLSTATE: HY000

    Message: Parquet reader cannot open %s. %s

  • Error number: 6105; Symbol: ER_LH_TOO_LARGE_VALUE_ERR; SQLSTATE: HY000

    Message: File %.*s: %s

  • Error number: 6106; Symbol: ER_LH_TOO_LARGE_ROW_ERR; SQLSTATE: HY000

    Message: File %.*s: %s

  • Error number: 6107; Symbol: ER_TABLESAMPLE_PERCENTAGE; SQLSTATE: 2202H

    Message: Tablesample percentage should range between 0 and 100.

  • Error number: 6108; Symbol: ER_TABLESAMPLE_ONLY_ON_BASE_TABLES; SQLSTATE: HY000

    Message: Tablesample can be applied only on base tables.

  • Error number: 6110; Symbol: ER_RESULT_SIZE_LIMIT_EXCEEDED; SQLSTATE: HY000

    Message: Result size limit exceeded.

  • Error number: 6111; Symbol: ER_LANGUAGE_COMPONENT_INTERNAL; SQLSTATE: HY000

    Message: Language component: Internal error.

  • Error number: 6112; Symbol: ER_LANGUAGE_COMPONENT_CONCURRENCY_LIMIT; SQLSTATE: HY000

    Message: Language component: Concurrency limit (%s) has been reached.

  • Error number: 6113; Symbol: ER_LANGUAGE_COMPONENT_RUNTIME; SQLSTATE: HY000

    Message: %s> %s

  • Error number: 6114; Symbol: ER_LANGUAGE_COMPONENT_TIMEZONE; SQLSTATE: HY000

    Message: %s> Time zone %s is not supported.

  • Error number: 6115; Symbol: ER_LANGUAGE_COMPONENT_KEYWORD; SQLSTATE: HY000

    Message: %s> The identifier '%s' is a reserved word.

  • Error number: 6116; Symbol: ER_LANGUAGE_COMPONENT_SET_SYSTEM_VARIABLE; SQLSTATE: HY000

    Message: Language component: System variable '%s' cannot be configured when component is active.

  • Error number: 6117; Symbol: ER_LANGUAGE_COMPONENT_UNSUPPORTED_TYPE; SQLSTATE: HY000

    Message: %s> %s

  • Error number: 6118; Symbol: ER_LANGUAGE_COMPONENT_CONVERSION; SQLSTATE: HY000

    Message: %s> %s

  • Error number: 6119; Symbol: ER_WARN_SP_STATEMENT_PARTIALLY_EXECUTED; SQLSTATE: HY000

    Message: Stored program statement is partially completed. Result set might not contain all the rows.

  • Error number: 6120; Symbol: ER_STMT_EXECUTION_NOT_ALLOWED_WITHIN_SP_OR_TRG_OR_UDF; SQLSTATE: HY000

    Message: Executing SQL statement using %s Statement Handle Interface is not allowed within stored function, trigger or loadable function (UDF).

  • Error number: 6121; Symbol: ER_LH_JSON_PARSING; SQLSTATE: HY000

    Message: Column %d of %s : %s

  • Error number: 6122; Symbol: ER_ENGINE_CANNOT_BE_DEFAULT; SQLSTATE: HY000

    Message: Engine %s cannot be set as default_storage_engine.

  • Error number: 6123; Symbol: ER_PARTITION_PREFIX_KEY_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Column '%s.%s.%s' having prefix key part '%s(%u)' in the PARTITION BY KEY() clause is not supported.

  • Error number: 6124; Symbol: ER_WARN_DEPRECATED_NON_STANDARD_KEY; SQLSTATE: HY000

    Message: Foreign key '%s' refers to non-unique key or partial key. This is deprecated and will be removed in a future release.

  • Error number: 6125; Symbol: ER_FK_NO_UNIQUE_INDEX_PARENT; SQLSTATE: HY000

    Message: Failed to add the foreign key constraint. Missing unique key for constraint '%s' in the referenced table '%s'

  • Error number: 6126; Symbol: ER_ACCESS_DENIED_NO_PROXY_GRANT; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s', missing proxy privilege.

  • Error number: 6127; Symbol: ER_ACCESS_DENIED_NO_PROXY; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s', proxied user doesn't exist.

  • Error number: 6128; Symbol: ER_LH_USER_DATA_ACCESS_FAILED; SQLSTATE: HY000

    Message: Unable to access the following data locations: %s

  • Error number: 6129; Symbol: ER_BULK_READER_ZSTD_ERROR; SQLSTATE: HY000

    Message: ZSTD decompression failed: %s

  • Error number: 6130; Symbol: ER_BULK_PARSER_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: 6131; Symbol: ER_LH_INVALID_JSON_FILE_FORMAT_SCHEMA; SQLSTATE: HY000

    Message: Invalid json file format schema: %s

  • Error number: 6132; Symbol: ER_LH_INFER_JSON_INVALID_SCHEMA; SQLSTATE: HY000

    Message: Inferred invalid schema. A single column with JSON type is the only valid schema for JSON file format.

  • Error number: 6133; Symbol: ER_LH_JSON_FILE_FORMAT_WARN_INFER_SCHEMA; SQLSTATE: HY000

    Message: Altered the inferred schema to a single JSON column.

  • Error number: 6134; Symbol: ER_NON_SCALAR_USED_AS_KEY; SQLSTATE: HY000

    Message: Non-scalar (e.g., vector) column '%s' cannot be used as key.

  • Error number: 6135; Symbol: ER_INCOMPATIBLE_TYPE_AGG; SQLSTATE: HY000

    Message: Columns aggregated with incompatible types: '%s', '%s'.

  • Error number: 6136; Symbol: ER_DATA_INCOMPATIBLE_WITH_VECTOR; SQLSTATE: HY000

    Message: Value of type '%s, size: %zu' cannot be converted to 'vector' type.

  • Error number: 6137; Symbol: ER_EXCEEDS_VECTOR_MAX_DIMENSIONS; SQLSTATE: HY000

    Message: Data size (%zu Bytes, %u dimensions) exceeds VECTOR max (%zu Bytes, %u dimensions) for column: '%s'

  • Error number: 6138; Symbol: ER_TO_VECTOR_CONVERSION; SQLSTATE: HY000

    Message: Data cannot be converted to a valid vector: '%.*s'

  • Error number: 6140; Symbol: ER_TP_CANNOT_DISABLE_MTL_WITH_DL; SQLSTATE: HY000

    Message: The variable thread_pool_max_transactions_limit cannot be set to 0 when thread_pool_dedicated_listernes is ON.

  • Error number: 6400; Symbol: ER_SERVER_OFFLINE_MODE_REASON; SQLSTATE: HY000

    Message: The server is currently in offline mode since %s, reason: %s

  • Error number: 6401; Symbol: ER_SERVER_OFFLINE_MODE_USER; SQLSTATE: HY000

    Message: The server is currently in offline mode since %s, set by user %s

  • Error number: 6402; Symbol: ER_LH_UNSTRUCTURED_NO_DATA_FOUND; SQLSTATE: HY000

    Message: No data was extracted from provided files.

  • Error number: 6403; Symbol: ER_LH_UNSTRUCTURED_FILE_PARSE_ERR; SQLSTATE: HY000

    Message: File: %.*s Could not be parsed.

  • Error number: 6404; Symbol: ER_LH_UNSTRUCTURED_ENCODING_ERR; SQLSTATE: HY000

    Message: Segments %d to %d in file: %.*s Could not be encoded.

  • Error number: 6405; Symbol: ER_LH_UNSTRUCTURED_FILE_TYPE_MISMATCH_ERR; SQLSTATE: HY000

    Message: File: %.*s is not a supported file type.

  • Error number: 6406; Symbol: ER_LH_UNSTRUCTURED_SCHEMA_ERR; SQLSTATE: HY000

    Message: Defined schema does not match expected for column: %s.

  • Error number: 6407; Symbol: ER_LH_COLUMN_ENGINE_ATTR_ERR; SQLSTATE: HY000

    Message: Invalid column engine attribute: %s.

  • Error number: 6408; Symbol: ER_LH_UNSTRUCTURED_OBJ_READ_ERR; SQLSTATE: HY000

    Message: File: %.*s Could not be read.

  • Error number: 6409; Symbol: ER_LH_NO_SEGMENTS_GENERATED; SQLSTATE: HY000

    Message: File: %.*s did not result in segments.

  • Error number: 6410; Symbol: ER_LH_UNSTRUCTURED_FILE_TOO_LARGE; SQLSTATE: HY000

    Message: File: %s is too large.

  • Error number: 6411; Symbol: ER_EXCEEDED_MAX_REGULAR_STATEMENT_HANDLE_LIMIT; SQLSTATE: HY000

    Message: Exceeded limit of %u regular SQL statement handles per session.

  • Error number: 6412; Symbol: ER_EXPLAIN_ANALYZE_JSON_FORMAT_VERSION_NOT_SUPPORTED; SQLSTATE: 0A000

    Message: EXPLAIN ANALYZE does not support FORMAT=JSON with explain_json_format_version=1.

  • Error number: 6413; Symbol: ER_NON_DML_DYNAMIC_PARAMETERS; SQLSTATE: HY000

    Message: Dynamic parameters can only be used in DML statements.

  • Error number: 6414; Symbol: ER_DEPRECATE_NON_COMPOSABLE_MULTIPLE_ENGINE; SQLSTATE: HY000

    Message: Combining the storage engines %s and %s is deprecated, but the statement or transaction updates both the %s table %s.%s and the %s table %s.%s.

  • Error number: 6415; Symbol: ER_BULK_JSON_INVALID; SQLSTATE: HY000

    Message: Bulk load reports invalid JSON: error='%s', table='%s', field='%s'

  • Error number: 6416; Symbol: ER_BULK_BLOB_TOO_BIG; SQLSTATE: HY000

    Message: Column data bigger than %zu bytes for column='%s' of table='%s'

  • Error number: 6417; Symbol: ER_NO_QUERY_PLAN_FOUND; SQLSTATE: HY000

    Message: No query execution plan was found for the statement.

  • Error number: 6418; Symbol: ER_LH_CP_TOO_MANY_CHANGES; SQLSTATE: HY000

    Message: More than %llu changes detected. Certain changes are ignored.

  • Error number: 6419; Symbol: ER_LH_CP_NOT_ENABLED; SQLSTATE: HY000

    Message: Lakehouse Incremental Load is not enabled.

  • Error number: 6420; Symbol: ER_LH_CP_NO_VECTOR_STORE; SQLSTATE: HY000

    Message: Lakehouse Incremental Load is not supported for vector store tables.

  • Error number: 6421; Symbol: ER_LH_CP_NO_VALIDATION_MODE; SQLSTATE: HY000

    Message: Lakehouse Incremental Load is not supported with validation mode.

  • Error number: 6422; Symbol: ER_LH_CP_MISSING_FILES_MODE; SQLSTATE: HY000

    Message: Lakehouse Incremental Load is not supported with allow_missing_files disabled.

  • Error number: 6423; Symbol: ER_LH_CP_COMMIT_FAILED; SQLSTATE: HY000

    Message: Lakehouse Incremental Load commit operation failed.

  • Error number: 6424; Symbol: ER_LH_UNSTRUCTURED_INVALID_LANGUAGE; SQLSTATE: HY000

    Message: Invalid language code. %s.

  • Error number: 6425; Symbol: ER_LH_VECTOR_TOO_MANY_ENTRIES; SQLSTATE: HY000

    Message: Column %d in %s: Vector has more entries than its dimension: %s

  • Error number: MY-010000; Symbol: ER_PARSER_TRACE; SQLSTATE: XX999

    Message: Parser saw: %s

  • Error number: MY-010001; Symbol: ER_BOOTSTRAP_CANT_THREAD; SQLSTATE: HY000

    Message: Can't create thread to handle bootstrap (errno: %d)

  • Error number: MY-010002; Symbol: ER_TRIGGER_INVALID_VALUE; SQLSTATE: HY000

    Message: Trigger for table '%s'.'%s': invalid %s value (%s).

  • Error number: MY-010003; Symbol: ER_OPT_WRONG_TREE; SQLSTATE: HY000

    Message: Wrong tree: %s

  • Error number: MY-010004; Symbol: ER_DD_FAILSAFE; SQLSTATE: HY000

    Message: Error: Invalid %s

  • Error number: MY-010005; Symbol: ER_DD_NO_WRITES_NO_REPOPULATION; SQLSTATE: HY000

    Message: Skip re-populating collations and character sets tables in %s%sread-only mode.

  • Error number: MY-010006; Symbol: ER_DD_VERSION_FOUND; SQLSTATE: HY000

    Message: Using data dictionary with version '%d'.

  • Error number: MY-010007; Symbol: ER_DD_VERSION_INSTALLED; SQLSTATE: HY000

    Message: Installed data dictionary with version %d

  • Error number: MY-010008; Symbol: ER_DD_VERSION_UNSUPPORTED; SQLSTATE: HY000

    Message: Data Dictionary version '%d' not supported.

  • Error number: MY-010010; Symbol: ER_LOG_SYSLOG_CANNOT_OPEN; SQLSTATE: HY000

    Message: Cannot open %s; check privileges, or remove syseventlog from --log-error-services!

  • Error number: MY-010011; Symbol: ER_LOG_SLOW_CANNOT_OPEN; SQLSTATE: HY000

    Message: either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or

  • Error number: MY-010012; Symbol: ER_LOG_GENERAL_CANNOT_OPEN; SQLSTATE: HY000

    Message: either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" or

  • Error number: MY-010013; Symbol: ER_LOG_CANNOT_WRITE; SQLSTATE: HY000

    Message: Failed to write to %s: %s

  • Error number: MY-010014; Symbol: ER_RPL_ZOMBIE_ENCOUNTERED; SQLSTATE: HY000

    Message: While initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).

  • Error number: MY-010015; Symbol: ER_RPL_GTID_TABLE_CANNOT_OPEN; SQLSTATE: HY000

    Message: Gtid table is not ready to be used. Table '%s.%s' cannot be opened.

  • Error number: MY-010016; Symbol: ER_SYSTEM_SCHEMA_NOT_FOUND; SQLSTATE: HY000

    Message: System schema directory does not exist.

  • Error number: MY-010017; Symbol: ER_DD_INIT_UPGRADE_FAILED; SQLSTATE: HY000

    Message: Error in initializing dictionary, upgrade will do a cleanup and exit

  • Error number: MY-010018; Symbol: ER_VIEW_UNKNOWN_CHARSET_OR_COLLATION; SQLSTATE: HY000

    Message: View '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').

  • Error number: MY-010019; Symbol: ER_DD_VIEW_CANT_ALLOC_CHARSET; SQLSTATE: HY000

    Message: Error in allocating memory for character set name for view %s.%s.

  • Error number: MY-010020; Symbol: ER_DD_INIT_FAILED; SQLSTATE: HY000

    Message: Data Dictionary initialization failed.

  • Error number: MY-010021; Symbol: ER_DD_UPDATING_PLUGIN_MD_FAILED; SQLSTATE: HY000

    Message: Failed to update plugin metadata in dictionary tables.

  • Error number: MY-010023; Symbol: ER_DD_VIEW_CANT_CREATE; SQLSTATE: HY000

    Message: Error in Creating View %s.%s

  • Error number: MY-010024; Symbol: ER_DD_METADATA_NOT_FOUND; SQLSTATE: HY000

    Message: Unable to start server. Cannot find the meta data for data dictionary table '%s'.

  • Error number: MY-010025; Symbol: ER_DD_CACHE_NOT_EMPTY_AT_SHUTDOWN; SQLSTATE: HY000

    Message: Dictionary cache not empty at shutdown.

  • Error number: MY-010026; Symbol: ER_DD_OBJECT_REMAINS; SQLSTATE: HY000

    Message: Dictionary objects used but not released.

  • Error number: MY-010027; Symbol: ER_DD_OBJECT_REMAINS_IN_RELEASER; SQLSTATE: HY000

    Message: Dictionary objects left in default releaser.

  • Error number: MY-010028; Symbol: ER_DD_OBJECT_RELEASER_REMAINS; SQLSTATE: HY000

    Message: Dictionary object auto releaser not deleted

  • Error number: MY-010029; Symbol: ER_DD_CANT_GET_OBJECT_KEY; SQLSTATE: HY000

    Message: Error: Unable to create primary object key

  • Error number: MY-010030; Symbol: ER_DD_CANT_CREATE_OBJECT_KEY; SQLSTATE: HY000

    Message: Error: Unable to create object key

  • Error number: MY-010031; Symbol: ER_CANT_CREATE_HANDLE_MGR_THREAD; SQLSTATE: HY000

    Message: Can't create handle_manager thread (errno= %d)

  • Error number: MY-010032; Symbol: ER_RPL_REPO_HAS_GAPS; SQLSTATE: HY000

    Message: It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.

  • Error number: MY-010033; Symbol: ER_INVALID_VALUE_FOR_ENFORCE_GTID_CONSISTENCY; SQLSTATE: HY000

    Message: option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.

  • Error number: MY-010034; Symbol: ER_CHANGED_ENFORCE_GTID_CONSISTENCY; SQLSTATE: HY000

    Message: Changed ENFORCE_GTID_CONSISTENCY from %s to %s.

  • Error number: MY-010035; Symbol: ER_CHANGED_GTID_MODE; SQLSTATE: HY000

    Message: Changed GTID_MODE from %s to %s.

  • Error number: MY-010036; Symbol: ER_DISABLED_STORAGE_ENGINE_AS_DEFAULT; SQLSTATE: HY000

    Message: %s is set to a disabled storage engine %s.

  • Error number: MY-010037; Symbol: ER_DEBUG_SYNC_HIT; SQLSTATE: HY000

    Message: Debug sync points hit: %s

  • Error number: MY-010038; Symbol: ER_DEBUG_SYNC_EXECUTED; SQLSTATE: HY000

    Message: Debug sync points executed: %s

  • Error number: MY-010039; Symbol: ER_DEBUG_SYNC_THREAD_MAX; SQLSTATE: HY000

    Message: Debug sync points max active per thread: %s

  • Error number: MY-010040; Symbol: ER_DEBUG_SYNC_OOM; SQLSTATE: HY000

    Message: Debug Sync Facility disabled due to lack of memory.

  • Error number: MY-010041; Symbol: ER_CANT_INIT_TC_LOG; SQLSTATE: HY000

    Message: Can't init tc log

  • Error number: MY-010042; Symbol: ER_EVENT_CANT_INIT_QUEUE; SQLSTATE: HY000

    Message: Event Scheduler: Can't initialize the execution queue

  • Error number: MY-010043; Symbol: ER_EVENT_PURGING_QUEUE; SQLSTATE: HY000

    Message: Event Scheduler: Purging the queue. %u events

  • Error number: MY-010044; Symbol: ER_EVENT_LAST_EXECUTION; SQLSTATE: HY000

    Message: Event Scheduler: Last execution of %s.%s. %s

  • Error number: MY-010045; Symbol: ER_EVENT_MESSAGE_STACK; SQLSTATE: HY000

    Message: %*s

  • Error number: MY-010046; Symbol: ER_EVENT_EXECUTION_FAILED; SQLSTATE: HY000

    Message: Event Scheduler: [%s].[%s.%s] event execution failed.

  • Error number: MY-010047; Symbol: ER_CANT_INIT_SCHEDULER_THREAD; SQLSTATE: HY000

    Message: Event Scheduler: Cannot initialize the scheduler thread

  • Error number: MY-010048; Symbol: ER_SCHEDULER_STOPPED; SQLSTATE: HY000

    Message: Event Scheduler: Stopped

  • Error number: MY-010049; Symbol: ER_CANT_CREATE_SCHEDULER_THREAD; SQLSTATE: HY000

    Message: Event scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)

  • Error number: MY-010050; Symbol: ER_SCHEDULER_WAITING; SQLSTATE: HY000

    Message: Event Scheduler: Waiting for the scheduler thread to reply

  • Error number: MY-010051; Symbol: ER_SCHEDULER_STARTED; SQLSTATE: HY000

    Message: Event Scheduler: scheduler thread started with id %u

  • Error number: MY-010052; Symbol: ER_SCHEDULER_STOPPING_FAILED_TO_GET_EVENT; SQLSTATE: HY000

    Message: Event Scheduler: Serious error during getting next event to execute. Stopping

  • Error number: MY-010053; Symbol: ER_SCHEDULER_STOPPING_FAILED_TO_CREATE_WORKER; SQLSTATE: HY000

    Message: Event_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event scheduler

  • Error number: MY-010054; Symbol: ER_SCHEDULER_KILLING; SQLSTATE: HY000

    Message: Event Scheduler: Killing the scheduler thread, thread id %u

  • Error number: MY-010055; Symbol: ER_UNABLE_TO_RESOLVE_IP; SQLSTATE: HY000

    Message: IP address '%s' could not be resolved: %s

  • Error number: MY-010056; Symbol: ER_UNABLE_TO_RESOLVE_HOSTNAME; SQLSTATE: HY000

    Message: Host name '%s' could not be resolved: %s

  • Error number: MY-010057; Symbol: ER_HOSTNAME_RESEMBLES_IPV4; SQLSTATE: HY000

    Message: IP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.

  • Error number: MY-010058; Symbol: ER_HOSTNAME_DOESNT_RESOLVE_TO; SQLSTATE: HY000

    Message: Hostname '%s' does not resolve to '%s'.

  • Error number: MY-010059; Symbol: ER_ADDRESSES_FOR_HOSTNAME_HEADER; SQLSTATE: HY000

    Message: Hostname '%s' has the following IP addresses:

  • Error number: MY-010060; Symbol: ER_ADDRESSES_FOR_HOSTNAME_LIST_ITEM; SQLSTATE: HY000

    Message: - %s

  • Error number: MY-010061; Symbol: ER_TRG_WITHOUT_DEFINER; SQLSTATE: HY000

    Message: Definer clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.

  • Error number: MY-010062; Symbol: ER_TRG_NO_CLIENT_CHARSET; SQLSTATE: HY000

    Message: Client character set is missing for trigger of table %s. Using default character set.

  • Error number: MY-010063; Symbol: ER_PARSING_VIEW; SQLSTATE: HY000

    Message: Error in parsing view %s.%s

  • Error number: MY-010064; Symbol: ER_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP; SQLSTATE: HY000

    Message: Failed to bootstrap components infrastructure.

  • Error number: MY-010065; Symbol: ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN; SQLSTATE: HY000

    Message: Failed to shutdown components infrastructure.

  • Error number: MY-010066; Symbol: ER_COMPONENTS_PERSIST_LOADER_BOOTSTRAP; SQLSTATE: HY000

    Message: Failed to bootstrap persistent components loader.

  • Error number: MY-010067; Symbol: ER_DEPART_WITH_GRACE; SQLSTATE: HY000

    Message: Giving %d client threads a chance to die gracefully

  • Error number: MY-010068; Symbol: ER_CA_SELF_SIGNED; SQLSTATE: HY000

    Message: CA certificate %s is self signed.

  • Error number: MY-010069; Symbol: ER_SSL_LIBRARY_ERROR; SQLSTATE: HY000

    Message: Failed to set up SSL because of the following SSL library error: %s

  • Error number: MY-010070; Symbol: ER_NO_THD_NO_UUID; SQLSTATE: HY000

    Message: Failed to generate a server UUID because it is failed to allocate the THD.

  • Error number: MY-010071; Symbol: ER_UUID_SALT; SQLSTATE: HY000

    Message: Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu,

  • Error number: MY-010072; Symbol: ER_UUID_IS; SQLSTATE: HY000

    Message: Generated uuid: '%s', server_start_time: %lu, bytes_sent: %llu

  • Error number: MY-010073; Symbol: ER_UUID_INVALID; SQLSTATE: HY000

    Message: The server_uuid stored in auto.cnf file is not a valid UUID.

  • Error number: MY-010074; Symbol: ER_UUID_SCRUB; SQLSTATE: HY000

    Message: Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server.

  • Error number: MY-010075; Symbol: ER_CREATING_NEW_UUID; SQLSTATE: HY000

    Message: No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.

  • Error number: MY-010076; Symbol: ER_CANT_CREATE_UUID; SQLSTATE: HY000

    Message: Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.

  • Error number: MY-010077; Symbol: ER_UNKNOWN_UNSUPPORTED_STORAGE_ENGINE; SQLSTATE: HY000

    Message: Unknown/unsupported storage engine: %s

  • Error number: MY-010078; Symbol: ER_SECURE_AUTH_VALUE_UNSUPPORTED; SQLSTATE: HY000

    Message: Unsupported value 0 for secure-auth

  • Error number: MY-010079; Symbol: ER_INVALID_INSTRUMENT; SQLSTATE: HY000

    Message: Invalid instrument name or value for performance_schema_instrument '%s'.

  • Error number: MY-010080; Symbol: ER_INNODB_MANDATORY; SQLSTATE: HY000

    Message: The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.

  • Error number: MY-010083; Symbol: ER_VERBOSE_REQUIRES_HELP; SQLSTATE: HY000

    Message: --verbose is for use with --help; did you mean --log-error-verbosity?

  • Error number: MY-010084; Symbol: ER_POINTLESS_WITHOUT_SLOWLOG; SQLSTATE: HY000

    Message: options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not set

  • Error number: MY-010085; Symbol: ER_WASTEFUL_NET_BUFFER_SIZE; SQLSTATE: HY000

    Message: net_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.

  • Error number: MY-010086; Symbol: ER_DEPRECATED_TIMESTAMP_IMPLICIT_DEFAULTS; SQLSTATE: HY000

    Message: TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

  • Error number: MY-010087; Symbol: ER_FT_BOOL_SYNTAX_INVALID; SQLSTATE: HY000

    Message: Invalid ft-boolean-syntax string: %s

  • Error number: MY-010088; Symbol: ER_CREDENTIALLESS_AUTO_USER_BAD; SQLSTATE: HY000

    Message: 'NO_AUTO_CREATE_USER' sql mode was not set.

  • Error number: MY-010089; Symbol: ER_CONNECTION_HANDLING_OOM; SQLSTATE: HY000

    Message: Could not allocate memory for connection handling

  • Error number: MY-010090; Symbol: ER_THREAD_HANDLING_OOM; SQLSTATE: HY000

    Message: Could not allocate memory for thread handling

  • Error number: MY-010091; Symbol: ER_CANT_CREATE_TEST_FILE; SQLSTATE: HY000

    Message: Can't create test file %s

  • Error number: MY-010092; Symbol: ER_CANT_CREATE_PID_FILE; SQLSTATE: HY000

    Message: Can't start server: can't create PID file: %s

  • Error number: MY-010093; Symbol: ER_CANT_REMOVE_PID_FILE; SQLSTATE: HY000

    Message: Unable to delete pid file: %s

  • Error number: MY-010094; Symbol: ER_CANT_CREATE_SHUTDOWN_THREAD; SQLSTATE: HY000

    Message: Can't create thread to handle shutdown requests (errno= %d)

  • Error number: MY-010095; Symbol: ER_SEC_FILE_PRIV_CANT_ACCESS_DIR; SQLSTATE: HY000

    Message: Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %s

  • Error number: MY-010096; Symbol: ER_SEC_FILE_PRIV_IGNORED; SQLSTATE: HY000

    Message: Ignoring --secure-file-priv value as server is running with --initialize(-insecure).

  • Error number: MY-010097; Symbol: ER_SEC_FILE_PRIV_EMPTY; SQLSTATE: HY000

    Message: Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.

  • Error number: MY-010098; Symbol: ER_SEC_FILE_PRIV_NULL; SQLSTATE: HY000

    Message: --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled

  • Error number: MY-010099; Symbol: ER_SEC_FILE_PRIV_DIRECTORY_INSECURE; SQLSTATE: HY000

    Message: Insecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.

  • Error number: MY-010100; Symbol: ER_SEC_FILE_PRIV_CANT_STAT; SQLSTATE: HY000

    Message: Failed to get stat for directory pointed out by --secure-file-priv

  • Error number: MY-010101; Symbol: ER_SEC_FILE_PRIV_DIRECTORY_PERMISSIONS; SQLSTATE: HY000

    Message: Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.

  • Error number: MY-010102; Symbol: ER_SEC_FILE_PRIV_ARGUMENT_TOO_LONG; SQLSTATE: HY000

    Message: Value for --secure-file-priv is longer than maximum limit of %d

  • Error number: MY-010103; Symbol: ER_CANT_CREATE_NAMED_PIPES_THREAD; SQLSTATE: HY000

    Message: Can't create thread to handle named pipes (errno= %d)

  • Error number: MY-010104; Symbol: ER_CANT_CREATE_TCPIP_THREAD; SQLSTATE: HY000

    Message: Can't create thread to handle TCP/IP (errno= %d)

  • Error number: MY-010105; Symbol: ER_CANT_CREATE_SHM_THREAD; SQLSTATE: HY000

    Message: Can't create thread to handle shared memory (errno= %d)

  • Error number: MY-010106; Symbol: ER_CANT_CREATE_INTERRUPT_THREAD; SQLSTATE: HY000

    Message: Can't create interrupt-thread (error %d, errno: %d)

  • Error number: MY-010107; Symbol: ER_WRITABLE_CONFIG_REMOVED; SQLSTATE: HY000

    Message: World-writable config file '%s' has been removed.

  • Error number: MY-010108; Symbol: ER_CORE_VALUES; SQLSTATE: HY000

    Message: setrlimit could not change the size of core files to 'infinity'; We may not be able to generate a core file on signals

  • Error number: MY-010109; Symbol: ER_WRONG_DATETIME_SPEC; SQLSTATE: HY000

    Message: Wrong date/time format specifier: %s

  • Error number: MY-010110; Symbol: ER_RPL_BINLOG_FILTERS_OOM; SQLSTATE: HY000

    Message: Could not allocate replication and binlog filters: %s

  • Error number: MY-010111; Symbol: ER_KEYCACHE_OOM; SQLSTATE: HY000

    Message: Cannot allocate the keycache

  • Error number: MY-010112; Symbol: ER_CONFIRMING_THE_FUTURE; SQLSTATE: HY000

    Message: Current time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.

  • Error number: MY-010113; Symbol: ER_BACK_IN_TIME; SQLSTATE: HY000

    Message: Iteration %d: Obtained valid current time from system

  • Error number: MY-010114; Symbol: ER_FUTURE_DATE; SQLSTATE: HY000

    Message: Iteration %d: Current time obtained from system is greater than 2038

  • Error number: MY-010115; Symbol: ER_UNSUPPORTED_DATE; SQLSTATE: HY000

    Message: This MySQL server doesn't support dates later then 2038

  • Error number: MY-010116; Symbol: ER_STARTING_AS; SQLSTATE: HY000

    Message: %s (mysqld %s) starting as process %lu

  • Error number: MY-010117; Symbol: ER_SHUTTING_DOWN_REPLICA_THREADS; SQLSTATE: HY000

    Message: Shutting down replica threads

  • Error number: MY-010118; Symbol: ER_DISCONNECTING_REMAINING_CLIENTS; SQLSTATE: HY000

    Message: Forcefully disconnecting %d remaining clients

  • Error number: MY-010119; Symbol: ER_ABORTING; SQLSTATE: HY000

    Message: Aborting

  • Error number: MY-010120; Symbol: ER_BINLOG_END; SQLSTATE: HY000

    Message: Binlog end

  • Error number: MY-010121; Symbol: ER_CALL_ME_LOCALHOST; SQLSTATE: HY000

    Message: gethostname failed, using '%s' as hostname

  • Error number: MY-010122; Symbol: ER_USER_REQUIRES_ROOT; SQLSTATE: HY000

    Message: One can only use the --user switch if running as root

  • Error number: MY-010123; Symbol: ER_REALLY_RUN_AS_ROOT; SQLSTATE: HY000

    Message: Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

  • Error number: MY-010124; Symbol: ER_USER_WHAT_USER; SQLSTATE: HY000

    Message: Fatal error: Can't change to run as user '%s' ; Please check that the user exists!

  • Error number: MY-010125; Symbol: ER_TRANSPORTS_WHAT_TRANSPORTS; SQLSTATE: HY000

    Message: Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.

  • Error number: MY-010126; Symbol: ER_FAIL_SETGID; SQLSTATE: HY000

    Message: setgid: %s

  • Error number: MY-010127; Symbol: ER_FAIL_SETUID; SQLSTATE: HY000

    Message: setuid: %s

  • Error number: MY-010128; Symbol: ER_FAIL_SETREGID; SQLSTATE: HY000

    Message: setregid: %s

  • Error number: MY-010129; Symbol: ER_FAIL_SETREUID; SQLSTATE: HY000

    Message: setreuid: %s

  • Error number: MY-010130; Symbol: ER_FAIL_CHROOT; SQLSTATE: HY000

    Message: chroot: %s

  • Error number: MY-010131; Symbol: ER_WIN_LISTEN_BUT_HOW; SQLSTATE: HY000

    Message: TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS

  • Error number: MY-010132; Symbol: ER_NOT_RIGHT_NOW; SQLSTATE: HY000

    Message: CTRL-C ignored during startup

  • Error number: MY-010133; Symbol: ER_FIXING_CLIENT_CHARSET; SQLSTATE: HY000

    Message: '%s' can not be used as client character set. '%s' will be used as default client character set.

  • Error number: MY-010134; Symbol: ER_OOM; SQLSTATE: HY000

    Message: Out of memory

  • Error number: MY-010135; Symbol: ER_FAILED_TO_LOCK_MEM; SQLSTATE: HY000

    Message: Failed to lock memory. Errno: %d

  • Error number: MY-010136; Symbol: ER_MYINIT_FAILED; SQLSTATE: HY000

    Message: my_init() failed.

  • Error number: MY-010137; Symbol: ER_BEG_INITFILE; SQLSTATE: HY000

    Message: Execution of init_file \'%s\' started.

  • Error number: MY-010138; Symbol: ER_END_INITFILE; SQLSTATE: HY000

    Message: Execution of init_file \'%s\' ended.

  • Error number: MY-010139; Symbol: ER_CHANGED_MAX_OPEN_FILES; SQLSTATE: HY000

    Message: Changed limits: max_open_files: %lu (requested %lu)

  • Error number: MY-010140; Symbol: ER_CANT_INCREASE_MAX_OPEN_FILES; SQLSTATE: HY000

    Message: Could not increase number of max_open_files to more than %lu (request: %lu)

  • Error number: MY-010141; Symbol: ER_CHANGED_MAX_CONNECTIONS; SQLSTATE: HY000

    Message: Changed limits: max_connections: %lu (requested %lu)

  • Error number: MY-010142; Symbol: ER_CHANGED_TABLE_OPEN_CACHE; SQLSTATE: HY000

    Message: Changed limits: table_open_cache: %lu (requested %lu)

  • Error number: MY-010143; Symbol: ER_THE_USER_ABIDES; SQLSTATE: HY000

    Message: Ignoring user change to '%s' because the user was set to '%s' earlier on the command line

  • Error number: MY-010144; Symbol: ER_RPL_CANT_ADD_DO_TABLE; SQLSTATE: HY000

    Message: Could not add do table rule '%s'!

  • Error number: MY-010145; Symbol: ER_RPL_CANT_ADD_IGNORE_TABLE; SQLSTATE: HY000

    Message: Could not add ignore table rule '%s'!

  • Error number: MY-010146; Symbol: ER_TRACK_VARIABLES_BOGUS; SQLSTATE: HY000

    Message: The variable session_track_system_variables either has duplicate values or invalid values.

  • Error number: MY-010147; Symbol: ER_EXCESS_ARGUMENTS; SQLSTATE: HY000

    Message: Too many arguments (first extra is '%s').

  • Error number: MY-010148; Symbol: ER_VERBOSE_HINT; SQLSTATE: HY000

    Message: Use --verbose --help to get a list of available options!

  • Error number: MY-010149; Symbol: ER_CANT_READ_ERRMSGS; SQLSTATE: HY000

    Message: Unable to read errmsg.sys file

  • Error number: MY-010150; Symbol: ER_CANT_INIT_DBS; SQLSTATE: HY000

    Message: Can't init databases

  • Error number: MY-010151; Symbol: ER_LOG_OUTPUT_CONTRADICTORY; SQLSTATE: HY000

    Message: There were other values specified to log-output besides NONE. Disabling slow and general logs anyway.

  • Error number: MY-010152; Symbol: ER_NO_CSV_NO_LOG_TABLES; SQLSTATE: HY000

    Message: CSV engine is not present, falling back to the log files

  • Error number: MY-010153; Symbol: ER_RPL_REWRITEDB_MISSING_ARROW; SQLSTATE: HY000

    Message: Bad syntax in replicate-rewrite-db - missing '->'!

  • Error number: MY-010154; Symbol: ER_RPL_REWRITEDB_EMPTY_FROM; SQLSTATE: HY000

    Message: Bad syntax in replicate-rewrite-db - empty FROM db!

  • Error number: MY-010155; Symbol: ER_RPL_REWRITEDB_EMPTY_TO; SQLSTATE: HY000

    Message: Bad syntax in replicate-rewrite-db - empty TO db!

  • Error number: MY-010156; Symbol: ER_LOG_FILES_GIVEN_LOG_OUTPUT_IS_TABLE; SQLSTATE: HY000

    Message: Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.

  • Error number: MY-010157; Symbol: ER_LOG_FILE_INVALID; SQLSTATE: HY000

    Message: Invalid value for %s: %s

  • Error number: MY-010158; Symbol: ER_LOWER_CASE_TABLE_NAMES_CS_DD_ON_CI_FS_UNSUPPORTED; SQLSTATE: HY000

    Message: The server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.

  • Error number: MY-010159; Symbol: ER_LOWER_CASE_TABLE_NAMES_USING_2; SQLSTATE: HY000

    Message: Setting lower_case_table_names=2 because file system for %s is case insensitive

  • Error number: MY-010160; Symbol: ER_LOWER_CASE_TABLE_NAMES_USING_0; SQLSTATE: HY000

    Message: lower_case_table_names was set to 2, even though your the file system '%s' is case sensitive. Now setting lower_case_table_names to 0 to avoid future problems.

  • Error number: MY-010161; Symbol: ER_NEED_LOG_BIN; SQLSTATE: HY000

    Message: You need to use --log-bin to make %s work.

  • Error number: MY-010162; Symbol: ER_NEED_FILE_INSTEAD_OF_DIR; SQLSTATE: HY000

    Message: Path '%s' is a directory name, please specify a file name for %s option

  • Error number: MY-010163; Symbol: ER_LOG_BIN_BETTER_WITH_NAME; SQLSTATE: HY000

    Message: No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.

  • Error number: MY-010164; Symbol: ER_BINLOG_NEEDS_SERVERID; SQLSTATE: HY000

    Message: You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentation

  • Error number: MY-010165; Symbol: ER_RPL_CANT_MAKE_PATHS; SQLSTATE: HY000

    Message: Unable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).

  • Error number: MY-010166; Symbol: ER_CANT_INITIALIZE_GTID; SQLSTATE: HY000

    Message: Failed to initialize GTID structures.

  • Error number: MY-010167; Symbol: ER_CANT_INITIALIZE_EARLY_PLUGINS; SQLSTATE: HY000

    Message: Failed to initialize early plugins.

  • Error number: MY-010168; Symbol: ER_CANT_INITIALIZE_BUILTIN_PLUGINS; SQLSTATE: HY000

    Message: Failed to initialize builtin plugins.

  • Error number: MY-010169; Symbol: ER_CANT_INITIALIZE_DYNAMIC_PLUGINS; SQLSTATE: HY000

    Message: Failed to initialize dynamic plugins.

  • Error number: MY-010170; Symbol: ER_PERFSCHEMA_INIT_FAILED; SQLSTATE: HY000

    Message: Performance schema disabled (reason: init failed).

  • Error number: MY-010171; Symbol: ER_STACKSIZE_UNEXPECTED; SQLSTATE: HY000

    Message: Asked for %lu thread stack, but got %ld

  • Error number: MY-010173; Symbol: ER_CANT_STAT_DATADIR; SQLSTATE: HY000

    Message: Can't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/group

  • Error number: MY-010174; Symbol: ER_CANT_CHOWN_DATADIR; SQLSTATE: HY000

    Message: Can't change data directory owner to %s

  • Error number: MY-010175; Symbol: ER_CANT_SET_UP_PERSISTED_VALUES; SQLSTATE: HY000

    Message: Setting persistent options failed.

  • Error number: MY-010176; Symbol: ER_CANT_SAVE_GTIDS; SQLSTATE: HY000

    Message: Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.

  • Error number: MY-010178; Symbol: ER_CANT_JOIN_SHUTDOWN_THREAD; SQLSTATE: HY000

    Message: Could not join %sthread. error:%d

  • Error number: MY-010179; Symbol: ER_CANT_HASH_DO_AND_IGNORE_RULES; SQLSTATE: HY000

    Message: An error occurred while building do_table and ignore_table rules to hashes for global replication filter.

  • Error number: MY-010180; Symbol: ER_CANT_OPEN_CA; SQLSTATE: HY000

    Message: Error opening CA certificate file

  • Error number: MY-010181; Symbol: ER_CANT_ACCESS_CAPATH; SQLSTATE: HY000

    Message: Error accessing directory pointed by --ssl-capath

  • Error number: MY-010182; Symbol: ER_SSL_TRYING_DATADIR_DEFAULTS; SQLSTATE: HY000

    Message: Found %s, %s and %s in data directory. Trying to enable SSL support using them.

  • Error number: MY-010183; Symbol: ER_AUTO_OPTIONS_FAILED; SQLSTATE: HY000

    Message: Failed to create %s(file: '%s', errno %d)

  • Error number: MY-010184; Symbol: ER_CANT_INIT_TIMER; SQLSTATE: HY000

    Message: Failed to initialize timer component (errno %d).

  • Error number: MY-010185; Symbol: ER_SERVERID_TOO_LARGE; SQLSTATE: HY000

    Message: server-id configured is too large to represent with server-id-bits configured.

  • Error number: MY-010186; Symbol: ER_DEFAULT_SE_UNAVAILABLE; SQLSTATE: HY000

    Message: Default%s storage engine (%s) is not available

  • Error number: MY-010187; Symbol: ER_CANT_OPEN_ERROR_LOG; SQLSTATE: HY000

    Message: Could not open file '%s' for error logging%s%s

  • Error number: MY-010188; Symbol: ER_INVALID_ERROR_LOG_NAME; SQLSTATE: HY000

    Message: Invalid log file name after expanding symlinks: '%s'

  • Error number: MY-010189; Symbol: ER_RPL_INFINITY_DENIED; SQLSTATE: HY000

    Message: using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.

  • Error number: MY-010190; Symbol: ER_RPL_INFINITY_IGNORED; SQLSTATE: HY000

    Message: using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.

  • Error number: MY-010192; Symbol: ER_TABLE_CHECK_INTACT; SQLSTATE: HY000

    Message: %s

  • Error number: MY-010193; Symbol: ER_DD_TABLESPACE_NOT_FOUND; SQLSTATE: HY000

    Message: Unable to start server. The data dictionary tablespace '%s' does not exist.

  • Error number: MY-010194; Symbol: ER_DD_TRG_CONNECTION_COLLATION_MISSING; SQLSTATE: HY000

    Message: Connection collation is missing for trigger of table %s. Using default connection collation.

  • Error number: MY-010195; Symbol: ER_DD_TRG_DB_COLLATION_MISSING; SQLSTATE: HY000

    Message: Database collation is missing for trigger of table %s. Using Default character set.

  • Error number: MY-010196; Symbol: ER_DD_TRG_DEFINER_OOM; SQLSTATE: HY000

    Message: Error in Memory allocation for Definer %s for Trigger.

  • Error number: MY-010197; Symbol: ER_DD_TRG_FILE_UNREADABLE; SQLSTATE: HY000

    Message: Error in reading %s.TRG file.

  • Error number: MY-010198; Symbol: ER_TRG_CANT_PARSE; SQLSTATE: HY000

    Message: Error in parsing Triggers from %s.TRG file.

  • Error number: MY-010199; Symbol: ER_DD_TRG_CANT_ADD; SQLSTATE: HY000

    Message: Error in creating DD entry for Trigger %s.%s

  • Error number: MY-010200; Symbol: ER_DD_CANT_RESOLVE_VIEW; SQLSTATE: HY000

    Message: Resolving dependency for the view '%s.%s' failed. View is no more valid to use

  • Error number: MY-010201; Symbol: ER_DD_VIEW_WITHOUT_DEFINER; SQLSTATE: HY000

    Message: %s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.

  • Error number: MY-010202; Symbol: ER_PLUGIN_INIT_FAILED; SQLSTATE: HY000

    Message: Plugin '%s' init function returned error.

  • Error number: MY-010203; Symbol: ER_RPL_TRX_DELEGATES_INIT_FAILED; SQLSTATE: HY000

    Message: Initialization of transaction delegates failed. Please report a bug.

  • Error number: MY-010204; Symbol: ER_RPL_BINLOG_STORAGE_DELEGATES_INIT_FAILED; SQLSTATE: HY000

    Message: Initialization binlog storage delegates failed. Please report a bug.

  • Error number: MY-010205; Symbol: ER_RPL_BINLOG_TRANSMIT_DELEGATES_INIT_FAILED; SQLSTATE: HY000

    Message: Initialization of binlog transmit delegates failed. Please report a bug.

  • Error number: MY-010206; Symbol: ER_RPL_BINLOG_RELAY_DELEGATES_INIT_FAILED; SQLSTATE: HY000

    Message: Initialization binlog relay IO delegates failed. Please report a bug.

  • Error number: MY-010207; Symbol: ER_RPL_PLUGIN_FUNCTION_FAILED; SQLSTATE: HY000

    Message: Run function '...' in plugin '%s' failed

  • Error number: MY-010208; Symbol: ER_SQL_HA_READ_FAILED; SQLSTATE: HY000

    Message: mysql_ha_read: Got error %d when reading table '%s'

  • Error number: MY-010209; Symbol: ER_SR_BOGUS_VALUE; SQLSTATE: HY000

    Message: Stored routine '%s'.'%s': invalid value in column %s.

  • Error number: MY-010210; Symbol: ER_SR_INVALID_CONTEXT; SQLSTATE: HY000

    Message: Invalid creation context '%s.%s'.

  • Error number: MY-010211; Symbol: ER_READING_TABLE_FAILED; SQLSTATE: HY000

    Message: Got error %d when reading table '%s'

  • Error number: MY-010212; Symbol: ER_DES_FILE_WRONG_KEY; SQLSTATE: HY000

    Message: load_des_file: Found wrong key_number: %c

  • Error number: MY-010214; Symbol: ER_JSON_PARSE_ERROR; SQLSTATE: HY000

    Message: Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.

  • Error number: MY-010215; Symbol: ER_CONFIG_OPTION_WITHOUT_GROUP; SQLSTATE: HY000

    Message: Found option without preceding group in config file

  • Error number: MY-010216; Symbol: ER_VALGRIND_DO_QUICK_LEAK_CHECK; SQLSTATE: HY000

    Message: VALGRIND_DO_QUICK_LEAK_CHECK

  • Error number: MY-010217; Symbol: ER_VALGRIND_COUNT_LEAKS; SQLSTATE: HY000

    Message: VALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'

  • Error number: MY-010218; Symbol: ER_LOAD_DATA_INFILE_FAILED_IN_UNEXPECTED_WAY; SQLSTATE: HY000

    Message: LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.

  • Error number: MY-010219; Symbol: ER_UNKNOWN_ERROR_NUMBER; SQLSTATE: HY000

    Message: Got unknown error: %d

  • Error number: MY-010220; Symbol: ER_UDF_CANT_ALLOC_FOR_STRUCTURES; SQLSTATE: HY000

    Message: Can't allocate memory for udf structures

  • Error number: MY-010221; Symbol: ER_UDF_CANT_ALLOC_FOR_FUNCTION; SQLSTATE: HY000

    Message: Can't alloc memory for udf function: '%s'

  • Error number: MY-010222; Symbol: ER_UDF_INVALID_ROW_IN_FUNCTION_TABLE; SQLSTATE: HY000

    Message: Invalid row in mysql.func table for function '%s'

  • Error number: MY-010223; Symbol: ER_UDF_CANT_OPEN_FUNCTION_TABLE; SQLSTATE: HY000

    Message: Could not open the mysql.func table. Please perform the MySQL upgrade procedure.

  • Error number: MY-010224; Symbol: ER_XA_RECOVER_FOUND_TRX_IN_SE; SQLSTATE: HY000

    Message: Found %d prepared transaction(s) in %s

  • Error number: MY-010225; Symbol: ER_XA_RECOVER_FOUND_XA_TRX; SQLSTATE: HY000

    Message: Found %d prepared XA transactions

  • Error number: MY-010229; Symbol: ER_XA_STARTING_RECOVERY; SQLSTATE: HY000

    Message: Starting XA crash recovery...

  • Error number: MY-010230; Symbol: ER_XA_NO_MULTI_2PC_HEURISTIC_RECOVER; SQLSTATE: HY000

    Message: --tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.

  • Error number: MY-010231; Symbol: ER_XA_RECOVER_EXPLANATION; SQLSTATE: HY000

    Message: Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.

  • Error number: MY-010232; Symbol: ER_XA_RECOVERY_DONE; SQLSTATE: HY000

    Message: XA crash recovery finished.

  • Error number: MY-010233; Symbol: ER_TRX_GTID_COLLECT_REJECT; SQLSTATE: HY000

    Message: Failed to collect GTID to send in the response packet!

  • Error number: MY-010234; Symbol: ER_SQL_AUTHOR_DEFAULT_ROLES_FAIL; SQLSTATE: HY000

    Message: MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %s

  • Error number: MY-010235; Symbol: ER_SQL_USER_TABLE_CREATE_WARNING; SQLSTATE: HY000

    Message: Following users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %s

  • Error number: MY-010236; Symbol: ER_SQL_USER_TABLE_ALTER_WARNING; SQLSTATE: HY000

    Message: Following users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %s

  • Error number: MY-010237; Symbol: ER_ROW_IN_WRONG_PARTITION_PLEASE_REPAIR; SQLSTATE: HY000

    Message: Table '%s' corrupted: row in wrong partition: %s -- Please REPAIR the table!

  • Error number: MY-010238; Symbol: ER_MYISAM_CRASHED_ERROR_IN_THREAD; SQLSTATE: HY000

    Message: Got an error from thread_id=%u, %s:%d

  • Error number: MY-010239; Symbol: ER_MYISAM_CRASHED_ERROR_IN; SQLSTATE: HY000

    Message: Got an error from unknown thread, %s:%d

  • Error number: MY-010240; Symbol: ER_TOO_MANY_STORAGE_ENGINES; SQLSTATE: HY000

    Message: Too many storage engines!

  • Error number: MY-010241; Symbol: ER_SE_TYPECODE_CONFLICT; SQLSTATE: HY000

    Message: Storage engine '%s' has conflicting typecode. Assigning value %d.

  • Error number: MY-010242; Symbol: ER_TRX_WRITE_SET_OOM; SQLSTATE: HY000

    Message: Out of memory on transaction write set extraction

  • Error number: MY-010243; Symbol: ER_HANDLERTON_OOM; SQLSTATE: HY000

    Message: Unable to allocate memory for plugin '%s' handlerton.

  • Error number: MY-010244; Symbol: ER_CONN_SHM_LISTENER; SQLSTATE: HY000

    Message: Shared memory setting up listener

  • Error number: MY-010245; Symbol: ER_CONN_SHM_CANT_CREATE_SERVICE; SQLSTATE: HY000

    Message: Can't create shared memory service: %s. : %s

  • Error number: MY-010246; Symbol: ER_CONN_SHM_CANT_CREATE_CONNECTION; SQLSTATE: HY000

    Message: Can't create shared memory connection: %s. : %s

  • Error number: MY-010247; Symbol: ER_CONN_PIP_CANT_CREATE_EVENT; SQLSTATE: HY000

    Message: Can't create event, last error=%u

  • Error number: MY-010248; Symbol: ER_CONN_PIP_CANT_CREATE_PIPE; SQLSTATE: HY000

    Message: Can't create new named pipe!: %s

  • Error number: MY-010249; Symbol: ER_CONN_PER_THREAD_NO_THREAD; SQLSTATE: HY000

    Message: Can't create thread to handle new connection(errno= %d)

  • Error number: MY-010250; Symbol: ER_CONN_TCP_NO_SOCKET; SQLSTATE: HY000

    Message: Failed to create a socket for %s '%s': errno: %d.

  • Error number: MY-010251; Symbol: ER_CONN_TCP_CREATED; SQLSTATE: HY000

    Message: Server socket created on IP: '%s'.

  • Error number: MY-010252; Symbol: ER_CONN_TCP_ADDRESS; SQLSTATE: HY000

    Message: Server hostname (bind-address): '%s'; port: %d

  • Error number: MY-010253; Symbol: ER_CONN_TCP_IPV6_AVAILABLE; SQLSTATE: HY000

    Message: IPv6 is available.

  • Error number: MY-010254; Symbol: ER_CONN_TCP_IPV6_UNAVAILABLE; SQLSTATE: HY000

    Message: IPv6 is not available.

  • Error number: MY-010255; Symbol: ER_CONN_TCP_ERROR_WITH_STRERROR; SQLSTATE: HY000

    Message: Can't create IP socket: %s

  • Error number: MY-010256; Symbol: ER_CONN_TCP_CANT_RESOLVE_HOSTNAME; SQLSTATE: HY000

    Message: Can't start server: cannot resolve hostname!

  • Error number: MY-010257; Symbol: ER_CONN_TCP_IS_THERE_ANOTHER_USING_PORT; SQLSTATE: HY000

    Message: Do you already have another mysqld server running on port: %d ?

  • Error number: MY-010258; Symbol: ER_CONN_UNIX_IS_THERE_ANOTHER_USING_SOCKET; SQLSTATE: HY000

    Message: Do you already have another mysqld server running on socket: %s ?

  • Error number: MY-010259; Symbol: ER_CONN_UNIX_PID_CLAIMED_SOCKET_FILE; SQLSTATE: HY000

    Message: Another process with pid %d is using unix socket file.

  • Error number: MY-010260; Symbol: ER_CONN_TCP_CANT_RESET_V6ONLY; SQLSTATE: HY000

    Message: Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.

  • Error number: MY-010261; Symbol: ER_CONN_TCP_BIND_RETRY; SQLSTATE: HY000

    Message: Retrying bind on TCP/IP port %u

  • Error number: MY-010262; Symbol: ER_CONN_TCP_BIND_FAIL; SQLSTATE: HY000

    Message: Can't start server: Bind on TCP/IP port: %s

  • Error number: MY-010263; Symbol: ER_CONN_TCP_IP_NOT_LOGGED; SQLSTATE: HY000

    Message: Fails to print out IP-address.

  • Error number: MY-010264; Symbol: ER_CONN_TCP_RESOLVE_INFO; SQLSTATE: HY000

    Message: - '%s' resolves to '%s';

  • Error number: MY-010265; Symbol: ER_CONN_TCP_START_FAIL; SQLSTATE: HY000

    Message: Can't start server: listen() on TCP/IP port: %s

  • Error number: MY-010266; Symbol: ER_CONN_TCP_LISTEN_FAIL; SQLSTATE: HY000

    Message: listen() on TCP/IP failed with error %d

  • Error number: MY-010267; Symbol: ER_CONN_UNIX_PATH_TOO_LONG; SQLSTATE: HY000

    Message: The socket file path is too long (> %u): %s

  • Error number: MY-010268; Symbol: ER_CONN_UNIX_LOCK_FILE_FAIL; SQLSTATE: HY000

    Message: Unable to setup unix socket lock file.

  • Error number: MY-010269; Symbol: ER_CONN_UNIX_NO_FD; SQLSTATE: HY000

    Message: Can't start server: UNIX Socket : %s

  • Error number: MY-010270; Symbol: ER_CONN_UNIX_NO_BIND_NO_START; SQLSTATE: HY000

    Message: Can't start server : Bind on unix socket: %s

  • Error number: MY-010271; Symbol: ER_CONN_UNIX_LISTEN_FAILED; SQLSTATE: HY000

    Message: listen() on Unix socket failed with error %d

  • Error number: MY-010272; Symbol: ER_CONN_UNIX_LOCK_FILE_GIVING_UP; SQLSTATE: HY000

    Message: Unable to create unix socket lock file %s after retries.

  • Error number: MY-010273; Symbol: ER_CONN_UNIX_LOCK_FILE_CANT_CREATE; SQLSTATE: HY000

    Message: Could not create unix socket lock file %s.

  • Error number: MY-010274; Symbol: ER_CONN_UNIX_LOCK_FILE_CANT_OPEN; SQLSTATE: HY000

    Message: Could not open unix socket lock file %s.

  • Error number: MY-010275; Symbol: ER_CONN_UNIX_LOCK_FILE_CANT_READ; SQLSTATE: HY000

    Message: Could not read unix socket lock file %s.

  • Error number: MY-010276; Symbol: ER_CONN_UNIX_LOCK_FILE_EMPTY; SQLSTATE: HY000

    Message: Unix socket lock file is empty %s.

  • Error number: MY-010277; Symbol: ER_CONN_UNIX_LOCK_FILE_PIDLESS; SQLSTATE: HY000

    Message: Invalid pid in unix socket lock file %s.

  • Error number: MY-010278; Symbol: ER_CONN_UNIX_LOCK_FILE_CANT_WRITE; SQLSTATE: HY000

    Message: Could not write unix socket lock file %s errno %d.

  • Error number: MY-010279; Symbol: ER_CONN_UNIX_LOCK_FILE_CANT_DELETE; SQLSTATE: HY000

    Message: Could not remove unix socket lock file %s errno %d.

  • Error number: MY-010280; Symbol: ER_CONN_UNIX_LOCK_FILE_CANT_SYNC; SQLSTATE: HY000

    Message: Could not sync unix socket lock file %s errno %d.

  • Error number: MY-010281; Symbol: ER_CONN_UNIX_LOCK_FILE_CANT_CLOSE; SQLSTATE: HY000

    Message: Could not close unix socket lock file %s errno %d.

  • Error number: MY-010282; Symbol: ER_CONN_SOCKET_SELECT_FAILED; SQLSTATE: HY000

    Message: mysqld: Got error %d from select

  • Error number: MY-010283; Symbol: ER_CONN_SOCKET_ACCEPT_FAILED; SQLSTATE: HY000

    Message: Error in accept: %s

  • Error number: MY-010284; Symbol: ER_AUTH_RSA_CANT_FIND; SQLSTATE: HY000

    Message: RSA %s key file not found: %s. Some authentication plugins will not work.

  • Error number: MY-010285; Symbol: ER_AUTH_RSA_CANT_PARSE; SQLSTATE: HY000

    Message: Failure to parse RSA %s key (file exists): %s: %s

  • Error number: MY-010286; Symbol: ER_AUTH_RSA_CANT_READ; SQLSTATE: HY000

    Message: Failure to read key file: %s

  • Error number: MY-010287; Symbol: ER_AUTH_RSA_FILES_NOT_FOUND; SQLSTATE: HY000

    Message: RSA key files not found. Some authentication plugins will not work.

  • Error number: MY-010288; Symbol: ER_CONN_ATTR_TRUNCATED; SQLSTATE: HY000

    Message: Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %s

  • Error number: MY-010289; Symbol: ER_X509_CIPHERS_MISMATCH; SQLSTATE: HY000

    Message: X.509 ciphers mismatch: should be '%s' but is '%s'

  • Error number: MY-010290; Symbol: ER_X509_ISSUER_MISMATCH; SQLSTATE: HY000

    Message: X.509 issuer mismatch: should be '%s' but is '%s'

  • Error number: MY-010291; Symbol: ER_X509_SUBJECT_MISMATCH; SQLSTATE: HY000

    Message: X.509 subject mismatch: should be '%s' but is '%s'

  • Error number: MY-010292; Symbol: ER_AUTH_CANT_ACTIVATE_ROLE; SQLSTATE: HY000

    Message: Failed to activate default role %s for %s

  • Error number: MY-010293; Symbol: ER_X509_NEEDS_RSA_PRIVKEY; SQLSTATE: HY000

    Message: Could not generate RSA private key required for X.509 certificate.

  • Error number: MY-010294; Symbol: ER_X509_CANT_WRITE_KEY; SQLSTATE: HY000

    Message: Could not write key file: %s

  • Error number: MY-010295; Symbol: ER_X509_CANT_CHMOD_KEY; SQLSTATE: HY000

    Message: Could not set file permission for %s

  • Error number: MY-010296; Symbol: ER_X509_CANT_READ_CA_KEY; SQLSTATE: HY000

    Message: Could not read CA key file: %s

  • Error number: MY-010297; Symbol: ER_X509_CANT_READ_CA_CERT; SQLSTATE: HY000

    Message: Could not read CA certificate file: %s

  • Error number: MY-010298; Symbol: ER_X509_CANT_CREATE_CERT; SQLSTATE: HY000

    Message: Could not generate X.509 certificate.

  • Error number: MY-010299; Symbol: ER_X509_CANT_WRITE_CERT; SQLSTATE: HY000

    Message: Could not write certificate file: %s

  • Error number: MY-010300; Symbol: ER_AUTH_CANT_CREATE_RSA_PAIR; SQLSTATE: HY000

    Message: Could not generate RSA Private/Public key pair

  • Error number: MY-010301; Symbol: ER_AUTH_CANT_WRITE_PRIVKEY; SQLSTATE: HY000

    Message: Could not write private key file: %s

  • Error number: MY-010302; Symbol: ER_AUTH_CANT_WRITE_PUBKEY; SQLSTATE: HY000

    Message: Could not write public key file: %s

  • Error number: MY-010303; Symbol: ER_AUTH_SSL_CONF_PREVENTS_CERT_GENERATION; SQLSTATE: HY000

    Message: Skipping generation of SSL certificates as options related to SSL are specified.

  • Error number: MY-010304; Symbol: ER_AUTH_USING_EXISTING_CERTS; SQLSTATE: HY000

    Message: Skipping generation of SSL certificates as certificate files are present in data directory.

  • Error number: MY-010305; Symbol: ER_AUTH_CERTS_SAVED_TO_DATADIR; SQLSTATE: HY000

    Message: Auto generated SSL certificates are placed in data directory.

  • Error number: MY-010306; Symbol: ER_AUTH_CERT_GENERATION_DISABLED; SQLSTATE: HY000

    Message: Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.

  • Error number: MY-010307; Symbol: ER_AUTH_RSA_CONF_PREVENTS_KEY_GENERATION; SQLSTATE: HY000

    Message: Skipping generation of RSA key pair through %s as options related to RSA keys are specified.

  • Error number: MY-010308; Symbol: ER_AUTH_KEY_GENERATION_SKIPPED_PAIR_PRESENT; SQLSTATE: HY000

    Message: Skipping generation of RSA key pair through %s as key files are present in data directory.

  • Error number: MY-010309; Symbol: ER_AUTH_KEYS_SAVED_TO_DATADIR; SQLSTATE: HY000

    Message: Auto generated RSA key files through %s are placed in data directory.

  • Error number: MY-010310; Symbol: ER_AUTH_KEY_GENERATION_DISABLED; SQLSTATE: HY000

    Message: Skipping generation of RSA key pair as %s is set to OFF.

  • Error number: MY-010311; Symbol: ER_AUTHCACHE_PROXIES_PRIV_SKIPPED_NEEDS_RESOLVE; SQLSTATE: HY000

    Message: 'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.

  • Error number: MY-010312; Symbol: ER_AUTHCACHE_PLUGIN_MISSING; SQLSTATE: HY000

    Message: The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.

  • Error number: MY-010313; Symbol: ER_AUTHCACHE_PLUGIN_CONFIG; SQLSTATE: HY000

    Message: The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.

  • Error number: MY-010315; Symbol: ER_AUTHCACHE_USER_SKIPPED_NEEDS_RESOLVE; SQLSTATE: HY000

    Message: 'user' entry '%s@%s' ignored in --skip-name-resolve mode.

  • Error number: MY-010316; Symbol: ER_AUTHCACHE_USER_TABLE_DODGY; SQLSTATE: HY000

    Message: Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.

  • Error number: MY-010317; Symbol: ER_AUTHCACHE_USER_IGNORED_DEPRECATED_PASSWORD; SQLSTATE: HY000

    Message: User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.

  • Error number: MY-010318; Symbol: ER_AUTHCACHE_USER_IGNORED_NEEDS_PLUGIN; SQLSTATE: HY000

    Message: User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.

  • Error number: MY-010319; Symbol: ER_AUTHCACHE_USER_IGNORED_INVALID_PASSWORD; SQLSTATE: HY000

    Message: Found invalid password for user: '%s@%s'; Ignoring user

  • Error number: MY-010320; Symbol: ER_AUTHCACHE_EXPIRED_PASSWORD_UNSUPPORTED; SQLSTATE: HY000

    Message: 'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.

  • Error number: MY-010321; Symbol: ER_NO_SUPER_WITHOUT_USER_PLUGIN; SQLSTATE: HY000

    Message: Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.

  • Error number: MY-010322; Symbol: ER_AUTHCACHE_DB_IGNORED_EMPTY_NAME; SQLSTATE: HY000

    Message: Found an entry in the 'db' table with empty database name; Skipped

  • Error number: MY-010323; Symbol: ER_AUTHCACHE_DB_SKIPPED_NEEDS_RESOLVE; SQLSTATE: HY000

    Message: 'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.

  • Error number: MY-010324; Symbol: ER_AUTHCACHE_DB_ENTRY_LOWERCASED_REVOKE_WILL_FAIL; SQLSTATE: HY000

    Message: 'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.

  • Error number: MY-010325; Symbol: ER_AUTHCACHE_TABLE_PROXIES_PRIV_MISSING; SQLSTATE: HY000

    Message: The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.

  • Error number: MY-010326; Symbol: ER_AUTHCACHE_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES; SQLSTATE: HY000

    Message: Fatal error: Can't open and lock privilege tables: %s

  • Error number: MY-010327; Symbol: ER_AUTHCACHE_CANT_INIT_GRANT_SUBSYSTEM; SQLSTATE: HY000

    Message: Fatal: can't initialize grant subsystem - '%s'

  • Error number: MY-010328; Symbol: ER_AUTHCACHE_PROCS_PRIV_SKIPPED_NEEDS_RESOLVE; SQLSTATE: HY000

    Message: 'procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.

  • Error number: MY-010329; Symbol: ER_AUTHCACHE_PROCS_PRIV_ENTRY_IGNORED_BAD_ROUTINE_TYPE; SQLSTATE: HY000

    Message: 'procs_priv' entry '%s' ignored, bad routine type

  • Error number: MY-010330; Symbol: ER_AUTHCACHE_TABLES_PRIV_SKIPPED_NEEDS_RESOLVE; SQLSTATE: HY000

    Message: 'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.

  • Error number: MY-010331; Symbol: ER_USER_NOT_IN_EXTRA_USERS_BINLOG_POSSIBLY_INCOMPLETE; SQLSTATE: HY000

    Message: Failed to add %s in extra_users. Binary log entry may miss some of the users.

  • Error number: MY-010332; Symbol: ER_DD_SCHEMA_NOT_FOUND; SQLSTATE: HY000

    Message: Unable to start server. The data dictionary schema '%s' does not exist.

  • Error number: MY-010333; Symbol: ER_DD_TABLE_NOT_FOUND; SQLSTATE: HY000

    Message: Unable to start server. The data dictionary table '%s' does not exist.

  • Error number: MY-010334; Symbol: ER_DD_SE_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to initialize DD Storage Engine

  • Error number: MY-010335; Symbol: ER_DD_ABORTING_PARTIAL_UPGRADE; SQLSTATE: HY000

    Message: Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.

  • Error number: MY-010336; Symbol: ER_DD_FRM_EXISTS_FOR_TABLE; SQLSTATE: HY000

    Message: Found .frm file with same name as one of the Dictionary Tables.

  • Error number: MY-010337; Symbol: ER_DD_CREATED_FOR_UPGRADE; SQLSTATE: HY000

    Message: Created Data Dictionary for upgrade

  • Error number: MY-010338; Symbol: ER_ERRMSG_CANT_FIND_FILE; SQLSTATE: HY000

    Message: Can't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.

  • Error number: MY-010340; Symbol: ER_ERRMSG_MISSING_IN_FILE; SQLSTATE: HY000

    Message: Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!

  • Error number: MY-010341; Symbol: ER_ERRMSG_OOM; SQLSTATE: HY000

    Message: Not enough memory for messagefile '%s'

  • Error number: MY-010342; Symbol: ER_ERRMSG_CANT_READ; SQLSTATE: HY000

    Message: Can't read from messagefile '%s'

  • Error number: MY-010343; Symbol: ER_TABLE_INCOMPATIBLE_DECIMAL_FIELD; SQLSTATE: HY000

    Message: Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!

  • Error number: MY-010344; Symbol: ER_TABLE_INCOMPATIBLE_YEAR_FIELD; SQLSTATE: HY000

    Message: Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!

  • Error number: MY-010345; Symbol: ER_INVALID_CHARSET_AND_DEFAULT_IS_MB; SQLSTATE: HY000

    Message: '%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed

  • Error number: MY-010346; Symbol: ER_TABLE_WRONG_KEY_DEFINITION; SQLSTATE: HY000

    Message: Found wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!

  • Error number: MY-010347; Symbol: ER_CANT_OPEN_FRM_FILE; SQLSTATE: HY000

    Message: Unable to open file %s

  • Error number: MY-010348; Symbol: ER_CANT_READ_FRM_FILE; SQLSTATE: HY000

    Message: Error in reading file %s

  • Error number: MY-010349; Symbol: ER_TABLE_CREATED_WITH_DIFFERENT_VERSION; SQLSTATE: HY000

    Message: Table '%s' was created with a different version of MySQL and cannot be read

  • Error number: MY-010350; Symbol: ER_VIEW_UNPARSABLE; SQLSTATE: HY000

    Message: Unable to read view %s

  • Error number: MY-010351; Symbol: ER_FILE_TYPE_UNKNOWN; SQLSTATE: HY000

    Message: File %s has unknown type in its header.

  • Error number: MY-010352; Symbol: ER_INVALID_INFO_IN_FRM; SQLSTATE: HY000

    Message: Incorrect information in file %s

  • Error number: MY-010353; Symbol: ER_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES; SQLSTATE: HY000

    Message: Can't open and lock privilege tables: %s

  • Error number: MY-010354; Symbol: ER_AUDIT_PLUGIN_DOES_NOT_SUPPORT_AUDIT_AUTH_EVENTS; SQLSTATE: HY000

    Message: Plugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.

  • Error number: MY-010355; Symbol: ER_AUDIT_PLUGIN_HAS_INVALID_DATA; SQLSTATE: HY000

    Message: Plugin '%s' has invalid data.

  • Error number: MY-010356; Symbol: ER_TZ_OOM_INITIALIZING_TIME_ZONES; SQLSTATE: HY000

    Message: Fatal error: OOM while initializing time zones

  • Error number: MY-010357; Symbol: ER_TZ_CANT_OPEN_AND_LOCK_TIME_ZONE_TABLE; SQLSTATE: HY000

    Message: Can't open and lock time zone table: %s trying to live without them

  • Error number: MY-010358; Symbol: ER_TZ_OOM_LOADING_LEAP_SECOND_TABLE; SQLSTATE: HY000

    Message: Fatal error: Out of memory while loading mysql.time_zone_leap_second table

  • Error number: MY-010359; Symbol: ER_TZ_TOO_MANY_LEAPS_IN_LEAP_SECOND_TABLE; SQLSTATE: HY000

    Message: Fatal error: While loading mysql.time_zone_leap_second table: too much leaps

  • Error number: MY-010360; Symbol: ER_TZ_ERROR_LOADING_LEAP_SECOND_TABLE; SQLSTATE: HY000

    Message: Fatal error: Error while loading mysql.time_zone_leap_second table

  • Error number: MY-010361; Symbol: ER_TZ_UNKNOWN_OR_ILLEGAL_DEFAULT_TIME_ZONE; SQLSTATE: HY000

    Message: Fatal error: Illegal or unknown default time zone '%s'

  • Error number: MY-010362; Symbol: ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE; SQLSTATE: HY000

    Message: Can't find description of time zone '%.*s'

  • Error number: MY-010363; Symbol: ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE_ID; SQLSTATE: HY000

    Message: Can't find description of time zone '%u'

  • Error number: MY-010364; Symbol: ER_TZ_TRANSITION_TYPE_TABLE_TYPE_TOO_LARGE; SQLSTATE: HY000

    Message: Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type id

  • Error number: MY-010365; Symbol: ER_TZ_TRANSITION_TYPE_TABLE_ABBREVIATIONS_EXCEED_SPACE; SQLSTATE: HY000

    Message: Error while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviations

  • Error number: MY-010366; Symbol: ER_TZ_TRANSITION_TYPE_TABLE_LOAD_ERROR; SQLSTATE: HY000

    Message: Error while loading time zone description from mysql.time_zone_transition_type table

  • Error number: MY-010367; Symbol: ER_TZ_TRANSITION_TABLE_TOO_MANY_TRANSITIONS; SQLSTATE: HY000

    Message: Error while loading time zone description from mysql.time_zone_transition table: too much transitions

  • Error number: MY-010368; Symbol: ER_TZ_TRANSITION_TABLE_BAD_TRANSITION_TYPE; SQLSTATE: HY000

    Message: Error while loading time zone description from mysql.time_zone_transition table: bad transition type id

  • Error number: MY-010369; Symbol: ER_TZ_TRANSITION_TABLE_LOAD_ERROR; SQLSTATE: HY000

    Message: Error while loading time zone description from mysql.time_zone_transition table

  • Error number: MY-010370; Symbol: ER_TZ_NO_TRANSITION_TYPES_IN_TIME_ZONE; SQLSTATE: HY000

    Message: loading time zone without transition types

  • Error number: MY-010371; Symbol: ER_TZ_OOM_LOADING_TIME_ZONE_DESCRIPTION; SQLSTATE: HY000

    Message: Out of memory while loading time zone description

  • Error number: MY-010372; Symbol: ER_TZ_CANT_BUILD_MKTIME_MAP; SQLSTATE: HY000

    Message: Unable to build mktime map for time zone

  • Error number: MY-010373; Symbol: ER_TZ_OOM_WHILE_LOADING_TIME_ZONE; SQLSTATE: HY000

    Message: Out of memory while loading time zone

  • Error number: MY-010374; Symbol: ER_TZ_OOM_WHILE_SETTING_TIME_ZONE; SQLSTATE: HY000

    Message: Fatal error: Out of memory while setting new time zone

  • Error number: MY-010375; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_CONDITION_BAD; SQLSTATE: HY000

    Message: Replica SQL thread is stopped because UNTIL condition is bad(%s:%llu).

  • Error number: MY-010376; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_POSITION_REACHED; SQLSTATE: HY000

    Message: Replica SQL thread stopped because it reached its UNTIL position %llu

  • Error number: MY-010377; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_ALREADY_APPLIED; SQLSTATE: HY000

    Message: Replica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already applied

  • Error number: MY-010378; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_REACHED; SQLSTATE: HY000

    Message: Replica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %s

  • Error number: MY-010379; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_AFTER_GTIDS_REACHED; SQLSTATE: HY000

    Message: Replica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %s

  • Error number: MY-010380; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_GAP_TRX_PROCESSED; SQLSTATE: HY000

    Message: Replica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.

  • Error number: MY-010381; Symbol: ER_GROUP_REPLICATION_PLUGIN_NOT_INSTALLED; SQLSTATE: HY000

    Message: Group Replication plugin is not installed.

  • Error number: MY-010382; Symbol: ER_GTID_ALREADY_ADDED_BY_USER; SQLSTATE: HY000

    Message: The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.

  • Error number: MY-010383; Symbol: ER_FAILED_TO_DELETE_FROM_GTID_EXECUTED_TABLE; SQLSTATE: HY000

    Message: Failed to delete the row: '%s' from the gtid_executed table.

  • Error number: MY-010384; Symbol: ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE; SQLSTATE: HY000

    Message: Failed to compress the gtid_executed table.

  • Error number: MY-010385; Symbol: ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE_OOM; SQLSTATE: HY000

    Message: Failed to compress the gtid_executed table, because it is failed to allocate the THD.

  • Error number: MY-010386; Symbol: ER_FAILED_TO_INIT_THREAD_ATTR_FOR_GTID_TABLE_COMPRESSION; SQLSTATE: HY000

    Message: Failed to initialize thread attribute when creating compression thread.

  • Error number: MY-010387; Symbol: ER_FAILED_TO_CREATE_GTID_TABLE_COMPRESSION_THREAD; SQLSTATE: HY000

    Message: Can not create thread to compress gtid_executed table (errno= %d)

  • Error number: MY-010388; Symbol: ER_FAILED_TO_JOIN_GTID_TABLE_COMPRESSION_THREAD; SQLSTATE: HY000

    Message: Could not join gtid_executed table compression thread. error:%d

  • Error number: MY-010389; Symbol: ER_NPIPE_FAILED_TO_INIT_SECURITY_DESCRIPTOR; SQLSTATE: HY000

    Message: Can't start server : Initialize security descriptor: %s

  • Error number: MY-010390; Symbol: ER_NPIPE_FAILED_TO_SET_SECURITY_DESCRIPTOR; SQLSTATE: HY000

    Message: Can't start server : Set security descriptor: %s

  • Error number: MY-010391; Symbol: ER_NPIPE_PIPE_ALREADY_IN_USE; SQLSTATE: HY000

    Message: Can't start server : Named Pipe "%s" already in use.

  • Error number: MY-010405; Symbol: ER_RPL_CANT_OPEN_INFO_TABLE; SQLSTATE: HY000

    Message: Info table is not ready to be used. Table '%s.%s' cannot be opened.

  • Error number: MY-010406; Symbol: ER_RPL_CANT_SCAN_INFO_TABLE; SQLSTATE: HY000

    Message: Info table is not ready to be used. Table '%s.%s' cannot be scanned.

  • Error number: MY-010407; Symbol: ER_RPL_CORRUPTED_INFO_TABLE; SQLSTATE: HY000

    Message: Corrupted table %s.%s. Check out table definition.

  • Error number: MY-010408; Symbol: ER_RPL_CORRUPTED_KEYS_IN_INFO_TABLE; SQLSTATE: HY000

    Message: Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.

  • Error number: MY-010409; Symbol: ER_RPL_WORKER_ID_IS; SQLSTATE: HY000

    Message: Choosing worker id %lu, the following is going to be %lu

  • Error number: MY-010410; Symbol: ER_RPL_INCONSISTENT_TIMESTAMPS_IN_TRX; SQLSTATE: HY000

    Message: Transaction %s in file %s is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld). There may be a bug in how these timestamps were generated. Transaction will be applied in isolation

  • Error number: MY-010411; Symbol: ER_RPL_INCONSISTENT_SEQUENCE_NO_IN_TRX; SQLSTATE: HY000

    Message: Transaction %s sequence number in file %s is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld). There may be a bug in how these timestamps were generated. Transaction will be applied in isolation

  • Error number: MY-010413; Symbol: ER_RPL_CHANNELS_REQUIRE_NON_ZERO_SERVER_ID; SQLSTATE: HY000

    Message: For the creation of replication channels the server id must be different from 0

  • Error number: MY-010415; Symbol: ER_RPL_ERROR_CREATING_CONNECTION_METADATA; SQLSTATE: HY000

    Message: Error creating connection metadata: %s.

  • Error number: MY-010418; Symbol: ER_RPL_ERROR_CREATING_APPLIER_METADATA; SQLSTATE: HY000

    Message: Error creating applier metadata: %s.

  • Error number: MY-010420; Symbol: ER_RPL_FAILED_TO_DELETE_FROM_REPLICA_WORKERS_INFO_REPOSITORY; SQLSTATE: HY000

    Message: Could not delete from Replica Workers info repository.

  • Error number: MY-010421; Symbol: ER_RPL_FAILED_TO_RESET_STATE_IN_REPLICA_INFO_REPOSITORY; SQLSTATE: HY000

    Message: Could not store the reset Replica Worker state into the replica info repository.

  • Error number: MY-010423; Symbol: ER_RPL_REPLICA_GENERIC_MESSAGE; SQLSTATE: HY000

    Message: Replica: %s

  • Error number: MY-010424; Symbol: ER_RPL_REPLICA_COULD_NOT_CREATE_CHANNEL_LIST; SQLSTATE: HY000

    Message: Replica: Could not create channel list

  • Error number: MY-010425; Symbol: ER_RPL_MULTISOURCE_REQUIRES_TABLE_TYPE_REPOSITORIES; SQLSTATE: HY000

    Message: Replica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.

  • Error number: MY-010426; Symbol: ER_RPL_REPLICA_FAILED_TO_INIT_A_CONNECTION_METADATA_STRUCTURE; SQLSTATE: HY000

    Message: Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.

  • Error number: MY-010427; Symbol: ER_RPL_REPLICA_FAILED_TO_INIT_CONNECTION_METADATA_STRUCTURE; SQLSTATE: HY000

    Message: Failed to initialize the connection metadata structure%s

  • Error number: MY-010428; Symbol: ER_RPL_REPLICA_FAILED_TO_CREATE_CHANNEL_FROM_CONNECTION_METADATA; SQLSTATE: HY000

    Message: Replica: Failed to create a channel from connection metadata repository.

  • Error number: MY-010429; Symbol: ER_RPL_FAILED_TO_CREATE_NEW_INFO_FILE; SQLSTATE: HY000

    Message: Failed to create a new info file (file '%s', errno %d)

  • Error number: MY-010430; Symbol: ER_RPL_FAILED_TO_CREATE_CACHE_FOR_INFO_FILE; SQLSTATE: HY000

    Message: Failed to create a cache on info file (file '%s')

  • Error number: MY-010431; Symbol: ER_RPL_FAILED_TO_OPEN_INFO_FILE; SQLSTATE: HY000

    Message: Failed to open the existing info file (file '%s', errno %d)

  • Error number: MY-010432; Symbol: ER_RPL_GTID_MEMORY_FINALLY_AVAILABLE; SQLSTATE: HY000

    Message: Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.

  • Error number: MY-010433; Symbol: ER_SERVER_COST_UNKNOWN_COST_CONSTANT; SQLSTATE: HY000

    Message: Unknown cost constant "%s" in mysql.server_cost table

  • Error number: MY-010434; Symbol: ER_SERVER_COST_INVALID_COST_CONSTANT; SQLSTATE: HY000

    Message: Invalid value for cost constant "%s" in mysql.server_cost table: %.1f

  • Error number: MY-010435; Symbol: ER_ENGINE_COST_UNKNOWN_COST_CONSTANT; SQLSTATE: HY000

    Message: Unknown cost constant "%s" in mysql.engine_cost table

  • Error number: MY-010436; Symbol: ER_ENGINE_COST_UNKNOWN_STORAGE_ENGINE; SQLSTATE: HY000

    Message: Unknown storage engine "%s" in mysql.engine_cost table

  • Error number: MY-010437; Symbol: ER_ENGINE_COST_INVALID_DEVICE_TYPE_FOR_SE; SQLSTATE: HY000

    Message: Invalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost table

  • Error number: MY-010438; Symbol: ER_ENGINE_COST_INVALID_CONST_CONSTANT_FOR_SE_AND_DEVICE; SQLSTATE: HY000

    Message: Invalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1f

  • Error number: MY-010439; Symbol: ER_SERVER_COST_FAILED_TO_READ; SQLSTATE: HY000

    Message: Error while reading from mysql.server_cost table.

  • Error number: MY-010440; Symbol: ER_ENGINE_COST_FAILED_TO_READ; SQLSTATE: HY000

    Message: Error while reading from mysql.engine_cost table.

  • Error number: MY-010441; Symbol: ER_FAILED_TO_OPEN_COST_CONSTANT_TABLES; SQLSTATE: HY000

    Message: Failed to open optimizer cost constant tables

  • Error number: MY-010442; Symbol: ER_RPL_UNSUPPORTED_UNIGNORABLE_EVENT_IN_STREAM; SQLSTATE: HY000

    Message: Unsupported non-ignorable event fed into the event stream.

  • Error number: MY-010443; Symbol: ER_RPL_GTID_LOG_EVENT_IN_STREAM; SQLSTATE: HY000

    Message: GTID_LOG_EVENT, GTID_TAGGED_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.

  • Error number: MY-010444; Symbol: ER_RPL_UNEXPECTED_BEGIN_IN_STREAM; SQLSTATE: HY000

    Message: QUERY(BEGIN) is not expected in an event stream in the middle of a %s.

  • Error number: MY-010445; Symbol: ER_RPL_UNEXPECTED_COMMIT_ROLLBACK_OR_XID_LOG_EVENT_IN_STREAM; SQLSTATE: HY000

    Message: QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.

  • Error number: MY-010446; Symbol: ER_RPL_UNEXPECTED_XA_ROLLBACK_IN_STREAM; SQLSTATE: HY000

    Message: QUERY(XA ROLLBACK) is not expected in an event stream %s.

  • Error number: MY-010447; Symbol: ER_EVENT_EXECUTION_FAILED_CANT_AUTHENTICATE_USER; SQLSTATE: HY000

    Message: Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.

  • Error number: MY-010448; Symbol: ER_EVENT_EXECUTION_FAILED_USER_LOST_EVEN_PRIVILEGE; SQLSTATE: HY000

    Message: Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.

  • Error number: MY-010449; Symbol: ER_EVENT_ERROR_DURING_COMPILATION; SQLSTATE: HY000

    Message: Event Scheduler: %serror during compilation of %s.%s

  • Error number: MY-010450; Symbol: ER_EVENT_DROPPING; SQLSTATE: HY000

    Message: Event Scheduler: Dropping %s.%s

  • Error number: MY-010452; Symbol: ER_RPL_INCOMPATIBLE_DECIMAL_IN_RBR; SQLSTATE: HY000

    Message: In RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.

  • Error number: MY-010453; Symbol: ER_INIT_ROOT_WITHOUT_PASSWORD; SQLSTATE: HY000

    Message: root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.

  • Error number: MY-010454; Symbol: ER_INIT_GENERATING_TEMP_PASSWORD_FOR_ROOT; SQLSTATE: HY000

    Message: A temporary password is generated for root@localhost: %s

  • Error number: MY-010455; Symbol: ER_INIT_CANT_OPEN_BOOTSTRAP_FILE; SQLSTATE: HY000

    Message: Failed to open the bootstrap file %s

  • Error number: MY-010456; Symbol: ER_INIT_BOOTSTRAP_COMPLETE; SQLSTATE: HY000

    Message: Bootstrapping complete

  • Error number: MY-010457; Symbol: ER_INIT_DATADIR_NOT_EMPTY_WONT_INITIALIZE; SQLSTATE: HY000

    Message: --initialize specified but the data directory has files in it. Aborting.

  • Error number: MY-010458; Symbol: ER_INIT_DATADIR_EXISTS_WONT_INITIALIZE; SQLSTATE: HY000

    Message: --initialize specified on an existing data directory.

  • Error number: MY-010459; Symbol: ER_INIT_DATADIR_EXISTS_AND_PATH_TOO_LONG_WONT_INITIALIZE; SQLSTATE: HY000

    Message: --initialize specified but the data directory exists and the path is too long. Aborting.

  • Error number: MY-010460; Symbol: ER_INIT_DATADIR_EXISTS_AND_NOT_WRITABLE_WONT_INITIALIZE; SQLSTATE: HY000

    Message: --initialize specified but the data directory exists and is not writable. Aborting.

  • Error number: MY-010461; Symbol: ER_INIT_CREATING_DD; SQLSTATE: HY000

    Message: Creating the data directory %s

  • Error number: MY-010462; Symbol: ER_RPL_BINLOG_STARTING_DUMP; SQLSTATE: HY000

    Message: Start binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)

  • Error number: MY-010463; Symbol: ER_RPL_BINLOG_SOURCE_SENDS_HEARTBEAT; SQLSTATE: HY000

    Message: source sends heartbeat message

  • Error number: MY-010464; Symbol: ER_RPL_BINLOG_SKIPPING_REMAINING_HEARTBEAT_INFO; SQLSTATE: HY000

    Message: the rest of heartbeat info skipped ...

  • Error number: MY-010465; Symbol: ER_RPL_BINLOG_SOURCE_USES_CHECKSUM_AND_REPLICA_CANT; SQLSTATE: HY000

    Message: Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process them

  • Error number: MY-010467; Symbol: ER_KILLING_THREAD; SQLSTATE: HY000

    Message: Killing thread %lu

  • Error number: MY-010468; Symbol: ER_DETACHING_SESSION_LEFT_BY_PLUGIN; SQLSTATE: HY000

    Message: Plugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.

  • Error number: MY-010469; Symbol: ER_CANT_DETACH_SESSION_LEFT_BY_PLUGIN; SQLSTATE: HY000

    Message: Failed to detach the session.

  • Error number: MY-010470; Symbol: ER_DETACHED_SESSIONS_LEFT_BY_PLUGIN; SQLSTATE: HY000

    Message: Closed forcefully %u session%s left opened by plugin %s

  • Error number: MY-010471; Symbol: ER_FAILED_TO_DECREMENT_NUMBER_OF_THREADS; SQLSTATE: HY000

    Message: Failed to decrement the number of threads

  • Error number: MY-010472; Symbol: ER_PLUGIN_DID_NOT_DEINITIALIZE_THREADS; SQLSTATE: HY000

    Message: Plugin %s did not deinitialize %u threads

  • Error number: MY-010473; Symbol: ER_KILLED_THREADS_OF_PLUGIN; SQLSTATE: HY000

    Message: Killed %u threads of plugin %s

  • Error number: MY-010517; Symbol: ER_DBUG_CHECK_SHARES_OPEN; SQLSTATE: HY000

    Message: dbug_check_shares open:

  • Error number: MY-010518; Symbol: ER_DBUG_CHECK_SHARES_INFO; SQLSTATE: HY000

    Message: %s.%s: state: %s(%u) use_count: %u

  • Error number: MY-010519; Symbol: ER_DBUG_CHECK_SHARES_DROPPED; SQLSTATE: HY000

    Message: dbug_check_shares dropped:

  • Error number: MY-010520; Symbol: ER_INVALID_OR_OLD_TABLE_OR_DB_NAME; SQLSTATE: HY000

    Message: Invalid (old?) table or database name '%s'

  • Error number: MY-010521; Symbol: ER_TC_RECOVERING_AFTER_CRASH_USING; SQLSTATE: HY000

    Message: Recovering after a crash using %s

  • Error number: MY-010522; Symbol: ER_TC_CANT_AUTO_RECOVER_WITH_TC_HEURISTIC_RECOVER; SQLSTATE: HY000

    Message: Cannot perform automatic crash recovery when --tc-heuristic-recover is used

  • Error number: MY-010523; Symbol: ER_TC_BAD_MAGIC_IN_TC_LOG; SQLSTATE: HY000

    Message: Bad magic header in tc log

  • Error number: MY-010524; Symbol: ER_TC_NEED_N_SE_SUPPORTING_2PC_FOR_RECOVERY; SQLSTATE: HY000

    Message: Recovery failed! You must enable exactly %d storage engines that support two-phase commit protocol

  • Error number: MY-010525; Symbol: ER_TC_RECOVERY_FAILED_THESE_ARE_YOUR_OPTIONS; SQLSTATE: HY000

    Message: Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}

  • Error number: MY-010526; Symbol: ER_TC_HEURISTIC_RECOVERY_MODE; SQLSTATE: HY000

    Message: Heuristic crash recovery mode

  • Error number: MY-010527; Symbol: ER_TC_HEURISTIC_RECOVERY_FAILED; SQLSTATE: HY000

    Message: Heuristic crash recovery failed

  • Error number: MY-010528; Symbol: ER_TC_RESTART_WITHOUT_TC_HEURISTIC_RECOVER; SQLSTATE: HY000

    Message: Please restart mysqld without --tc-heuristic-recover

  • Error number: MY-010529; Symbol: ER_RPL_REPLICA_FAILED_TO_CREATE_OR_RECOVER_INFO_REPOSITORIES; SQLSTATE: HY000

    Message: Failed to create or recover replication info repositories.

  • Error number: MY-010530; Symbol: ER_RPL_REPLICA_AUTO_POSITION_IS_1_AND_GTID_MODE_IS_OFF; SQLSTATE: HY000

    Message: Detected misconfiguration: replication channel '%s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.

  • Error number: MY-010531; Symbol: ER_RPL_REPLICA_CANT_START_REPLICA_FOR_CHANNEL; SQLSTATE: HY000

    Message: Replica: Could not start replica for channel '%s'. operation discontinued

  • Error number: MY-010532; Symbol: ER_RPL_REPLICA_CANT_STOP_REPLICA_FOR_CHANNEL; SQLSTATE: HY000

    Message: Replica: Could not stop replica for channel '%s' operation discontinued

  • Error number: MY-010533; Symbol: ER_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE; SQLSTATE: HY000

    Message: Error during --relay-log-recovery: Could not locate rotate event from the source.

  • Error number: MY-010534; Symbol: ER_RPL_RECOVERY_ERROR_READ_RELAY_LOG; SQLSTATE: HY000

    Message: Error during --relay-log-recovery: Error reading events from relay log: %d

  • Error number: MY-010536; Symbol: ER_RPL_RECOVERY_SKIPPED_GROUP_REPLICATION_CHANNEL; SQLSTATE: HY000

    Message: Relay log recovery skipped for group replication channel.

  • Error number: MY-010537; Symbol: ER_RPL_RECOVERY_ERROR; SQLSTATE: HY000

    Message: Error during --relay-log-recovery: %s

  • Error number: MY-010538; Symbol: ER_RPL_RECOVERY_IO_ERROR_READING_RELAY_LOG_INDEX; SQLSTATE: HY000

    Message: Error during --relay-log-recovery: Could not read relay log index file due to an IO error.

  • Error number: MY-010539; Symbol: ER_RPL_RECOVERY_FILE_SOURCE_POS_INFO; SQLSTATE: HY000

    Message: Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.

  • Error number: MY-010540; Symbol: ER_RPL_RECOVERY_REPLICATE_SAME_SERVER_ID_REQUIRES_POSITION; SQLSTATE: HY000

    Message: Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.

  • Error number: MY-010541; Symbol: ER_RPL_MTA_RECOVERY_STARTING_COORDINATOR; SQLSTATE: HY000

    Message: MTA recovery: starting coordinator thread to fill MTA gaps.

  • Error number: MY-010542; Symbol: ER_RPL_MTA_RECOVERY_FAILED_TO_START_COORDINATOR; SQLSTATE: HY000

    Message: MTA recovery: failed to start the coordinator thread. Check the error log for additional details.

  • Error number: MY-010543; Symbol: ER_RPL_MTA_AUTOMATIC_RECOVERY_FAILED; SQLSTATE: HY000

    Message: MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.

  • Error number: MY-010544; Symbol: ER_RPL_MTA_RECOVERY_CANT_OPEN_RELAY_LOG; SQLSTATE: HY000

    Message: Failed to open the relay log '%s' (relay_log_pos %s).

  • Error number: MY-010545; Symbol: ER_RPL_MTA_RECOVERY_SUCCESSFUL; SQLSTATE: HY000

    Message: MTA recovery: completed successfully.

  • Error number: MY-010546; Symbol: ER_RPL_SERVER_ID_MISSING; SQLSTATE: HY000

    Message: Server id not set, will not start replica%s

  • Error number: MY-010547; Symbol: ER_RPL_CANT_CREATE_REPLICA_THREAD; SQLSTATE: HY000

    Message: Can't create replica thread%s.

  • Error number: MY-010548; Symbol: ER_RPL_REPLICA_IO_THREAD_WAS_KILLED; SQLSTATE: HY000

    Message: The replica IO thread%s was killed while executing initialization query '%s'

  • Error number: MY-010550; Symbol: ER_RPL_REPLICA_USES_CHECKSUM_AND_SOURCE_PRE_50; SQLSTATE: HY000

    Message: Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0.

  • Error number: MY-010551; Symbol: ER_RPL_REPLICA_SECONDS_BEHIND_SOURCE_DUBIOUS; SQLSTATE: HY000

    Message: "SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)

  • Error number: MY-010552; Symbol: ER_RPL_REPLICA_CANT_FLUSH_CONNECTION_METADATA_REPOS; SQLSTATE: HY000

    Message: Failed to flush connection metadata repository.

  • Error number: MY-010553; Symbol: ER_RPL_REPLICA_REPORT_HOST_TOO_LONG; SQLSTATE: HY000

    Message: The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.

  • Error number: MY-010554; Symbol: ER_RPL_REPLICA_REPORT_USER_TOO_LONG; SQLSTATE: HY000

    Message: The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.

  • Error number: MY-010555; Symbol: ER_RPL_REPLICA_REPORT_PASSWORD_TOO_LONG; SQLSTATE: HY000

    Message: The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.

  • Error number: MY-010556; Symbol: ER_RPL_REPLICA_ERROR_RETRYING; SQLSTATE: HY000

    Message: Error on %s: %d %s, will retry in %d secs

  • Error number: MY-010557; Symbol: ER_RPL_REPLICA_ERROR_READING_FROM_SERVER; SQLSTATE: HY000

    Message: Error reading packet from server%s: %s (server_errno=%d)

  • Error number: MY-010558; Symbol: ER_RPL_REPLICA_DUMP_THREAD_KILLED_BY_SOURCE; SQLSTATE: HY000

    Message: Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %s

  • Error number: MY-010559; Symbol: ER_RPL_MTA_STATISTICS; SQLSTATE: HY000

    Message: Multi-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %llu

  • Error number: MY-010560; Symbol: ER_RPL_MTA_RECOVERY_COMPLETE; SQLSTATE: HY000

    Message: Replica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.

  • Error number: MY-010561; Symbol: ER_RPL_REPLICA_CANT_INIT_RELAY_LOG_POSITION; SQLSTATE: HY000

    Message: Error initializing relay log position%s: %s

  • Error number: MY-010563; Symbol: ER_RPL_REPLICA_IO_THREAD_KILLED; SQLSTATE: HY000

    Message: Replica I/O thread%s killed while connecting to source

  • Error number: MY-010564; Symbol: ER_RPL_REPLICA_IO_THREAD_CANT_REGISTER_ON_SOURCE; SQLSTATE: HY000

    Message: Replica I/O thread couldn't register on source

  • Error number: MY-010565; Symbol: ER_RPL_REPLICA_FORCING_TO_RECONNECT_IO_THREAD; SQLSTATE: HY000

    Message: Forcing to reconnect replica I/O thread%s

  • Error number: MY-010566; Symbol: ER_RPL_REPLICA_ERROR_REQUESTING_BINLOG_DUMP; SQLSTATE: HY000

    Message: Failed on request_dump()%s

  • Error number: MY-010567; Symbol: ER_RPL_LOG_ENTRY_EXCEEDS_REPLICA_MAX_ALLOWED_PACKET; SQLSTATE: HY000

    Message: Log entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packet

  • Error number: MY-010568; Symbol: ER_RPL_REPLICA_STOPPING_AS_SOURCE_OOM; SQLSTATE: HY000

    Message: Stopping replica I/O thread due to out-of-memory error from source

  • Error number: MY-010569; Symbol: ER_RPL_REPLICA_IO_THREAD_ABORTED_WAITING_FOR_RELAY_LOG_SPACE; SQLSTATE: HY000

    Message: Replica I/O thread aborted while waiting for relay log space

  • Error number: MY-010570; Symbol: ER_RPL_REPLICA_IO_THREAD_EXITING; SQLSTATE: HY000

    Message: Replica I/O thread exiting%s, read up to log '%s', position %s

  • Error number: MY-010571; Symbol: ER_RPL_REPLICA_CANT_INITIALIZE_REPLICA_WORKER; SQLSTATE: HY000

    Message: Failed during replica worker initialization%s

  • Error number: MY-010572; Symbol: ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA_FOR_WORKER; SQLSTATE: HY000

    Message: Replica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %llu

  • Error number: MY-010573; Symbol: ER_RPL_ERROR_LOOKING_FOR_LOG; SQLSTATE: HY000

    Message: Error looking for %s.

  • Error number: MY-010574; Symbol: ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA; SQLSTATE: HY000

    Message: Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.

  • Error number: MY-010575; Symbol: ER_RPL_CANT_FIND_FOLLOWUP_FILE; SQLSTATE: HY000

    Message: Error looking for file after %s.

  • Error number: MY-010576; Symbol: ER_RPL_MTA_CHECKPOINT_PERIOD_DIFFERS_FROM_CNT; SQLSTATE: HY000

    Message: This an error cnt != mta_checkpoint_period

  • Error number: MY-010577; Symbol: ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED; SQLSTATE: HY000

    Message: Failed during replica worker thread creation%s

  • Error number: MY-010578; Symbol: ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED_WITH_ERRNO; SQLSTATE: HY000

    Message: Failed during replica worker thread creation%s (errno= %d)

  • Error number: MY-010579; Symbol: ER_RPL_REPLICA_FAILED_TO_INIT_PARTITIONS_HASH; SQLSTATE: HY000

    Message: Failed to init partitions hash

  • Error number: MY-010581; Symbol: ER_RPL_REPLICA_SQL_THREAD_STARTING; SQLSTATE: HY000

    Message: Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s

  • Error number: MY-010582; Symbol: ER_RPL_REPLICA_SKIP_COUNTER_EXECUTED; SQLSTATE: HY000

    Message: 'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld'

  • Error number: MY-010583; Symbol: ER_RPL_REPLICA_ADDITIONAL_ERROR_INFO_FROM_DA; SQLSTATE: HY000

    Message: Replica (additional info): %s Error_code: MY-%06d

  • Error number: MY-010584; Symbol: ER_RPL_REPLICA_ERROR_INFO_FROM_DA; SQLSTATE: HY000

    Message: Replica: %s Error_code: MY-%06d

  • Error number: MY-010585; Symbol: ER_RPL_REPLICA_ERROR_LOADING_USER_DEFINED_LIBRARY; SQLSTATE: HY000

    Message: Error loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %s

  • Error number: MY-010586; Symbol: ER_RPL_REPLICA_ERROR_RUNNING_QUERY; SQLSTATE: HY000

    Message: Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %s

  • Error number: MY-010587; Symbol: ER_RPL_REPLICA_SQL_THREAD_EXITING; SQLSTATE: HY000

    Message: Replica SQL thread%s exiting, replication stopped in log '%s' at position %s

  • Error number: MY-010588; Symbol: ER_RPL_REPLICA_READ_INVALID_EVENT_FROM_SOURCE; SQLSTATE: HY000

    Message: Read invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bug

  • Error number: MY-010589; Symbol: ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_CONFIGURATION; SQLSTATE: HY000

    Message: The queue event failed for channel '%s' as its configuration is invalid.

  • Error number: MY-010590; Symbol: ER_RPL_REPLICA_IO_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE; SQLSTATE: HY000

    Message: An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.

  • Error number: MY-010591; Symbol: ER_RPL_REPLICA_CANT_USE_CHARSET; SQLSTATE: HY000

    Message: '%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.

  • Error number: MY-010592; Symbol: ER_RPL_REPLICA_CONNECTED_TO_SOURCE_REPLICATION_RESUMED; SQLSTATE: HY000

    Message: Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %s

  • Error number: MY-010593; Symbol: ER_RPL_REPLICA_NEXT_LOG_IS_ACTIVE; SQLSTATE: HY000

    Message: next log '%s' is active

  • Error number: MY-010594; Symbol: ER_RPL_REPLICA_NEXT_LOG_IS_INACTIVE; SQLSTATE: HY000

    Message: next log '%s' is not active

  • Error number: MY-010595; Symbol: ER_RPL_REPLICA_SQL_THREAD_IO_ERROR_READING_EVENT; SQLSTATE: HY000

    Message: Replica SQL thread%s: I/O error reading event (errno: %d cur_log->error: %d)

  • Error number: MY-010596; Symbol: ER_RPL_REPLICA_ERROR_READING_RELAY_LOG_EVENTS; SQLSTATE: HY000

    Message: Error reading relay log event%s: %s

  • Error number: MY-010597; Symbol: ER_REPLICA_CHANGE_SOURCE_TO_EXECUTED; SQLSTATE: HY000

    Message: 'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.

  • Error number: MY-010598; Symbol: ER_RPL_REPLICA_NEW_C_M_NEEDS_REPOS_TYPE_OTHER_THAN_FILE; SQLSTATE: HY000

    Message: Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.

  • Error number: MY-010599; Symbol: ER_RPL_FAILED_TO_STAT_LOG_IN_INDEX; SQLSTATE: HY000

    Message: log %s listed in the index, but failed to stat.

  • Error number: MY-010600; Symbol: ER_RPL_LOG_NOT_FOUND_WHILE_COUNTING_RELAY_LOG_SPACE; SQLSTATE: HY000

    Message: Could not find first log while counting relay log space.

  • Error number: MY-010601; Symbol: ER_REPLICA_CANT_USE_TEMPDIR; SQLSTATE: HY000

    Message: Unable to use replica's temporary directory '%s'.

  • Error number: MY-010602; Symbol: ER_RPL_RELAY_LOG_NEEDS_FILE_NOT_DIRECTORY; SQLSTATE: HY000

    Message: Path '%s' is a directory name, please specify a file name for --relay-log option.

  • Error number: MY-010603; Symbol: ER_RPL_RELAY_LOG_INDEX_NEEDS_FILE_NOT_DIRECTORY; SQLSTATE: HY000

    Message: Path '%s' is a directory name, please specify a file name for --relay-log-index option.

  • Error number: MY-010604; Symbol: ER_RPL_PLEASE_USE_OPTION_RELAY_LOG; SQLSTATE: HY000

    Message: Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.

  • Error number: MY-010605; Symbol: ER_RPL_OPEN_INDEX_FILE_FAILED; SQLSTATE: HY000

    Message: Failed in open_index_file() called from Relay_log_info::rli_init_info().

  • Error number: MY-010606; Symbol: ER_RPL_CANT_INITIALIZE_GTID_SETS_IN_AM_INIT_INFO; SQLSTATE: HY000

    Message: Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().

  • Error number: MY-010607; Symbol: ER_RPL_CANT_OPEN_LOG_IN_AM_INIT_INFO; SQLSTATE: HY000

    Message: Failed in open_log() called from Relay_log_info::rli_init_info().

  • Error number: MY-010608; Symbol: ER_RPL_ERROR_WRITING_RELAY_LOG_CONFIGURATION; SQLSTATE: HY000

    Message: Error writing relay log configuration.

  • Error number: MY-010709; Symbol: ER_TREE_CORRUPT_PARENT_SHOULD_POINT_AT_PARENT; SQLSTATE: HY000

    Message: Wrong tree: Parent doesn't point at parent

  • Error number: MY-010710; Symbol: ER_TREE_CORRUPT_ROOT_SHOULD_BE_BLACK; SQLSTATE: HY000

    Message: Wrong tree: Root should be black

  • Error number: MY-010711; Symbol: ER_TREE_CORRUPT_2_CONSECUTIVE_REDS; SQLSTATE: HY000

    Message: Wrong tree: Found two red in a row

  • Error number: MY-010712; Symbol: ER_TREE_CORRUPT_RIGHT_IS_LEFT; SQLSTATE: HY000

    Message: Wrong tree: Found right == left

  • Error number: MY-010713; Symbol: ER_TREE_CORRUPT_INCORRECT_BLACK_COUNT; SQLSTATE: HY000

    Message: Wrong tree: Incorrect black-count: %d - %d

  • Error number: MY-010714; Symbol: ER_WRONG_COUNT_FOR_ORIGIN; SQLSTATE: HY000

    Message: Use_count: Wrong count %lu for origin %p

  • Error number: MY-010715; Symbol: ER_WRONG_COUNT_FOR_KEY; SQLSTATE: HY000

    Message: Use_count: Wrong count for key at %p, %lu should be %lu

  • Error number: MY-010716; Symbol: ER_WRONG_COUNT_OF_ELEMENTS; SQLSTATE: HY000

    Message: Wrong number of elements: %u (should be %u) for tree at %p

  • Error number: MY-010717; Symbol: ER_RPL_ERROR_READING_REPLICA_WORKER_CONFIGURATION; SQLSTATE: HY000

    Message: Error reading replica worker configuration

  • Error number: MY-010719; Symbol: ER_RPL_FAILED_TO_OPEN_RELAY_LOG; SQLSTATE: HY000

    Message: Failed to open relay log %s, error: %s

  • Error number: MY-010720; Symbol: ER_RPL_WORKER_CANT_READ_RELAY_LOG; SQLSTATE: HY000

    Message: Error when worker read relay log events,relay log name %s, position %llu

  • Error number: MY-010721; Symbol: ER_RPL_WORKER_CANT_FIND_NEXT_RELAY_LOG; SQLSTATE: HY000

    Message: Failed to find next relay log when retrying the transaction, current relay log is %s

  • Error number: MY-010722; Symbol: ER_RPL_MTA_REPLICA_COORDINATOR_HAS_WAITED; SQLSTATE: HY000

    Message: Multi-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.

  • Error number: MY-010723; Symbol: ER_BINLOG_FAILED_TO_WRITE_DROP_FOR_TEMP_TABLES; SQLSTATE: HY000

    Message: Failed to write the DROP statement for temporary tables to binary log

  • Error number: MY-010724; Symbol: ER_BINLOG_OOM_WRITING_DELETE_WHILE_OPENING_HEAP_TABLE; SQLSTATE: HY000

    Message: When opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary log

  • Error number: MY-010725; Symbol: ER_FAILED_TO_REPAIR_TABLE; SQLSTATE: HY000

    Message: Couldn't repair table: %s.%s

  • Error number: MY-010726; Symbol: ER_FAILED_TO_REMOVE_TEMP_TABLE; SQLSTATE: HY000

    Message: Could not remove temporary table: '%s', error: %d

  • Error number: MY-010727; Symbol: ER_SYSTEM_TABLE_NOT_TRANSACTIONAL; SQLSTATE: HY000

    Message: System table '%.*s' is expected to be transactional.

  • Error number: MY-010728; Symbol: ER_RPL_ERROR_WRITING_SOURCE_CONFIGURATION; SQLSTATE: HY000

    Message: Error writing source configuration.

  • Error number: MY-010729; Symbol: ER_RPL_ERROR_READING_SOURCE_CONFIGURATION; SQLSTATE: HY000

    Message: Error reading source configuration.

  • Error number: MY-010730; Symbol: ER_RPL_SSL_INFO_IN_CONNECTION_METADATA_IGNORED; SQLSTATE: HY000

    Message: SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.

  • Error number: MY-010731; Symbol: ER_PLUGIN_FAILED_DEINITIALIZATION; SQLSTATE: HY000

    Message: Plugin '%s' of type %s failed deinitialization

  • Error number: MY-010732; Symbol: ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_DEINITIALIZATION; SQLSTATE: HY000

    Message: Plugin '%s' has ref_count=%d after deinitialization.

  • Error number: MY-010733; Symbol: ER_PLUGIN_SHUTTING_DOWN_PLUGIN; SQLSTATE: HY000

    Message: Shutting down plugin '%s'

  • Error number: MY-010734; Symbol: ER_PLUGIN_REGISTRATION_FAILED; SQLSTATE: HY000

    Message: Plugin '%s' registration as a %s failed.

  • Error number: MY-010735; Symbol: ER_PLUGIN_CANT_OPEN_PLUGIN_TABLE; SQLSTATE: HY000

    Message: Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.

  • Error number: MY-010736; Symbol: ER_PLUGIN_CANT_LOAD; SQLSTATE: HY000

    Message: Couldn't load plugin named '%s' with soname '%s'.

  • Error number: MY-010737; Symbol: ER_PLUGIN_LOAD_PARAMETER_TOO_LONG; SQLSTATE: HY000

    Message: plugin-load parameter too long

  • Error number: MY-010738; Symbol: ER_PLUGIN_FORCING_SHUTDOWN; SQLSTATE: HY000

    Message: Plugin '%s' will be forced to shutdown

  • Error number: MY-010739; Symbol: ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_SHUTDOWN; SQLSTATE: HY000

    Message: Plugin '%s' has ref_count=%d after shutdown.

  • Error number: MY-010740; Symbol: ER_PLUGIN_UNKNOWN_VARIABLE_TYPE; SQLSTATE: HY000

    Message: Unknown variable type code 0x%x in plugin '%s'.

  • Error number: MY-010741; Symbol: ER_PLUGIN_VARIABLE_SET_READ_ONLY; SQLSTATE: HY000

    Message: Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag

  • Error number: MY-010742; Symbol: ER_PLUGIN_VARIABLE_MISSING_NAME; SQLSTATE: HY000

    Message: Missing variable name in plugin '%s'.

  • Error number: MY-010743; Symbol: ER_PLUGIN_VARIABLE_NOT_ALLOCATED_THREAD_LOCAL; SQLSTATE: HY000

    Message: Thread local variable '%s' not allocated in plugin '%s'.

  • Error number: MY-010744; Symbol: ER_PLUGIN_OOM; SQLSTATE: HY000

    Message: Out of memory for plugin '%s'.

  • Error number: MY-010745; Symbol: ER_PLUGIN_BAD_OPTIONS; SQLSTATE: HY000

    Message: Bad options for plugin '%s'.

  • Error number: MY-010746; Symbol: ER_PLUGIN_PARSING_OPTIONS_FAILED; SQLSTATE: HY000

    Message: Parsing options for plugin '%s' failed.

  • Error number: MY-010747; Symbol: ER_PLUGIN_DISABLED; SQLSTATE: HY000

    Message: Plugin '%s' is disabled.

  • Error number: MY-010748; Symbol: ER_PLUGIN_HAS_CONFLICTING_SYSTEM_VARIABLES; SQLSTATE: HY000

    Message: Plugin '%s' has conflicting system variables

  • Error number: MY-010749; Symbol: ER_PLUGIN_CANT_SET_PERSISTENT_OPTIONS; SQLSTATE: HY000

    Message: Setting persistent options for plugin '%s' failed.

  • Error number: MY-010750; Symbol: ER_MY_NET_WRITE_FAILED_FALLING_BACK_ON_STDERR; SQLSTATE: HY000

    Message: Failed on my_net_write, writing to stderr instead: %s

  • Error number: MY-010751; Symbol: ER_RETRYING_REPAIR_WITHOUT_QUICK; SQLSTATE: HY000

    Message: Retrying repair of: '%s' without quick

  • Error number: MY-010752; Symbol: ER_RETRYING_REPAIR_WITH_KEYCACHE; SQLSTATE: HY000

    Message: Retrying repair of: '%s' with keycache

  • Error number: MY-010753; Symbol: ER_FOUND_ROWS_WHILE_REPAIRING; SQLSTATE: HY000

    Message: Found %s of %s rows when repairing '%s'

  • Error number: MY-010754; Symbol: ER_ERROR_DURING_OPTIMIZE_TABLE; SQLSTATE: HY000

    Message: Warning: Optimize table got errno %d on %s.%s, retrying

  • Error number: MY-010755; Symbol: ER_ERROR_ENABLING_KEYS; SQLSTATE: HY000

    Message: Warning: Enabling keys got errno %d on %s.%s, retrying

  • Error number: MY-010756; Symbol: ER_CHECKING_TABLE; SQLSTATE: HY000

    Message: Checking table: '%s'

  • Error number: MY-010757; Symbol: ER_RECOVERING_TABLE; SQLSTATE: HY000

    Message: Recovering table: '%s'

  • Error number: MY-010758; Symbol: ER_CANT_CREATE_TABLE_SHARE_FROM_FRM; SQLSTATE: HY000

    Message: Error in creating TABLE_SHARE from %s.frm file.

  • Error number: MY-010759; Symbol: ER_CANT_LOCK_TABLE; SQLSTATE: HY000

    Message: Unable to acquire lock on %s.%s

  • Error number: MY-010760; Symbol: ER_CANT_ALLOC_TABLE_OBJECT; SQLSTATE: HY000

    Message: Error in allocation memory for TABLE object.

  • Error number: MY-010761; Symbol: ER_CANT_CREATE_HANDLER_OBJECT_FOR_TABLE; SQLSTATE: HY000

    Message: Error in creating handler object for table %s.%s

  • Error number: MY-010762; Symbol: ER_CANT_SET_HANDLER_REFERENCE_FOR_TABLE; SQLSTATE: HY000

    Message: Error in setting handler reference for table %s.%s

  • Error number: MY-010763; Symbol: ER_CANT_LOCK_TABLESPACE; SQLSTATE: HY000

    Message: Unable to acquire lock on tablespace name %s

  • Error number: MY-010764; Symbol: ER_CANT_UPGRADE_GENERATED_COLUMNS_TO_DD; SQLSTATE: HY000

    Message: Error in processing generated columns for table %s.%s

  • Error number: MY-010765; Symbol: ER_DD_ERROR_CREATING_ENTRY; SQLSTATE: HY000

    Message: Error in Creating DD entry for %s.%s

  • Error number: MY-010766; Symbol: ER_DD_CANT_FETCH_TABLE_DATA; SQLSTATE: HY000

    Message: Error in fetching %s.%s table data from dictionary

  • Error number: MY-010767; Symbol: ER_DD_CANT_FIX_SE_DATA; SQLSTATE: HY000

    Message: Error in fixing SE data for %s.%s

  • Error number: MY-010768; Symbol: ER_DD_CANT_CREATE_SP; SQLSTATE: HY000

    Message: Error in creating stored program '%s.%s'

  • Error number: MY-010769; Symbol: ER_CANT_OPEN_DB_OPT_USING_DEFAULT_CHARSET; SQLSTATE: HY000

    Message: Unable to open db.opt file %s. Using default Character set.

  • Error number: MY-010770; Symbol: ER_CANT_CREATE_CACHE_FOR_DB_OPT; SQLSTATE: HY000

    Message: Unable to intialize IO cache to open db.opt file %s.

  • Error number: MY-010771; Symbol: ER_CANT_IDENTIFY_CHARSET_USING_DEFAULT; SQLSTATE: HY000

    Message: Unable to identify the charset in %s. Using default character set.

  • Error number: MY-010772; Symbol: ER_DB_OPT_NOT_FOUND_USING_DEFAULT_CHARSET; SQLSTATE: HY000

    Message: db.opt file not found for %s database. Using default Character set.

  • Error number: MY-010773; Symbol: ER_EVENT_CANT_GET_TIMEZONE_FROM_FIELD; SQLSTATE: HY000

    Message: Event '%s'.'%s': invalid value in column mysql.event.time_zone.

    This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary.

  • Error number: MY-010774; Symbol: ER_EVENT_CANT_FIND_TIMEZONE; SQLSTATE: HY000

    Message: Event '%s'.'%s': has invalid time zone value

    This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary.

  • Error number: MY-010775; Symbol: ER_EVENT_CANT_GET_CHARSET; SQLSTATE: HY000

    Message: Event '%s'.'%s': invalid value in column mysql.event.character_set_client.

    This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary.

  • Error number: MY-010776; Symbol: ER_EVENT_CANT_GET_COLLATION; SQLSTATE: HY000

    Message: Event '%s'.'%s': invalid value in column mysql.event.collation_connection.

    This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary.

  • Error number: MY-010777; Symbol: ER_EVENT_CANT_OPEN_TABLE_MYSQL_EVENT; SQLSTATE: HY000

    Message: Failed to open mysql.event Table.

    This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary.

  • Error number: MY-010778; Symbol: ER_CANT_PARSE_STORED_ROUTINE_BODY; SQLSTATE: HY000

    Message: Parsing '%s.%s' routine body failed.%s

  • Error number: MY-010779; Symbol: ER_CANT_OPEN_TABLE_MYSQL_PROC; SQLSTATE: HY000

    Message: Failed to open mysql.proc Table.

    This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.proc system table and migrates its contents to the internal data dictionary.

  • Error number: MY-010780; Symbol: ER_CANT_READ_TABLE_MYSQL_PROC; SQLSTATE: HY000

    Message: Failed to read mysql.proc table.

    This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.proc system table and migrates its contents to the internal data dictionary.

  • Error number: MY-010781; Symbol: ER_FILE_EXISTS_DURING_UPGRADE; SQLSTATE: HY000

    Message: Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.

  • Error number: MY-010782; Symbol: ER_CANT_OPEN_DATADIR_AFTER_UPGRADE_FAILURE; SQLSTATE: HY000

    Message: Unable to open the data directory %s during clean up after upgrade failed

  • Error number: MY-010783; Symbol: ER_CANT_SET_PATH_FOR; SQLSTATE: HY000

    Message: Failed to set path %s

  • Error number: MY-010784; Symbol: ER_CANT_OPEN_DIR; SQLSTATE: HY000

    Message: Failed to open dir %s

  • Error number: MY-010801; Symbol: ER_EVENT_ERROR_CREATING_QUERY_TO_WRITE_TO_BINLOG; SQLSTATE: HY000

    Message: Event Error: An error occurred while creating query string, before writing it into binary log.

  • Error number: MY-010802; Symbol: ER_EVENT_SCHEDULER_ERROR_LOADING_FROM_DB; SQLSTATE: HY000

    Message: Event Scheduler: Error while loading from disk.

  • Error number: MY-010803; Symbol: ER_EVENT_SCHEDULER_ERROR_GETTING_EVENT_OBJECT; SQLSTATE: HY000

    Message: Event Scheduler: Error getting event object.

  • Error number: MY-010804; Symbol: ER_EVENT_SCHEDULER_GOT_BAD_DATA_FROM_TABLE; SQLSTATE: HY000

    Message: Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corrupted

  • Error number: MY-010805; Symbol: ER_EVENT_CANT_GET_LOCK_FOR_DROPPING_EVENT; SQLSTATE: HY000

    Message: Unable to obtain lock for dropping event %s from schema %s

  • Error number: MY-010806; Symbol: ER_EVENT_UNABLE_TO_DROP_EVENT; SQLSTATE: HY000

    Message: Unable to drop event %s from schema %s

  • Error number: MY-010808; Symbol: ER_BINLOG_CANT_RESIZE_CACHE; SQLSTATE: HY000

    Message: Unable to resize binlog IOCACHE auxiliary file

  • Error number: MY-010809; Symbol: ER_BINLOG_FILE_BEING_READ_NOT_PURGED; SQLSTATE: HY000

    Message: file %s was not purged because it was being read by thread number %u

  • Error number: MY-010810; Symbol: ER_BINLOG_IO_ERROR_READING_HEADER; SQLSTATE: HY000

    Message: I/O error reading the header from the binary log, errno=%d, io cache code=%d

  • Error number: MY-010813; Symbol: ER_BINLOG_FILE_EXTENSION_NUMBER_EXHAUSTED; SQLSTATE: HY000

    Message: Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.

  • Error number: MY-010814; Symbol: ER_BINLOG_FILE_NAME_TOO_LONG; SQLSTATE: HY000

    Message: Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.

  • Error number: MY-010815; Symbol: ER_BINLOG_FILE_EXTENSION_NUMBER_RUNNING_LOW; SQLSTATE: HY000

    Message: Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.

  • Error number: MY-010816; Symbol: ER_BINLOG_CANT_OPEN_FOR_LOGGING; SQLSTATE: HY000

    Message: Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.

  • Error number: MY-010817; Symbol: ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::open_index_file failed to sync the index file.

  • Error number: MY-010818; Symbol: ER_BINLOG_ERROR_READING_GTIDS_FROM_RELAY_LOG; SQLSTATE: HY000

    Message: Error reading GTIDs from relaylog: %d

  • Error number: MY-010819; Symbol: ER_BINLOG_EVENTS_READ_FROM_APPLIER_METADATA; SQLSTATE: HY000

    Message: %lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.

  • Error number: MY-010820; Symbol: ER_BINLOG_ERROR_READING_GTIDS_FROM_BINARY_LOG; SQLSTATE: HY000

    Message: Error reading GTIDs from binary log: %d

  • Error number: MY-010821; Symbol: ER_BINLOG_EVENTS_READ_FROM_BINLOG_INFO; SQLSTATE: HY000

    Message: Read %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.

  • Error number: MY-010822; Symbol: ER_BINLOG_CANT_GENERATE_NEW_FILE_NAME; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::open failed to generate new file name.

  • Error number: MY-010823; Symbol: ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE_IN_OPEN; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::open failed to sync the index file.

  • Error number: MY-010824; Symbol: ER_BINLOG_CANT_USE_FOR_LOGGING; SQLSTATE: HY000

    Message: Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.

  • Error number: MY-010825; Symbol: ER_BINLOG_FAILED_TO_CLOSE_INDEX_FILE_WHILE_REBUILDING; SQLSTATE: HY000

    Message: While rebuilding index file %s: Failed to close the index file.

  • Error number: MY-010826; Symbol: ER_BINLOG_FAILED_TO_DELETE_INDEX_FILE_WHILE_REBUILDING; SQLSTATE: HY000

    Message: While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.

  • Error number: MY-010827; Symbol: ER_BINLOG_FAILED_TO_RENAME_INDEX_FILE_WHILE_REBUILDING; SQLSTATE: HY000

    Message: While rebuilding index file %s: Failed to rename the new index file to the existing index file.

  • Error number: MY-010828; Symbol: ER_BINLOG_FAILED_TO_OPEN_INDEX_FILE_AFTER_REBUILDING; SQLSTATE: HY000

    Message: After rebuilding the index file %s: Failed to open the index file.

  • Error number: MY-010829; Symbol: ER_BINLOG_CANT_APPEND_LOG_TO_TMP_INDEX; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.

  • Error number: MY-010830; Symbol: ER_BINLOG_CANT_LOCATE_OLD_BINLOG_OR_RELAY_LOG_FILES; SQLSTATE: HY000

    Message: Failed to locate old binlog or relay log files

  • Error number: MY-010831; Symbol: ER_BINLOG_CANT_DELETE_FILE; SQLSTATE: HY000

    Message: Failed to delete file '%s'

  • Error number: MY-010832; Symbol: ER_BINLOG_CANT_SET_TMP_INDEX_NAME; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.

  • Error number: MY-010833; Symbol: ER_BINLOG_FAILED_TO_OPEN_TEMPORARY_INDEX_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.

  • Error number: MY-010835; Symbol: ER_BINLOG_CANT_OPEN_TMP_INDEX; SQLSTATE: HY000

    Message: %s failed to open the crash safe index file.

  • Error number: MY-010836; Symbol: ER_BINLOG_CANT_COPY_INDEX_TO_TMP; SQLSTATE: HY000

    Message: %s failed to copy index file to crash safe index file.

  • Error number: MY-010837; Symbol: ER_BINLOG_CANT_CLOSE_TMP_INDEX; SQLSTATE: HY000

    Message: %s failed to close the crash safe index file.

  • Error number: MY-010838; Symbol: ER_BINLOG_CANT_MOVE_TMP_TO_INDEX; SQLSTATE: HY000

    Message: %s failed to move crash safe index file to index file.

  • Error number: MY-010839; Symbol: ER_BINLOG_PURGE_LOGS_CALLED_WITH_FILE_NOT_IN_INDEX; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.

  • Error number: MY-010840; Symbol: ER_BINLOG_PURGE_LOGS_CANT_SYNC_INDEX_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_logs failed to sync the index file.

  • Error number: MY-010841; Symbol: ER_BINLOG_PURGE_LOGS_CANT_COPY_TO_REGISTER_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.

  • Error number: MY-010842; Symbol: ER_BINLOG_PURGE_LOGS_CANT_FLUSH_REGISTER_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_logs failed to flush register file.

  • Error number: MY-010843; Symbol: ER_BINLOG_PURGE_LOGS_CANT_UPDATE_INDEX_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_logs failed to update the index file

  • Error number: MY-010844; Symbol: ER_BINLOG_PURGE_LOGS_FAILED_TO_PURGE_LOG; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.

  • Error number: MY-010845; Symbol: ER_BINLOG_FAILED_TO_SET_PURGE_INDEX_FILE_NAME; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.

  • Error number: MY-010846; Symbol: ER_BINLOG_FAILED_TO_OPEN_REGISTER_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::open_purge_index_file failed to open register file.

  • Error number: MY-010847; Symbol: ER_BINLOG_FAILED_TO_REINIT_REGISTER_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for read

  • Error number: MY-010848; Symbol: ER_BINLOG_FAILED_TO_READ_REGISTER_FILE; SQLSTATE: HY000

    Message: MYSQL_BIN_LOG::purge_index_entry error %d reading from register file.

  • Error number: MY-010849; Symbol: ER_CANT_STAT_FILE; SQLSTATE: HY000

    Message: Failed to execute mysql_file_stat on file '%s'

  • Error number: MY-010850; Symbol: ER_BINLOG_CANT_DELETE_LOG_FILE_DOES_INDEX_MATCH_FILES; SQLSTATE: HY000

    Message: Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog files

  • Error number: MY-010851; Symbol: ER_BINLOG_CANT_DELETE_FILE_AND_READ_BINLOG_INDEX; SQLSTATE: HY000

    Message: Failed to delete file '%s' and read the binlog index file

  • Error number: MY-010852; Symbol: ER_BINLOG_FAILED_TO_DELETE_LOG_FILE; SQLSTATE: HY000

    Message: Failed to delete log file '%s'

  • Error number: MY-010853; Symbol: ER_BINLOG_LOGGING_INCIDENT_TO_STOP_REPLICAS; SQLSTATE: HY000

    Message: %s An incident event has been written to the binary log which will stop the replicas.

  • Error number: MY-010854; Symbol: ER_BINLOG_CANT_FIND_LOG_IN_INDEX; SQLSTATE: HY000

    Message: find_log_pos() failed (error: %d)

  • Error number: MY-010855; Symbol: ER_BINLOG_RECOVERING_AFTER_CRASH_USING; SQLSTATE: HY000

    Message: Recovering after a crash using %s

  • Error number: MY-010856; Symbol: ER_BINLOG_CANT_OPEN_CRASHED_BINLOG; SQLSTATE: HY000

    Message: Failed to open the crashed binlog file when source server is recovering it.

  • Error number: MY-010857; Symbol: ER_BINLOG_CANT_TRIM_CRASHED_BINLOG; SQLSTATE: HY000

    Message: Failed to trim the crashed binlog file when source server is recovering it.

  • Error number: MY-010858; Symbol: ER_BINLOG_CRASHED_BINLOG_TRIMMED; SQLSTATE: HY000

    Message: Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.

  • Error number: MY-010859; Symbol: ER_BINLOG_CANT_CLEAR_IN_USE_FLAG_FOR_CRASHED_BINLOG; SQLSTATE: HY000

    Message: Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.

  • Error number: MY-010860; Symbol: ER_BINLOG_FAILED_TO_RUN_AFTER_SYNC_HOOK; SQLSTATE: HY000

    Message: Failed to run 'after_sync' hooks

  • Error number: MY-010861; Symbol: ER_TURNING_LOGGING_OFF_FOR_THE_DURATION; SQLSTATE: HY000

    Message: %s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.

  • Error number: MY-010862; Symbol: ER_BINLOG_FAILED_TO_RUN_AFTER_FLUSH_HOOK; SQLSTATE: HY000

    Message: Failed to run 'after_flush' hooks

  • Error number: MY-010864; Symbol: ER_BINLOG_WARNING_SUPPRESSED; SQLSTATE: HY000

    Message: The following warning was suppressed %d times during the last %d seconds in the error log

  • Error number: MY-010865; Symbol: ER_NDB_LOG_ENTRY; SQLSTATE: HY000

    Message: NDB: %s

  • Error number: MY-010866; Symbol: ER_NDB_LOG_ENTRY_WITH_PREFIX; SQLSTATE: HY000

    Message: NDB %s: %s

  • Error number: MY-010868; Symbol: ER_INNODB_UNKNOWN_COLLATION; SQLSTATE: HY000

    Message: Unknown collation #%lu.

  • Error number: MY-010869; Symbol: ER_INNODB_INVALID_LOG_GROUP_HOME_DIR; SQLSTATE: HY000

    Message: syntax error in innodb_log_group_home_dir

  • Error number: MY-010870; Symbol: ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY; SQLSTATE: HY000

    Message: syntax error in innodb_undo_directory

  • Error number: MY-010871; Symbol: ER_INNODB_ILLEGAL_COLON_IN_POOL; SQLSTATE: HY000

    Message: InnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.

  • Error number: MY-010872; Symbol: ER_INNODB_INVALID_PAGE_SIZE; SQLSTATE: HY000

    Message: InnoDB: Invalid page size=%lu.

  • Error number: MY-010873; Symbol: ER_INNODB_DIRTY_WATER_MARK_NOT_LOW; SQLSTATE: HY000

    Message: InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lf

  • Error number: MY-010874; Symbol: ER_INNODB_IO_CAPACITY_EXCEEDS_MAX; SQLSTATE: HY000

    Message: InnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu

  • Error number: MY-010875; Symbol: ER_INNODB_FILES_SAME; SQLSTATE: HY000

    Message: %s and %s file names seem to be the same.

  • Error number: MY-010876; Symbol: ER_INNODB_UNREGISTERED_TRX_ACTIVE; SQLSTATE: HY000

    Message: Transaction not registered for MySQL 2PC, but transaction is active

  • Error number: MY-010877; Symbol: ER_INNODB_CLOSING_CONNECTION_ROLLS_BACK; SQLSTATE: HY000

    Message: MySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.

  • Error number: MY-010878; Symbol: ER_INNODB_TRX_XLATION_TABLE_OOM; SQLSTATE: HY000

    Message: InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%lu

  • Error number: MY-010879; Symbol: ER_INNODB_CANT_FIND_INDEX_IN_INNODB_DD; SQLSTATE: HY000

    Message: Cannot find index %s in InnoDB index dictionary.

  • Error number: MY-010880; Symbol: ER_INNODB_INDEX_COLUMN_INFO_UNLIKE_MYSQLS; SQLSTATE: HY000

    Message: Found index %s whose column info does not match that of MySQL.

  • Error number: MY-010882; Symbol: ER_INNODB_CANT_BUILD_INDEX_XLATION_TABLE_FOR; SQLSTATE: HY000

    Message: Build InnoDB index translation table for Table %s failed

  • Error number: MY-010883; Symbol: ER_INNODB_PK_NOT_IN_MYSQL; SQLSTATE: HY000

    Message: Table %s has a primary key in InnoDB data dictionary, but not in MySQL!

  • Error number: MY-010884; Symbol: ER_INNODB_PK_ONLY_IN_MYSQL; SQLSTATE: HY000

    Message: Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.

  • Error number: MY-010885; Symbol: ER_INNODB_CLUSTERED_INDEX_PRIVATE; SQLSTATE: HY000

    Message: Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.

  • Error number: MY-010887; Symbol: ER_ERRMSG_REPLACEMENT_DODGY; SQLSTATE: HY000

    Message: Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.

  • Error number: MY-010888; Symbol: ER_ERRMSG_REPLACEMENTS_FAILED; SQLSTATE: HY000

    Message: Table for error message replacements could not be found or read, or one or more replacements could not be applied.

  • Error number: MY-010889; Symbol: ER_NPIPE_CANT_CREATE; SQLSTATE: HY000

    Message: %s: %s

  • Error number: MY-010890; Symbol: ER_PARTITION_MOVE_CREATED_DUPLICATE_ROW_PLEASE_FIX; SQLSTATE: HY000

    Message: Table '%s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %s

  • Error number: MY-010891; Symbol: ER_AUDIT_CANT_ABORT_COMMAND; SQLSTATE: HY000

    Message: Command '%s' cannot be aborted. The trigger error was (%d) [%s]: %s

  • Error number: MY-010892; Symbol: ER_AUDIT_CANT_ABORT_EVENT; SQLSTATE: HY000

    Message: Event '%s' cannot be aborted. The trigger error was (%d) [%s]: %s

  • Error number: MY-010893; Symbol: ER_AUDIT_WARNING; SQLSTATE: HY000

    Message: %s. The trigger error was (%d) [%s]: %s

  • Error number: MY-010897; Symbol: ER_RPL_REPLICA_INSECURE_CHANGE_SOURCE; SQLSTATE: HY000

    Message: Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.

  • Error number: MY-010899; Symbol: ER_RPL_REPLICA_INCORRECT_CHANNEL; SQLSTATE: HY000

    Message: Replica channel '%s' does not exist.

  • Error number: MY-010900; Symbol: ER_FAILED_TO_FIND_DL_ENTRY; SQLSTATE: HY000

    Message: Can't find symbol '%s' in library.

  • Error number: MY-010901; Symbol: ER_FAILED_TO_OPEN_SHARED_LIBRARY; SQLSTATE: HY000

    Message: Can't open shared library '%s' (errno: %d %s).

  • Error number: MY-010902; Symbol: ER_THREAD_PRIORITY_IGNORED; SQLSTATE: HY000

    Message: Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.

  • Error number: MY-010903; Symbol: ER_BINLOG_CACHE_SIZE_TOO_LARGE; SQLSTATE: HY000

    Message: Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.

  • Error number: MY-010904; Symbol: ER_BINLOG_STMT_CACHE_SIZE_TOO_LARGE; SQLSTATE: HY000

    Message: Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.

  • Error number: MY-010905; Symbol: ER_FAILED_TO_GENERATE_UNIQUE_LOGFILE; SQLSTATE: HY000

    Message: Can't generate a unique log-filename %s.(1-999).

  • Error number: MY-010906; Symbol: ER_FAILED_TO_READ_FILE; SQLSTATE: HY000

    Message: Error reading file '%s' (errno: %d - %s)

  • Error number: MY-010907; Symbol: ER_FAILED_TO_WRITE_TO_FILE; SQLSTATE: HY000

    Message: Error writing file '%s' (errno: %d - %s)

  • Error number: MY-010908; Symbol: ER_BINLOG_UNSAFE_MESSAGE_AND_STATEMENT; SQLSTATE: HY000

    Message: %s Statement: %s

  • Error number: MY-010909; Symbol: ER_FORCE_CLOSE_THREAD; SQLSTATE: HY000

    Message: %s: Forcing close of thread %ld user: '%s'.

  • Error number: MY-010910; Symbol: ER_SERVER_SHUTDOWN_COMPLETE; SQLSTATE: HY000

    Message: %s: Shutdown complete (mysqld %s) %s.

  • Error number: MY-010911; Symbol: ER_RPL_CANT_HAVE_SAME_BASENAME; SQLSTATE: HY000

    Message: Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.

  • Error number: MY-010912; Symbol: ER_RPL_GTID_MODE_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON; SQLSTATE: HY000

    Message: GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.

  • Error number: MY-010913; Symbol: ER_WARN_NO_SERVERID_SPECIFIED; SQLSTATE: HY000

    Message: You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.

  • Error number: MY-010914; Symbol: ER_ABORTING_USER_CONNECTION; SQLSTATE: HY000

    Message: Aborted connection %u to db: '%s' user: '%s' host: '%s' (%s).

  • Error number: MY-010915; Symbol: ER_SQL_MODE_MERGED_WITH_STRICT_MODE; SQLSTATE: HY000

    Message: 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.

  • Error number: MY-010916; Symbol: ER_GTID_PURGED_WAS_UPDATED; SQLSTATE: HY000

    Message: @@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.

  • Error number: MY-010917; Symbol: ER_GTID_EXECUTED_WAS_UPDATED; SQLSTATE: HY000

    Message: @@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.

  • Error number: MY-010918; Symbol: ER_DEPRECATE_MSG_WITH_REPLACEMENT; SQLSTATE: HY000

    Message: '%s' is deprecated and will be removed in a future release. Please use %s instead.

  • Error number: MY-010919; Symbol: ER_TRG_CREATION_CTX_NOT_SET; SQLSTATE: HY000

    Message: Triggers for table `%s`.`%s` have no creation context

  • Error number: MY-010920; Symbol: ER_FILE_HAS_OLD_FORMAT; SQLSTATE: HY000

    Message: '%s' has an old format, you should re-create the '%s' object(s)

  • Error number: MY-010921; Symbol: ER_VIEW_CREATION_CTX_NOT_SET; SQLSTATE: HY000

    Message: View `%s`.`%s` has no creation context

  • Error number: MY-010923; Symbol: ER_TABLE_UPGRADE_REQUIRED; SQLSTATE: HY000

    Message: Table upgrade required. Please do "REPAIR TABLE `%s`" or dump/reload to fix it!

  • Error number: MY-010924; Symbol: ER_GET_ERRNO_FROM_STORAGE_ENGINE; SQLSTATE: HY000

    Message: Got error %d - '%s' from storage engine.

  • Error number: MY-010925; Symbol: ER_ACCESS_DENIED_ERROR_WITHOUT_PASSWORD; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s'

  • Error number: MY-010926; Symbol: ER_ACCESS_DENIED_ERROR_WITH_PASSWORD; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s' (using password: %s)

  • Error number: MY-010927; Symbol: ER_ACCESS_DENIED_FOR_USER_ACCOUNT_LOCKED; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s'. Account is locked.

  • Error number: MY-010929; Symbol: ER_SYSTEM_TABLES_NOT_SUPPORTED_BY_STORAGE_ENGINE; SQLSTATE: HY000

    Message: Storage engine '%s' does not support system tables. [%s.%s].

  • Error number: MY-010931; Symbol: ER_SERVER_STARTUP_MSG; SQLSTATE: HY000

    Message: %s: ready for connections. Version: '%s' socket: '%s' port: %d %s.

  • Error number: MY-010932; Symbol: ER_FAILED_TO_FIND_LOCALE_NAME; SQLSTATE: HY000

    Message: Unknown locale: '%s'.

  • Error number: MY-010933; Symbol: ER_FAILED_TO_FIND_COLLATION_NAME; SQLSTATE: HY000

    Message: Unknown collation: '%s'.

  • Error number: MY-010934; Symbol: ER_SERVER_OUT_OF_RESOURCES; SQLSTATE: HY000

    Message: Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space

  • Error number: MY-010935; Symbol: ER_SERVER_OUTOFMEMORY; SQLSTATE: HY000

    Message: Out of memory; restart server and try again (needed %d bytes)

  • Error number: MY-010936; Symbol: ER_INVALID_COLLATION_FOR_CHARSET; SQLSTATE: HY000

    Message: COLLATION '%s' is not valid for CHARACTER SET '%s'

  • Error number: MY-010937; Symbol: ER_CANT_START_ERROR_LOG_SERVICE; SQLSTATE: HY000

    Message: Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).

  • Error number: MY-010938; Symbol: ER_CREATING_NEW_UUID_FIRST_START; SQLSTATE: HY000

    Message: Generating a new UUID: %s.

  • Error number: MY-010939; Symbol: ER_FAILED_TO_GET_ABSOLUTE_PATH; SQLSTATE: HY000

    Message: Failed to get absolute path of program executable %s

  • Error number: MY-010940; Symbol: ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP; SQLSTATE: HY000

    Message: Failed to bootstrap performance schema components infrastructure.

  • Error number: MY-010941; Symbol: ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_SHUTDOWN; SQLSTATE: HY000

    Message: Failed to deinit performance schema components infrastructure.

  • Error number: MY-010942; Symbol: ER_DUP_FD_OPEN_FAILED; SQLSTATE: HY000

    Message: Could not open duplicate fd for %s: %s.

  • Error number: MY-010943; Symbol: ER_SYSTEM_VIEW_INIT_FAILED; SQLSTATE: HY000

    Message: System views initialization failed.

  • Error number: MY-010944; Symbol: ER_RESOURCE_GROUP_POST_INIT_FAILED; SQLSTATE: HY000

    Message: Resource group post initialization failed.

  • Error number: MY-010945; Symbol: ER_RESOURCE_GROUP_SUBSYSTEM_INIT_FAILED; SQLSTATE: HY000

    Message: Resource Group subsystem initialization failed.

  • Error number: MY-010946; Symbol: ER_FAILED_START_MYSQLD_DAEMON; SQLSTATE: HY000

    Message: Failed to start mysqld daemon. Check mysqld error log.

  • Error number: MY-010947; Symbol: ER_CANNOT_CHANGE_TO_ROOT_DIR; SQLSTATE: HY000

    Message: Cannot change to root directory: %s.

  • Error number: MY-010948; Symbol: ER_PERSISTENT_PRIVILEGES_BOOTSTRAP; SQLSTATE: HY000

    Message: Failed to bootstrap persistent privileges.

  • Error number: MY-010949; Symbol: ER_BASEDIR_SET_TO; SQLSTATE: HY000

    Message: Basedir set to %s.

  • Error number: MY-010950; Symbol: ER_RPL_FILTER_ADD_WILD_DO_TABLE_FAILED; SQLSTATE: HY000

    Message: Could not add wild do table rule '%s'!

  • Error number: MY-010951; Symbol: ER_RPL_FILTER_ADD_WILD_IGNORE_TABLE_FAILED; SQLSTATE: HY000

    Message: Could not add wild ignore table rule '%s'!

  • Error number: MY-010952; Symbol: ER_PRIVILEGE_SYSTEM_INIT_FAILED; SQLSTATE: HY000

    Message: The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.

  • Error number: MY-010953; Symbol: ER_CANNOT_SET_LOG_ERROR_SERVICES; SQLSTATE: HY000

    Message: Cannot set services "%s" requested in --log-error-services, using defaults.

  • Error number: MY-010954; Symbol: ER_PERFSCHEMA_TABLES_INIT_FAILED; SQLSTATE: HY000

    Message: Performance schema tables initialization failed.

  • Error number: MY-010958; Symbol: ER_BINLOG_FILE_OPEN_FAILED; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-010959; Symbol: ER_BINLOG_EVENT_WRITE_TO_STMT_CACHE_FAILED; SQLSTATE: HY000

    Message: Failed to write an incident event into stmt_cache.

  • Error number: MY-010960; Symbol: ER_REPLICA_RELAY_LOG_TRUNCATE_INFO; SQLSTATE: HY000

    Message: Relaylog file %s size was %llu, but was truncated at %llu.

  • Error number: MY-010961; Symbol: ER_REPLICA_RELAY_LOG_PURGE_FAILED; SQLSTATE: HY000

    Message: Unable to purge relay log files. %s:%s.

  • Error number: MY-010962; Symbol: ER_RPL_REPLICA_FILTER_CREATE_FAILED; SQLSTATE: HY000

    Message: Replica: failed in creating filter for channel '%s'.

  • Error number: MY-010963; Symbol: ER_RPL_REPLICA_GLOBAL_FILTERS_COPY_FAILED; SQLSTATE: HY000

    Message: Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.

  • Error number: MY-010964; Symbol: ER_RPL_REPLICA_RESET_FILTER_OPTIONS; SQLSTATE: HY000

    Message: There are per-channel replication filter(s) configured for channel '%s' which does not exist. The filter(s) have been discarded.

  • Error number: MY-010965; Symbol: ER_MISSING_GRANT_SYSTEM_TABLE; SQLSTATE: HY000

    Message: The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.

  • Error number: MY-010966; Symbol: ER_MISSING_ACL_SYSTEM_TABLE; SQLSTATE: HY000

    Message: ACL table mysql.%.*s missing. Some operations may fail.

  • Error number: MY-010967; Symbol: ER_ANONYMOUS_AUTH_ID_NOT_ALLOWED_IN_MANDATORY_ROLES; SQLSTATE: HY000

    Message: Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.

  • Error number: MY-010968; Symbol: ER_UNKNOWN_AUTH_ID_IN_MANDATORY_ROLE; SQLSTATE: HY000

    Message: Can't set mandatory_role: There's no such authorization ID %s@%s.

  • Error number: MY-010969; Symbol: ER_WRITE_ROW_TO_PARTITION_FAILED; SQLSTATE: HY000

    Message: Table '%s' failed to move/insert a row from part %d into part %d: %s.

  • Error number: MY-010970; Symbol: ER_RESOURCE_GROUP_METADATA_UPDATE_SKIPPED; SQLSTATE: HY000

    Message: Skipped updating resource group metadata in InnoDB read only mode.

  • Error number: MY-010971; Symbol: ER_FAILED_TO_PERSIST_RESOURCE_GROUP_METADATA; SQLSTATE: HY000

    Message: Failed to persist resource group %s to Data Dictionary.

  • Error number: MY-010972; Symbol: ER_FAILED_TO_DESERIALIZE_RESOURCE_GROUP; SQLSTATE: HY000

    Message: Failed to deserialize resource group %s.

  • Error number: MY-010973; Symbol: ER_FAILED_TO_UPDATE_RESOURCE_GROUP; SQLSTATE: HY000

    Message: Update of resource group %s failed.

  • Error number: MY-010974; Symbol: ER_RESOURCE_GROUP_VALIDATION_FAILED; SQLSTATE: HY000

    Message: Validation of resource group %s failed. Resource group is disabled.

  • Error number: MY-010975; Symbol: ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP; SQLSTATE: HY000

    Message: Unable to allocate memory for Resource Group %s.

  • Error number: MY-010976; Symbol: ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP_HASH; SQLSTATE: HY000

    Message: Failed to allocate memory for resource group hash.

  • Error number: MY-010977; Symbol: ER_FAILED_TO_ADD_RESOURCE_GROUP_TO_MAP; SQLSTATE: HY000

    Message: Failed to add resource group %s to resource group map.

  • Error number: MY-010978; Symbol: ER_RESOURCE_GROUP_IS_DISABLED; SQLSTATE: HY000

    Message: Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).

  • Error number: MY-010979; Symbol: ER_FAILED_TO_APPLY_RESOURCE_GROUP_CONTROLLER; SQLSTATE: HY000

    Message: Unable to apply resource group controller %s.

  • Error number: MY-010980; Symbol: ER_FAILED_TO_ACQUIRE_LOCK_ON_RESOURCE_GROUP; SQLSTATE: HY000

    Message: Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.

  • Error number: MY-010981; Symbol: ER_PFS_NOTIFICATION_FUNCTION_REGISTER_FAILED; SQLSTATE: HY000

    Message: PFS %s notification function registration failed.

  • Error number: MY-010982; Symbol: ER_RES_GRP_SET_THR_AFFINITY_FAILED; SQLSTATE: HY000

    Message: Unable to bind thread id %llu to cpu id %u (error code %d - %s).

  • Error number: MY-010983; Symbol: ER_RES_GRP_SET_THR_AFFINITY_TO_CPUS_FAILED; SQLSTATE: HY000

    Message: Unable to bind thread id %llu to cpu ids (error code %d - %s).

  • Error number: MY-010984; Symbol: ER_RES_GRP_THD_UNBIND_FROM_CPU_FAILED; SQLSTATE: HY000

    Message: Unbind thread id %llu failed. (error code %d - %s).

  • Error number: MY-010985; Symbol: ER_RES_GRP_SET_THREAD_PRIORITY_FAILED; SQLSTATE: HY000

    Message: Setting thread priority %d to thread id %llu failed. (error code %d - %s).

  • Error number: MY-010986; Symbol: ER_RES_GRP_FAILED_TO_DETERMINE_NICE_CAPABILITY; SQLSTATE: HY000

    Message: Unable to determine CAP_SYS_NICE capability.

  • Error number: MY-010987; Symbol: ER_RES_GRP_FAILED_TO_GET_THREAD_HANDLE; SQLSTATE: HY000

    Message: %s failed: Failed to get handle for thread %llu.

  • Error number: MY-010988; Symbol: ER_RES_GRP_GET_THREAD_PRIO_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Retrieval of thread priority unsupported on %s.

  • Error number: MY-010989; Symbol: ER_RES_GRP_FAILED_DETERMINE_CPU_COUNT; SQLSTATE: HY000

    Message: Unable to determine the number of CPUs.

  • Error number: MY-010990; Symbol: ER_RES_GRP_FEATURE_NOT_AVAILABLE; SQLSTATE: HY000

    Message: Resource group feature shall not be available. Incompatible thread handling option.

  • Error number: MY-010991; Symbol: ER_RES_GRP_INVALID_THREAD_PRIORITY; SQLSTATE: HY000

    Message: Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].

  • Error number: MY-010992; Symbol: ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_CPUID_FAILED; SQLSTATE: HY000

    Message: bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %s).

  • Error number: MY-010993; Symbol: ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_THREAD_FAILED; SQLSTATE: HY000

    Message: bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %s).

  • Error number: MY-010994; Symbol: ER_RES_GRP_SOLARIS_PROCESSOR_AFFINITY_FAILED; SQLSTATE: HY000

    Message: %s failed: processor_affinity failed (error code %d - %s).

  • Error number: MY-010995; Symbol: ER_DD_UPGRADE_RENAME_IDX_STATS_FILE_FAILED; SQLSTATE: HY000

    Message: Error in renaming mysql_index_stats.ibd.

  • Error number: MY-010996; Symbol: ER_DD_UPGRADE_DD_OPEN_FAILED; SQLSTATE: HY000

    Message: Error in opening data directory %s.

  • Error number: MY-010997; Symbol: ER_DD_UPGRADE_FAILED_TO_FETCH_TABLESPACES; SQLSTATE: HY000

    Message: Error in fetching list of tablespaces.

  • Error number: MY-010998; Symbol: ER_DD_UPGRADE_FAILED_TO_ACQUIRE_TABLESPACE; SQLSTATE: HY000

    Message: Error in acquiring Tablespace for SDI insertion %s.

  • Error number: MY-010999; Symbol: ER_DD_UPGRADE_FAILED_TO_RESOLVE_TABLESPACE_ENGINE; SQLSTATE: HY000

    Message: Error in resolving Engine name for tablespace %s with engine %s.

  • Error number: MY-011000; Symbol: ER_FAILED_TO_CREATE_SDI_FOR_TABLESPACE; SQLSTATE: HY000

    Message: Error in creating SDI for %s tablespace.

  • Error number: MY-011001; Symbol: ER_FAILED_TO_STORE_SDI_FOR_TABLESPACE; SQLSTATE: HY000

    Message: Error in storing SDI for %s tablespace.

  • Error number: MY-011002; Symbol: ER_DD_UPGRADE_FAILED_TO_FETCH_TABLES; SQLSTATE: HY000

    Message: Error in fetching list of tables.

  • Error number: MY-011003; Symbol: ER_DD_UPGRADE_DD_POPULATED; SQLSTATE: HY000

    Message: Finished populating Data Dictionary tables with data.

  • Error number: MY-011004; Symbol: ER_DD_UPGRADE_INFO_FILE_OPEN_FAILED; SQLSTATE: HY000

    Message: Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.

  • Error number: MY-011005; Symbol: ER_DD_UPGRADE_INFO_FILE_CLOSE_FAILED; SQLSTATE: HY000

    Message: Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.

  • Error number: MY-011006; Symbol: ER_DD_UPGRADE_TABLESPACE_MIGRATION_FAILED; SQLSTATE: HY000

    Message: Got error %d from SE while migrating tablespaces.

  • Error number: MY-011007; Symbol: ER_DD_UPGRADE_FAILED_TO_CREATE_TABLE_STATS; SQLSTATE: HY000

    Message: Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.

  • Error number: MY-011008; Symbol: ER_DD_UPGRADE_TABLE_STATS_MIGRATE_COMPLETED; SQLSTATE: HY000

    Message: Finished migrating TABLE statistics data.

  • Error number: MY-011009; Symbol: ER_DD_UPGRADE_FAILED_TO_CREATE_INDEX_STATS; SQLSTATE: HY000

    Message: Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.

  • Error number: MY-011010; Symbol: ER_DD_UPGRADE_INDEX_STATS_MIGRATE_COMPLETED; SQLSTATE: HY000

    Message: Finished migrating INDEX statistics data.

  • Error number: MY-011011; Symbol: ER_DD_UPGRADE_FAILED_FIND_VALID_DATA_DIR; SQLSTATE: HY000

    Message: Failed to find valid data directory.

  • Error number: MY-011012; Symbol: ER_DD_UPGRADE_START; SQLSTATE: HY000

    Message: Starting upgrade of data directory.

  • Error number: MY-011013; Symbol: ER_DD_UPGRADE_FAILED_INIT_DD_SE; SQLSTATE: HY000

    Message: Failed to initialize DD Storage Engine.

  • Error number: MY-011014; Symbol: ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_ABORT; SQLSTATE: HY000

    Message: Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.

  • Error number: MY-011015; Symbol: ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_CONTINUE; SQLSTATE: HY000

    Message: Found partially upgraded DD. Upgrade will continue and start the server.

  • Error number: MY-011016; Symbol: ER_DD_UPGRADE_SE_LOGS_FAILED; SQLSTATE: HY000

    Message: Error in upgrading engine logs.

  • Error number: MY-011017; Symbol: ER_DD_UPGRADE_SDI_INFO_UPDATE_FAILED; SQLSTATE: HY000

    Message: Error in updating SDI information.

  • Error number: MY-011018; Symbol: ER_SKIP_UPDATING_METADATA_IN_SE_RO_MODE; SQLSTATE: HY000

    Message: Skip updating %s metadata in InnoDB read-only mode.

  • Error number: MY-011019; Symbol: ER_CREATED_SYSTEM_WITH_VERSION; SQLSTATE: HY000

    Message: Created system views with I_S version %d.

  • Error number: MY-011020; Symbol: ER_UNKNOWN_ERROR_DETECTED_IN_SE; SQLSTATE: HY000

    Message: Unknown error detected %d in handler.

  • Error number: MY-011021; Symbol: ER_READ_LOG_EVENT_FAILED; SQLSTATE: HY000

    Message: Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.

  • Error number: MY-011022; Symbol: ER_ROW_DATA_TOO_BIG_TO_WRITE_IN_BINLOG; SQLSTATE: HY000

    Message: The row data is greater than 4GB, which is too big to write to the binary log.

  • Error number: MY-011023; Symbol: ER_FAILED_TO_CONSTRUCT_DROP_EVENT_QUERY; SQLSTATE: HY000

    Message: Unable to construct DROP EVENT SQL query string.

  • Error number: MY-011024; Symbol: ER_FAILED_TO_BINLOG_DROP_EVENT; SQLSTATE: HY000

    Message: Unable to binlog drop event %s.%s.

  • Error number: MY-011025; Symbol: ER_FAILED_TO_START_REPLICA_THREAD; SQLSTATE: HY000

    Message: Failed to start replica threads for channel '%s'.

  • Error number: MY-011026; Symbol: ER_RPL_IO_THREAD_KILLED; SQLSTATE: HY000

    Message: %s%s.

  • Error number: MY-011027; Symbol: ER_REPLICA_RECONNECT_FAILED; SQLSTATE: HY000

    Message: Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.

  • Error number: MY-011028; Symbol: ER_REPLICA_KILLED_AFTER_RECONNECT; SQLSTATE: HY000

    Message: Replica I/O thread killed during or after reconnect.

  • Error number: MY-011029; Symbol: ER_REPLICA_NOT_STARTED_ON_SOME_CHANNELS; SQLSTATE: HY000

    Message: Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.

  • Error number: MY-011030; Symbol: ER_FAILED_TO_ADD_RPL_FILTER; SQLSTATE: HY000

    Message: Failed to add a replication filter into filter map for channel '%s'.

  • Error number: MY-011031; Symbol: ER_PER_CHANNEL_RPL_FILTER_CONF_FOR_GRP_RPL; SQLSTATE: HY000

    Message: There are per-channel replication filter(s) configured for group replication channel '%s' which is disallowed. The filter(s) have been discarded.

  • Error number: MY-011032; Symbol: ER_RPL_FILTERS_NOT_ATTACHED_TO_CHANNEL; SQLSTATE: HY000

    Message: There are per-channel replication filter(s) configured for channel '%s' which does not exist. The filter(s) have been discarded.

  • Error number: MY-011033; Symbol: ER_FAILED_TO_BUILD_DO_AND_IGNORE_TABLE_HASHES; SQLSTATE: HY000

    Message: An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.

  • Error number: MY-011034; Symbol: ER_CLONE_PLUGIN_NOT_LOADED_TRACE; SQLSTATE: HY000

    Message: Clone plugin cannot be loaded.

  • Error number: MY-011035; Symbol: ER_CLONE_HANDLER_EXIST_TRACE; SQLSTATE: HY000

    Message: Clone Handler exists.

  • Error number: MY-011036; Symbol: ER_CLONE_CREATE_HANDLER_FAIL_TRACE; SQLSTATE: HY000

    Message: Could not create Clone Handler.

  • Error number: MY-011037; Symbol: ER_CYCLE_TIMER_IS_NOT_AVAILABLE; SQLSTATE: HY000

    Message: The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.

  • Error number: MY-011038; Symbol: ER_NANOSECOND_TIMER_IS_NOT_AVAILABLE; SQLSTATE: HY000

    Message: The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.

  • Error number: MY-011039; Symbol: ER_MICROSECOND_TIMER_IS_NOT_AVAILABLE; SQLSTATE: HY000

    Message: The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.

  • Error number: MY-011040; Symbol: ER_PFS_MALLOC_ARRAY_OVERFLOW; SQLSTATE: HY000

    Message: Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.

  • Error number: MY-011041; Symbol: ER_PFS_MALLOC_ARRAY_OOM; SQLSTATE: HY000

    Message: Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.

  • Error number: MY-011042; Symbol: ER_INNODB_FAILED_TO_FIND_IDX_WITH_KEY_NO; SQLSTATE: HY000

    Message: InnoDB could not find index %s key no %u for table %s through its index translation table.

  • Error number: MY-011043; Symbol: ER_INNODB_FAILED_TO_FIND_IDX; SQLSTATE: HY000

    Message: Cannot find index %s in InnoDB index translation table.

  • Error number: MY-011044; Symbol: ER_INNODB_FAILED_TO_FIND_IDX_FROM_DICT_CACHE; SQLSTATE: HY000

    Message: InnoDB could not find key no %u with name %s from dict cache for table %s.

  • Error number: MY-011045; Symbol: ER_INNODB_ACTIVE_INDEX_CHANGE_FAILED; SQLSTATE: HY000

    Message: InnoDB: change_active_index(%u) failed.

  • Error number: MY-011046; Symbol: ER_INNODB_DIFF_IN_REF_LEN; SQLSTATE: HY000

    Message: Stored ref len is %lu, but table ref len is %lu.

  • Error number: MY-011047; Symbol: ER_WRONG_TYPE_FOR_COLUMN_PREFIX_IDX_FLD; SQLSTATE: HY000

    Message: MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.

  • Error number: MY-011048; Symbol: ER_INNODB_CANNOT_CREATE_TABLE; SQLSTATE: HY000

    Message: Cannot create table %s.

  • Error number: MY-011049; Symbol: ER_INNODB_INTERNAL_INDEX; SQLSTATE: HY000

    Message: Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.

  • Error number: MY-011050; Symbol: ER_INNODB_IDX_CNT_MORE_THAN_DEFINED_IN_MYSQL; SQLSTATE: HY000

    Message: InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.

  • Error number: MY-011051; Symbol: ER_INNODB_IDX_CNT_FEWER_THAN_DEFINED_IN_MYSQL; SQLSTATE: HY000

    Message: Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?

  • Error number: MY-011052; Symbol: ER_INNODB_IDX_COLUMN_CNT_DIFF; SQLSTATE: HY000

    Message: Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?

  • Error number: MY-011053; Symbol: ER_INNODB_USE_MONITOR_GROUP_NAME; SQLSTATE: HY000

    Message: Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.

  • Error number: MY-011054; Symbol: ER_INNODB_MONITOR_DEFAULT_VALUE_NOT_DEFINED; SQLSTATE: HY000

    Message: Default value is not defined for this set option. Please specify correct counter or module name.

  • Error number: MY-011055; Symbol: ER_INNODB_MONITOR_IS_ENABLED; SQLSTATE: HY000

    Message: InnoDB: Monitor %s is already enabled.

  • Error number: MY-011056; Symbol: ER_INNODB_INVALID_MONITOR_COUNTER_NAME; SQLSTATE: HY000

    Message: Invalid monitor counter : %s.

  • Error number: MY-011057; Symbol: ER_WIN_LOAD_LIBRARY_FAILED; SQLSTATE: HY000

    Message: LoadLibrary("%s") failed: GetLastError returns %lu.

  • Error number: MY-011058; Symbol: ER_PARTITION_HANDLER_ADMIN_MSG; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-011059; Symbol: ER_RPL_AM_INIT_INFO_MSG; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-011060; Symbol: ER_DD_UPGRADE_TABLE_INTACT_ERROR; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-011061; Symbol: ER_SERVER_INIT_COMPILED_IN_COMMANDS; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-011062; Symbol: ER_MYISAM_CHECK_METHOD_ERROR; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-011063; Symbol: ER_MYISAM_CRASHED_ERROR; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-011064; Symbol: ER_WAITPID_FAILED; SQLSTATE: HY000

    Message: Unable to wait for process %lld.

  • Error number: MY-011065; Symbol: ER_FAILED_TO_FIND_MYSQLD_STATUS; SQLSTATE: HY000

    Message: Unable to determine if daemon is running: %s (rc=%d).

  • Error number: MY-011066; Symbol: ER_INNODB_ERROR_LOGGER_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011067; Symbol: ER_INNODB_ERROR_LOGGER_FATAL_MSG; SQLSTATE: HY000

    Message: [FATAL] InnoDB: %s

  • Error number: MY-011068; Symbol: ER_DEPRECATED_SYNTAX_WITH_REPLACEMENT; SQLSTATE: HY000

    Message: The syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.

  • Error number: MY-011069; Symbol: ER_DEPRECATED_SYNTAX_NO_REPLACEMENT; SQLSTATE: HY000

    Message: The syntax '%s' is deprecated and will be removed in a future release.

  • Error number: MY-011070; Symbol: ER_DEPRECATE_MSG_NO_REPLACEMENT; SQLSTATE: HY000

    Message: '%s' is deprecated and will be removed in a future release.

  • Error number: MY-011071; Symbol: ER_LOG_PRINTF_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011072; Symbol: ER_BINLOG_LOGGING_NOT_POSSIBLE; SQLSTATE: HY000

    Message: Binary logging not possible. Message: %s.

  • Error number: MY-011073; Symbol: ER_FAILED_TO_SET_PERSISTED_OPTIONS; SQLSTATE: HY000

    Message: Failed to set persisted options.

  • Error number: MY-011074; Symbol: ER_COMPONENTS_FAILED_TO_ACQUIRE_SERVICE_IMPLEMENTATION; SQLSTATE: HY000

    Message: Cannot acquire specified service implementation: '%s'.

  • Error number: MY-011075; Symbol: ER_RES_GRP_INVALID_VCPU_RANGE; SQLSTATE: HY000

    Message: Invalid VCPU range %u-%u.

  • Error number: MY-011076; Symbol: ER_RES_GRP_INVALID_VCPU_ID; SQLSTATE: HY000

    Message: Invalid cpu id %u.

  • Error number: MY-011077; Symbol: ER_ERROR_DURING_FLUSH_LOG_COMMIT_PHASE; SQLSTATE: HY000

    Message: Got error %d during FLUSH_LOGS.

  • Error number: MY-011078; Symbol: ER_DROP_DATABASE_FAILED_RMDIR_MANUALLY; SQLSTATE: HY000

    Message: Problem while dropping database. Can't remove database directory (%s). Please remove it manually.

  • Error number: MY-011080; Symbol: ER_BINLOG_MALFORMED_OR_OLD_RELAY_LOG; SQLSTATE: HY000

    Message: malformed or very old relay log which does not have FormatDescriptor.

  • Error number: MY-011081; Symbol: ER_DD_UPGRADE_VIEW_COLUMN_NAME_TOO_LONG; SQLSTATE: HY000

    Message: Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.

  • Error number: MY-011082; Symbol: ER_TABLE_NEEDS_DUMP_UPGRADE; SQLSTATE: HY000

    Message: Table upgrade required for `%s`.`%s`. Please dump/reload table to fix it!

  • Error number: MY-011083; Symbol: ER_DD_UPGRADE_FAILED_TO_UPDATE_VER_NO_IN_TABLESPACE; SQLSTATE: HY000

    Message: Error in updating version number in %s tablespace.

  • Error number: MY-011084; Symbol: ER_KEYRING_MIGRATION_FAILED; SQLSTATE: HY000

    Message: Keyring migration failed.

  • Error number: MY-011085; Symbol: ER_KEYRING_MIGRATION_SUCCESSFUL; SQLSTATE: HY000

    Message: Keyring migration successful.

  • Error number: MY-011086; Symbol: ER_RESTART_RECEIVED_INFO; SQLSTATE: HY000

    Message: Received RESTART from user %s. Restarting mysqld (Version: %s).

  • Error number: MY-011087; Symbol: ER_LCTN_CHANGED; SQLSTATE: HY000

    Message: Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').

  • Error number: MY-011088; Symbol: ER_DD_INITIALIZE; SQLSTATE: HY000

    Message: Data dictionary initializing version '%u'.

  • Error number: MY-011089; Symbol: ER_DD_RESTART; SQLSTATE: HY000

    Message: Data dictionary restarting version '%u'.

  • Error number: MY-011090; Symbol: ER_DD_UPGRADE; SQLSTATE: HY000

    Message: Data dictionary upgrading from version '%u' to '%u'.

  • Error number: MY-011091; Symbol: ER_DD_UPGRADE_OFF; SQLSTATE: HY000

    Message: Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.

  • Error number: MY-011092; Symbol: ER_DD_UPGRADE_VERSION_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Upgrading the data dictionary from dictionary version '%u' is not supported.

  • Error number: MY-011093; Symbol: ER_DD_UPGRADE_SCHEMA_UNAVAILABLE; SQLSTATE: HY000

    Message: Upgrading the data dictionary failed, temporary schema name '%s' not available.

  • Error number: MY-011094; Symbol: ER_DD_MINOR_DOWNGRADE; SQLSTATE: HY000

    Message: Data dictionary minor downgrade from version '%u' to '%u'.

  • Error number: MY-011095; Symbol: ER_DD_MINOR_DOWNGRADE_VERSION_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.

  • Error number: MY-011096; Symbol: ER_DD_NO_VERSION_FOUND; SQLSTATE: HY000

    Message: No data dictionary version number found.

  • Error number: MY-011097; Symbol: ER_THREAD_POOL_NOT_SUPPORTED_ON_PLATFORM; SQLSTATE: HY000

    Message: Thread pool not supported, requires a minimum of %s.

  • Error number: MY-011098; Symbol: ER_THREAD_POOL_SIZE_TOO_LOW; SQLSTATE: HY000

    Message: thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.

  • Error number: MY-011099; Symbol: ER_THREAD_POOL_SIZE_TOO_HIGH; SQLSTATE: HY000

    Message: thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.

  • Error number: MY-011100; Symbol: ER_THREAD_POOL_ALGORITHM_INVALID; SQLSTATE: HY000

    Message: thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.

  • Error number: MY-011101; Symbol: ER_THREAD_POOL_INVALID_STALL_LIMIT; SQLSTATE: HY000

    Message: thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.

  • Error number: MY-011102; Symbol: ER_THREAD_POOL_INVALID_PRIO_KICKUP_TIMER; SQLSTATE: HY000

    Message: Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.

  • Error number: MY-011103; Symbol: ER_THREAD_POOL_MAX_UNUSED_THREADS_INVALID; SQLSTATE: HY000

    Message: thread_pool_max_unused_threads cannot be set higher than %d.

  • Error number: MY-011104; Symbol: ER_THREAD_POOL_CON_HANDLER_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to instantiate the connection handler object.

  • Error number: MY-011105; Symbol: ER_THREAD_POOL_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to initialize thread pool plugin.

  • Error number: MY-011107; Symbol: ER_THREAD_POOL_CANNOT_SET_THREAD_SPECIFIC_DATA; SQLSTATE: HY000

    Message: Can't setup connection teardown thread-specific data.

  • Error number: MY-011108; Symbol: ER_THREAD_POOL_FAILED_TO_CREATE_CONNECT_HANDLER_THD; SQLSTATE: HY000

    Message: Creation of connect handler thread failed.

  • Error number: MY-011109; Symbol: ER_THREAD_POOL_FAILED_TO_CREATE_THD_AND_AUTH_CONN; SQLSTATE: HY000

    Message: Failed to create thd and authenticate connection.

  • Error number: MY-011110; Symbol: ER_THREAD_POOL_FAILED_PROCESS_CONNECT_EVENT; SQLSTATE: HY000

    Message: Failed to process connection event.

  • Error number: MY-011111; Symbol: ER_THREAD_POOL_FAILED_TO_CREATE_POOL; SQLSTATE: HY000

    Message: Can't create pool thread (error %d, errno: %d).

  • Error number: MY-011113; Symbol: ER_TRHEAD_POOL_LOW_LEVEL_INIT_FAILED; SQLSTATE: HY000

    Message: tp_group_low_level_init() failed.

  • Error number: MY-011114; Symbol: ER_THREAD_POOL_LOW_LEVEL_REARM_FAILED; SQLSTATE: HY000

    Message: Rearm failed even after 30 seconds, can't continue without notify socket.

  • Error number: MY-011115; Symbol: ER_THREAD_POOL_BUFFER_TOO_SMALL; SQLSTATE: HY000

    Message: %s: %s buffer is too small

  • Error number: MY-011116; Symbol: ER_MECAB_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Mecab v%s is not supported, the lowest version supported is v%s.

  • Error number: MY-011117; Symbol: ER_MECAB_NOT_VERIFIED; SQLSTATE: HY000

    Message: Mecab v%s is not verified, the highest version supported is v%s.

  • Error number: MY-011118; Symbol: ER_MECAB_CREATING_MODEL; SQLSTATE: HY000

    Message: Mecab: Trying createModel(%s).

  • Error number: MY-011119; Symbol: ER_MECAB_FAILED_TO_CREATE_MODEL; SQLSTATE: HY000

    Message: Mecab: createModel() failed: %s.

  • Error number: MY-011120; Symbol: ER_MECAB_FAILED_TO_CREATE_TRIGGER; SQLSTATE: HY000

    Message: Mecab: createTagger() failed: %s.

  • Error number: MY-011121; Symbol: ER_MECAB_UNSUPPORTED_CHARSET; SQLSTATE: HY000

    Message: Mecab: Unsupported dictionary charset %s.

  • Error number: MY-011122; Symbol: ER_MECAB_CHARSET_LOADED; SQLSTATE: HY000

    Message: Mecab: Loaded dictionary charset is %s.

  • Error number: MY-011123; Symbol: ER_MECAB_PARSE_FAILED; SQLSTATE: HY000

    Message: Mecab: parse() failed: %s.

  • Error number: MY-011124; Symbol: ER_MECAB_OOM_WHILE_PARSING_TEXT; SQLSTATE: HY000

    Message: Mecab: parse() failed: out of memory.

  • Error number: MY-011125; Symbol: ER_MECAB_CREATE_LATTICE_FAILED; SQLSTATE: HY000

    Message: Mecab: createLattice() failed: %s.

  • Error number: MY-011126; Symbol: ER_SEMISYNC_TRACE_ENTER_FUNC; SQLSTATE: HY000

    Message: ---> %s enter.

  • Error number: MY-011127; Symbol: ER_SEMISYNC_TRACE_EXIT_WITH_INT_EXIT_CODE; SQLSTATE: HY000

    Message: <--- %s exit (%d).

  • Error number: MY-011128; Symbol: ER_SEMISYNC_TRACE_EXIT_WITH_BOOL_EXIT_CODE; SQLSTATE: HY000

    Message: <--- %s exit (%s).

  • Error number: MY-011129; Symbol: ER_SEMISYNC_TRACE_EXIT; SQLSTATE: HY000

    Message: <--- %s exit.

  • Error number: MY-011130; Symbol: ER_SEMISYNC_RPL_INIT_FOR_TRX; SQLSTATE: HY000

    Message: Semi-sync replication initialized for transactions.

  • Error number: MY-011131; Symbol: ER_SEMISYNC_FAILED_TO_ALLOCATE_TRX_NODE; SQLSTATE: HY000

    Message: %s: transaction node allocation failed for: (%s, %lu).

  • Error number: MY-011132; Symbol: ER_SEMISYNC_BINLOG_WRITE_OUT_OF_ORDER; SQLSTATE: HY000

    Message: %s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).

  • Error number: MY-011133; Symbol: ER_SEMISYNC_INSERT_LOG_INFO_IN_ENTRY; SQLSTATE: HY000

    Message: %s: insert (%s, %lu) in entry(%u).

  • Error number: MY-011134; Symbol: ER_SEMISYNC_PROBE_LOG_INFO_IN_ENTRY; SQLSTATE: HY000

    Message: %s: probe (%s, %lu) in entry(%u).

  • Error number: MY-011135; Symbol: ER_SEMISYNC_CLEARED_ALL_ACTIVE_TRANSACTION_NODES; SQLSTATE: HY000

    Message: %s: cleared all nodes.

  • Error number: MY-011136; Symbol: ER_SEMISYNC_CLEARED_ACTIVE_TRANSACTION_TILL_POS; SQLSTATE: HY000

    Message: %s: cleared %d nodes back until pos (%s, %lu).

  • Error number: MY-011137; Symbol: ER_SEMISYNC_REPLY_MAGIC_NO_ERROR; SQLSTATE: HY000

    Message: Read semi-sync reply magic number error.

  • Error number: MY-011138; Symbol: ER_SEMISYNC_REPLY_PKT_LENGTH_TOO_SMALL; SQLSTATE: HY000

    Message: Read semi-sync reply length error: packet is too small.

  • Error number: MY-011139; Symbol: ER_SEMISYNC_REPLY_BINLOG_FILE_TOO_LARGE; SQLSTATE: HY000

    Message: Read semi-sync reply binlog file length too large.

  • Error number: MY-011140; Symbol: ER_SEMISYNC_SERVER_REPLY; SQLSTATE: HY000

    Message: %s: Got reply(%s, %lu) from server %u.

  • Error number: MY-011141; Symbol: ER_SEMISYNC_FUNCTION_CALLED_TWICE; SQLSTATE: HY000

    Message: %s called twice.

  • Error number: MY-011142; Symbol: ER_SEMISYNC_RPL_ENABLED_ON_SOURCE; SQLSTATE: HY000

    Message: Semi-sync replication enabled on the source.

  • Error number: MY-011143; Symbol: ER_SEMISYNC_SOURCE_OOM; SQLSTATE: HY000

    Message: Cannot allocate memory to enable semi-sync on the source.

  • Error number: MY-011144; Symbol: ER_SEMISYNC_DISABLED_ON_SOURCE; SQLSTATE: HY000

    Message: Semi-sync replication disabled on the source.

  • Error number: MY-011145; Symbol: ER_SEMISYNC_FORCED_SHUTDOWN; SQLSTATE: HY000

    Message: SEMISYNC: Forced shutdown. Some updates might not be replicated.

  • Error number: MY-011146; Symbol: ER_SEMISYNC_SOURCE_GOT_REPLY_AT_POS; SQLSTATE: HY000

    Message: %s: Got reply at (%s, %lu).

  • Error number: MY-011147; Symbol: ER_SEMISYNC_SOURCE_SIGNAL_ALL_WAITING_THREADS; SQLSTATE: HY000

    Message: %s: signal all waiting threads.

  • Error number: MY-011148; Symbol: ER_SEMISYNC_SOURCE_TRX_WAIT_POS; SQLSTATE: HY000

    Message: %s: wait pos (%s, %lu), repl(%d).

  • Error number: MY-011149; Symbol: ER_SEMISYNC_BINLOG_REPLY_IS_AHEAD; SQLSTATE: HY000

    Message: %s: Binlog reply is ahead (%s, %lu).

  • Error number: MY-011150; Symbol: ER_SEMISYNC_MOVE_BACK_WAIT_POS; SQLSTATE: HY000

    Message: %s: move back wait position (%s, %lu).

  • Error number: MY-011151; Symbol: ER_SEMISYNC_INIT_WAIT_POS; SQLSTATE: HY000

    Message: %s: init wait position (%s, %lu).

  • Error number: MY-011152; Symbol: ER_SEMISYNC_WAIT_TIME_FOR_BINLOG_SENT; SQLSTATE: HY000

    Message: %s: wait %lu ms for binlog sent (%s, %lu).

  • Error number: MY-011153; Symbol: ER_SEMISYNC_WAIT_FOR_BINLOG_TIMEDOUT; SQLSTATE: HY000

    Message: Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.

  • Error number: MY-011154; Symbol: ER_SEMISYNC_WAIT_TIME_ASSESSMENT_FOR_COMMIT_TRX_FAILED; SQLSTATE: HY000

    Message: Assessment of waiting time for commitTrx failed at wait position (%s, %lu).

  • Error number: MY-011155; Symbol: ER_SEMISYNC_RPL_SWITCHED_OFF; SQLSTATE: HY000

    Message: Semi-sync replication switched OFF.

  • Error number: MY-011156; Symbol: ER_SEMISYNC_RPL_SWITCHED_ON; SQLSTATE: HY000

    Message: Semi-sync replication switched ON at (%s, %lu).

  • Error number: MY-011157; Symbol: ER_SEMISYNC_NO_SPACE_IN_THE_PKT; SQLSTATE: HY000

    Message: No enough space in the packet for semi-sync extra header, semi-sync replication disabled.

  • Error number: MY-011158; Symbol: ER_SEMISYNC_SYNC_HEADER_UPDATE_INFO; SQLSTATE: HY000

    Message: %s: server(%d), (%s, %lu) sync(%d), repl(%d).

  • Error number: MY-011159; Symbol: ER_SEMISYNC_FAILED_TO_INSERT_TRX_NODE; SQLSTATE: HY000

    Message: Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.

  • Error number: MY-011160; Symbol: ER_SEMISYNC_TRX_SKIPPED_AT_POS; SQLSTATE: HY000

    Message: %s: Transaction skipped at (%s, %lu).

  • Error number: MY-011161; Symbol: ER_SEMISYNC_SOURCE_FAILED_ON_NET_FLUSH; SQLSTATE: HY000

    Message: Semi-sync source failed on net_flush() before waiting for replica reply.

  • Error number: MY-011162; Symbol: ER_SEMISYNC_RECEIVED_ACK_IS_SMALLER; SQLSTATE: HY000

    Message: The received ack is smaller than m_greatest_ack.

  • Error number: MY-011163; Symbol: ER_SEMISYNC_ADD_ACK_TO_SLOT; SQLSTATE: HY000

    Message: Add the ack into slot %u.

  • Error number: MY-011164; Symbol: ER_SEMISYNC_UPDATE_EXISTING_REPLICA_ACK; SQLSTATE: HY000

    Message: Update an exsiting ack in slot %u.

  • Error number: MY-011165; Symbol: ER_SEMISYNC_FAILED_TO_START_ACK_RECEIVER_THD; SQLSTATE: HY000

    Message: Failed to start semi-sync ACK receiver thread, could not create thread(errno:%d).

  • Error number: MY-011166; Symbol: ER_SEMISYNC_STARTING_ACK_RECEIVER_THD; SQLSTATE: HY000

    Message: Starting ack receiver thread.

  • Error number: MY-011167; Symbol: ER_SEMISYNC_FAILED_TO_WAIT_ON_DUMP_SOCKET; SQLSTATE: HY000

    Message: Failed to wait on semi-sync dump sockets, error: errno=%d.

  • Error number: MY-011168; Symbol: ER_SEMISYNC_STOPPING_ACK_RECEIVER_THREAD; SQLSTATE: HY000

    Message: Stopping ack receiver thread.

  • Error number: MY-011169; Symbol: ER_SEMISYNC_FAILED_REGISTER_REPLICA_TO_RECEIVER; SQLSTATE: HY000

    Message: Failed to register replica to semi-sync ACK receiver thread.

  • Error number: MY-011170; Symbol: ER_SEMISYNC_START_BINLOG_DUMP_TO_REPLICA; SQLSTATE: HY000

    Message: Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).

  • Error number: MY-011171; Symbol: ER_SEMISYNC_STOP_BINLOG_DUMP_TO_REPLICA; SQLSTATE: HY000

    Message: Stop %s binlog_dump to replica (server_id: %d).

  • Error number: MY-011172; Symbol: ER_SEMISYNC_UNREGISTER_TRX_OBSERVER_FAILED; SQLSTATE: HY000

    Message: unregister_trans_observer failed.

  • Error number: MY-011173; Symbol: ER_SEMISYNC_UNREGISTER_BINLOG_STORAGE_OBSERVER_FAILED; SQLSTATE: HY000

    Message: unregister_binlog_storage_observer failed.

  • Error number: MY-011174; Symbol: ER_SEMISYNC_UNREGISTER_BINLOG_TRANSMIT_OBSERVER_FAILED; SQLSTATE: HY000

    Message: unregister_binlog_transmit_observer failed.

  • Error number: MY-011175; Symbol: ER_SEMISYNC_UNREGISTERED_REPLICATOR; SQLSTATE: HY000

    Message: unregister_replicator OK.

  • Error number: MY-011176; Symbol: ER_SEMISYNC_SOCKET_FD_TOO_LARGE; SQLSTATE: HY000

    Message: Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).

  • Error number: MY-011177; Symbol: ER_SEMISYNC_REPLICA_REPLY; SQLSTATE: HY000

    Message: %s: reply - %d.

  • Error number: MY-011178; Symbol: ER_SEMISYNC_MISSING_MAGIC_NO_FOR_SEMISYNC_PKT; SQLSTATE: HY000

    Message: Missing magic number for semi-sync packet, packet len: %lu.

  • Error number: MY-011179; Symbol: ER_SEMISYNC_REPLICA_START; SQLSTATE: HY000

    Message: Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.

  • Error number: MY-011180; Symbol: ER_SEMISYNC_REPLICA_REPLY_WITH_BINLOG_INFO; SQLSTATE: HY000

    Message: %s: reply (%s, %lu).

  • Error number: MY-011181; Symbol: ER_SEMISYNC_REPLICA_NET_FLUSH_REPLY_FAILED; SQLSTATE: HY000

    Message: Semi-sync replica net_flush() reply failed.

  • Error number: MY-011182; Symbol: ER_SEMISYNC_REPLICA_SEND_REPLY_FAILED; SQLSTATE: HY000

    Message: Semi-sync replica send reply failed: %s (%d).

  • Error number: MY-011183; Symbol: ER_SEMISYNC_EXECUTION_FAILED_ON_SOURCE; SQLSTATE: HY000

    Message: Execution failed on source: %s; error %d

  • Error number: MY-011184; Symbol: ER_SEMISYNC_NOT_SUPPORTED_BY_SOURCE; SQLSTATE: HY000

    Message: Source server does not support semi-sync, fallback to asynchronous replication

  • Error number: MY-011185; Symbol: ER_SEMISYNC_REPLICA_SET_FAILED; SQLSTATE: HY000

    Message: Set 'rpl_semi_sync_replica=1' on source failed

  • Error number: MY-011186; Symbol: ER_SEMISYNC_FAILED_TO_STOP_ACK_RECEIVER_THD; SQLSTATE: HY000

    Message: Failed to stop ack receiver thread on my_thread_join, errno(%d).

  • Error number: MY-011187; Symbol: ER_FIREWALL_FAILED_TO_READ_FIREWALL_TABLES; SQLSTATE: HY000

    Message: Failed to read the firewall tables

  • Error number: MY-011188; Symbol: ER_FIREWALL_FAILED_TO_REG_DYNAMIC_PRIVILEGES; SQLSTATE: HY000

    Message: Failed to register dynamic privileges

  • Error number: MY-011189; Symbol: ER_FIREWALL_RECORDING_STMT_WAS_TRUNCATED; SQLSTATE: HY000

    Message: Statement was truncated and not recorded: %s

  • Error number: MY-011190; Symbol: ER_FIREWALL_RECORDING_STMT_WITHOUT_TEXT; SQLSTATE: HY000

    Message: Statement with no text was not recorded

  • Error number: MY-011191; Symbol: ER_FIREWALL_SUSPICIOUS_STMT; SQLSTATE: HY000

    Message: SUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %s

  • Error number: MY-011192; Symbol: ER_FIREWALL_ACCESS_DENIED; SQLSTATE: HY000

    Message: ACCESS DENIED for '%s'. Reason: %s Statement: %s

  • Error number: MY-011193; Symbol: ER_FIREWALL_SKIPPED_UNKNOWN_USER_MODE; SQLSTATE: HY000

    Message: Skipped unknown user mode '%s'

  • Error number: MY-011194; Symbol: ER_FIREWALL_RELOADING_CACHE; SQLSTATE: HY000

    Message: Reloading cache from disk

  • Error number: MY-011195; Symbol: ER_FIREWALL_RESET_FOR_USER; SQLSTATE: HY000

    Message: FIREWALL RESET for '%s'

  • Error number: MY-011196; Symbol: ER_FIREWALL_STATUS_FLUSHED; SQLSTATE: HY000

    Message: Counters are reset to zero

  • Error number: MY-011197; Symbol: ER_KEYRING_LOGGER_ERROR_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011198; Symbol: ER_AUDIT_LOG_FILTER_IS_NOT_INSTALLED; SQLSTATE: HY000

    Message: Audit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.

  • Error number: MY-011199; Symbol: ER_AUDIT_LOG_SWITCHING_TO_INCLUDE_LIST; SQLSTATE: HY000

    Message: Previously exclude list is used, now we start using include list, exclude list is set to NULL.

  • Error number: MY-011200; Symbol: ER_AUDIT_LOG_CANNOT_SET_LOG_POLICY_WITH_OTHER_POLICIES; SQLSTATE: HY000

    Message: Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.

  • Error number: MY-011201; Symbol: ER_AUDIT_LOG_ONLY_INCLUDE_LIST_USED; SQLSTATE: HY000

    Message: Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.

  • Error number: MY-011202; Symbol: ER_AUDIT_LOG_INDEX_MAP_CANNOT_ACCESS_DIR; SQLSTATE: HY000

    Message: Could not access '%s' directory.

  • Error number: MY-011203; Symbol: ER_AUDIT_LOG_WRITER_RENAME_FILE_FAILED; SQLSTATE: HY000

    Message: Could not rename file from '%s' to '%s'.

  • Error number: MY-011204; Symbol: ER_AUDIT_LOG_WRITER_DEST_FILE_ALREADY_EXISTS; SQLSTATE: HY000

    Message: File '%s' should not exist. It may be incomplete. The server crashed.

  • Error number: MY-011205; Symbol: ER_AUDIT_LOG_WRITER_RENAME_FILE_FAILED_REMOVE_FILE_MANUALLY; SQLSTATE: HY000

    Message: Could not rename file from '%s' to '%s'. Remove the file manually.

  • Error number: MY-011206; Symbol: ER_AUDIT_LOG_WRITER_INCOMPLETE_FILE_RENAMED; SQLSTATE: HY000

    Message: Incomplete file renamed from '%s' to '%s'.

  • Error number: MY-011207; Symbol: ER_AUDIT_LOG_WRITER_FAILED_TO_WRITE_TO_FILE; SQLSTATE: HY000

    Message: Error writing file \'%s\' (errno: %d - %s).

  • Error number: MY-011208; Symbol: ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_ENCRYPTION; SQLSTATE: HY000

    Message: Could not initialize audit log file encryption.

  • Error number: MY-011209; Symbol: ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_COMPRESSION; SQLSTATE: HY000

    Message: Could not initialize audit log file compression.

  • Error number: MY-011210; Symbol: ER_AUDIT_LOG_EC_WRITER_FAILED_TO_CREATE_FILE; SQLSTATE: HY000

    Message: Could not create '%s' file for audit logging.

  • Error number: MY-011211; Symbol: ER_AUDIT_LOG_RENAME_LOG_FILE_BEFORE_FLUSH; SQLSTATE: HY000

    Message: Audit log file (%s) must be manually renamed before audit_log_flush is set to true.

  • Error number: MY-011212; Symbol: ER_AUDIT_LOG_FILTER_RESULT_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011213; Symbol: ER_AUDIT_LOG_JSON_READER_FAILED_TO_PARSE; SQLSTATE: HY000

    Message: Error parsing JSON event. Event not accessible.

  • Error number: MY-011214; Symbol: ER_AUDIT_LOG_JSON_READER_BUF_TOO_SMALL; SQLSTATE: HY000

    Message: Buffer is too small to hold JSON event. Number of events skipped: %zu.

  • Error number: MY-011215; Symbol: ER_AUDIT_LOG_JSON_READER_FAILED_TO_OPEN_FILE; SQLSTATE: HY000

    Message: Could not open JSON file for reading. Reading next file if exists.

  • Error number: MY-011216; Symbol: ER_AUDIT_LOG_JSON_READER_FILE_PARSING_ERROR; SQLSTATE: HY000

    Message: JSON file parsing error. Reading next file if exists

  • Error number: MY-011219; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_STORE_TABLE_FLDS; SQLSTATE: HY000

    Message: Could not store field of the %s table.

  • Error number: MY-011220; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_UPDATE_TABLE; SQLSTATE: HY000

    Message: Could not update %s table.

  • Error number: MY-011221; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_INSERT_INTO_TABLE; SQLSTATE: HY000

    Message: Could not insert into %s table.

  • Error number: MY-011222; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_DELETE_FROM_TABLE; SQLSTATE: HY000

    Message: Could not delete from %s table.

  • Error number: MY-011223; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_INIT_TABLE_FOR_READ; SQLSTATE: HY000

    Message: Could not initialize %s table for reading.

  • Error number: MY-011224; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_READ_TABLE; SQLSTATE: HY000

    Message: Could not read %s table.

  • Error number: MY-011225; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_CLOSE_TABLE_AFTER_READING; SQLSTATE: HY000

    Message: Could not close %s table reading.

  • Error number: MY-011226; Symbol: ER_AUDIT_LOG_FILTER_USER_AND_HOST_CANNOT_BE_EMPTY; SQLSTATE: HY000

    Message: Both user and host columns of %s table cannot be empty.

  • Error number: MY-011227; Symbol: ER_AUDIT_LOG_FILTER_FLD_FILTERNAME_CANNOT_BE_EMPTY; SQLSTATE: HY000

    Message: Filtername column of %s table cannot be empty.

  • Error number: MY-011228; Symbol: ER_VALIDATE_PWD_DICT_FILE_NOT_SPECIFIED; SQLSTATE: HY000

    Message: Dictionary file not specified

  • Error number: MY-011229; Symbol: ER_VALIDATE_PWD_DICT_FILE_NOT_LOADED; SQLSTATE: HY000

    Message: Dictionary file not loaded

  • Error number: MY-011230; Symbol: ER_VALIDATE_PWD_DICT_FILE_TOO_BIG; SQLSTATE: HY000

    Message: Dictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loaded

  • Error number: MY-011231; Symbol: ER_VALIDATE_PWD_FAILED_TO_READ_DICT_FILE; SQLSTATE: HY000

    Message: Exception while reading the dictionary file

  • Error number: MY-011232; Symbol: ER_VALIDATE_PWD_FAILED_TO_GET_FLD_FROM_SECURITY_CTX; SQLSTATE: HY000

    Message: Can't retrieve the %s from the security context

  • Error number: MY-011233; Symbol: ER_VALIDATE_PWD_FAILED_TO_GET_SECURITY_CTX; SQLSTATE: HY000

    Message: Can't retrieve the security context

  • Error number: MY-011234; Symbol: ER_VALIDATE_PWD_LENGTH_CHANGED; SQLSTATE: HY000

    Message: Effective value of validate_password_length is changed. New value is %d

  • Error number: MY-011235; Symbol: ER_REWRITER_QUERY_ERROR_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011236; Symbol: ER_REWRITER_QUERY_FAILED; SQLSTATE: HY000

    Message: Rewritten query failed to parse:%s

  • Error number: MY-011237; Symbol: ER_XPLUGIN_STARTUP_FAILED; SQLSTATE: HY000

    Message: Startup failed with error "%s"

  • Error number: MY-011240; Symbol: ER_XPLUGIN_USING_SSL_CONF_FROM_SERVER; SQLSTATE: HY000

    Message: Using SSL configuration from MySQL Server

  • Error number: MY-011241; Symbol: ER_XPLUGIN_USING_SSL_CONF_FROM_MYSQLX; SQLSTATE: HY000

    Message: Using SSL configuration from Mysqlx Plugin

  • Error number: MY-011242; Symbol: ER_XPLUGIN_FAILED_TO_USE_SSL_CONF; SQLSTATE: HY000

    Message: Neither MySQL Server nor Mysqlx Plugin has valid SSL configuration

  • Error number: MY-011243; Symbol: ER_XPLUGIN_USING_SSL_FOR_TLS_CONNECTION; SQLSTATE: HY000

    Message: Using %s for TLS connections

  • Error number: MY-011244; Symbol: ER_XPLUGIN_REFERENCE_TO_SECURE_CONN_WITH_XPLUGIN; SQLSTATE: HY000

    Message: For more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation

  • Error number: MY-011245; Symbol: ER_XPLUGIN_ERROR_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011246; Symbol: ER_SHA_PWD_FAILED_TO_PARSE_AUTH_STRING; SQLSTATE: HY000

    Message: Failed to parse stored authentication string for %s. Please check if mysql.user table not corrupted

  • Error number: MY-011247; Symbol: ER_SHA_PWD_FAILED_TO_GENERATE_MULTI_ROUND_HASH; SQLSTATE: HY000

    Message: Error in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problem

  • Error number: MY-011248; Symbol: ER_SHA_PWD_AUTH_REQUIRES_RSA_OR_SSL; SQLSTATE: HY000

    Message: Authentication requires either RSA keys or SSL encryption

  • Error number: MY-011249; Symbol: ER_SHA_PWD_RSA_KEY_TOO_LONG; SQLSTATE: HY000

    Message: RSA key cipher length of %u is too long. Max value is %u

  • Error number: MY-011250; Symbol: ER_PLUGIN_COMMON_FAILED_TO_OPEN_FILTER_TABLES; SQLSTATE: HY000

    Message: Failed to open the %s filter tables

  • Error number: MY-011251; Symbol: ER_PLUGIN_COMMON_FAILED_TO_OPEN_TABLE; SQLSTATE: HY000

    Message: Failed to open '%s.%s' %s table

  • Error number: MY-011252; Symbol: ER_AUTH_LDAP_ERROR_LOGGER_ERROR_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011253; Symbol: ER_CONN_CONTROL_ERROR_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011254; Symbol: ER_GRP_RPL_ERROR_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011255; Symbol: ER_SHA_PWD_SALT_FOR_USER_CORRUPT; SQLSTATE: HY000

    Message: Password salt for user '%s' is corrupt

  • Error number: MY-011256; Symbol: ER_SYS_VAR_COMPONENT_OOM; SQLSTATE: HY000

    Message: Out of memory for component system variable '%s'.

  • Error number: MY-011257; Symbol: ER_SYS_VAR_COMPONENT_VARIABLE_SET_READ_ONLY; SQLSTATE: HY000

    Message: variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.

  • Error number: MY-011258; Symbol: ER_SYS_VAR_COMPONENT_UNKNOWN_VARIABLE_TYPE; SQLSTATE: HY000

    Message: Unknown variable type code 0x%x in component '%s'.

  • Error number: MY-011259; Symbol: ER_SYS_VAR_COMPONENT_FAILED_TO_PARSE_VARIABLE_OPTIONS; SQLSTATE: HY000

    Message: Parsing options for variable '%s' failed.

  • Error number: MY-011260; Symbol: ER_SYS_VAR_COMPONENT_FAILED_TO_MAKE_VARIABLE_PERSISTENT; SQLSTATE: HY000

    Message: Setting persistent options for component variable '%s' failed.

  • Error number: MY-011261; Symbol: ER_COMPONENT_FILTER_CONFUSED; SQLSTATE: HY000

    Message: The log-filter component "%s" got confused at "%s" (state: %s) ...

  • Error number: MY-011262; Symbol: ER_STOP_REPLICA_IO_THREAD_DISK_SPACE; SQLSTATE: HY000

    Message: Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.

  • Error number: MY-011263; Symbol: ER_LOG_FILE_CANNOT_OPEN; SQLSTATE: HY000

    Message: Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.

  • Error number: MY-011268; Symbol: ER_PERSIST_OPTION_STATUS; SQLSTATE: HY000

    Message: Configuring persisted options failed: "%s".

  • Error number: MY-011269; Symbol: ER_NOT_IMPLEMENTED_GET_TABLESPACE_STATISTICS; SQLSTATE: HY000

    Message: The storage engine '%s' does not provide dynamic table statistics

  • Error number: MY-011272; Symbol: ER_SSL_FIPS_MODE_ERROR; SQLSTATE: HY000

    Message: SSL fips mode error: %s

  • Error number: MY-011273; Symbol: ER_CONN_INIT_CONNECT_IGNORED; SQLSTATE: HY000

    Message: init_connect variable is ignored for user: %s host: %s due to expired password.

  • Error number: MY-011275; Symbol: ER_REWRITER_OOM; SQLSTATE: HY000

    Message: Out of memory.

  • Error number: MY-011276; Symbol: ER_REWRITER_TABLE_MALFORMED_ERROR; SQLSTATE: HY000

    Message: Wrong column count or names when loading rules.

  • Error number: MY-011277; Symbol: ER_REWRITER_LOAD_FAILED; SQLSTATE: HY000

    Message: Some rules failed to load.

  • Error number: MY-011278; Symbol: ER_REWRITER_READ_FAILED; SQLSTATE: HY000

    Message: Got error from storage engine while refreshing rewrite rules.

  • Error number: MY-011279; Symbol: ER_CONN_CONTROL_EVENT_COORDINATOR_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to initialize Connection_event_coordinator

  • Error number: MY-011280; Symbol: ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_UPDATE_FAILED; SQLSTATE: HY000

    Message: Failed to update connection delay triggered stats

  • Error number: MY-011281; Symbol: ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_RESET_FAILED; SQLSTATE: HY000

    Message: Failed to reset connection delay triggered stats

  • Error number: MY-011282; Symbol: ER_CONN_CONTROL_INVALID_CONN_DELAY_TYPE; SQLSTATE: HY000

    Message: Unexpected option type for connection delay.

  • Error number: MY-011283; Symbol: ER_CONN_CONTROL_DELAY_ACTION_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to initialize Connection_delay_action

  • Error number: MY-011284; Symbol: ER_CONN_CONTROL_FAILED_TO_SET_CONN_DELAY; SQLSTATE: HY000

    Message: Could not set %s delay for connection delay.

  • Error number: MY-011285; Symbol: ER_CONN_CONTROL_FAILED_TO_UPDATE_CONN_DELAY_HASH; SQLSTATE: HY000

    Message: Failed to update connection delay hash for account : %s

  • Error number: MY-011286; Symbol: ER_XPLUGIN_FORCE_STOP_CLIENT; SQLSTATE: HY000

    Message: %s: Force stopping client because exception occurred: %s

  • Error number: MY-011287; Symbol: ER_XPLUGIN_MAX_AUTH_ATTEMPTS_REACHED; SQLSTATE: HY000

    Message: %s.%u: Maximum number of authentication attempts reached, login failed.

  • Error number: MY-011288; Symbol: ER_XPLUGIN_BUFFER_PAGE_ALLOC_FAILED; SQLSTATE: HY000

    Message: Error allocating Buffer_page: %s

  • Error number: MY-011289; Symbol: ER_XPLUGIN_DETECTED_HANGING_CLIENTS; SQLSTATE: HY000

    Message: Detected %u hanging client(s)

  • Error number: MY-011290; Symbol: ER_XPLUGIN_FAILED_TO_ACCEPT_CLIENT; SQLSTATE: HY000

    Message: Error accepting client

  • Error number: MY-011291; Symbol: ER_XPLUGIN_FAILED_TO_SCHEDULE_CLIENT; SQLSTATE: HY000

    Message: Internal error scheduling client for execution

  • Error number: MY-011292; Symbol: ER_XPLUGIN_FAILED_TO_PREPARE_IO_INTERFACES; SQLSTATE: HY000

    Message: Preparation of I/O interfaces failed, X Protocol won't be accessible

  • Error number: MY-011293; Symbol: ER_XPLUGIN_SRV_SESSION_INIT_THREAD_FAILED; SQLSTATE: HY000

    Message: srv_session_init_thread returned error

  • Error number: MY-011294; Symbol: ER_XPLUGIN_UNABLE_TO_USE_USER_SESSION_ACCOUNT; SQLSTATE: HY000

    Message: Unable to use user mysql.session account when connecting the server for internal plugin requests.

  • Error number: MY-011295; Symbol: ER_XPLUGIN_REFERENCE_TO_USER_ACCOUNT_DOC_SECTION; SQLSTATE: HY000

    Message: For more information, please see the X Plugin User Account section in the MySQL documentation

  • Error number: MY-011296; Symbol: ER_XPLUGIN_UNEXPECTED_EXCEPTION_DISPATCHING_CMD; SQLSTATE: HY000

    Message: %s: Unexpected exception dispatching command: %s

  • Error number: MY-011297; Symbol: ER_XPLUGIN_EXCEPTION_IN_TASK_SCHEDULER; SQLSTATE: HY000

    Message: Exception in post: %s

  • Error number: MY-011298; Symbol: ER_XPLUGIN_TASK_SCHEDULING_FAILED; SQLSTATE: HY000

    Message: Internal error scheduling task

  • Error number: MY-011299; Symbol: ER_XPLUGIN_EXCEPTION_IN_EVENT_LOOP; SQLSTATE: HY000

    Message: Exception in event loop: "%s": %s

  • Error number: MY-011300; Symbol: ER_XPLUGIN_LISTENER_SETUP_FAILED; SQLSTATE: HY000

    Message: Setup of %s failed, %s

  • Error number: MY-011301; Symbol: ER_XPLUING_NET_STARTUP_FAILED; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011302; Symbol: ER_XPLUGIN_FAILED_AT_SSL_CONF; SQLSTATE: HY000

    Message: Failed at SSL configuration: "%s"

  • Error number: MY-011305; Symbol: ER_XPLUGIN_FAILED_TO_CREATE_SESSION_FOR_CONN; SQLSTATE: HY000

    Message: %s: Error creating session for connection from %s

  • Error number: MY-011306; Symbol: ER_XPLUGIN_FAILED_TO_INITIALIZE_SESSION; SQLSTATE: HY000

    Message: %s: Error initializing session for connection: %s

  • Error number: MY-011307; Symbol: ER_XPLUGIN_MESSAGE_TOO_LONG; SQLSTATE: HY000

    Message: %s: Message of size %u received, exceeding the limit of %i

  • Error number: MY-011308; Symbol: ER_XPLUGIN_UNINITIALIZED_MESSAGE; SQLSTATE: HY000

    Message: Message is not properly initialized: %s

  • Error number: MY-011309; Symbol: ER_XPLUGIN_FAILED_TO_SET_MIN_NUMBER_OF_WORKERS; SQLSTATE: HY000

    Message: Unable to set minimal number of workers to %u; actual value is %i

  • Error number: MY-011310; Symbol: ER_XPLUGIN_UNABLE_TO_ACCEPT_CONNECTION; SQLSTATE: HY000

    Message: Unable to accept connection, disconnecting client

  • Error number: MY-011311; Symbol: ER_XPLUGIN_ALL_IO_INTERFACES_DISABLED; SQLSTATE: HY000

    Message: All I/O interfaces are disabled, X Protocol won't be accessible

  • Error number: MY-011314; Symbol: ER_XPLUGIN_ERROR_READING_SOCKET; SQLSTATE: HY000

    Message: %s: Error reading from socket %s (%i)

  • Error number: MY-011315; Symbol: ER_XPLUGIN_PEER_DISCONNECTED_WHILE_READING_MSG_BODY; SQLSTATE: HY000

    Message: %s: peer disconnected while reading message body

  • Error number: MY-011316; Symbol: ER_XPLUGIN_READ_FAILED_CLOSING_CONNECTION; SQLSTATE: HY000

    Message: client_id:%s - %s while reading from socket, closing connection

  • Error number: MY-011322; Symbol: ER_XPLUGIN_LISTENER_SYS_VARIABLE_ERROR; SQLSTATE: HY000

    Message: Please see the MySQL documentation for '%s' system variables to fix the error

  • Error number: MY-011323; Symbol: ER_XPLUGIN_LISTENER_STATUS_MSG; SQLSTATE: HY000

    Message: X Plugin ready for connections. %s

  • Error number: MY-011324; Symbol: ER_XPLUGIN_RETRYING_BIND_ON_PORT; SQLSTATE: HY000

    Message: Retrying `bind()` on TCP/IP port %i

  • Error number: MY-011327; Symbol: ER_XPLUGIN_EXISTING_USER_ACCOUNT_WITH_INCOMPLETE_GRANTS; SQLSTATE: HY000

    Message: Using existing %s account for authentication. Incomplete grants will be fixed

  • Error number: MY-011332; Symbol: ER_XPLUGIN_IPv6_AVAILABLE; SQLSTATE: HY000

    Message: IPv6 is available

  • Error number: MY-011334; Symbol: ER_XPLUGIN_CLIENT_KILL_MSG; SQLSTATE: HY000

    Message: Kill client: %i %s

  • Error number: MY-011335; Symbol: ER_XPLUGIN_FAILED_TO_GET_SECURITY_CTX; SQLSTATE: HY000

    Message: Could not get security context for session

  • Error number: MY-011337; Symbol: ER_XPLUGIN_FAILED_TO_CLOSE_SQL_SESSION; SQLSTATE: HY000

    Message: Error closing SQL session

  • Error number: MY-011338; Symbol: ER_XPLUGIN_FAILED_TO_EXECUTE_ADMIN_CMD; SQLSTATE: HY000

    Message: Error executing admin command %s: %s

  • Error number: MY-011339; Symbol: ER_XPLUGIN_EMPTY_ADMIN_CMD; SQLSTATE: HY000

    Message: Error executing empty admin command

  • Error number: MY-011340; Symbol: ER_XPLUGIN_FAILED_TO_GET_SYS_VAR; SQLSTATE: HY000

    Message: Unable to retrieve system variable \'%s\'

  • Error number: MY-011341; Symbol: ER_XPLUGIN_FAILED_TO_GET_CREATION_STMT; SQLSTATE: HY000

    Message: Unable to get creation stmt for collection \'%s\'; query result size: %lu

  • Error number: MY-011342; Symbol: ER_XPLUGIN_FAILED_TO_GET_ENGINE_INFO; SQLSTATE: HY000

    Message: Unable to get engine info for collection \'%s\'; creation stmt: %s

  • Error number: MY-011345; Symbol: ER_XPLUGIN_FAILED_TO_SET_SO_REUSEADDR_FLAG; SQLSTATE: HY000

    Message: Failed to set SO_REUSEADDR flag (error: %d).

  • Error number: MY-011346; Symbol: ER_XPLUGIN_FAILED_TO_OPEN_INTERNAL_SESSION; SQLSTATE: HY000

    Message: Could not open internal MySQL session

  • Error number: MY-011347; Symbol: ER_XPLUGIN_FAILED_TO_SWITCH_CONTEXT; SQLSTATE: HY000

    Message: Unable to switch context to user %s

  • Error number: MY-011348; Symbol: ER_XPLUGIN_FAILED_TO_UNREGISTER_UDF; SQLSTATE: HY000

    Message: Can\'t unregister \'%s\' user defined function

  • Error number: MY-011351; Symbol: ER_XPLUGIN_FAILED_TO_RESET_IPV6_V6ONLY_FLAG; SQLSTATE: HY000

    Message: Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.

  • Error number: MY-011352; Symbol: ER_KEYRING_INVALID_KEY_TYPE; SQLSTATE: HY000

    Message: Invalid key type

  • Error number: MY-011353; Symbol: ER_KEYRING_INVALID_KEY_LENGTH; SQLSTATE: HY000

    Message: Invalid key length for given block cipher

  • Error number: MY-011358; Symbol: ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_INVALID_KEY; SQLSTATE: HY000

    Message: Error while %s key: invalid key_type

  • Error number: MY-011359; Symbol: ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_EMPTY_KEY_ID; SQLSTATE: HY000

    Message: Error while %s key: key_id cannot be empty

  • Error number: MY-011360; Symbol: ER_KEYRING_OPERATION_FAILED_DUE_TO_INTERNAL_ERROR; SQLSTATE: HY000

    Message: Failed to %s due to internal exception inside %s plugin

  • Error number: MY-011361; Symbol: ER_KEYRING_INCORRECT_FILE; SQLSTATE: HY000

    Message: Incorrect Keyring file

  • Error number: MY-011362; Symbol: ER_KEYRING_FOUND_MALFORMED_BACKUP_FILE; SQLSTATE: HY000

    Message: Found malformed keyring backup file - removing it

  • Error number: MY-011363; Symbol: ER_KEYRING_FAILED_TO_RESTORE_FROM_BACKUP_FILE; SQLSTATE: HY000

    Message: Error while restoring keyring from backup file cannot overwrite keyring with backup

  • Error number: MY-011364; Symbol: ER_KEYRING_FAILED_TO_FLUSH_KEYRING_TO_FILE; SQLSTATE: HY000

    Message: Error while flushing in-memory keyring into keyring file

  • Error number: MY-011365; Symbol: ER_KEYRING_FAILED_TO_GET_FILE_STAT; SQLSTATE: HY000

    Message: Error while reading stat for %s.Please check if file %s was not removed. OS returned this error: %s

  • Error number: MY-011366; Symbol: ER_KEYRING_FAILED_TO_REMOVE_FILE; SQLSTATE: HY000

    Message: Could not remove file %s OS retuned this error: %s

  • Error number: MY-011367; Symbol: ER_KEYRING_FAILED_TO_TRUNCATE_FILE; SQLSTATE: HY000

    Message: Could not truncate file %s. OS retuned this error: %s

  • Error number: MY-011368; Symbol: ER_KEYRING_UNKNOWN_ERROR; SQLSTATE: HY000

    Message: Unknown error %d

  • Error number: MY-011370; Symbol: ER_KEYRING_FILE_IO_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011371; Symbol: ER_KEYRING_FAILED_TO_LOAD_KEYRING_CONTENT; SQLSTATE: HY000

    Message: Error while loading keyring content. The keyring might be malformed

  • Error number: MY-011372; Symbol: ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING; SQLSTATE: HY000

    Message: Could not flush keys to keyring

  • Error number: MY-011373; Symbol: ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING_BACKUP; SQLSTATE: HY000

    Message: Could not flush keys to keyring's backup

  • Error number: MY-011374; Symbol: ER_KEYRING_KEY_FETCH_FAILED_DUE_TO_EMPTY_KEY_ID; SQLSTATE: HY000

    Message: Error while fetching key: key_id cannot be empty

  • Error number: MY-011375; Symbol: ER_KEYRING_FAILED_TO_REMOVE_KEY_DUE_TO_EMPTY_ID; SQLSTATE: HY000

    Message: Error while removing key: key_id cannot be empty

  • Error number: MY-011376; Symbol: ER_KEYRING_OKV_INCORRECT_KEY_VAULT_CONFIGURED; SQLSTATE: HY000

    Message: For keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materials

  • Error number: MY-011377; Symbol: ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INCORRECT_CONF; SQLSTATE: HY000

    Message: keyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.

  • Error number: MY-011378; Symbol: ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INTERNAL_ERROR; SQLSTATE: HY000

    Message: keyring_okv initialization failure due to internal exception inside the plugin

  • Error number: MY-011379; Symbol: ER_KEYRING_OKV_INVALID_KEY_TYPE; SQLSTATE: HY000

    Message: Invalid key type

  • Error number: MY-011380; Symbol: ER_KEYRING_OKV_INVALID_KEY_LENGTH_FOR_CIPHER; SQLSTATE: HY000

    Message: Invalid key length for given block cipher

  • Error number: MY-011381; Symbol: ER_KEYRING_OKV_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR; SQLSTATE: HY000

    Message: Failed to generate a key due to internal exception inside keyring_okv plugin

  • Error number: MY-011382; Symbol: ER_KEYRING_OKV_FAILED_TO_FIND_SERVER_ENTRY; SQLSTATE: HY000

    Message: Could not find entry for server in configuration file %s

  • Error number: MY-011383; Symbol: ER_KEYRING_OKV_FAILED_TO_FIND_STANDBY_SERVER_ENTRY; SQLSTATE: HY000

    Message: Could not find entry for standby server in configuration file %s

  • Error number: MY-011384; Symbol: ER_KEYRING_OKV_FAILED_TO_PARSE_CONF_FILE; SQLSTATE: HY000

    Message: Could not parse the %s file provided

  • Error number: MY-011385; Symbol: ER_KEYRING_OKV_FAILED_TO_LOAD_KEY_UID; SQLSTATE: HY000

    Message: Could not load keys' uids from the OKV server

  • Error number: MY-011386; Symbol: ER_KEYRING_OKV_FAILED_TO_INIT_SSL_LAYER; SQLSTATE: HY000

    Message: Could not initialize ssl layer

  • Error number: MY-011387; Symbol: ER_KEYRING_OKV_FAILED_TO_INIT_CLIENT; SQLSTATE: HY000

    Message: Could not initialize OKV client

  • Error number: MY-011388; Symbol: ER_KEYRING_OKV_CONNECTION_TO_SERVER_FAILED; SQLSTATE: HY000

    Message: Could not connect to the OKV server

  • Error number: MY-011389; Symbol: ER_KEYRING_OKV_FAILED_TO_REMOVE_KEY; SQLSTATE: HY000

    Message: Could not remove the key

  • Error number: MY-011390; Symbol: ER_KEYRING_OKV_FAILED_TO_ADD_ATTRIBUTE; SQLSTATE: HY000

    Message: Could not add attribute, attribute_name=%s attribute value=%s

  • Error number: MY-011391; Symbol: ER_KEYRING_OKV_FAILED_TO_GENERATE_KEY; SQLSTATE: HY000

    Message: Could not generate the key.

  • Error number: MY-011392; Symbol: ER_KEYRING_OKV_FAILED_TO_STORE_KEY; SQLSTATE: HY000

    Message: Could not store the key.

  • Error number: MY-011393; Symbol: ER_KEYRING_OKV_FAILED_TO_ACTIVATE_KEYS; SQLSTATE: HY000

    Message: Could not activate the key.

  • Error number: MY-011394; Symbol: ER_KEYRING_OKV_FAILED_TO_FETCH_KEY; SQLSTATE: HY000

    Message: Could not fetch generated key

  • Error number: MY-011395; Symbol: ER_KEYRING_OKV_FAILED_TO_STORE_OR_GENERATE_KEY; SQLSTATE: HY000

    Message: Could not store/generate the key - failed to set key attribute x-key-ready

  • Error number: MY-011396; Symbol: ER_KEYRING_OKV_FAILED_TO_RETRIEVE_KEY_SIGNATURE; SQLSTATE: HY000

    Message: Could not retrieve key signature from custom attributes

  • Error number: MY-011397; Symbol: ER_KEYRING_OKV_FAILED_TO_RETRIEVE_KEY; SQLSTATE: HY000

    Message: Could not retrieve key from OKV

  • Error number: MY-011398; Symbol: ER_KEYRING_OKV_FAILED_TO_LOAD_SSL_TRUST_STORE; SQLSTATE: HY000

    Message: Error loading trust store

  • Error number: MY-011399; Symbol: ER_KEYRING_OKV_FAILED_TO_SET_CERTIFICATE_FILE; SQLSTATE: HY000

    Message: Error setting the certificate file.

  • Error number: MY-011400; Symbol: ER_KEYRING_OKV_FAILED_TO_SET_KEY_FILE; SQLSTATE: HY000

    Message: Error setting the key file.

  • Error number: MY-011401; Symbol: ER_KEYRING_OKV_KEY_MISMATCH; SQLSTATE: HY000

    Message: Private key does not match the certificate public key

  • Error number: MY-011415; Symbol: ER_KEYRING_AWS_FAILED_TO_SET_CMK_ID; SQLSTATE: HY000

    Message: keyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.

  • Error number: MY-011416; Symbol: ER_KEYRING_AWS_FAILED_TO_SET_REGION; SQLSTATE: HY000

    Message: keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.

  • Error number: MY-011417; Symbol: ER_KEYRING_AWS_FAILED_TO_OPEN_CONF_FILE; SQLSTATE: HY000

    Message: Could not open keyring_aws configuration file: %s. OS returned this error: %s

  • Error number: MY-011418; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_ID_FROM_CONF_FILE; SQLSTATE: HY000

    Message: Could not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %s

  • Error number: MY-011419; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_FROM_CONF_FILE; SQLSTATE: HY000

    Message: Could not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %s

  • Error number: MY-011420; Symbol: ER_KEYRING_AWS_INVALID_CONF_FILE_PATH; SQLSTATE: HY000

    Message: Path to keyring aws configuration file cannot be empty

  • Error number: MY-011421; Symbol: ER_KEYRING_AWS_INVALID_DATA_FILE_PATH; SQLSTATE: HY000

    Message: Path to keyring_aws storage file cannot be empty.

  • Error number: MY-011422; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DIR; SQLSTATE: HY000

    Message: Unable to create/access keyring directory.

  • Error number: MY-011423; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DATA_FILE; SQLSTATE: HY000

    Message: Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.

  • Error number: MY-011424; Symbol: ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_INTERNAL_ERROR; SQLSTATE: HY000

    Message: keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:

  • Error number: MY-011425; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_DATA_FILE; SQLSTATE: HY000

    Message: Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Server

  • Error number: MY-011426; Symbol: ER_KEYRING_AWS_CMK_ID_NOT_SET; SQLSTATE: HY000

    Message: keyring_aws_cmk_id has to be set

  • Error number: MY-011427; Symbol: ER_KEYRING_AWS_FAILED_TO_GET_KMS_CREDENTIAL_FROM_CONF_FILE; SQLSTATE: HY000

    Message: Could not get AWS KMS credentials from the configuration file

  • Error number: MY-011428; Symbol: ER_KEYRING_AWS_INIT_FAILURE; SQLSTATE: HY000

    Message: keyring_aws initialization failure.

  • Error number: MY-011429; Symbol: ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_PLUGIN_INTERNAL_ERROR; SQLSTATE: HY000

    Message: keyring_aws initialization failure due to internal exception inside the plugin

  • Error number: MY-011430; Symbol: ER_KEYRING_AWS_INVALID_KEY_LENGTH_FOR_CIPHER; SQLSTATE: HY000

    Message: Invalid key length for given block cipher

  • Error number: MY-011431; Symbol: ER_KEYRING_AWS_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR; SQLSTATE: HY000

    Message: Failed to generate a key due to internal exception inside keyring_file plugin

  • Error number: MY-011432; Symbol: ER_KEYRING_AWS_INCORRECT_FILE; SQLSTATE: HY000

    Message: Incorrect Keyring file

  • Error number: MY-011433; Symbol: ER_KEYRING_AWS_FOUND_MALFORMED_BACKUP_FILE; SQLSTATE: HY000

    Message: Found malformed keyring backup file - removing it

  • Error number: MY-011434; Symbol: ER_KEYRING_AWS_FAILED_TO_RESTORE_FROM_BACKUP_FILE; SQLSTATE: HY000

    Message: Error while restoring keyring from backup file cannot overwrite keyring with backup

  • Error number: MY-011435; Symbol: ER_KEYRING_AWS_FAILED_TO_FLUSH_KEYRING_TO_FILE; SQLSTATE: HY000

    Message: Error while flushing in-memory keyring into keyring file

  • Error number: MY-011436; Symbol: ER_KEYRING_AWS_INCORRECT_REGION; SQLSTATE: HY000

    Message: Wrong region

  • Error number: MY-011437; Symbol: ER_KEYRING_AWS_FAILED_TO_CONNECT_KMS; SQLSTATE: HY000

    Message: Could not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %s

  • Error number: MY-011438; Symbol: ER_KEYRING_AWS_FAILED_TO_GENERATE_NEW_KEY; SQLSTATE: HY000

    Message: Could not generate a new key. AWS KMS returned this error: %s

  • Error number: MY-011439; Symbol: ER_KEYRING_AWS_FAILED_TO_ENCRYPT_KEY; SQLSTATE: HY000

    Message: Could not encrypt key. AWS KMS returned this error: %s

  • Error number: MY-011440; Symbol: ER_KEYRING_AWS_FAILED_TO_RE_ENCRYPT_KEY; SQLSTATE: HY000

    Message: Could not re-encrypt key. AWS KMS returned this error: %s

  • Error number: MY-011441; Symbol: ER_KEYRING_AWS_FAILED_TO_DECRYPT_KEY; SQLSTATE: HY000

    Message: Could not decrypt key. AWS KMS returned this error: %s

  • Error number: MY-011442; Symbol: ER_KEYRING_AWS_FAILED_TO_ROTATE_CMK; SQLSTATE: HY000

    Message: Could not rotate the CMK. AWS KMS returned this error: %s

  • Error number: MY-011443; Symbol: ER_GRP_RPL_GTID_ALREADY_USED; SQLSTATE: HY000

    Message: The requested GTID '%s:%lld' was already used, the transaction will rollback.

  • Error number: MY-011444; Symbol: ER_GRP_RPL_APPLIER_THD_KILLED; SQLSTATE: HY000

    Message: The group replication applier thread was killed.

  • Error number: MY-011445; Symbol: ER_GRP_RPL_EVENT_HANDLING_ERROR; SQLSTATE: HY000

    Message: Error at event handling! Got error: %d.

  • Error number: MY-011446; Symbol: ER_GRP_RPL_ERROR_GTID_EXECUTION_INFO; SQLSTATE: HY000

    Message: Error when extracting group GTID execution information, some recovery operations may face future issues.

  • Error number: MY-011448; Symbol: ER_GRP_RPL_CREATE_APPLIER_CACHE_ERROR; SQLSTATE: HY000

    Message: Failed to create group replication pipeline applier cache!

  • Error number: MY-011449; Symbol: ER_GRP_RPL_UNBLOCK_WAITING_THD; SQLSTATE: HY000

    Message: Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.

  • Error number: MY-011450; Symbol: ER_GRP_RPL_APPLIER_PIPELINE_NOT_DISPOSED; SQLSTATE: HY000

    Message: The group replication applier pipeline was not properly disposed. Check the error log for further info.

  • Error number: MY-011451; Symbol: ER_GRP_RPL_APPLIER_THD_EXECUTION_ABORTED; SQLSTATE: HY000

    Message: The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.

  • Error number: MY-011452; Symbol: ER_GRP_RPL_APPLIER_EXECUTION_FATAL_ERROR; SQLSTATE: HY000

    Message: Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.

  • Error number: MY-011453; Symbol: ER_GRP_RPL_ERROR_STOPPING_CHANNELS; SQLSTATE: HY000

    Message: Error stopping all replication channels while server was leaving the group. %s

  • Error number: MY-011454; Symbol: ER_GRP_RPL_ERROR_SENDING_SINGLE_PRIMARY_MSSG; SQLSTATE: HY000

    Message: Error sending single primary message informing that primary did apply relay logs.

  • Error number: MY-011457; Symbol: ER_GRP_RPL_BROADCAST_COMMIT_TRANS_MSSG_FAILED; SQLSTATE: HY000

    Message: Broadcast of committed transactions message failed.

  • Error number: MY-011458; Symbol: ER_GRP_RPL_GROUP_NAME_PARSE_ERROR; SQLSTATE: HY000

    Message: Unable to parse the group_replication_group_name during the Certification module initialization.

  • Error number: MY-011459; Symbol: ER_GRP_RPL_ADD_GRPSID_TO_GRPGTIDSID_MAP_ERROR; SQLSTATE: HY000

    Message: Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.

  • Error number: MY-011460; Symbol: ER_GRP_RPL_UPDATE_GRPGTID_EXECUTED_ERROR; SQLSTATE: HY000

    Message: Error updating group_gtid_executed GITD set during the Certification module initialization.

  • Error number: MY-011461; Symbol: ER_GRP_RPL_DONOR_TRANS_INFO_ERROR; SQLSTATE: HY000

    Message: Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.

  • Error number: MY-011462; Symbol: ER_GRP_RPL_SERVER_CONN_ERROR; SQLSTATE: HY000

    Message: Error when establishing a server connection during the Certification module initialization.

  • Error number: MY-011463; Symbol: ER_GRP_RPL_ERROR_FETCHING_GTID_EXECUTED_SET; SQLSTATE: HY000

    Message: Error when extracting this member GTID executed set. Certification module can't be properly initialized.

  • Error number: MY-011464; Symbol: ER_GRP_RPL_ADD_GTID_TO_GRPGTID_EXECUTED_ERROR; SQLSTATE: HY000

    Message: Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.

  • Error number: MY-011465; Symbol: ER_GRP_RPL_ERROR_FETCHING_GTID_SET; SQLSTATE: HY000

    Message: Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.

  • Error number: MY-011466; Symbol: ER_GRP_RPL_ADD_RETRIEVED_SET_TO_GRP_GTID_EXECUTED_ERROR; SQLSTATE: HY000

    Message: Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.

  • Error number: MY-011467; Symbol: ER_GRP_RPL_CERTIFICATION_INITIALIZATION_FAILURE; SQLSTATE: HY000

    Message: Error during Certification module initialization.

  • Error number: MY-011468; Symbol: ER_GRP_RPL_UPDATE_LAST_CONFLICT_FREE_TRANS_ERROR; SQLSTATE: HY000

    Message: Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.

  • Error number: MY-011469; Symbol: ER_GRP_RPL_UPDATE_TRANS_SNAPSHOT_REF_VER_ERROR; SQLSTATE: HY000

    Message: Error updating transaction snapshot version reference for internal storage.

  • Error number: MY-011472; Symbol: ER_GRP_RPL_CANT_GENERATE_GTID; SQLSTATE: HY000

    Message: Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.

  • Error number: MY-011473; Symbol: ER_GRP_RPL_INVALID_GTID_SET; SQLSTATE: HY000

    Message: Invalid stable transactions set.

  • Error number: MY-011474; Symbol: ER_GRP_RPL_UPDATE_GTID_SET_ERROR; SQLSTATE: HY000

    Message: Error updating stable transactions set.

  • Error number: MY-011475; Symbol: ER_GRP_RPL_RECEIVED_SET_MISSING_GTIDS; SQLSTATE: HY000

    Message: There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.

  • Error number: MY-011477; Symbol: ER_GRP_RPL_NULL_PACKET; SQLSTATE: HY000

    Message: Null packet on certifier's queue.

  • Error number: MY-011478; Symbol: ER_GRP_RPL_CANT_READ_GTID; SQLSTATE: HY000

    Message: Error reading GTIDs from the message.

  • Error number: MY-011479; Symbol: ER_GRP_RPL_PROCESS_GTID_SET_ERROR; SQLSTATE: HY000

    Message: Error processing stable transactions set.

  • Error number: MY-011480; Symbol: ER_GRP_RPL_PROCESS_INTERSECTION_GTID_SET_ERROR; SQLSTATE: HY000

    Message: Error processing intersection of stable transactions set.

  • Error number: MY-011481; Symbol: ER_GRP_RPL_SET_STABLE_TRANS_ERROR; SQLSTATE: HY000

    Message: Error setting stable transactions set.

  • Error number: MY-011482; Symbol: ER_GRP_RPL_CANT_READ_GRP_GTID_EXTRACTED; SQLSTATE: HY000

    Message: Error reading group_gtid_extracted from the View_change_log_event.

  • Error number: MY-011483; Symbol: ER_GRP_RPL_CANT_READ_WRITE_SET_ITEM; SQLSTATE: HY000

    Message: Error reading the write set item '%s' from the View_change_log_event.

  • Error number: MY-011484; Symbol: ER_GRP_RPL_INIT_CERTIFICATION_INFO_FAILURE; SQLSTATE: HY000

    Message: Error during certification_info initialization.

  • Error number: MY-011485; Symbol: ER_GRP_RPL_CONFLICT_DETECTION_DISABLED; SQLSTATE: HY000

    Message: Primary had applied all relay logs, disabled conflict detection.

  • Error number: MY-011486; Symbol: ER_GRP_RPL_MSG_DISCARDED; SQLSTATE: HY000

    Message: Message received while the plugin is not ready, message discarded.

  • Error number: MY-011487; Symbol: ER_GRP_RPL_MISSING_GRP_RPL_APPLIER; SQLSTATE: HY000

    Message: Message received without a proper group replication applier.

  • Error number: MY-011488; Symbol: ER_GRP_RPL_CERTIFIER_MSSG_PROCESS_ERROR; SQLSTATE: HY000

    Message: Error processing message in Certifier.

  • Error number: MY-011489; Symbol: ER_GRP_RPL_SRV_NOT_ONLINE; SQLSTATE: HY000

    Message: This server was not declared online since it is on status %s.

  • Error number: MY-011490; Symbol: ER_GRP_RPL_SRV_ONLINE; SQLSTATE: HY000

    Message: This server was declared online within the replication group.

  • Error number: MY-011491; Symbol: ER_GRP_RPL_DISABLE_SRV_READ_MODE_RESTRICTED; SQLSTATE: HY000

    Message: When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.

  • Error number: MY-011492; Symbol: ER_GRP_RPL_MEM_ONLINE; SQLSTATE: HY000

    Message: The member with address %s:%u was declared online within the replication group.

  • Error number: MY-011493; Symbol: ER_GRP_RPL_MEM_UNREACHABLE; SQLSTATE: HY000

    Message: Member with address %s:%u has become unreachable.

  • Error number: MY-011494; Symbol: ER_GRP_RPL_MEM_REACHABLE; SQLSTATE: HY000

    Message: Member with address %s:%u is reachable again.

  • Error number: MY-011495; Symbol: ER_GRP_RPL_SRV_BLOCKED; SQLSTATE: HY000

    Message: This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.

  • Error number: MY-011496; Symbol: ER_GRP_RPL_SRV_BLOCKED_FOR_SECS; SQLSTATE: HY000

    Message: This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.

  • Error number: MY-011497; Symbol: ER_GRP_RPL_CHANGE_GRP_MEM_NOT_PROCESSED; SQLSTATE: HY000

    Message: A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.

  • Error number: MY-011498; Symbol: ER_GRP_RPL_MEMBER_CONTACT_RESTORED; SQLSTATE: HY000

    Message: The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.

  • Error number: MY-011499; Symbol: ER_GRP_RPL_MEMBER_REMOVED; SQLSTATE: HY000

    Message: Members removed from the group: %s

  • Error number: MY-011500; Symbol: ER_GRP_RPL_PRIMARY_MEMBER_LEFT_GRP; SQLSTATE: HY000

    Message: Primary server with address %s left the group. Electing new Primary.

  • Error number: MY-011501; Symbol: ER_GRP_RPL_MEMBER_ADDED; SQLSTATE: HY000

    Message: Members joined the group: %s

  • Error number: MY-011502; Symbol: ER_GRP_RPL_MEMBER_EXIT_PLUGIN_ERROR; SQLSTATE: HY000

    Message: There was a previous plugin error while the member joined the group. The member will now exit the group.

  • Error number: MY-011503; Symbol: ER_GRP_RPL_MEMBER_CHANGE; SQLSTATE: HY000

    Message: Group membership changed to %s on view %s.

  • Error number: MY-011504; Symbol: ER_GRP_RPL_MEMBER_LEFT_GRP; SQLSTATE: HY000

    Message: Group membership changed: This member has left the group.

  • Error number: MY-011505; Symbol: ER_GRP_RPL_MEMBER_EXPELLED; SQLSTATE: HY000

    Message: Member was expelled from the group due to network failures, changing member status to ERROR.

  • Error number: MY-011506; Symbol: ER_GRP_RPL_SESSION_OPEN_FAILED; SQLSTATE: HY000

    Message: Unable to open session to (re)set read only mode. Skipping.

  • Error number: MY-011507; Symbol: ER_GRP_RPL_NEW_PRIMARY_ELECTED; SQLSTATE: HY000

    Message: A new primary with address %s:%u was elected. %s

  • Error number: MY-011508; Symbol: ER_GRP_RPL_DISABLE_READ_ONLY_FAILED; SQLSTATE: HY000

    Message: Unable to disable super read only flag. Try to disable it manually

  • Error number: MY-011509; Symbol: ER_GRP_RPL_ENABLE_READ_ONLY_FAILED; SQLSTATE: HY000

    Message: Unable to set super read only flag. Try to set it manually.

  • Error number: MY-011510; Symbol: ER_GRP_RPL_SRV_PRIMARY_MEM; SQLSTATE: HY000

    Message: This server is working as primary member.

  • Error number: MY-011511; Symbol: ER_GRP_RPL_SRV_SECONDARY_MEM; SQLSTATE: HY000

    Message: This server is working as secondary member with primary member address %s:%u.

  • Error number: MY-011512; Symbol: ER_GRP_RPL_NO_SUITABLE_PRIMARY_MEM; SQLSTATE: HY000

    Message: Unable to set any member as primary. No suitable candidate.

  • Error number: MY-011513; Symbol: ER_GRP_RPL_SUPER_READ_ONLY_ACTIVATE_ERROR; SQLSTATE: HY000

    Message: Error when activating super_read_only mode on start. The member will now exit the group.

  • Error number: MY-011514; Symbol: ER_GRP_RPL_EXCEEDS_AUTO_INC_VALUE; SQLSTATE: HY000

    Message: Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.

  • Error number: MY-011515; Symbol: ER_GRP_RPL_DATA_NOT_PROVIDED_BY_MEM; SQLSTATE: HY000

    Message: Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.

  • Error number: MY-011516; Symbol: ER_GRP_RPL_MEMBER_ALREADY_EXISTS; SQLSTATE: HY000

    Message: There is already a member with server_uuid %s. The member will now exit the group.

  • Error number: MY-011518; Symbol: ER_GRP_RPL_GTID_EXECUTED_EXTRACT_ERROR; SQLSTATE: HY000

    Message: Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.

  • Error number: MY-011519; Symbol: ER_GRP_RPL_GTID_SET_EXTRACT_ERROR; SQLSTATE: HY000

    Message: Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.

  • Error number: MY-011520; Symbol: ER_GRP_RPL_START_FAILED; SQLSTATE: HY000

    Message: The START GROUP_REPLICATION command failed since the group already has 9 members.

  • Error number: MY-011521; Symbol: ER_GRP_RPL_MEMBER_VER_INCOMPATIBLE; SQLSTATE: HY000

    Message: Member version is incompatible with the group.

  • Error number: MY-011522; Symbol: ER_GRP_RPL_TRANS_NOT_PRESENT_IN_GRP; SQLSTATE: HY000

    Message: The member contains transactions not present in the group. The member will now exit the group.

  • Error number: MY-011523; Symbol: ER_GRP_RPL_TRANS_GREATER_THAN_GRP; SQLSTATE: HY000

    Message: It was not possible to assess if the member has more transactions than the group. The member will now exit the group.

  • Error number: MY-011524; Symbol: ER_GRP_RPL_MEMBER_VERSION_LOWER_THAN_GRP; SQLSTATE: HY000

    Message: Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.

  • Error number: MY-011525; Symbol: ER_GRP_RPL_LOCAL_GTID_SETS_PROCESS_ERROR; SQLSTATE: HY000

    Message: Error processing local GTID sets when comparing this member transactions against the group.

  • Error number: MY-011526; Symbol: ER_GRP_RPL_MEMBER_TRANS_GREATER_THAN_GRP; SQLSTATE: HY000

    Message: This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %s

  • Error number: MY-011527; Symbol: ER_GRP_RPL_BLOCK_SIZE_DIFF_FROM_GRP; SQLSTATE: HY000

    Message: The member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.

  • Error number: MY-011528; Symbol: ER_GRP_RPL_TRANS_WRITE_SET_EXTRACT_DIFF_FROM_GRP; SQLSTATE: HY000

    Message: The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.

  • Error number: MY-011529; Symbol: ER_GRP_RPL_MEMBER_CFG_INCOMPATIBLE_WITH_GRP_CFG; SQLSTATE: HY000

    Message: The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).

  • Error number: MY-011530; Symbol: ER_GRP_RPL_MEMBER_STOP_RPL_CHANNELS_ERROR; SQLSTATE: HY000

    Message: Error stopping all replication channels while server was leaving the group. %s

  • Error number: MY-011531; Symbol: ER_GRP_RPL_PURGE_APPLIER_LOGS; SQLSTATE: HY000

    Message: Detected previous RESET BINARY LOGS AND GTIDS invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.

  • Error number: MY-011532; Symbol: ER_GRP_RPL_RESET_APPLIER_MODULE_LOGS_ERROR; SQLSTATE: HY000

    Message: Unknown error occurred while resetting applier's module logs.

  • Error number: MY-011533; Symbol: ER_GRP_RPL_APPLIER_THD_SETUP_ERROR; SQLSTATE: HY000

    Message: Failed to setup the group replication applier thread.

  • Error number: MY-011534; Symbol: ER_GRP_RPL_APPLIER_THD_START_ERROR; SQLSTATE: HY000

    Message: Error while starting the group replication applier thread

  • Error number: MY-011535; Symbol: ER_GRP_RPL_APPLIER_THD_STOP_ERROR; SQLSTATE: HY000

    Message: Failed to stop the group replication applier thread.

  • Error number: MY-011536; Symbol: ER_GRP_RPL_FETCH_TRANS_DATA_FAILED; SQLSTATE: HY000

    Message: Failed to fetch transaction data containing required transaction info for applier

  • Error number: MY-011537; Symbol: ER_GRP_RPL_REPLICA_IO_THD_PRIMARY_UNKNOWN; SQLSTATE: HY000

    Message: Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.

  • Error number: MY-011538; Symbol: ER_GRP_RPL_SALVE_IO_THD_ON_SECONDARY_MEMBER; SQLSTATE: HY000

    Message: Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.

  • Error number: MY-011539; Symbol: ER_GRP_RPL_REPLICA_SQL_THD_PRIMARY_UNKNOWN; SQLSTATE: HY000

    Message: Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.

  • Error number: MY-011540; Symbol: ER_GRP_RPL_REPLICA_SQL_THD_ON_SECONDARY_MEMBER; SQLSTATE: HY000

    Message: Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.

  • Error number: MY-011541; Symbol: ER_GRP_RPL_NEEDS_INNODB_TABLE; SQLSTATE: HY000

    Message: Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.

  • Error number: MY-011542; Symbol: ER_GRP_RPL_PRIMARY_KEY_NOT_DEFINED; SQLSTATE: HY000

    Message: Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.

  • Error number: MY-011543; Symbol: ER_GRP_RPL_FK_WITH_CASCADE_UNSUPPORTED; SQLSTATE: HY000

    Message: Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.

  • Error number: MY-011544; Symbol: ER_GRP_RPL_AUTO_INC_RESET; SQLSTATE: HY000

    Message: group_replication_auto_increment_increment is reset to %lu

  • Error number: MY-011545; Symbol: ER_GRP_RPL_AUTO_INC_OFFSET_RESET; SQLSTATE: HY000

    Message: auto_increment_offset is reset to %lu

  • Error number: MY-011546; Symbol: ER_GRP_RPL_AUTO_INC_SET; SQLSTATE: HY000

    Message: group_replication_auto_increment_increment is set to %lu

  • Error number: MY-011547; Symbol: ER_GRP_RPL_AUTO_INC_OFFSET_SET; SQLSTATE: HY000

    Message: auto_increment_offset is set to %lu

  • Error number: MY-011548; Symbol: ER_GRP_RPL_FETCH_TRANS_CONTEXT_FAILED; SQLSTATE: HY000

    Message: Failed to fetch transaction context containing required transaction info for certification

  • Error number: MY-011549; Symbol: ER_GRP_RPL_FETCH_FORMAT_DESC_LOG_EVENT_FAILED; SQLSTATE: HY000

    Message: Failed to fetch Format_description_log_event containing required server info for applier

  • Error number: MY-011550; Symbol: ER_GRP_RPL_FETCH_TRANS_CONTEXT_LOG_EVENT_FAILED; SQLSTATE: HY000

    Message: Failed to fetch Transaction_context_log_event containing required transaction info for certification

  • Error number: MY-011551; Symbol: ER_GRP_RPL_FETCH_SNAPSHOT_VERSION_FAILED; SQLSTATE: HY000

    Message: Failed to read snapshot version from transaction context event required for certification

  • Error number: MY-011552; Symbol: ER_GRP_RPL_FETCH_GTID_LOG_EVENT_FAILED; SQLSTATE: HY000

    Message: Failed to fetch Gtid_log_event containing required transaction info for certification

  • Error number: MY-011553; Symbol: ER_GRP_RPL_UPDATE_SERV_CERTIFICATE_FAILED; SQLSTATE: HY000

    Message: Unable to update certification result on server side, thread_id: %lu

  • Error number: MY-011554; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITH_LOCAL_GTID_FAILED; SQLSTATE: HY000

    Message: Unable to add gtid information to the group_gtid_executed set when gtid was provided for local transactions

  • Error number: MY-011555; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_LOCAL_GTID_FAILED; SQLSTATE: HY000

    Message: Unable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactions

  • Error number: MY-011556; Symbol: ER_GRP_RPL_NOTIFY_CERTIFICATION_OUTCOME_FAILED; SQLSTATE: HY000

    Message: Failed to notify certification outcome

  • Error number: MY-011557; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITH_REMOTE_GTID_FAILED; SQLSTATE: HY000

    Message: Unable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactions

  • Error number: MY-011558; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_REMOTE_GTID_FAILED; SQLSTATE: HY000

    Message: Unable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactions

  • Error number: MY-011559; Symbol: ER_GRP_RPL_FETCH_VIEW_CHANGE_LOG_EVENT_FAILED; SQLSTATE: HY000

    Message: Failed to fetch View_change_log_event containing required info for certification

  • Error number: MY-011562; Symbol: ER_GRP_RPL_FETCH_LOG_EVENT_FAILED; SQLSTATE: HY000

    Message: Failed to fetch Log_event containing required server info for applier

  • Error number: MY-011563; Symbol: ER_GRP_RPL_START_GRP_RPL_FAILED; SQLSTATE: HY000

    Message: Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.

  • Error number: MY-011564; Symbol: ER_GRP_RPL_CONN_INTERNAL_PLUGIN_FAIL; SQLSTATE: HY000

    Message: Failed to establish an internal server connection to execute plugin operations

  • Error number: MY-011565; Symbol: ER_GRP_RPL_SUPER_READ_ON; SQLSTATE: HY000

    Message: Setting super_read_only=ON.

  • Error number: MY-011566; Symbol: ER_GRP_RPL_SUPER_READ_OFF; SQLSTATE: HY000

    Message: Setting super_read_only=OFF.

  • Error number: MY-011567; Symbol: ER_GRP_RPL_KILLED_SESSION_ID; SQLSTATE: HY000

    Message: killed session id: %d status: %d

  • Error number: MY-011568; Symbol: ER_GRP_RPL_KILLED_FAILED_ID; SQLSTATE: HY000

    Message: killed failed id: %d failed: %d

  • Error number: MY-011569; Symbol: ER_GRP_RPL_INTERNAL_QUERY; SQLSTATE: HY000

    Message: Internal query: %s result in error. Error number: %ld

  • Error number: MY-011570; Symbol: ER_GRP_RPL_COPY_FROM_EMPTY_STRING; SQLSTATE: HY000

    Message: Error copying from empty string

  • Error number: MY-011571; Symbol: ER_GRP_RPL_QUERY_FAIL; SQLSTATE: HY000

    Message: Query execution resulted in failure. errno: %d

  • Error number: MY-011572; Symbol: ER_GRP_RPL_CREATE_SESSION_UNABLE; SQLSTATE: HY000

    Message: Unable to create a session for executing the queries on the server

  • Error number: MY-011573; Symbol: ER_GRP_RPL_MEMBER_NOT_FOUND; SQLSTATE: HY000

    Message: The member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connection

  • Error number: MY-011574; Symbol: ER_GRP_RPL_MAXIMUM_CONNECTION_RETRIES_REACHED; SQLSTATE: HY000

    Message: Maximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.

  • Error number: MY-011575; Symbol: ER_GRP_RPL_ALL_DONORS_LEFT_ABORT_RECOVERY; SQLSTATE: HY000

    Message: All donors left. Aborting group replication incremental recovery.

  • Error number: MY-011576; Symbol: ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_DONOR; SQLSTATE: HY000

    Message: Establishing group recovery connection with a possible donor. Attempt %d/%d

  • Error number: MY-011577; Symbol: ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_ANOTHER_DONOR; SQLSTATE: HY000

    Message: Retrying group recovery connection with another donor. Attempt %d/%d

  • Error number: MY-011578; Symbol: ER_GRP_RPL_NO_VALID_DONOR; SQLSTATE: HY000

    Message: No valid donors exist in the group, retrying

  • Error number: MY-011579; Symbol: ER_GRP_RPL_CONFIG_RECOVERY; SQLSTATE: HY000

    Message: Error when configuring the asynchronous recovery channel connection to the donor.

  • Error number: MY-011580; Symbol: ER_GRP_RPL_ESTABLISHING_CONN_GRP_REC_DONOR; SQLSTATE: HY000

    Message: Establishing connection to a group replication recovery donor %s at %s port: %d.

  • Error number: MY-011581; Symbol: ER_GRP_RPL_CREATE_GRP_RPL_REC_CHANNEL; SQLSTATE: HY000

    Message: Error while creating the group replication recovery channel with donor %s at %s port: %d.

  • Error number: MY-011582; Symbol: ER_GRP_RPL_DONOR_SERVER_CONN; SQLSTATE: HY000

    Message: There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.

  • Error number: MY-011583; Symbol: ER_GRP_RPL_CHECK_STATUS_TABLE; SQLSTATE: HY000

    Message: For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.

  • Error number: MY-011584; Symbol: ER_GRP_RPL_STARTING_GRP_REC; SQLSTATE: HY000

    Message: Error while starting the group replication incremental recovery receiver/applier threads

  • Error number: MY-011585; Symbol: ER_GRP_RPL_DONOR_CONN_TERMINATION; SQLSTATE: HY000

    Message: Terminating existing group replication donor connection and purging the corresponding logs.

  • Error number: MY-011586; Symbol: ER_GRP_RPL_STOPPING_GRP_REC; SQLSTATE: HY000

    Message: Error when stopping the group replication incremental recovery's donor connection

  • Error number: MY-011587; Symbol: ER_GRP_RPL_PURGE_REC; SQLSTATE: HY000

    Message: Error when purging the group replication recovery's relay logs

  • Error number: MY-011588; Symbol: ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_APPLIER; SQLSTATE: HY000

    Message: Unable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.

  • Error number: MY-011589; Symbol: ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_FAILOVER; SQLSTATE: HY000

    Message: Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.

  • Error number: MY-011590; Symbol: ER_GRP_RPL_FAILED_TO_NOTIFY_GRP_MEMBERSHIP_EVENT; SQLSTATE: HY000

    Message: Unexpected error when notifying an internal component named %s regarding a group membership event.

  • Error number: MY-011591; Symbol: ER_GRP_RPL_FAILED_TO_BROADCAST_GRP_MEMBERSHIP_NOTIFICATION; SQLSTATE: HY000

    Message: An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!

  • Error number: MY-011592; Symbol: ER_GRP_RPL_FAILED_TO_BROADCAST_MEMBER_STATUS_NOTIFICATION; SQLSTATE: HY000

    Message: An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!

  • Error number: MY-011593; Symbol: ER_GRP_RPL_OOM_FAILED_TO_GENERATE_IDENTIFICATION_HASH; SQLSTATE: HY000

    Message: No memory to generate write identification hash

  • Error number: MY-011594; Symbol: ER_GRP_RPL_WRITE_IDENT_HASH_BASE64_ENCODING_FAILED; SQLSTATE: HY000

    Message: Base 64 encoding of the write identification hash failed

  • Error number: MY-011595; Symbol: ER_GRP_RPL_INVALID_BINLOG_FORMAT; SQLSTATE: HY000

    Message: Binlog format should be ROW for Group Replication

  • Error number: MY-011598; Symbol: ER_GRP_RPL_UNSUPPORTED_TRANS_ISOLATION; SQLSTATE: HY000

    Message: Transaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group Replication

  • Error number: MY-011599; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_STOPPING; SQLSTATE: HY000

    Message: Transaction cannot be executed while Group Replication is stopping.

  • Error number: MY-011600; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_RECOVERING; SQLSTATE: HY000

    Message: Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.

  • Error number: MY-011601; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_ERROR_STATE; SQLSTATE: HY000

    Message: Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin

  • Error number: MY-011602; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_OFFLINE_MODE; SQLSTATE: HY000

    Message: Transaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the plugin

  • Error number: MY-011603; Symbol: ER_GRP_RPL_MULTIPLE_CACHE_TYPE_NOT_SUPPORTED_FOR_SESSION; SQLSTATE: HY000

    Message: We can only use one cache type at a time on session %u

  • Error number: MY-011604; Symbol: ER_GRP_RPL_FAILED_TO_REINIT_BINLOG_CACHE_FOR_READ; SQLSTATE: HY000

    Message: Failed to reinit binlog cache log for read on session %u

  • Error number: MY-011605; Symbol: ER_GRP_RPL_FAILED_TO_CREATE_TRANS_CONTEXT; SQLSTATE: HY000

    Message: Failed to create the context of the current transaction on session %u

  • Error number: MY-011606; Symbol: ER_GRP_RPL_FAILED_TO_EXTRACT_TRANS_WRITE_SET; SQLSTATE: HY000

    Message: Failed to extract the set of items written during the execution of the current transaction on session %u

  • Error number: MY-011607; Symbol: ER_GRP_RPL_FAILED_TO_GATHER_TRANS_WRITE_SET; SQLSTATE: HY000

    Message: Failed to gather the set of items written during the execution of the current transaction on session %u

  • Error number: MY-011608; Symbol: ER_GRP_RPL_TRANS_SIZE_EXCEEDS_LIMIT; SQLSTATE: HY000

    Message: Error on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.

  • Error number: MY-011611; Symbol: ER_GRP_RPL_WRITE_TO_TRANSACTION_MESSAGE_FAILED; SQLSTATE: HY000

    Message: Error while writing to transaction message on session %u

  • Error number: MY-011612; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_OUTCOME_NOTIFICTION; SQLSTATE: HY000

    Message: Unable to register for getting notifications regarding the outcome of the transaction on session %u

  • Error number: MY-011613; Symbol: ER_GRP_RPL_MSG_TOO_LONG_BROADCASTING_TRANS_FAILED; SQLSTATE: HY000

    Message: Error broadcasting transaction to the group on session %u. Message is too big.

  • Error number: MY-011614; Symbol: ER_GRP_RPL_BROADCASTING_TRANS_TO_GRP_FAILED; SQLSTATE: HY000

    Message: Error while broadcasting the transaction to the group on session %u

  • Error number: MY-011615; Symbol: ER_GRP_RPL_ERROR_WHILE_WAITING_FOR_CONFLICT_DETECTION; SQLSTATE: HY000

    Message: Error while waiting for conflict detection procedure to finish on session %u

  • Error number: MY-011620; Symbol: ER_GRP_RPL_FATAL_REC_PROCESS; SQLSTATE: HY000

    Message: Fatal error during the incremental recovery process of Group Replication. The server will leave the group.

  • Error number: MY-011622; Symbol: ER_GRP_RPL_UNABLE_TO_EVALUATE_APPLIER_STATUS; SQLSTATE: HY000

    Message: Unable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.

  • Error number: MY-011623; Symbol: ER_GRP_RPL_ONLY_ONE_SERVER_ALIVE; SQLSTATE: HY000

    Message: Only one server alive. Declaring this server as online within the replication group

  • Error number: MY-011624; Symbol: ER_GRP_RPL_CERTIFICATION_REC_PROCESS; SQLSTATE: HY000

    Message: Error when processing certification information in the incremental recovery process

  • Error number: MY-011625; Symbol: ER_GRP_RPL_UNABLE_TO_ENSURE_EXECUTION_REC; SQLSTATE: HY000

    Message: Unable to ensure the execution of group transactions received during recovery.

  • Error number: MY-011626; Symbol: ER_GRP_RPL_WHILE_SENDING_MSG_REC; SQLSTATE: HY000

    Message: Error while sending message in the group replication incremental recovery process.

  • Error number: MY-011628; Symbol: ER_GRP_RPL_READ_UNABLE_FOR_READ_ONLY_SUPER_READ_ONLY; SQLSTATE: HY000

    Message: Unable to read the server values for the read_only and super_read_only variables.

  • Error number: MY-011629; Symbol: ER_GRP_RPL_UNABLE_TO_RESET_SERVER_READ_MODE; SQLSTATE: HY000

    Message: Unable to reset the server read mode settings. Try to reset them manually.

  • Error number: MY-011630; Symbol: ER_GRP_RPL_UNABLE_TO_CERTIFY_PLUGIN_TRANS; SQLSTATE: HY000

    Message: Due to a plugin error, some transactions were unable to be certified and will now rollback.

  • Error number: MY-011631; Symbol: ER_GRP_RPL_UNBLOCK_CERTIFIED_TRANS; SQLSTATE: HY000

    Message: Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the service

  • Error number: MY-011633; Symbol: ER_GRP_RPL_FAILED_TO_START_WITH_INVALID_SERVER_ID; SQLSTATE: HY000

    Message: Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.

  • Error number: MY-011634; Symbol: ER_GRP_RPL_FORCE_MEMBERS_MUST_BE_EMPTY; SQLSTATE: HY000

    Message: group_replication_force_members must be empty on group start. Current value: '%s'

  • Error number: MY-011635; Symbol: ER_GRP_RPL_PLUGIN_STRUCT_INIT_NOT_POSSIBLE_ON_SERVER_START; SQLSTATE: HY000

    Message: It was not possible to guarantee the initialization of plugin structures on server start

  • Error number: MY-011636; Symbol: ER_GRP_RPL_FAILED_TO_ENABLE_SUPER_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Could not enable the server read only mode and guarantee a safe recovery execution

  • Error number: MY-011637; Symbol: ER_GRP_RPL_FAILED_TO_INIT_COMMUNICATION_ENGINE; SQLSTATE: HY000

    Message: Error on group communication engine initialization

  • Error number: MY-011638; Symbol: ER_GRP_RPL_FAILED_TO_START_ON_SECONDARY_WITH_ASYNC_CHANNELS; SQLSTATE: HY000

    Message: Can't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.

  • Error number: MY-011639; Symbol: ER_GRP_RPL_FAILED_TO_START_COMMUNICATION_ENGINE; SQLSTATE: HY000

    Message: Error on group communication engine start

  • Error number: MY-011640; Symbol: ER_GRP_RPL_TIMEOUT_ON_VIEW_AFTER_JOINING_GRP; SQLSTATE: HY000

    Message: Timeout on wait for view after joining group

  • Error number: MY-011641; Symbol: ER_GRP_RPL_FAILED_TO_CALL_GRP_COMMUNICATION_INTERFACE; SQLSTATE: HY000

    Message: Error calling group communication interfaces

  • Error number: MY-011642; Symbol: ER_GRP_RPL_MEMBER_SERVER_UUID_IS_INCOMPATIBLE_WITH_GRP; SQLSTATE: HY000

    Message: Member server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.

  • Error number: MY-011643; Symbol: ER_GRP_RPL_MEMBER_CONF_INFO; SQLSTATE: HY000

    Message: Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";

  • Error number: MY-011644; Symbol: ER_GRP_RPL_FAILED_TO_CONFIRM_IF_SERVER_LEFT_GRP; SQLSTATE: HY000

    Message: Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.

  • Error number: MY-011645; Symbol: ER_GRP_RPL_SERVER_IS_ALREADY_LEAVING; SQLSTATE: HY000

    Message: Skipping leave operation: concurrent attempt to leave the group is on-going.

  • Error number: MY-011646; Symbol: ER_GRP_RPL_SERVER_ALREADY_LEFT; SQLSTATE: HY000

    Message: Skipping leave operation: member already left the group.

  • Error number: MY-011647; Symbol: ER_GRP_RPL_WAITING_FOR_VIEW_UPDATE; SQLSTATE: HY000

    Message: Going to wait for view modification

  • Error number: MY-011648; Symbol: ER_GRP_RPL_TIMEOUT_RECEIVING_VIEW_CHANGE_ON_SHUTDOWN; SQLSTATE: HY000

    Message: While leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more details

  • Error number: MY-011649; Symbol: ER_GRP_RPL_REQUESTING_NON_MEMBER_SERVER_TO_LEAVE; SQLSTATE: HY000

    Message: Requesting to leave the group despite of not being a member

  • Error number: MY-011650; Symbol: ER_GRP_RPL_IS_STOPPING; SQLSTATE: HY000

    Message: Plugin 'group_replication' is stopping.

  • Error number: MY-011651; Symbol: ER_GRP_RPL_IS_STOPPED; SQLSTATE: HY000

    Message: Plugin 'group_replication' has been stopped.

  • Error number: MY-011652; Symbol: ER_GRP_RPL_FAILED_TO_ENABLE_READ_ONLY_MODE_ON_SHUTDOWN; SQLSTATE: HY000

    Message: On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.

  • Error number: MY-011653; Symbol: ER_GRP_RPL_RECOVERY_MODULE_TERMINATION_TIMED_OUT_ON_SHUTDOWN; SQLSTATE: HY000

    Message: On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more details

  • Error number: MY-011654; Symbol: ER_GRP_RPL_APPLIER_TERMINATION_TIMED_OUT_ON_SHUTDOWN; SQLSTATE: HY000

    Message: On shutdown there was a timeout on the Group Replication applier termination.

  • Error number: MY-011655; Symbol: ER_GRP_RPL_FAILED_TO_SHUTDOWN_REGISTRY_MODULE; SQLSTATE: HY000

    Message: Unexpected failure while shutting down registry module!

  • Error number: MY-011656; Symbol: ER_GRP_RPL_FAILED_TO_INIT_HANDLER; SQLSTATE: HY000

    Message: Failure during Group Replication handler initialization

  • Error number: MY-011657; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_SERVER_STATE_OBSERVER; SQLSTATE: HY000

    Message: Failure when registering the server state observers

  • Error number: MY-011658; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_STATE_OBSERVER; SQLSTATE: HY000

    Message: Failure when registering the transactions state observers

  • Error number: MY-011659; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_BINLOG_STATE_OBSERVER; SQLSTATE: HY000

    Message: Failure when registering the binlog state observers

  • Error number: MY-011660; Symbol: ER_GRP_RPL_FAILED_TO_START_ON_BOOT; SQLSTATE: HY000

    Message: Unable to start Group Replication on boot

  • Error number: MY-011661; Symbol: ER_GRP_RPL_FAILED_TO_STOP_ON_PLUGIN_UNINSTALL; SQLSTATE: HY000

    Message: Failure when stopping Group Replication on plugin uninstall

  • Error number: MY-011662; Symbol: ER_GRP_RPL_FAILED_TO_UNREGISTER_SERVER_STATE_OBSERVER; SQLSTATE: HY000

    Message: Failure when unregistering the server state observers

  • Error number: MY-011663; Symbol: ER_GRP_RPL_FAILED_TO_UNREGISTER_TRANS_STATE_OBSERVER; SQLSTATE: HY000

    Message: Failure when unregistering the transactions state observers

  • Error number: MY-011664; Symbol: ER_GRP_RPL_FAILED_TO_UNREGISTER_BINLOG_STATE_OBSERVER; SQLSTATE: HY000

    Message: Failure when unregistering the binlog state observers

  • Error number: MY-011665; Symbol: ER_GRP_RPL_ALL_OBSERVERS_UNREGISTERED; SQLSTATE: HY000

    Message: All Group Replication server observers have been successfully unregistered

  • Error number: MY-011666; Symbol: ER_GRP_RPL_FAILED_TO_PARSE_THE_GRP_NAME; SQLSTATE: HY000

    Message: Unable to parse the group_replication_group_name.

  • Error number: MY-011667; Symbol: ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_GRP; SQLSTATE: HY000

    Message: Unable to parse the group_replication_group_name.

  • Error number: MY-011668; Symbol: ER_GRP_RPL_APPLIER_NOT_STARTED_DUE_TO_RUNNING_PREV_SHUTDOWN; SQLSTATE: HY000

    Message: Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.

  • Error number: MY-011669; Symbol: ER_GRP_RPL_FAILED_TO_INIT_APPLIER_MODULE; SQLSTATE: HY000

    Message: Unable to initialize the Group Replication applier module.

  • Error number: MY-011670; Symbol: ER_GRP_RPL_APPLIER_INITIALIZED; SQLSTATE: HY000

    Message: Group Replication applier module successfully initialized!

  • Error number: MY-011671; Symbol: ER_GRP_RPL_COMMUNICATION_SSL_CONF_INFO; SQLSTATE: HY000

    Message: Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"

  • Error number: MY-011672; Symbol: ER_GRP_RPL_ABORTS_AS_SSL_NOT_SUPPORTED_BY_MYSQLD; SQLSTATE: HY000

    Message: MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abort

  • Error number: MY-011673; Symbol: ER_GRP_RPL_SSL_DISABLED; SQLSTATE: HY000

    Message: Group communication SSL configuration: group_replication_ssl_mode: "%s"

  • Error number: MY-011674; Symbol: ER_GRP_RPL_UNABLE_TO_INIT_COMMUNICATION_ENGINE; SQLSTATE: HY000

    Message: Unable to initialize the group communication engine

  • Error number: MY-011675; Symbol: ER_GRP_RPL_BINLOG_DISABLED; SQLSTATE: HY000

    Message: Binlog must be enabled for Group Replication

  • Error number: MY-011676; Symbol: ER_GRP_RPL_GTID_MODE_OFF; SQLSTATE: HY000

    Message: Gtid mode should be ON for Group Replication

  • Error number: MY-011677; Symbol: ER_GRP_RPL_LOG_REPLICA_UPDATES_NOT_SET; SQLSTATE: HY000

    Message: LOG_REPLICA_UPDATES should be ON for Group Replication

  • Error number: MY-011679; Symbol: ER_GRP_RPL_APPLIER_METADATA_REPO_MUST_BE_TABLE; SQLSTATE: HY000

    Message: Applier metadata repository must be set to TABLE

  • Error number: MY-011680; Symbol: ER_GRP_RPL_CONNECTION_METADATA_REPO_MUST_BE_TABLE; SQLSTATE: HY000

    Message: Connection metadata repository must be set to TABLE.

  • Error number: MY-011681; Symbol: ER_GRP_RPL_INCORRECT_TYPE_SET_FOR_PARALLEL_APPLIER; SQLSTATE: HY000

    Message: In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.

  • Error number: MY-011682; Symbol: ER_GRP_RPL_REPLICA_PRESERVE_COMMIT_ORDER_NOT_SET; SQLSTATE: HY000

    Message: Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.

  • Error number: MY-011683; Symbol: ER_GRP_RPL_SINGLE_PRIM_MODE_NOT_ALLOWED_WITH_UPDATE_EVERYWHERE; SQLSTATE: HY000

    Message: It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.

  • Error number: MY-011684; Symbol: ER_GRP_RPL_MODULE_TERMINATE_ERROR; SQLSTATE: HY000

    Message: error_message: %s

  • Error number: MY-011685; Symbol: ER_GRP_RPL_GRP_NAME_OPTION_MANDATORY; SQLSTATE: HY000

    Message: The group_replication_group_name option is mandatory

  • Error number: MY-011686; Symbol: ER_GRP_RPL_GRP_NAME_IS_TOO_LONG; SQLSTATE: HY000

    Message: The group_replication_group_name '%s' is not a valid UUID, its length is too big

  • Error number: MY-011687; Symbol: ER_GRP_RPL_GRP_NAME_IS_NOT_VALID_UUID; SQLSTATE: HY000

    Message: The group_replication_group_name '%s' is not a valid UUID

  • Error number: MY-011688; Symbol: ER_GRP_RPL_FLOW_CTRL_MIN_QUOTA_GREATER_THAN_MAX_QUOTA; SQLSTATE: HY000

    Message: group_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quota

  • Error number: MY-011689; Symbol: ER_GRP_RPL_FLOW_CTRL_MIN_RECOVERY_QUOTA_GREATER_THAN_MAX_QUOTA; SQLSTATE: HY000

    Message: group_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quota

  • Error number: MY-011690; Symbol: ER_GRP_RPL_FLOW_CTRL_MAX_QUOTA_SMALLER_THAN_MIN_QUOTAS; SQLSTATE: HY000

    Message: group_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quota

  • Error number: MY-011691; Symbol: ER_GRP_RPL_INVALID_SSL_RECOVERY_STRING; SQLSTATE: HY000

    Message: The given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limit

  • Error number: MY-011694; Symbol: ER_GRP_RPL_GRP_COMMUNICATION_INIT_WITH_CONF; SQLSTATE: HY000

    Message: Initialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'

  • Error number: MY-011695; Symbol: ER_GRP_RPL_UNKNOWN_GRP_RPL_APPLIER_PIPELINE_REQUESTED; SQLSTATE: HY000

    Message: Unknown group replication applier pipeline requested

  • Error number: MY-011696; Symbol: ER_GRP_RPL_FAILED_TO_BOOTSTRAP_EVENT_HANDLING_INFRASTRUCTURE; SQLSTATE: HY000

    Message: Unable to bootstrap group replication event handling infrastructure. Unknown handler type: %d

  • Error number: MY-011697; Symbol: ER_GRP_RPL_APPLIER_HANDLER_NOT_INITIALIZED; SQLSTATE: HY000

    Message: One of the group replication applier handlers is null due to an initialization error

  • Error number: MY-011698; Symbol: ER_GRP_RPL_APPLIER_HANDLER_IS_IN_USE; SQLSTATE: HY000

    Message: A group replication applier handler, marked as unique, is already in use.

  • Error number: MY-011699; Symbol: ER_GRP_RPL_APPLIER_HANDLER_ROLE_IS_IN_USE; SQLSTATE: HY000

    Message: A group replication applier handler role, that was marked as unique, is already in use.

  • Error number: MY-011700; Symbol: ER_GRP_RPL_FAILED_TO_INIT_APPLIER_HANDLER; SQLSTATE: HY000

    Message: Error on group replication applier handler initialization

  • Error number: MY-011701; Symbol: ER_GRP_RPL_SQL_SERVICE_FAILED_TO_INIT_SESSION_THREAD; SQLSTATE: HY000

    Message: Error when initializing a session thread for internal server connection.

  • Error number: MY-011702; Symbol: ER_GRP_RPL_SQL_SERVICE_COMM_SESSION_NOT_INITIALIZED; SQLSTATE: HY000

    Message: Error running internal SQL query: %s. The internal server communication session is not initialized

  • Error number: MY-011703; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_SESSION_KILLED; SQLSTATE: HY000

    Message: Error running internal SQL query: %s. The internal server session was killed or server is shutting down.

  • Error number: MY-011704; Symbol: ER_GRP_RPL_SQL_SERVICE_FAILED_TO_RUN_SQL_QUERY; SQLSTATE: HY000

    Message: Error running internal SQL query: %s. Got internal SQL error: %s(%d)

  • Error number: MY-011705; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_INTERNAL_FAILURE; SQLSTATE: HY000

    Message: Error running internal SQL query: %s. Internal failure.

  • Error number: MY-011706; Symbol: ER_GRP_RPL_SQL_SERVICE_RETRIES_EXCEEDED_ON_SESSION_STATE; SQLSTATE: HY000

    Message: Error, maximum number of retries exceeded when waiting for the internal server session state to be operating

  • Error number: MY-011707; Symbol: ER_GRP_RPL_SQL_SERVICE_FAILED_TO_FETCH_SECURITY_CTX; SQLSTATE: HY000

    Message: Error when trying to fetch security context when contacting the server for internal plugin requests.

  • Error number: MY-011708; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_ACCESS_DENIED_FOR_USER; SQLSTATE: HY000

    Message: There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.

  • Error number: MY-011709; Symbol: ER_GRP_RPL_SQL_SERVICE_MAX_CONN_ERROR_FROM_SERVER; SQLSTATE: HY000

    Message: Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.

  • Error number: MY-011710; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_ERROR_ON_CONN; SQLSTATE: HY000

    Message: Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %s

  • Error number: MY-011711; Symbol: ER_GRP_RPL_UNREACHABLE_MAJORITY_TIMEOUT_FOR_MEMBER; SQLSTATE: HY000

    Message: This member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.

  • Error number: MY-011712; Symbol: ER_GRP_RPL_SERVER_SET_TO_READ_ONLY_DUE_TO_ERRORS; SQLSTATE: HY000

    Message: The server was automatically set into read only mode after an error was detected.

  • Error number: MY-011713; Symbol: ER_GRP_RPL_GMS_LISTENER_FAILED_TO_LOG_NOTIFICATION; SQLSTATE: HY000

    Message: Unable to log notification to table (errno: %lu) (res: %d)! Message: %s

  • Error number: MY-011714; Symbol: ER_GRP_RPL_GRP_COMMUNICATION_ENG_INIT_FAILED; SQLSTATE: HY000

    Message: Failure in group communication engine '%s' initialization

  • Error number: MY-011715; Symbol: ER_GRP_RPL_SET_GRP_COMMUNICATION_ENG_LOGGER_FAILED; SQLSTATE: HY000

    Message: Unable to set the group communication engine logger

  • Error number: MY-011716; Symbol: ER_GRP_RPL_DEBUG_OPTIONS; SQLSTATE: HY000

    Message: Current debug options are: '%s'.

  • Error number: MY-011717; Symbol: ER_GRP_RPL_INVALID_DEBUG_OPTIONS; SQLSTATE: HY000

    Message: Some debug options in '%s' are not valid.

  • Error number: MY-011718; Symbol: ER_GRP_RPL_EXIT_GRP_GCS_ERROR; SQLSTATE: HY000

    Message: Error calling group communication interfaces while trying to leave the group

  • Error number: MY-011719; Symbol: ER_GRP_RPL_GRP_MEMBER_OFFLINE; SQLSTATE: HY000

    Message: Member is not ONLINE, it is not possible to force a new group membership

  • Error number: MY-011720; Symbol: ER_GRP_RPL_GCS_INTERFACE_ERROR; SQLSTATE: HY000

    Message: Error calling group communication interfaces

  • Error number: MY-011721; Symbol: ER_GRP_RPL_FORCE_MEMBER_VALUE_SET_ERROR; SQLSTATE: HY000

    Message: Error setting group_replication_force_members value '%s' on group communication interfaces

  • Error number: MY-011722; Symbol: ER_GRP_RPL_FORCE_MEMBER_VALUE_SET; SQLSTATE: HY000

    Message: The group_replication_force_members value '%s' was set in the group communication interfaces

  • Error number: MY-011723; Symbol: ER_GRP_RPL_FORCE_MEMBER_VALUE_TIME_OUT; SQLSTATE: HY000

    Message: Timeout on wait for view after setting group_replication_force_members value '%s' into group communication interfaces

  • Error number: MY-011724; Symbol: ER_GRP_RPL_BROADCAST_COMMIT_MSSG_TOO_BIG; SQLSTATE: HY000

    Message: Broadcast of committed transactions message failed. Message is too big.

  • Error number: MY-011725; Symbol: ER_GRP_RPL_SEND_STATS_ERROR; SQLSTATE: HY000

    Message: Error while sending stats message

  • Error number: MY-011726; Symbol: ER_GRP_RPL_MEMBER_STATS_INFO; SQLSTATE: HY000

    Message: Flow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%d

  • Error number: MY-011727; Symbol: ER_GRP_RPL_FLOW_CONTROL_STATS; SQLSTATE: HY000

    Message: Flow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lld

  • Error number: MY-011728; Symbol: ER_GRP_RPL_UNABLE_TO_CONVERT_PACKET_TO_EVENT; SQLSTATE: HY000

    Message: Unable to convert a packet into an event on the applier. Error: %s

  • Error number: MY-011729; Symbol: ER_GRP_RPL_PIPELINE_CREATE_FAILED; SQLSTATE: HY000

    Message: Failed to create group replication pipeline cache.

  • Error number: MY-011730; Symbol: ER_GRP_RPL_PIPELINE_REINIT_FAILED_WRITE; SQLSTATE: HY000

    Message: Failed to reinit group replication pipeline cache for write.

  • Error number: MY-011731; Symbol: ER_GRP_RPL_UNABLE_TO_CONVERT_EVENT_TO_PACKET; SQLSTATE: HY000

    Message: Unable to convert the event into a packet on the applier. Error: %s

  • Error number: MY-011732; Symbol: ER_GRP_RPL_PIPELINE_FLUSH_FAIL; SQLSTATE: HY000

    Message: Failed to flush group replication pipeline cache.

  • Error number: MY-011733; Symbol: ER_GRP_RPL_PIPELINE_REINIT_FAILED_READ; SQLSTATE: HY000

    Message: Failed to reinit group replication pipeline cache for read.

  • Error number: MY-011735; Symbol: ER_GRP_RPL_GCS_GR_ERROR_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011736; Symbol: ER_GRP_RPL_REPLICA_IO_THREAD_UNBLOCKED; SQLSTATE: HY000

    Message: The replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.

  • Error number: MY-011737; Symbol: ER_GRP_RPL_REPLICA_IO_THREAD_ERROR_OUT; SQLSTATE: HY000

    Message: The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.

  • Error number: MY-011738; Symbol: ER_GRP_RPL_REPLICA_APPLIER_THREAD_UNBLOCKED; SQLSTATE: HY000

    Message: The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.

  • Error number: MY-011739; Symbol: ER_GRP_RPL_REPLICA_APPLIER_THREAD_ERROR_OUT; SQLSTATE: HY000

    Message: The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.

  • Error number: MY-011740; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_OR_GET_CONNECTION; SQLSTATE: HY000

    Message: LDAP authentication initialize: failed to create/ get connection from the pool.

  • Error number: MY-011741; Symbol: ER_LDAP_AUTH_DEINIT_FAILED; SQLSTATE: HY000

    Message: LDAP authentication de_initialize Failed

  • Error number: MY-011742; Symbol: ER_LDAP_AUTH_SKIPPING_USER_GROUP_SEARCH; SQLSTATE: HY000

    Message: Skipping group search, No group attribute mentioned

  • Error number: MY-011743; Symbol: ER_LDAP_AUTH_POOL_DISABLE_MAX_SIZE_ZERO; SQLSTATE: HY000

    Message: Pool max size is 0, connection pool is disabled

  • Error number: MY-011744; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT_CREATOR; SQLSTATE: HY000

    Message: Connection pool initialization, failed to create LDAP object creator

  • Error number: MY-011745; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT; SQLSTATE: HY000

    Message: Connection pool initialization, failed to create LDAP object

  • Error number: MY-011746; Symbol: ER_LDAP_AUTH_TLS_CONF; SQLSTATE: HY000

    Message: LDAP TLS configuration

  • Error number: MY-011747; Symbol: ER_LDAP_AUTH_TLS_CONNECTION; SQLSTATE: HY000

    Message: LDAP TLS connection

  • Error number: MY-011748; Symbol: ER_LDAP_AUTH_CONN_POOL_NOT_CREATED; SQLSTATE: HY000

    Message: LDAP pool is not created.

  • Error number: MY-011749; Symbol: ER_LDAP_AUTH_CONN_POOL_INITIALIZING; SQLSTATE: HY000

    Message: LDAP pool is initializing

  • Error number: MY-011750; Symbol: ER_LDAP_AUTH_CONN_POOL_DEINITIALIZING; SQLSTATE: HY000

    Message: LDAP pool is de-initializing

  • Error number: MY-011751; Symbol: ER_LDAP_AUTH_ZERO_MAX_POOL_SIZE_UNCHANGED; SQLSTATE: HY000

    Message: Pool max size old and new values are 0

  • Error number: MY-011752; Symbol: ER_LDAP_AUTH_POOL_REINITIALIZING; SQLSTATE: HY000

    Message: LDAP pool is re-initializing

  • Error number: MY-011753; Symbol: ER_LDAP_AUTH_FAILED_TO_WRITE_PACKET; SQLSTATE: HY000

    Message: Plug-in has failed to write the packet.

  • Error number: MY-011754; Symbol: ER_LDAP_AUTH_SETTING_USERNAME; SQLSTATE: HY000

    Message: Setting LDAP user name as : %s

  • Error number: MY-011755; Symbol: ER_LDAP_AUTH_USER_AUTH_DATA; SQLSTATE: HY000

    Message: User authentication data: %s size: %lu

  • Error number: MY-011757; Symbol: ER_LDAP_AUTH_USER_GROUP_SEARCH_INFO; SQLSTATE: HY000

    Message: Group search information base DN: %s scope: %d filter: %s attribute: %s

  • Error number: MY-011758; Symbol: ER_LDAP_AUTH_GRP_SEARCH_SPECIAL_HDL; SQLSTATE: HY000

    Message: Special handling for group search, {GA} found

  • Error number: MY-011759; Symbol: ER_LDAP_AUTH_GRP_IS_FULL_DN; SQLSTATE: HY000

    Message: Group search special handling, group full DN found.

  • Error number: MY-011760; Symbol: ER_LDAP_AUTH_USER_NOT_FOUND_IN_ANY_GRP; SQLSTATE: HY000

    Message: User %s is not member of any group.

  • Error number: MY-011761; Symbol: ER_LDAP_AUTH_USER_FOUND_IN_MANY_GRPS; SQLSTATE: HY000

    Message: User %s is member of more than one group

  • Error number: MY-011762; Symbol: ER_LDAP_AUTH_USER_HAS_MULTIPLE_GRP_NAMES; SQLSTATE: HY000

    Message: For user %s has multiple user group names. Please check if group attribute name is correct

  • Error number: MY-011763; Symbol: ER_LDAP_AUTH_SEARCHED_USER_GRP_NAME; SQLSTATE: HY000

    Message: Searched group name: %s

  • Error number: MY-011764; Symbol: ER_LDAP_AUTH_OBJECT_CREATE_TIMESTAMP; SQLSTATE: HY000

    Message: LDAP authentication object creation time_stamp: %s dn: %s

  • Error number: MY-011765; Symbol: ER_LDAP_AUTH_CERTIFICATE_NAME; SQLSTATE: HY000

    Message: Certificate name: %s

  • Error number: MY-011766; Symbol: ER_LDAP_AUTH_FAILED_TO_POOL_DEINIT; SQLSTATE: HY000

    Message: Failed to pool de-initialized: pool is already reconstructing

  • Error number: MY-011767; Symbol: ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_RECONSTRUCTING; SQLSTATE: HY000

    Message: Pool initialization failed: pool is already initialized

  • Error number: MY-011768; Symbol: ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_INIT_STATE; SQLSTATE: HY000

    Message: Pool initialization failed: pool is initializing

  • Error number: MY-011769; Symbol: ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_DEINIT_STATE; SQLSTATE: HY000

    Message: Pool initialization failed: pool is de-initializing

  • Error number: MY-011770; Symbol: ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_POOL_IN_RECONSTRUCT_STATE; SQLSTATE: HY000

    Message: Failed to pool deinitialized: pool is already reconstructing

  • Error number: MY-011771; Symbol: ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_NOT_READY_POOL; SQLSTATE: HY000

    Message: Failed to pool deinitialized : pool is not ready

  • Error number: MY-011772; Symbol: ER_LDAP_AUTH_FAILED_TO_GET_CONNECTION_AS_PLUGIN_NOT_READY; SQLSTATE: HY000

    Message: Ldap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializing

  • Error number: MY-011773; Symbol: ER_LDAP_AUTH_CONNECTION_POOL_INIT_FAILED; SQLSTATE: HY000

    Message: Connection pool has failed to initialized

  • Error number: MY-011774; Symbol: ER_LDAP_AUTH_MAX_ALLOWED_CONNECTION_LIMIT_HIT; SQLSTATE: HY000

    Message: Ldap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.

  • Error number: MY-011775; Symbol: ER_LDAP_AUTH_MAX_POOL_SIZE_SET_FAILED; SQLSTATE: HY000

    Message: Set max pool size failed.

  • Error number: MY-011776; Symbol: ER_LDAP_AUTH_PLUGIN_FAILED_TO_READ_PACKET; SQLSTATE: HY000

    Message: Plug-in has failed to read the packet from client

  • Error number: MY-011777; Symbol: ER_LDAP_AUTH_CREATING_LDAP_CONNECTION; SQLSTATE: HY000

    Message: Ldap_authentication::initialize: creating new LDAP connection.

  • Error number: MY-011778; Symbol: ER_LDAP_AUTH_GETTING_CONNECTION_FROM_POOL; SQLSTATE: HY000

    Message: Ldap_authentication::initialize: getting connection from pool.

  • Error number: MY-011779; Symbol: ER_LDAP_AUTH_RETURNING_CONNECTION_TO_POOL; SQLSTATE: HY000

    Message: Ldap_authentication::de_initialize putting back connection in the pool

  • Error number: MY-011780; Symbol: ER_LDAP_AUTH_SEARCH_USER_GROUP_ATTR_NOT_FOUND; SQLSTATE: HY000

    Message: Ldap_authentication::search_user_group no group attribute found

  • Error number: MY-011781; Symbol: ER_LDAP_AUTH_LDAP_INFO_NULL; SQLSTATE: HY000

    Message: Ldap_connetion_pool::put ldap info null

  • Error number: MY-011782; Symbol: ER_LDAP_AUTH_FREEING_CONNECTION; SQLSTATE: HY000

    Message: Ldap_connection_pool::put connection is freeing.

  • Error number: MY-011783; Symbol: ER_LDAP_AUTH_CONNECTION_PUSHED_TO_POOL; SQLSTATE: HY000

    Message: Ldap_connection_pool::put connection in pushed in the pool

  • Error number: MY-011784; Symbol: ER_LDAP_AUTH_CONNECTION_CREATOR_ENTER; SQLSTATE: HY000

    Message: Ldap_connection_creator::Ldap_connection_creator

  • Error number: MY-011785; Symbol: ER_LDAP_AUTH_STARTING_TLS; SQLSTATE: HY000

    Message: starting TLS

  • Error number: MY-011786; Symbol: ER_LDAP_AUTH_CONNECTION_GET_LDAP_INFO_NULL; SQLSTATE: HY000

    Message: Ldap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)

  • Error number: MY-011787; Symbol: ER_LDAP_AUTH_DELETING_CONNECTION_KEY; SQLSTATE: HY000

    Message: Ldap_connection_pool::deinit: deleting connection key %s

  • Error number: MY-011788; Symbol: ER_LDAP_AUTH_POOLED_CONNECTION_KEY; SQLSTATE: HY000

    Message: Ldap_connection_pool::get pooled connection key: %s

  • Error number: MY-011789; Symbol: ER_LDAP_AUTH_CREATE_CONNECTION_KEY; SQLSTATE: HY000

    Message: Ldap_connection_pool::get create connection key: %s

  • Error number: MY-011790; Symbol: ER_LDAP_AUTH_COMMUNICATION_HOST_INFO; SQLSTATE: HY000

    Message: LDAP communication host %s port %u

  • Error number: MY-011791; Symbol: ER_LDAP_AUTH_METHOD_TO_CLIENT; SQLSTATE: HY000

    Message: Sending authentication method to client : %s

  • Error number: MY-011792; Symbol: ER_LDAP_AUTH_SASL_REQUEST_FROM_CLIENT; SQLSTATE: HY000

    Message: SASL request received from mysql client: %s

  • Error number: MY-011793; Symbol: ER_LDAP_AUTH_SASL_PROCESS_SASL; SQLSTATE: HY000

    Message: Ldap_sasl_authentication::process_sasl rc: %s

  • Error number: MY-011794; Symbol: ER_LDAP_AUTH_SASL_BIND_SUCCESS_INFO; SQLSTATE: HY000

    Message: Ldap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %s

  • Error number: MY-011795; Symbol: ER_LDAP_AUTH_STARTED_FOR_USER; SQLSTATE: HY000

    Message: LDAP authentication started for user name: %s

  • Error number: MY-011796; Symbol: ER_LDAP_AUTH_DISTINGUISHED_NAME; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011797; Symbol: ER_LDAP_AUTH_INIT_FAILED; SQLSTATE: HY000

    Message: LDAP authentication initialize is failed with: %s

  • Error number: MY-011798; Symbol: ER_LDAP_AUTH_OR_GROUP_RETRIEVAL_FAILED; SQLSTATE: HY000

    Message: LDAP authentication failed or group retrieval failed: %s

  • Error number: MY-011799; Symbol: ER_LDAP_AUTH_USER_GROUP_SEARCH_FAILED; SQLSTATE: HY000

    Message: Search user group has failed: %s

  • Error number: MY-011800; Symbol: ER_LDAP_AUTH_USER_BIND_FAILED; SQLSTATE: HY000

    Message: LDAP user bind has failed: %s

  • Error number: MY-011801; Symbol: ER_LDAP_AUTH_POOL_GET_FAILED_TO_CREATE_CONNECTION; SQLSTATE: HY000

    Message: Connection pool get: Failed to create LDAP connection. %s

  • Error number: MY-011802; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_CONNECTION; SQLSTATE: HY000

    Message: Failed to create new LDAP connection: %s

  • Error number: MY-011803; Symbol: ER_LDAP_AUTH_FAILED_TO_ESTABLISH_TLS_CONNECTION; SQLSTATE: HY000

    Message: Failed to establish TLS connection: %s

  • Error number: MY-011804; Symbol: ER_LDAP_AUTH_FAILED_TO_SEARCH_DN; SQLSTATE: HY000

    Message: Failed to search user full dn: %s

  • Error number: MY-011805; Symbol: ER_LDAP_AUTH_CONNECTION_POOL_REINIT_ENTER; SQLSTATE: HY000

    Message: Ldap_connection_pool::reinit

  • Error number: MY-011806; Symbol: ER_SYSTEMD_NOTIFY_PATH_TOO_LONG; SQLSTATE: HY000

    Message: The path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.

  • Error number: MY-011807; Symbol: ER_SYSTEMD_NOTIFY_CONNECT_FAILED; SQLSTATE: HY000

    Message: Failed to connect to systemd notification socket named %s. Error: '%s'

  • Error number: MY-011808; Symbol: ER_SYSTEMD_NOTIFY_WRITE_FAILED; SQLSTATE: HY000

    Message: Failed to write '%s' to systemd notification. Error: '%s'

  • Error number: MY-011809; Symbol: ER_FOUND_MISSING_GTIDS; SQLSTATE: HY000

    Message: Cannot replicate to server with server_uuid='%s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.

  • Error number: MY-011810; Symbol: ER_PID_FILE_PRIV_DIRECTORY_INSECURE; SQLSTATE: HY000

    Message: Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.

  • Error number: MY-011811; Symbol: ER_CANT_CHECK_PID_PATH; SQLSTATE: HY000

    Message: Can't start server: can't check PID filepath: %s

  • Error number: MY-011812; Symbol: ER_VALIDATE_PWD_STATUS_VAR_REGISTRATION_FAILED; SQLSTATE: HY000

    Message: validate_password status variables registration failed.

  • Error number: MY-011813; Symbol: ER_VALIDATE_PWD_STATUS_VAR_UNREGISTRATION_FAILED; SQLSTATE: HY000

    Message: validate_password status variables unregistration failed.

  • Error number: MY-011814; Symbol: ER_VALIDATE_PWD_DICT_FILE_OPEN_FAILED; SQLSTATE: HY000

    Message: Dictionary file open failed

  • Error number: MY-011815; Symbol: ER_VALIDATE_PWD_COULD_BE_NULL; SQLSTATE: HY000

    Message: given password string could be null

  • Error number: MY-011816; Symbol: ER_VALIDATE_PWD_STRING_CONV_TO_LOWERCASE_FAILED; SQLSTATE: HY000

    Message: failed to convert the password string to lower case

  • Error number: MY-011817; Symbol: ER_VALIDATE_PWD_STRING_CONV_TO_BUFFER_FAILED; SQLSTATE: HY000

    Message: failed to convert the password string into a buffer

  • Error number: MY-011818; Symbol: ER_VALIDATE_PWD_STRING_HANDLER_MEM_ALLOCATION_FAILED; SQLSTATE: HY000

    Message: memory allocation failed for string handler

  • Error number: MY-011819; Symbol: ER_VALIDATE_PWD_STRONG_POLICY_DICT_FILE_UNSPECIFIED; SQLSTATE: HY000

    Message: Since the validate_password_policy is mentioned as Strong, dictionary file must be specified

  • Error number: MY-011820; Symbol: ER_VALIDATE_PWD_CONVERT_TO_BUFFER_FAILED; SQLSTATE: HY000

    Message: convert_to_buffer service failed

  • Error number: MY-011821; Symbol: ER_VALIDATE_PWD_VARIABLE_REGISTRATION_FAILED; SQLSTATE: HY000

    Message: %s variable registration failed.

  • Error number: MY-011822; Symbol: ER_VALIDATE_PWD_VARIABLE_UNREGISTRATION_FAILED; SQLSTATE: HY000

    Message: %s variable unregistration failed.

  • Error number: MY-011823; Symbol: ER_KEYRING_MIGRATION_EXTRA_OPTIONS; SQLSTATE: HY000

    Message: Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.

  • Error number: MY-011825; Symbol: ER_IB_MSG_0; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011826; Symbol: ER_IB_MSG_1; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011827; Symbol: ER_IB_MSG_2; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011828; Symbol: ER_IB_MSG_3; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011829; Symbol: ER_IB_MSG_4; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011830; Symbol: ER_IB_MSG_5; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011831; Symbol: ER_IB_MSG_6; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011832; Symbol: ER_IB_MSG_7; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011833; Symbol: ER_IB_MSG_8; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011834; Symbol: ER_IB_MSG_9; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011835; Symbol: ER_IB_MSG_10; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011836; Symbol: ER_IB_MSG_11; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011837; Symbol: ER_IB_MSG_12; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011838; Symbol: ER_IB_MSG_13; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011839; Symbol: ER_IB_MSG_14; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011840; Symbol: ER_IB_MSG_15; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011841; Symbol: ER_IB_MSG_16; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011842; Symbol: ER_IB_MSG_17; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011843; Symbol: ER_IB_MSG_18; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011844; Symbol: ER_IB_MSG_19; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011845; Symbol: ER_IB_MSG_20; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011846; Symbol: ER_IB_MSG_21; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011847; Symbol: ER_IB_MSG_22; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011848; Symbol: ER_IB_MSG_23; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011849; Symbol: ER_IB_MSG_24; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011850; Symbol: ER_IB_MSG_25; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011851; Symbol: ER_IB_MSG_26; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011852; Symbol: ER_IB_MSG_27; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011853; Symbol: ER_IB_MSG_28; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011854; Symbol: ER_IB_MSG_29; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011855; Symbol: ER_IB_MSG_30; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011857; Symbol: ER_IB_MSG_32; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011858; Symbol: ER_IB_MSG_33; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011859; Symbol: ER_IB_MSG_34; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011860; Symbol: ER_IB_MSG_35; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011861; Symbol: ER_IB_MSG_36; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011862; Symbol: ER_IB_MSG_37; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011863; Symbol: ER_IB_MSG_38; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011864; Symbol: ER_IB_MSG_39; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011865; Symbol: ER_IB_MSG_40; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011866; Symbol: ER_IB_MSG_41; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011867; Symbol: ER_IB_MSG_42; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011868; Symbol: ER_IB_MSG_43; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011869; Symbol: ER_IB_MSG_44; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011870; Symbol: ER_IB_MSG_45; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011871; Symbol: ER_IB_MSG_46; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011872; Symbol: ER_IB_MSG_47; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011873; Symbol: ER_IB_MSG_48; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011874; Symbol: ER_IB_MSG_49; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011875; Symbol: ER_IB_MSG_50; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011876; Symbol: ER_IB_MSG_51; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011877; Symbol: ER_IB_MSG_52; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011878; Symbol: ER_IB_MSG_53; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011879; Symbol: ER_IB_MSG_54; SQLSTATE: HY000

    Message: Failed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s

  • Error number: MY-011880; Symbol: ER_IB_MSG_55; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011881; Symbol: ER_IB_MSG_56; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011882; Symbol: ER_IB_MSG_57; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011883; Symbol: ER_IB_MSG_58; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011884; Symbol: ER_IB_MSG_59; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011885; Symbol: ER_IB_MSG_60; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011886; Symbol: ER_IB_MSG_61; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011887; Symbol: ER_IB_MSG_62; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011888; Symbol: ER_IB_MSG_63; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011889; Symbol: ER_IB_MSG_64; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011890; Symbol: ER_IB_MSG_65; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011891; Symbol: ER_IB_MSG_66; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011892; Symbol: ER_IB_MSG_67; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011893; Symbol: ER_IB_MSG_68; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011894; Symbol: ER_IB_MSG_69; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011895; Symbol: ER_IB_MSG_70; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011896; Symbol: ER_IB_MSG_71; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011897; Symbol: ER_IB_MSG_72; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011898; Symbol: ER_IB_MSG_73; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011899; Symbol: ER_IB_MSG_74; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011900; Symbol: ER_IB_MSG_75; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011901; Symbol: ER_IB_MSG_76; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011902; Symbol: ER_IB_MSG_77; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011903; Symbol: ER_IB_MSG_78; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011904; Symbol: ER_IB_MSG_79; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011905; Symbol: ER_IB_MSG_80; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011906; Symbol: ER_IB_MSG_81; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011907; Symbol: ER_IB_MSG_82; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011908; Symbol: ER_IB_MSG_83; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011909; Symbol: ER_IB_MSG_84; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011910; Symbol: ER_IB_MSG_85; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011911; Symbol: ER_IB_MSG_86; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011920; Symbol: ER_IB_MSG_95; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011921; Symbol: ER_IB_MSG_96; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011922; Symbol: ER_IB_MSG_97; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011923; Symbol: ER_IB_MSG_98; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011924; Symbol: ER_IB_MSG_99; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011925; Symbol: ER_IB_MSG_100; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011926; Symbol: ER_IB_MSG_101; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011927; Symbol: ER_IB_MSG_102; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011928; Symbol: ER_IB_MSG_103; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011929; Symbol: ER_IB_MSG_104; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011930; Symbol: ER_IB_MSG_105; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011931; Symbol: ER_IB_MSG_106; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011932; Symbol: ER_IB_MSG_107; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011933; Symbol: ER_IB_MSG_108; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011934; Symbol: ER_IB_MSG_109; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011935; Symbol: ER_IB_MSG_110; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011936; Symbol: ER_IB_MSG_111; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011937; Symbol: ER_IB_MSG_112; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011944; Symbol: ER_IB_MSG_119; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011945; Symbol: ER_IB_MSG_120; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011946; Symbol: ER_IB_MSG_121; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011947; Symbol: ER_IB_MSG_122; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011948; Symbol: ER_IB_MSG_123; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011949; Symbol: ER_IB_MSG_124; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011950; Symbol: ER_IB_MSG_125; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011951; Symbol: ER_IB_MSG_126; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011952; Symbol: ER_IB_MSG_127; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011953; Symbol: ER_IB_MSG_128; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011954; Symbol: ER_IB_MSG_129; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011955; Symbol: ER_IB_MSG_130; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011956; Symbol: ER_IB_MSG_131; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011957; Symbol: ER_IB_MSG_132; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011958; Symbol: ER_IB_MSG_133; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011959; Symbol: ER_IB_MSG_134; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011960; Symbol: ER_IB_MSG_135; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011961; Symbol: ER_IB_MSG_136; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011962; Symbol: ER_IB_MSG_137; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011963; Symbol: ER_IB_MSG_138; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011964; Symbol: ER_IB_MSG_139; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011965; Symbol: ER_IB_MSG_140; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011966; Symbol: ER_IB_MSG_141; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011967; Symbol: ER_IB_MSG_142; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011968; Symbol: ER_IB_MSG_143; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011969; Symbol: ER_IB_MSG_144; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011970; Symbol: ER_IB_MSG_145; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011971; Symbol: ER_IB_MSG_146; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011972; Symbol: ER_IB_MSG_147; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011973; Symbol: ER_IB_MSG_148; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011974; Symbol: ER_IB_CLONE_INTERNAL; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011975; Symbol: ER_IB_CLONE_TIMEOUT; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011976; Symbol: ER_IB_CLONE_STATUS_FILE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011977; Symbol: ER_IB_CLONE_SQL; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011978; Symbol: ER_IB_CLONE_VALIDATE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011979; Symbol: ER_IB_CLONE_PUNCH_HOLE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011980; Symbol: ER_IB_CLONE_GTID_PERSIST; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011981; Symbol: ER_IB_MSG_156; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011982; Symbol: ER_IB_MSG_157; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011983; Symbol: ER_IB_MSG_158; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011984; Symbol: ER_IB_MSG_159; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011985; Symbol: ER_IB_MSG_160; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011986; Symbol: ER_IB_MSG_161; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011987; Symbol: ER_IB_MSG_162; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011988; Symbol: ER_IB_MSG_163; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011989; Symbol: ER_IB_MSG_164; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011990; Symbol: ER_IB_MSG_165; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011991; Symbol: ER_IB_MSG_166; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011992; Symbol: ER_IB_MSG_167; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011993; Symbol: ER_IB_MSG_168; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011994; Symbol: ER_IB_MSG_169; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011995; Symbol: ER_IB_MSG_170; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011996; Symbol: ER_IB_MSG_171; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011997; Symbol: ER_IB_MSG_172; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011998; Symbol: ER_IB_MSG_173; SQLSTATE: HY000

    Message: %s

  • Error number: MY-011999; Symbol: ER_IB_MSG_174; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012000; Symbol: ER_IB_MSG_175; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012001; Symbol: ER_IB_MSG_176; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012002; Symbol: ER_IB_MSG_177; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012003; Symbol: ER_IB_MSG_178; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012004; Symbol: ER_IB_MSG_179; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012005; Symbol: ER_IB_MSG_180; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012006; Symbol: ER_IB_LONG_AHI_DISABLE_WAIT; SQLSTATE: HY000

    Message: Waited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"

  • Error number: MY-012007; Symbol: ER_IB_MSG_182; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012008; Symbol: ER_IB_MSG_183; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012009; Symbol: ER_IB_MSG_184; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012012; Symbol: ER_IB_MSG_187; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012013; Symbol: ER_IB_MSG_188; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012014; Symbol: ER_IB_MSG_189; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012015; Symbol: ER_IB_MSG_190; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012016; Symbol: ER_IB_MSG_191; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012017; Symbol: ER_IB_MSG_192; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012018; Symbol: ER_IB_MSG_193; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012019; Symbol: ER_IB_MSG_194; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012020; Symbol: ER_IB_MSG_195; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012021; Symbol: ER_IB_MSG_196; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012022; Symbol: ER_IB_MSG_197; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012023; Symbol: ER_IB_MSG_198; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012024; Symbol: ER_IB_MSG_199; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012025; Symbol: ER_IB_MSG_200; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012026; Symbol: ER_IB_MSG_201; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012027; Symbol: ER_IB_MSG_202; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012028; Symbol: ER_IB_MSG_203; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012029; Symbol: ER_IB_MSG_204; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012030; Symbol: ER_IB_MSG_205; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012031; Symbol: ER_IB_MSG_206; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012032; Symbol: ER_IB_MSG_207; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012033; Symbol: ER_IB_MSG_208; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012034; Symbol: ER_IB_MSG_209; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012035; Symbol: ER_IB_MSG_210; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012036; Symbol: ER_IB_MSG_211; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012037; Symbol: ER_IB_MSG_212; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012038; Symbol: ER_IB_MSG_213; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012039; Symbol: ER_IB_MSG_214; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012040; Symbol: ER_IB_MSG_215; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012041; Symbol: ER_IB_MSG_216; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012042; Symbol: ER_IB_MSG_217; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012043; Symbol: ER_IB_MSG_218; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012044; Symbol: ER_IB_MSG_219; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012045; Symbol: ER_IB_MSG_220; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012046; Symbol: ER_IB_MSG_221; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012047; Symbol: ER_IB_MSG_222; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012048; Symbol: ER_IB_MSG_223; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012049; Symbol: ER_IB_MSG_224; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012050; Symbol: ER_IB_MSG_225; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012051; Symbol: ER_IB_MSG_226; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012054; Symbol: ER_IB_MSG_229; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012055; Symbol: ER_IB_MSG_230; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012056; Symbol: ER_IB_MSG_231; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012057; Symbol: ER_IB_MSG_232; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012058; Symbol: ER_IB_MSG_233; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012059; Symbol: ER_IB_MSG_234; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012060; Symbol: ER_IB_MSG_235; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012061; Symbol: ER_IB_MSG_236; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012062; Symbol: ER_IB_MSG_237; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012063; Symbol: ER_IB_MSG_238; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012064; Symbol: ER_IB_MSG_239; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012065; Symbol: ER_IB_MSG_240; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012066; Symbol: ER_IB_MSG_241; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012067; Symbol: ER_IB_MSG_242; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012068; Symbol: ER_IB_MSG_243; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012069; Symbol: ER_IB_MSG_244; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012070; Symbol: ER_IB_MSG_245; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012071; Symbol: ER_IB_MSG_246; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012072; Symbol: ER_IB_MSG_247; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012073; Symbol: ER_IB_MSG_248; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012074; Symbol: ER_IB_MSG_249; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012075; Symbol: ER_IB_MSG_250; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012076; Symbol: ER_IB_MSG_251; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012077; Symbol: ER_IB_MSG_252; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012078; Symbol: ER_IB_MSG_253; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012079; Symbol: ER_IB_MSG_254; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012080; Symbol: ER_IB_MSG_255; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012081; Symbol: ER_IB_MSG_256; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012082; Symbol: ER_IB_MSG_257; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012083; Symbol: ER_IB_MSG_258; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012084; Symbol: ER_IB_MSG_259; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012085; Symbol: ER_IB_MSG_260; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012086; Symbol: ER_IB_MSG_261; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012087; Symbol: ER_IB_MSG_262; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012088; Symbol: ER_IB_MSG_263; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012089; Symbol: ER_IB_MSG_264; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012090; Symbol: ER_IB_MSG_265; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012091; Symbol: ER_IB_MSG_266; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012092; Symbol: ER_IB_MSG_267; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012093; Symbol: ER_IB_MSG_268; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012094; Symbol: ER_IB_MSG_269; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012095; Symbol: ER_IB_MSG_270; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012096; Symbol: ER_IB_MSG_271; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012097; Symbol: ER_IB_MSG_272; SQLSTATE: HY000

    Message: Table flags are 0x%lx in the data dictionary but the flags in file %s are 0x%llx!

  • Error number: MY-012098; Symbol: ER_IB_MSG_273; SQLSTATE: HY000

    Message: Can't read encryption key from file %s!

  • Error number: MY-012103; Symbol: ER_IB_MSG_278; SQLSTATE: HY000

    Message: Tablespace %s, waiting for IO to stop for %lld seconds

  • Error number: MY-012105; Symbol: ER_IB_MSG_280; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012106; Symbol: ER_IB_MSG_281; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012107; Symbol: ER_IB_MSG_282; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012108; Symbol: ER_IB_MSG_283; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012109; Symbol: ER_IB_MSG_284; SQLSTATE: HY000

    Message: You must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.

  • Error number: MY-012110; Symbol: ER_IB_MSG_285; SQLSTATE: HY000

    Message: Max tablespace id is too high, %lu

  • Error number: MY-012111; Symbol: ER_IB_WARN_ACCESSING_NONEXISTINC_SPACE; SQLSTATE: HY000

    Message: Trying to access missing tablespace %lu

  • Error number: MY-012112; Symbol: ER_IB_MSG_287; SQLSTATE: HY000

    Message: Trying to close/delete tablespace '%s' but there are %lu pending operations on it.

  • Error number: MY-012113; Symbol: ER_IB_MSG_288; SQLSTATE: HY000

    Message: Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.

  • Error number: MY-012114; Symbol: ER_IB_MSG_289; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012116; Symbol: ER_IB_MSG_291; SQLSTATE: HY000

    Message: While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %s

  • Error number: MY-012117; Symbol: ER_IB_MSG_292; SQLSTATE: HY000

    Message: Cannot delete tablespace %lu in DISCARD TABLESPACE: %s

  • Error number: MY-012118; Symbol: ER_IB_MSG_293; SQLSTATE: HY000

    Message: Cannot rename '%s' to '%s' for space ID %lu because the source file does not exist.

  • Error number: MY-012119; Symbol: ER_IB_MSG_294; SQLSTATE: HY000

    Message: Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.

  • Error number: MY-012120; Symbol: ER_IB_MSG_295; SQLSTATE: HY000

    Message: Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.

  • Error number: MY-012121; Symbol: ER_IB_MSG_296; SQLSTATE: HY000

    Message: Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.

  • Error number: MY-012122; Symbol: ER_IB_MSG_297; SQLSTATE: HY000

    Message: Rename waiting for IO to resume

  • Error number: MY-012123; Symbol: ER_IB_MSG_298; SQLSTATE: HY000

    Message: Cannot find tablespace for '%s' in the tablespace memory cache

  • Error number: MY-012124; Symbol: ER_IB_MSG_299; SQLSTATE: HY000

    Message: Cannot find tablespace for '%s' in the tablespace memory cache

  • Error number: MY-012125; Symbol: ER_IB_MSG_300; SQLSTATE: HY000

    Message: Tablespace '%s' is already in the tablespace memory cache

  • Error number: MY-012126; Symbol: ER_IB_MSG_301; SQLSTATE: HY000

    Message: Cannot create file '%s'

  • Error number: MY-012127; Symbol: ER_IB_MSG_UNEXPECTED_FILE_EXISTS; SQLSTATE: HY000

    Message: The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.

  • Error number: MY-012128; Symbol: ER_IB_MSG_303; SQLSTATE: HY000

    Message: posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.

  • Error number: MY-012129; Symbol: ER_IB_MSG_304; SQLSTATE: HY000

    Message: Could not write the first page to tablespace '%s'

  • Error number: MY-012130; Symbol: ER_IB_MSG_305; SQLSTATE: HY000

    Message: File flush of tablespace '%s' failed

  • Error number: MY-012131; Symbol: ER_IB_MSG_306; SQLSTATE: HY000

    Message: Could not find a valid tablespace file for `%s`. %s

  • Error number: MY-012132; Symbol: ER_IB_MSG_307; SQLSTATE: HY000

    Message: Ignoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID

  • Error number: MY-012133; Symbol: ER_IB_MSG_308; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012134; Symbol: ER_IB_MSG_309; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012135; Symbol: ER_IB_MSG_310; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012136; Symbol: ER_IB_MSG_311; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012137; Symbol: ER_IB_MSG_312; SQLSTATE: HY000

    Message: Can't set encryption information for tablespace %s!

  • Error number: MY-012138; Symbol: ER_IB_MSG_313; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012139; Symbol: ER_IB_MSG_314; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012140; Symbol: ER_IB_MSG_315; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012141; Symbol: ER_IB_MSG_316; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012142; Symbol: ER_IB_MSG_317; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012143; Symbol: ER_IB_MSG_318; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012144; Symbol: ER_IB_MSG_319; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012145; Symbol: ER_IB_MSG_320; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012146; Symbol: ER_IB_MSG_321; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012147; Symbol: ER_IB_MSG_322; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012148; Symbol: ER_IB_MSG_323; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012149; Symbol: ER_IB_MSG_324; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012150; Symbol: ER_IB_MSG_325; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012151; Symbol: ER_IB_MSG_326; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012153; Symbol: ER_IB_MSG_328; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012154; Symbol: ER_IB_MSG_329; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012155; Symbol: ER_IB_MSG_330; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012156; Symbol: ER_IB_MSG_331; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012157; Symbol: ER_IB_MSG_332; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012158; Symbol: ER_IB_MSG_333; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012159; Symbol: ER_IB_MSG_334; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012160; Symbol: ER_IB_MSG_335; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012161; Symbol: ER_IB_MSG_336; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012162; Symbol: ER_IB_MSG_337; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012163; Symbol: ER_IB_MSG_338; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012164; Symbol: ER_IB_MSG_339; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012165; Symbol: ER_IB_MSG_340; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012166; Symbol: ER_IB_MSG_341; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012167; Symbol: ER_IB_MSG_342; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012168; Symbol: ER_IB_MSG_343; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012169; Symbol: ER_IB_MSG_344; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012170; Symbol: ER_IB_MSG_345; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012171; Symbol: ER_IB_MSG_346; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012172; Symbol: ER_IB_MSG_347; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012173; Symbol: ER_IB_MSG_348; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012174; Symbol: ER_IB_MSG_349; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012175; Symbol: ER_IB_MSG_350; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012177; Symbol: ER_IB_MSG_UNPROTECTED_LOCATION_ALLOWED; SQLSTATE: HY000

    Message: The datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.

  • Error number: MY-012179; Symbol: ER_IB_MSG_354; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012180; Symbol: ER_IB_MSG_355; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012181; Symbol: ER_IB_MSG_356; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012182; Symbol: ER_IB_MSG_357; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012183; Symbol: ER_IB_MSG_358; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012184; Symbol: ER_IB_MSG_359; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012185; Symbol: ER_IB_MSG_360; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012186; Symbol: ER_IB_MSG_361; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012187; Symbol: ER_IB_MSG_362; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012189; Symbol: ER_IB_MSG_364; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012190; Symbol: ER_IB_MSG_365; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012191; Symbol: ER_IB_MSG_IGNORE_SCAN_PATH; SQLSTATE: HY000

    Message: Scan path '%s' is ignored because %s

  • Error number: MY-012192; Symbol: ER_IB_MSG_367; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012193; Symbol: ER_IB_MSG_368; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012194; Symbol: ER_IB_MSG_369; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012195; Symbol: ER_IB_MSG_370; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012196; Symbol: ER_IB_MSG_371; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012197; Symbol: ER_IB_MSG_372; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012198; Symbol: ER_IB_MSG_373; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012199; Symbol: ER_IB_MSG_374; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012200; Symbol: ER_IB_MSG_375; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012201; Symbol: ER_IB_MSG_376; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012202; Symbol: ER_IB_MSG_377; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012203; Symbol: ER_IB_MSG_378; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012204; Symbol: ER_IB_MSG_379; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012205; Symbol: ER_IB_MSG_380; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012206; Symbol: ER_IB_MSG_381; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012207; Symbol: ER_IB_MSG_382; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012208; Symbol: ER_IB_MSG_383; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012209; Symbol: ER_IB_MSG_384; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012210; Symbol: ER_IB_MSG_385; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012211; Symbol: ER_IB_MSG_386; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012212; Symbol: ER_IB_MSG_387; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012213; Symbol: ER_IB_MSG_GENERAL_TABLESPACE_UNDER_DATADIR; SQLSTATE: HY000

    Message: A general tablespace cannot be located under the datadir. Cannot open file '%s'.

  • Error number: MY-012214; Symbol: ER_IB_MSG_IMPLICIT_TABLESPACE_IN_DATADIR; SQLSTATE: HY000

    Message: A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.

  • Error number: MY-012215; Symbol: ER_IB_MSG_390; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012216; Symbol: ER_IB_MSG_391; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012217; Symbol: ER_IB_MSG_392; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012218; Symbol: ER_IB_MSG_393; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012219; Symbol: ER_IB_MSG_394; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012220; Symbol: ER_IB_MSG_395; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012221; Symbol: ER_IB_MSG_396; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012222; Symbol: ER_IB_MSG_397; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012223; Symbol: ER_IB_MSG_398; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012224; Symbol: ER_IB_MSG_399; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012226; Symbol: ER_IB_MSG_401; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012227; Symbol: ER_IB_MSG_402; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012228; Symbol: ER_IB_MSG_403; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012229; Symbol: ER_IB_MSG_404; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012230; Symbol: ER_IB_MSG_405; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012231; Symbol: ER_IB_MSG_406; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012232; Symbol: ER_IB_MSG_407; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012233; Symbol: ER_IB_MSG_408; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012234; Symbol: ER_IB_MSG_409; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012235; Symbol: ER_IB_MSG_410; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012236; Symbol: ER_IB_MSG_411; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012237; Symbol: ER_IB_MSG_412; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012238; Symbol: ER_IB_MSG_413; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012239; Symbol: ER_IB_MSG_414; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012240; Symbol: ER_IB_MSG_415; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012241; Symbol: ER_IB_MSG_416; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012242; Symbol: ER_IB_MSG_417; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012243; Symbol: ER_IB_MSG_418; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012244; Symbol: ER_IB_MSG_419; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012245; Symbol: ER_IB_MSG_420; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012246; Symbol: ER_IB_MSG_421; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012247; Symbol: ER_IB_MSG_422; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012248; Symbol: ER_IB_MSG_423; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012249; Symbol: ER_IB_MSG_424; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012250; Symbol: ER_IB_MSG_425; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012251; Symbol: ER_IB_MSG_426; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012252; Symbol: ER_IB_MSG_427; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012253; Symbol: ER_IB_MSG_428; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012254; Symbol: ER_IB_MSG_429; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012255; Symbol: ER_IB_MSG_430; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012256; Symbol: ER_IB_MSG_431; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012257; Symbol: ER_IB_MSG_432; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012258; Symbol: ER_IB_MSG_433; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012259; Symbol: ER_IB_MSG_434; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012260; Symbol: ER_IB_MSG_435; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012261; Symbol: ER_IB_MSG_436; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012262; Symbol: ER_IB_MSG_437; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012263; Symbol: ER_IB_MSG_438; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012264; Symbol: ER_IB_MSG_439; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012265; Symbol: ER_IB_MSG_440; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012266; Symbol: ER_IB_MSG_441; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012267; Symbol: ER_IB_MSG_442; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012268; Symbol: ER_IB_MSG_443; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012270; Symbol: ER_IB_MSG_445; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012271; Symbol: ER_IB_MSG_446; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012272; Symbol: ER_IB_MSG_447; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012273; Symbol: ER_IB_MSG_448; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012274; Symbol: ER_IB_MSG_449; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012275; Symbol: ER_IB_MSG_450; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012276; Symbol: ER_IB_MSG_451; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012277; Symbol: ER_IB_MSG_452; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012278; Symbol: ER_IB_MSG_453; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012279; Symbol: ER_IB_MSG_454; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012280; Symbol: ER_IB_MSG_455; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012281; Symbol: ER_IB_MSG_456; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012282; Symbol: ER_IB_MSG_457; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012283; Symbol: ER_IB_MSG_458; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012284; Symbol: ER_IB_MSG_459; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012285; Symbol: ER_IB_MSG_460; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012286; Symbol: ER_IB_MSG_461; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012287; Symbol: ER_IB_MSG_462; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012288; Symbol: ER_IB_MSG_463; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012289; Symbol: ER_IB_MSG_464; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012290; Symbol: ER_IB_MSG_465; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012291; Symbol: ER_IB_MSG_466; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012292; Symbol: ER_IB_MSG_467; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012293; Symbol: ER_IB_MSG_468; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012294; Symbol: ER_IB_MSG_469; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012295; Symbol: ER_IB_MSG_470; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012296; Symbol: ER_IB_MSG_471; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012297; Symbol: ER_IB_MSG_472; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012298; Symbol: ER_IB_MSG_473; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012299; Symbol: ER_IB_MSG_474; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012300; Symbol: ER_IB_MSG_475; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012301; Symbol: ER_IB_MSG_476; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012302; Symbol: ER_IB_MSG_477; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012303; Symbol: ER_IB_MSG_478; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012304; Symbol: ER_IB_MSG_479; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012305; Symbol: ER_IB_MSG_480; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012306; Symbol: ER_IB_MSG_481; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012307; Symbol: ER_IB_MSG_482; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012308; Symbol: ER_IB_MSG_483; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012309; Symbol: ER_IB_MSG_484; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012310; Symbol: ER_IB_MSG_485; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012311; Symbol: ER_IB_MSG_486; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012312; Symbol: ER_IB_MSG_487; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012313; Symbol: ER_IB_MSG_488; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012314; Symbol: ER_IB_MSG_489; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012315; Symbol: ER_IB_MSG_490; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012316; Symbol: ER_IB_MSG_491; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012317; Symbol: ER_IB_MSG_492; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012318; Symbol: ER_IB_MSG_493; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012319; Symbol: ER_IB_MSG_494; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012320; Symbol: ER_IB_MSG_495; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012321; Symbol: ER_IB_MSG_496; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012322; Symbol: ER_IB_MSG_497; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012323; Symbol: ER_IB_MSG_498; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012324; Symbol: ER_IB_MSG_499; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012325; Symbol: ER_IB_MSG_500; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012326; Symbol: ER_IB_MSG_501; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012327; Symbol: ER_IB_MSG_502; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012328; Symbol: ER_IB_MSG_503; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012329; Symbol: ER_IB_MSG_504; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012330; Symbol: ER_IB_MSG_505; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012331; Symbol: ER_IB_MSG_506; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012332; Symbol: ER_IB_MSG_507; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012333; Symbol: ER_IB_MSG_508; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012334; Symbol: ER_IB_MSG_509; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012335; Symbol: ER_IB_MSG_510; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012336; Symbol: ER_IB_MSG_511; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012337; Symbol: ER_IB_MSG_512; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012338; Symbol: ER_IB_MSG_513; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012339; Symbol: ER_IB_MSG_514; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012340; Symbol: ER_IB_MSG_515; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012341; Symbol: ER_IB_MSG_516; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012342; Symbol: ER_IB_MSG_517; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012343; Symbol: ER_IB_MSG_518; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012344; Symbol: ER_IB_MSG_519; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012345; Symbol: ER_IB_MSG_520; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012346; Symbol: ER_IB_MSG_521; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012347; Symbol: ER_IB_MSG_522; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012348; Symbol: ER_IB_MSG_523; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012349; Symbol: ER_IB_MSG_524; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012350; Symbol: ER_IB_MSG_525; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012351; Symbol: ER_IB_MSG_526; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012352; Symbol: ER_IB_MSG_527; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012355; Symbol: ER_IB_MSG_530; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012356; Symbol: ER_IB_MSG_531; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012357; Symbol: ER_IB_MSG_532; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012358; Symbol: ER_IB_MSG_533; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012359; Symbol: ER_IB_MSG_534; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012362; Symbol: ER_IB_MSG_537; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012363; Symbol: ER_IB_MSG_538; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012364; Symbol: ER_IB_MSG_539; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012365; Symbol: ER_IB_MSG_540; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012366; Symbol: ER_IB_MSG_541; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012368; Symbol: ER_IB_MSG_543; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012369; Symbol: ER_IB_MSG_544; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012370; Symbol: ER_IB_MSG_545; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012371; Symbol: ER_IB_MSG_546; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012372; Symbol: ER_IB_MSG_547; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012373; Symbol: ER_IB_MSG_548; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012374; Symbol: ER_IB_MSG_549; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012375; Symbol: ER_IB_MSG_550; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012376; Symbol: ER_IB_MSG_551; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012377; Symbol: ER_IB_MSG_552; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012378; Symbol: ER_IB_MSG_553; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012379; Symbol: ER_IB_MSG_554; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012380; Symbol: ER_IB_MSG_555; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012381; Symbol: ER_IB_MSG_556; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012382; Symbol: ER_IB_MSG_557; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012383; Symbol: ER_IB_MSG_558; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012384; Symbol: ER_IB_MSG_559; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012385; Symbol: ER_IB_MSG_560; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012386; Symbol: ER_IB_MSG_561; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012387; Symbol: ER_IB_MSG_562; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012388; Symbol: ER_IB_MSG_563; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012389; Symbol: ER_IB_MSG_564; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012390; Symbol: ER_IB_MSG_INVALID_LOCATION_FOR_TABLE; SQLSTATE: HY000

    Message: Cannot create a tablespace for table %s because the directory is not a valid location. %s

  • Error number: MY-012391; Symbol: ER_IB_MSG_566; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012392; Symbol: ER_IB_MSG_567; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012393; Symbol: ER_IB_MSG_568; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012394; Symbol: ER_IB_MSG_569; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012395; Symbol: ER_IB_MSG_570; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012396; Symbol: ER_IB_MSG_571; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012398; Symbol: ER_IB_MSG_573; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012399; Symbol: ER_IB_MSG_574; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012403; Symbol: ER_IB_MSG_578; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012404; Symbol: ER_IB_MSG_579; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012405; Symbol: ER_IB_MSG_580; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012406; Symbol: ER_IB_MSG_581; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012407; Symbol: ER_IB_MSG_582; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012408; Symbol: ER_IB_MSG_583; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012409; Symbol: ER_IB_MSG_584; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012410; Symbol: ER_IB_MSG_585; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012411; Symbol: ER_IB_MSG_586; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012412; Symbol: ER_IB_MSG_587; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012413; Symbol: ER_IB_MSG_588; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012414; Symbol: ER_IB_MSG_589; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012415; Symbol: ER_IB_MSG_590; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012416; Symbol: ER_IB_MSG_591; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012417; Symbol: ER_IB_MSG_592; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012418; Symbol: ER_IB_MSG_593; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012419; Symbol: ER_IB_MSG_594; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012420; Symbol: ER_IB_MSG_595; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012421; Symbol: ER_IB_MSG_596; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012422; Symbol: ER_IB_MSG_597; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012423; Symbol: ER_IB_MSG_598; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012424; Symbol: ER_IB_MSG_599; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012425; Symbol: ER_IB_MSG_600; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012426; Symbol: ER_IB_MSG_601; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012427; Symbol: ER_IB_MSG_602; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012428; Symbol: ER_IB_MSG_603; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012429; Symbol: ER_IB_MSG_604; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012430; Symbol: ER_IB_MSG_605; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012431; Symbol: ER_IB_MSG_606; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012432; Symbol: ER_IB_MSG_607; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012433; Symbol: ER_IB_MSG_608; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012434; Symbol: ER_IB_MSG_609; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012436; Symbol: ER_IB_MSG_611; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012437; Symbol: ER_IB_MSG_612; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012438; Symbol: ER_IB_MSG_613; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012439; Symbol: ER_IB_MSG_614; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012440; Symbol: ER_IB_MSG_615; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012441; Symbol: ER_IB_MSG_616; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012442; Symbol: ER_IB_MSG_617; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012444; Symbol: ER_IB_MSG_619; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012445; Symbol: ER_IB_MSG_IBUF_CURSOR_RESTORATION_FAILED; SQLSTATE: HY000

    Message: ibuf cursor restoration fails!. ibuf record inserted to page %s:%s

  • Error number: MY-012447; Symbol: ER_IB_MSG_IBUF_FAILED_TO_RESTORE_POSITION; SQLSTATE: HY000

    Message: Failed to restore ibuf position.

  • Error number: MY-012448; Symbol: ER_IB_MSG_623; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012449; Symbol: ER_IB_MSG_624; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012451; Symbol: ER_IB_MSG_626; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012452; Symbol: ER_IB_MSG_627; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012453; Symbol: ER_IB_MSG_628; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012454; Symbol: ER_IB_MSG_629; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012455; Symbol: ER_IB_MSG_630; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012456; Symbol: ER_IB_MSG_631; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012457; Symbol: ER_IB_MSG_632; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012458; Symbol: ER_IB_MSG_633; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012459; Symbol: ER_IB_MSG_634; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012460; Symbol: ER_IB_MSG_635; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012461; Symbol: ER_IB_MSG_636; SQLSTATE: HY000

    Message: Blocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).

  • Error number: MY-012462; Symbol: ER_IB_MSG_637; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012463; Symbol: ER_IB_MSG_638; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012464; Symbol: ER_IB_MSG_639; SQLSTATE: HY000

    Message: Blocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.

  • Error number: MY-012467; Symbol: ER_IB_MSG_642; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012468; Symbol: ER_IB_MSG_643; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012469; Symbol: ER_IB_MSG_644; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012470; Symbol: ER_IB_MSG_645; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012471; Symbol: ER_IB_MSG_646; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012472; Symbol: ER_IB_MSG_647; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012473; Symbol: ER_IB_MSG_648; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012474; Symbol: ER_IB_MSG_649; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012475; Symbol: ER_IB_MSG_650; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012476; Symbol: ER_IB_MSG_651; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012477; Symbol: ER_IB_MSG_652; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012478; Symbol: ER_IB_MSG_DDL_LOG_DELETE_BY_ID_OK; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012479; Symbol: ER_IB_MSG_654; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012480; Symbol: ER_IB_MSG_655; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012481; Symbol: ER_IB_MSG_656; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012482; Symbol: ER_IB_MSG_657; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012483; Symbol: ER_IB_MSG_658; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012484; Symbol: ER_IB_MSG_659; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012485; Symbol: ER_IB_MSG_660; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012486; Symbol: ER_IB_MSG_661; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012487; Symbol: ER_IB_MSG_662; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012488; Symbol: ER_IB_MSG_663; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012519; Symbol: ER_IB_MSG_694; SQLSTATE: HY000

    Message: ############### CORRUPT LOG RECORD FOUND ###############

  • Error number: MY-012520; Symbol: ER_IB_MSG_695; SQLSTATE: HY000

    Message: Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %llu

  • Error number: MY-012521; Symbol: ER_IB_MSG_696; SQLSTATE: HY000

    Message: Hex dump starting %llu bytes before and ending %llu bytes after the corrupted record:

  • Error number: MY-012522; Symbol: ER_IB_MSG_697; SQLSTATE: HY000

    Message: Set innodb_force_recovery to ignore this error.

  • Error number: MY-012523; Symbol: ER_IB_MSG_LOG_CORRUPT; SQLSTATE: HY000

    Message: The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s

  • Error number: MY-012524; Symbol: ER_IB_MSG_UNPROCESSED_REDO_LOG_RECORDS; SQLSTATE: HY000

    Message: %zu pages with log records were left unprocessed!

  • Error number: MY-012525; Symbol: ER_IB_MSG_LOG_FORMAT_OLD_AND_LOG_CORRUPTED; SQLSTATE: HY000

    Message: Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %s

  • Error number: MY-012526; Symbol: ER_IB_MSG_LOG_FORMAT_OLD_AND_NO_CLEAN_SHUTDOWN; SQLSTATE: HY000

    Message: Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s

  • Error number: MY-012529; Symbol: ER_IB_MSG_LOG_FORMAT_BEFORE_8_0_30; SQLSTATE: HY000

    Message: Redo log format is v%lu. The redo log was created before MySQL 8.0.30.

  • Error number: MY-012530; Symbol: ER_IB_MSG_LOG_FILE_FORMAT_UNKNOWN; SQLSTATE: HY000

    Message: Unknown redo log format (v%lu) in file %s. Please follow the instructions at %s

  • Error number: MY-012531; Symbol: ER_IB_MSG_RECOVERY_CHECKPOINT_NOT_FOUND; SQLSTATE: HY000

    Message: No valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.

  • Error number: MY-012532; Symbol: ER_IB_MSG_707; SQLSTATE: HY000

    Message: Applying a batch of %llu redo log records ...

  • Error number: MY-012533; Symbol: ER_IB_MSG_708; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012534; Symbol: ER_IB_MSG_709; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012535; Symbol: ER_IB_MSG_710; SQLSTATE: HY000

    Message: Apply batch completed!

  • Error number: MY-012536; Symbol: ER_IB_MSG_711; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012537; Symbol: ER_IB_MSG_712; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012538; Symbol: ER_IB_MSG_713; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012539; Symbol: ER_IB_MSG_714; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012540; Symbol: ER_IB_MSG_715; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012541; Symbol: ER_IB_MSG_716; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012543; Symbol: ER_IB_MSG_718; SQLSTATE: HY000

    Message: Extending tablespace : %lu space name: %s to new size: %lu pages during recovery.

  • Error number: MY-012544; Symbol: ER_IB_MSG_719; SQLSTATE: HY000

    Message: Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.

  • Error number: MY-012545; Symbol: ER_IB_MSG_720; SQLSTATE: HY000

    Message: Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.

  • Error number: MY-012546; Symbol: ER_IB_MSG_RECOVERY_SKIPPED_IN_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Skipped necessary redo log applying, --innodb-read-only set!

  • Error number: MY-012547; Symbol: ER_IB_MSG_722; SQLSTATE: HY000

    Message: Log scan progressed past the checkpoint LSN %llu.

  • Error number: MY-012548; Symbol: ER_IB_MSG_723; SQLSTATE: HY000

    Message: Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.

  • Error number: MY-012549; Symbol: ER_IB_MSG_724; SQLSTATE: HY000

    Message: Set innodb_force_recovery to ignore this error.

  • Error number: MY-012550; Symbol: ER_IB_MSG_725; SQLSTATE: HY000

    Message: Doing recovery: scanned up to log sequence number %llu

  • Error number: MY-012551; Symbol: ER_IB_MSG_726; SQLSTATE: HY000

    Message: Database was not shutdown normally!

  • Error number: MY-012552; Symbol: ER_IB_MSG_727; SQLSTATE: HY000

    Message: Starting crash recovery.

  • Error number: MY-012553; Symbol: ER_IB_MSG_728; SQLSTATE: HY000

    Message: The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo

  • Error number: MY-012554; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_MEB_AND_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Cannot restore from mysqlbackup, InnoDB running in read-only mode!

  • Error number: MY-012555; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_MEB; SQLSTATE: HY000

    Message: The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.

  • Error number: MY-012556; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_CLONE; SQLSTATE: HY000

    Message: Opening cloned database

  • Error number: MY-012557; Symbol: ER_IB_MSG_LOG_FORMAT_OLD; SQLSTATE: HY000

    Message: Redo log is from an earlier version, v%lu.

  • Error number: MY-012559; Symbol: ER_IB_MSG_RECOVERY_CHECKPOINT_FROM_BEFORE_CLEAN_SHUTDOWN; SQLSTATE: HY000

    Message: Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.

  • Error number: MY-012560; Symbol: ER_IB_MSG_RECOVERY_IS_NEEDED; SQLSTATE: HY000

    Message: The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!

  • Error number: MY-012561; Symbol: ER_IB_MSG_RECOVERY_IN_READ_ONLY; SQLSTATE: HY000

    Message: Can't initiate database recovery, running in read-only-mode.

  • Error number: MY-012562; Symbol: ER_IB_MSG_737; SQLSTATE: HY000

    Message: We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!

  • Error number: MY-012563; Symbol: ER_IB_MSG_738; SQLSTATE: HY000

    Message: Waiting for recv_writer to finish flushing of buffer pool

  • Error number: MY-012564; Symbol: ER_IB_MSG_739; SQLSTATE: HY000

    Message: Recovery parsing buffer extended to %zu.

  • Error number: MY-012565; Symbol: ER_IB_MSG_740; SQLSTATE: HY000

    Message: Out of memory while resizing recovery parsing buffer.

  • Error number: MY-012566; Symbol: ER_IB_MSG_741; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012567; Symbol: ER_IB_MSG_742; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012568; Symbol: ER_IB_MSG_743; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012569; Symbol: ER_IB_MSG_744; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012570; Symbol: ER_IB_MSG_745; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012571; Symbol: ER_IB_MSG_746; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012572; Symbol: ER_IB_MSG_747; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012573; Symbol: ER_IB_MSG_748; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012574; Symbol: ER_IB_MSG_749; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012575; Symbol: ER_IB_MSG_750; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012576; Symbol: ER_IB_MSG_751; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012577; Symbol: ER_IB_MSG_752; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012578; Symbol: ER_IB_MSG_753; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012579; Symbol: ER_IB_MSG_754; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012580; Symbol: ER_IB_MSG_755; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012581; Symbol: ER_IB_MSG_756; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012582; Symbol: ER_IB_MSG_757; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012583; Symbol: ER_IB_MSG_758; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012584; Symbol: ER_IB_MSG_759; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012585; Symbol: ER_IB_MSG_760; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012586; Symbol: ER_IB_MSG_761; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012587; Symbol: ER_IB_MSG_762; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012588; Symbol: ER_IB_MSG_763; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012589; Symbol: ER_IB_MSG_764; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012590; Symbol: ER_IB_MSG_765; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012591; Symbol: ER_IB_MSG_766; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012592; Symbol: ER_IB_MSG_767; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012593; Symbol: ER_IB_MSG_768; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012594; Symbol: ER_IB_MSG_769; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012595; Symbol: ER_IB_MSG_770; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012596; Symbol: ER_IB_MSG_771; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012597; Symbol: ER_IB_MSG_772; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012598; Symbol: ER_IB_MSG_773; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012599; Symbol: ER_IB_MSG_774; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012600; Symbol: ER_IB_MSG_775; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012601; Symbol: ER_IB_MSG_776; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012602; Symbol: ER_IB_MSG_777; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012603; Symbol: ER_IB_MSG_778; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012604; Symbol: ER_IB_MSG_779; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012605; Symbol: ER_IB_MSG_780; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012606; Symbol: ER_IB_MSG_781; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012607; Symbol: ER_IB_MSG_782; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012608; Symbol: ER_IB_MSG_783; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012609; Symbol: ER_IB_MSG_784; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012610; Symbol: ER_IB_MSG_785; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012611; Symbol: ER_IB_MSG_786; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012612; Symbol: ER_IB_MSG_787; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012613; Symbol: ER_IB_MSG_788; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012614; Symbol: ER_IB_MSG_789; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012615; Symbol: ER_IB_MSG_790; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012616; Symbol: ER_IB_MSG_791; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012617; Symbol: ER_IB_MSG_792; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012618; Symbol: ER_IB_MSG_793; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012619; Symbol: ER_IB_MSG_794; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012620; Symbol: ER_IB_MSG_795; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012621; Symbol: ER_IB_MSG_796; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012622; Symbol: ER_IB_MSG_797; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012623; Symbol: ER_IB_MSG_798; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012624; Symbol: ER_IB_MSG_799; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012626; Symbol: ER_IB_MSG_801; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012627; Symbol: ER_IB_MSG_802; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012628; Symbol: ER_IB_MSG_803; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012629; Symbol: ER_IB_MSG_804; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012630; Symbol: ER_IB_MSG_805; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012631; Symbol: ER_IB_MSG_806; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012632; Symbol: ER_IB_MSG_807; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012633; Symbol: ER_IB_MSG_808; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012634; Symbol: ER_IB_MSG_809; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012635; Symbol: ER_IB_MSG_810; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012636; Symbol: ER_IB_MSG_811; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012637; Symbol: ER_IB_MSG_812; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012638; Symbol: ER_IB_MSG_813; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012639; Symbol: ER_IB_MSG_814; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012640; Symbol: ER_IB_MSG_815; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012641; Symbol: ER_IB_MSG_816; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012642; Symbol: ER_IB_MSG_817; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012643; Symbol: ER_IB_MSG_818; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012644; Symbol: ER_IB_MSG_819; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012645; Symbol: ER_IB_MSG_820; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012646; Symbol: ER_IB_MSG_821; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012647; Symbol: ER_IB_MSG_822; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012648; Symbol: ER_IB_MSG_823; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012649; Symbol: ER_IB_MSG_824; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012650; Symbol: ER_IB_MSG_825; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012651; Symbol: ER_IB_MSG_826; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012652; Symbol: ER_IB_MSG_827; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012653; Symbol: ER_IB_MSG_828; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012654; Symbol: ER_IB_MSG_829; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012656; Symbol: ER_IB_MSG_831; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012657; Symbol: ER_IB_MSG_832; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012658; Symbol: ER_IB_MSG_833; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012659; Symbol: ER_IB_MSG_834; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012660; Symbol: ER_IB_MSG_835; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012661; Symbol: ER_IB_MSG_836; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012662; Symbol: ER_IB_MSG_837; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012663; Symbol: ER_IB_MSG_838; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012664; Symbol: ER_IB_MSG_839; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012665; Symbol: ER_IB_MSG_840; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012666; Symbol: ER_IB_MSG_841; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012667; Symbol: ER_IB_MSG_842; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012668; Symbol: ER_IB_MSG_CANT_ENCRYPT_REDO_LOG_DATA; SQLSTATE: HY000

    Message: Can't encrypt data of redo log

  • Error number: MY-012669; Symbol: ER_IB_MSG_844; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012670; Symbol: ER_IB_MSG_845; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012671; Symbol: ER_IB_MSG_CANT_DECRYPT_REDO_LOG; SQLSTATE: HY000

    Message: Decryption of redo log block at offset %llu in file %s failed because there's no keyring configured

  • Error number: MY-012672; Symbol: ER_IB_MSG_847; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012673; Symbol: ER_IB_MSG_848; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012674; Symbol: ER_IB_MSG_849; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012675; Symbol: ER_IB_MSG_850; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012676; Symbol: ER_IB_MSG_851; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012677; Symbol: ER_IB_MSG_852; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012678; Symbol: ER_IB_MSG_853; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012679; Symbol: ER_IB_MSG_854; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012680; Symbol: ER_IB_MSG_855; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012681; Symbol: ER_IB_MSG_856; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012682; Symbol: ER_IB_MSG_857; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012683; Symbol: ER_IB_MSG_858; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012684; Symbol: ER_IB_MSG_859; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012685; Symbol: ER_IB_MSG_860; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012686; Symbol: ER_IB_MSG_861; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012687; Symbol: ER_IB_MSG_862; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012688; Symbol: ER_IB_MSG_863; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012689; Symbol: ER_IB_MSG_864; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012690; Symbol: ER_IB_MSG_865; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012691; Symbol: ER_IB_MSG_866; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012692; Symbol: ER_IB_MSG_867; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012693; Symbol: ER_IB_MSG_868; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012694; Symbol: ER_IB_MSG_869; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012695; Symbol: ER_IB_MSG_870; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012696; Symbol: ER_IB_MSG_871; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012697; Symbol: ER_IB_MSG_872; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012698; Symbol: ER_IB_MSG_873; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012699; Symbol: ER_IB_MSG_874; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012700; Symbol: ER_IB_MSG_875; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012701; Symbol: ER_IB_MSG_876; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012702; Symbol: ER_IB_MSG_877; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012703; Symbol: ER_IB_MSG_878; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012704; Symbol: ER_IB_MSG_879; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012705; Symbol: ER_IB_MSG_880; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012706; Symbol: ER_IB_MSG_881; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012707; Symbol: ER_IB_MSG_882; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012708; Symbol: ER_IB_MSG_883; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012709; Symbol: ER_IB_MSG_884; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012710; Symbol: ER_IB_MSG_885; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012711; Symbol: ER_IB_MSG_886; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012712; Symbol: ER_IB_MSG_887; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012713; Symbol: ER_IB_MSG_888; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012714; Symbol: ER_IB_MSG_889; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012715; Symbol: ER_IB_MSG_890; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012716; Symbol: ER_IB_MSG_891; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012717; Symbol: ER_IB_MSG_892; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012718; Symbol: ER_IB_MSG_893; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012719; Symbol: ER_IB_MSG_894; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012720; Symbol: ER_IB_MSG_895; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012721; Symbol: ER_IB_MSG_896; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012722; Symbol: ER_IB_MSG_897; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012723; Symbol: ER_IB_MSG_898; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012724; Symbol: ER_IB_MSG_899; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012725; Symbol: ER_IB_MSG_900; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012726; Symbol: ER_IB_MSG_901; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012727; Symbol: ER_IB_MSG_902; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012728; Symbol: ER_IB_MSG_903; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012729; Symbol: ER_IB_MSG_904; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012730; Symbol: ER_IB_MSG_905; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012731; Symbol: ER_IB_MSG_906; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012732; Symbol: ER_IB_MSG_907; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012733; Symbol: ER_IB_MSG_908; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012734; Symbol: ER_IB_MSG_909; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012735; Symbol: ER_IB_MSG_910; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012736; Symbol: ER_IB_MSG_911; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012737; Symbol: ER_IB_MSG_912; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012738; Symbol: ER_IB_MSG_913; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012739; Symbol: ER_IB_MSG_914; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012740; Symbol: ER_IB_MSG_915; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012741; Symbol: ER_IB_MSG_916; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012742; Symbol: ER_IB_MSG_917; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012743; Symbol: ER_IB_MSG_918; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012744; Symbol: ER_IB_MSG_919; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012745; Symbol: ER_IB_MSG_920; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012746; Symbol: ER_IB_MSG_921; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012747; Symbol: ER_IB_MSG_922; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012748; Symbol: ER_IB_MSG_923; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012749; Symbol: ER_IB_MSG_924; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012750; Symbol: ER_IB_MSG_925; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012751; Symbol: ER_IB_MSG_926; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012752; Symbol: ER_IB_MSG_927; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012753; Symbol: ER_IB_MSG_928; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012754; Symbol: ER_IB_MSG_929; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012755; Symbol: ER_IB_MSG_930; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012756; Symbol: ER_IB_MSG_931; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012757; Symbol: ER_IB_MSG_932; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012758; Symbol: ER_IB_MSG_933; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012759; Symbol: ER_IB_MSG_934; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012760; Symbol: ER_IB_MSG_935; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012761; Symbol: ER_IB_MSG_936; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012762; Symbol: ER_IB_MSG_937; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012763; Symbol: ER_IB_MSG_938; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012764; Symbol: ER_IB_MSG_939; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012765; Symbol: ER_IB_MSG_940; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012766; Symbol: ER_IB_MSG_941; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012767; Symbol: ER_IB_MSG_942; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012768; Symbol: ER_IB_MSG_943; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012769; Symbol: ER_IB_MSG_944; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012770; Symbol: ER_IB_MSG_945; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012771; Symbol: ER_IB_MSG_946; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012772; Symbol: ER_IB_IMPORT_INDEX_METADATA_READ_FAILED; SQLSTATE: HY000

    Message: IO Error: %s

  • Error number: MY-012773; Symbol: ER_IB_MSG_948; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012774; Symbol: ER_IB_MSG_949; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012775; Symbol: ER_IB_MSG_950; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012776; Symbol: ER_IB_MSG_951; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012777; Symbol: ER_IB_MSG_952; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012778; Symbol: ER_IB_MSG_953; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012779; Symbol: ER_IB_MSG_954; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012780; Symbol: ER_IB_MSG_955; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012781; Symbol: ER_IB_MSG_956; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012782; Symbol: ER_IB_MSG_957; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012783; Symbol: ER_IB_MSG_958; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012784; Symbol: ER_IB_MSG_959; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012785; Symbol: ER_IB_MSG_960; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012786; Symbol: ER_IB_MSG_961; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012787; Symbol: ER_IB_MSG_962; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012788; Symbol: ER_IB_MSG_963; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012789; Symbol: ER_IB_MSG_964; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012790; Symbol: ER_IB_MSG_965; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012791; Symbol: ER_IB_MSG_966; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012792; Symbol: ER_IB_MSG_967; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012793; Symbol: ER_IB_MSG_968; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012794; Symbol: ER_IB_MSG_969; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012795; Symbol: ER_IB_MSG_970; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012796; Symbol: ER_IB_MSG_971; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012797; Symbol: ER_IB_MSG_972; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012798; Symbol: ER_IB_MSG_973; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012799; Symbol: ER_IB_MSG_974; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012800; Symbol: ER_IB_MSG_975; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012801; Symbol: ER_IB_MSG_976; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012802; Symbol: ER_IB_MSG_977; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012803; Symbol: ER_IB_MSG_978; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012804; Symbol: ER_IB_MSG_979; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012805; Symbol: ER_IB_MSG_980; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012806; Symbol: ER_IB_MSG_981; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012807; Symbol: ER_IB_MSG_982; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012808; Symbol: ER_IB_MSG_983; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012809; Symbol: ER_IB_MSG_984; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012810; Symbol: ER_IB_MSG_985; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012811; Symbol: ER_IB_MSG_986; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012812; Symbol: ER_IB_MSG_987; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012813; Symbol: ER_IB_MSG_988; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012814; Symbol: ER_IB_MSG_989; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012815; Symbol: ER_IB_MSG_990; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012816; Symbol: ER_IB_MSG_991; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012817; Symbol: ER_IB_MSG_992; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012818; Symbol: ER_IB_MSG_993; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012819; Symbol: ER_IB_MSG_994; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012820; Symbol: ER_IB_MSG_995; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012821; Symbol: ER_IB_MSG_996; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012822; Symbol: ER_IB_MSG_997; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012823; Symbol: ER_IB_MSG_998; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012824; Symbol: ER_IB_MSG_999; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012825; Symbol: ER_IB_MSG_1000; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012826; Symbol: ER_IB_MSG_1001; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012827; Symbol: ER_IB_MSG_1002; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012828; Symbol: ER_IB_MSG_1003; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012829; Symbol: ER_IB_MSG_1004; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012830; Symbol: ER_IB_MSG_1005; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012831; Symbol: ER_IB_MSG_1006; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012832; Symbol: ER_IB_MSG_1007; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012833; Symbol: ER_IB_MSG_1008; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012834; Symbol: ER_IB_MSG_1009; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012835; Symbol: ER_IB_MSG_1010; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012836; Symbol: ER_IB_MSG_1011; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012837; Symbol: ER_IB_MSG_1012; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012838; Symbol: ER_IB_MSG_1013; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012839; Symbol: ER_IB_IMPORT_START_CFG_NAME; SQLSTATE: HY000

    Message: Writing table metadata to '%s'

  • Error number: MY-012840; Symbol: ER_IB_MSG_1015; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012841; Symbol: ER_IB_MSG_1016; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012842; Symbol: ER_IB_MSG_1017; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012843; Symbol: ER_IB_MSG_1018; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012844; Symbol: ER_IB_MSG_1019; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012845; Symbol: ER_IB_MSG_1020; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012846; Symbol: ER_IB_MSG_1021; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012847; Symbol: ER_IB_MSG_1022; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012848; Symbol: ER_IB_MSG_1023; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012849; Symbol: ER_IB_MSG_1024; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012850; Symbol: ER_IB_MSG_1025; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012851; Symbol: ER_IB_MSG_1026; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012852; Symbol: ER_IB_MSG_1027; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012853; Symbol: ER_IB_MSG_1028; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012854; Symbol: ER_IB_MSG_1029; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012855; Symbol: ER_IB_MSG_1030; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012856; Symbol: ER_IB_MSG_1031; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012857; Symbol: ER_IB_MSG_1032; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012858; Symbol: ER_IB_MSG_1033; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012859; Symbol: ER_IB_MSG_1034; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012860; Symbol: ER_IB_MSG_1035; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012861; Symbol: ER_IB_MSG_1036; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012862; Symbol: ER_IB_MSG_1037; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012863; Symbol: ER_IB_MSG_1038; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012864; Symbol: ER_IB_MSG_1039; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012865; Symbol: ER_IB_MSG_1040; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012866; Symbol: ER_IB_MSG_1041; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012867; Symbol: ER_IB_MSG_1042; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012868; Symbol: ER_IB_MSG_1043; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012869; Symbol: ER_IB_MSG_1044; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012870; Symbol: ER_IB_MSG_1045; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012871; Symbol: ER_IB_MSG_1046; SQLSTATE: HY000

    Message: Old log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.com

  • Error number: MY-012872; Symbol: ER_IB_MSG_1047; SQLSTATE: HY000

    Message: Semaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.

  • Error number: MY-012873; Symbol: ER_IB_MSG_1048; SQLSTATE: HY000

    Message: Waiting for %llu table(s) to be dropped

  • Error number: MY-012874; Symbol: ER_IB_MSG_1049; SQLSTATE: HY000

    Message: Waiting for change buffer merge to complete number of bytes of change buffer just merged: %llu

  • Error number: MY-012876; Symbol: ER_IB_MSG_1051; SQLSTATE: HY000

    Message: Can't set undo tablespace(s) to be encrypted in read-only-mode.

  • Error number: MY-012877; Symbol: ER_IB_MSG_1052; SQLSTATE: HY000

    Message: Can't set undo tablespace '%s' to be encrypted.

  • Error number: MY-012878; Symbol: ER_IB_MSG_1053; SQLSTATE: HY000

    Message: Can't set undo tablespace '%s' to be encrypted. Failed to write header page.

  • Error number: MY-012879; Symbol: ER_IB_MSG_1054; SQLSTATE: HY000

    Message: Can't set undo tablespace '%s' to be encrypted. Error %d - %s

  • Error number: MY-012880; Symbol: ER_IB_MSG_1055; SQLSTATE: HY000

    Message: Encryption is enabled for undo tablespace '%s'.

  • Error number: MY-012881; Symbol: ER_IB_MSG_1056; SQLSTATE: HY000

    Message: Can't rotate encryption on undo tablespace '%s'.

  • Error number: MY-012882; Symbol: ER_IB_MSG_1057; SQLSTATE: HY000

    Message: Encryption is enabled for undo tablespace '%s'.

  • Error number: MY-012883; Symbol: ER_IB_MSG_1058; SQLSTATE: HY000

    Message: os_file_get_status() failed on '%s'. Can't determine file permissions.

  • Error number: MY-012884; Symbol: ER_IB_MSG_1059; SQLSTATE: HY000

    Message: %s can't be opened in %s mode.

  • Error number: MY-012885; Symbol: ER_IB_MSG_1060; SQLSTATE: HY000

    Message: '%s' not a regular file.

  • Error number: MY-012886; Symbol: ER_IB_MSG_LOG_FILE_OS_CREATE_FAILED; SQLSTATE: HY000

    Message: Cannot create %s

  • Error number: MY-012887; Symbol: ER_IB_MSG_FILE_RESIZE; SQLSTATE: HY000

    Message: Setting file %s size to %llu MB. Progress : %u%%

  • Error number: MY-012888; Symbol: ER_IB_MSG_LOG_FILE_RESIZE_FAILED; SQLSTATE: HY000

    Message: Cannot resize redo log file %s to %llu MB (%s)

  • Error number: MY-012889; Symbol: ER_IB_MSG_LOG_FILES_CREATE_AND_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Cannot create redo log files in read-only mode (--innodb-read-only).

  • Error number: MY-012890; Symbol: ER_IB_MSG_1065; SQLSTATE: HY000

    Message: Redo log encryption is enabled, but the keyring is not loaded.

  • Error number: MY-012891; Symbol: ER_IB_MSG_LOG_FILE_PREPARE_ON_CREATE_FAILED; SQLSTATE: HY000

    Message: Failed to create redo log file %s (error: %d) for start LSN %llu

  • Error number: MY-012893; Symbol: ER_IB_MSG_LOG_FILES_INITIALIZED; SQLSTATE: HY000

    Message: New redo log files created, LSN=%llu

  • Error number: MY-012894; Symbol: ER_IB_MSG_LOG_FILE_OPEN_FAILED; SQLSTATE: HY000

    Message: Unable to open '%s' (error: %d).

  • Error number: MY-012895; Symbol: ER_IB_MSG_1070; SQLSTATE: HY000

    Message: Cannot create construction log file '%s' for undo tablespace '%s'.

  • Error number: MY-012896; Symbol: ER_IB_MSG_1071; SQLSTATE: HY000

    Message: Creating UNDO Tablespace %s

  • Error number: MY-012897; Symbol: ER_IB_MSG_1072; SQLSTATE: HY000

    Message: Setting file %s size to %llu MB

  • Error number: MY-012898; Symbol: ER_IB_MSG_1073; SQLSTATE: HY000

    Message: Physically writing the file full

  • Error number: MY-012899; Symbol: ER_IB_MSG_1074; SQLSTATE: HY000

    Message: Error in creating %s: probably out of disk space

  • Error number: MY-012900; Symbol: ER_IB_MSG_1075; SQLSTATE: HY000

    Message: Can't set encryption metadata for space %s

  • Error number: MY-012901; Symbol: ER_IB_MSG_1076; SQLSTATE: HY000

    Message: Cannot read first page of '%s' - %s

  • Error number: MY-012902; Symbol: ER_IB_MSG_1077; SQLSTATE: HY000

    Message: Undo tablespace number %lu was being truncated when mysqld quit.

  • Error number: MY-012903; Symbol: ER_IB_MSG_1078; SQLSTATE: HY000

    Message: Cannot recover a truncated undo tablespace in read-only mode

  • Error number: MY-012904; Symbol: ER_IB_MSG_1079; SQLSTATE: HY000

    Message: Reconstructing undo tablespace number %lu.

  • Error number: MY-012905; Symbol: ER_IB_MSG_1080; SQLSTATE: HY000

    Message: Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?

  • Error number: MY-012906; Symbol: ER_IB_MSG_1081; SQLSTATE: HY000

    Message: UNDO tablespace %s must be %s

  • Error number: MY-012907; Symbol: ER_IB_MSG_1082; SQLSTATE: HY000

    Message: Error creating file for %s

  • Error number: MY-012908; Symbol: ER_IB_MSG_1083; SQLSTATE: HY000

    Message: Error reading encryption for %s

  • Error number: MY-012909; Symbol: ER_IB_MSG_CANNOT_OPEN_57_UNDO; SQLSTATE: HY000

    Message: Unable to open undo tablespace number %lu

  • Error number: MY-012910; Symbol: ER_IB_MSG_1085; SQLSTATE: HY000

    Message: Opened %llu existing undo tablespaces.

  • Error number: MY-012911; Symbol: ER_IB_MSG_1086; SQLSTATE: HY000

    Message: Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.

  • Error number: MY-012912; Symbol: ER_IB_MSG_1087; SQLSTATE: HY000

    Message: Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.

  • Error number: MY-012913; Symbol: ER_IB_MSG_1088; SQLSTATE: HY000

    Message: Could not create undo tablespace '%s'.

  • Error number: MY-012914; Symbol: ER_IB_MSG_1089; SQLSTATE: HY000

    Message: Error %d - %s - opening newly created undo tablespace '%s'.

  • Error number: MY-012915; Symbol: ER_IB_MSG_1090; SQLSTATE: HY000

    Message: Created %llu undo tablespaces.

  • Error number: MY-012916; Symbol: ER_IB_MSG_1091; SQLSTATE: HY000

    Message: Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctly

  • Error number: MY-012917; Symbol: ER_IB_MSG_1092; SQLSTATE: HY000

    Message: Encryption is enabled for undo tablespace number %lu.

  • Error number: MY-012918; Symbol: ER_IB_MSG_1093; SQLSTATE: HY000

    Message: Unable to initialize the header page in undo tablespace number %lu.

  • Error number: MY-012919; Symbol: ER_IB_MSG_1094; SQLSTATE: HY000

    Message: Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.

  • Error number: MY-012920; Symbol: ER_IB_MSG_1095; SQLSTATE: HY000

    Message: Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.

  • Error number: MY-012921; Symbol: ER_IB_MSG_1096; SQLSTATE: HY000

    Message: Deleting %llu new independent undo tablespaces that we just created.

  • Error number: MY-012922; Symbol: ER_IB_MSG_1097; SQLSTATE: HY000

    Message: Waiting for purge to start

  • Error number: MY-012923; Symbol: ER_IB_MSG_1098; SQLSTATE: HY000

    Message: Creating shared tablespace for temporary tables

  • Error number: MY-012924; Symbol: ER_IB_MSG_1099; SQLSTATE: HY000

    Message: The %s data file must be writable!

  • Error number: MY-012925; Symbol: ER_IB_MSG_1100; SQLSTATE: HY000

    Message: Could not create the shared %s.

  • Error number: MY-012926; Symbol: ER_IB_MSG_1101; SQLSTATE: HY000

    Message: Unable to create the shared %s.

  • Error number: MY-012927; Symbol: ER_IB_MSG_1102; SQLSTATE: HY000

    Message: The %s data file cannot be re-opened after check_file_spec() succeeded!

  • Error number: MY-012928; Symbol: ER_IB_MSG_1103; SQLSTATE: HY000

    Message: %d threads created by InnoDB had not exited at shutdown!

  • Error number: MY-012929; Symbol: ER_IB_MSG_1104; SQLSTATE: HY000

    Message: InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.

  • Error number: MY-012930; Symbol: ER_IB_MSG_1105; SQLSTATE: HY000

    Message: Plugin initialization aborted %swith error %s.

  • Error number: MY-012931; Symbol: ER_IB_MSG_BUF_PENDING_IO; SQLSTATE: HY000

    Message: Waiting for %zu buffer page I/Os to complete.

  • Error number: MY-012932; Symbol: ER_IB_MSG_1107; SQLSTATE: HY000

    Message: PUNCH HOLE support available

  • Error number: MY-012933; Symbol: ER_IB_MSG_1108; SQLSTATE: HY000

    Message: PUNCH HOLE support not available

  • Error number: MY-012934; Symbol: ER_IB_MSG_1109; SQLSTATE: HY000

    Message: Size of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.

  • Error number: MY-012935; Symbol: ER_IB_MSG_1110; SQLSTATE: HY000

    Message: Database upgrade cannot be accomplished in read-only mode.

  • Error number: MY-012936; Symbol: ER_IB_MSG_1111; SQLSTATE: HY000

    Message: Database upgrade cannot be accomplished with innodb_force_recovery > 0

  • Error number: MY-012937; Symbol: ER_IB_MSG_1112; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012938; Symbol: ER_IB_MSG_1113; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012939; Symbol: ER_IB_MSG_1114; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012940; Symbol: ER_IB_MSG_1115; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012941; Symbol: ER_IB_MSG_1116; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012942; Symbol: ER_IB_MSG_1117; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012944; Symbol: ER_IB_MSG_1119; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012945; Symbol: ER_IB_MSG_1120; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012946; Symbol: ER_IB_MSG_1121; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012947; Symbol: ER_IB_MSG_1122; SQLSTATE: HY000

    Message: MySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.

  • Error number: MY-012948; Symbol: ER_IB_MSG_1123; SQLSTATE: HY000

    Message: Compressed tables use zlib %s

  • Error number: MY-012949; Symbol: ER_IB_MSG_1124; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012950; Symbol: ER_IB_MSG_1125; SQLSTATE: HY000

    Message: Startup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.

  • Error number: MY-012951; Symbol: ER_IB_MSG_1126; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012952; Symbol: ER_IB_MSG_1127; SQLSTATE: HY000

    Message: Unable to create monitor file %s: %s

  • Error number: MY-012953; Symbol: ER_IB_MSG_1128; SQLSTATE: HY000

    Message: Disabling background ibuf IO read threads.

  • Error number: MY-012954; Symbol: ER_IB_MSG_1129; SQLSTATE: HY000

    Message: Cannot initialize AIO sub-system

  • Error number: MY-012955; Symbol: ER_IB_MSG_1130; SQLSTATE: HY000

    Message: Initializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c

  • Error number: MY-012956; Symbol: ER_IB_MSG_1131; SQLSTATE: HY000

    Message: Cannot allocate memory for the buffer pool

  • Error number: MY-012957; Symbol: ER_IB_MSG_1132; SQLSTATE: HY000

    Message: Completed initialization of buffer pool

  • Error number: MY-012958; Symbol: ER_IB_MSG_1133; SQLSTATE: HY000

    Message: Small buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.

  • Error number: MY-012959; Symbol: ER_IB_MSG_1134; SQLSTATE: HY000

    Message: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!

  • Error number: MY-012960; Symbol: ER_IB_MSG_DATA_DIRECTORY_NOT_INITIALIZED_OR_CORRUPTED; SQLSTATE: HY000

    Message: Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.

  • Error number: MY-012961; Symbol: ER_IB_MSG_LOG_FILES_INVALID_SET; SQLSTATE: HY000

    Message: Only one redo log file found

  • Error number: MY-012962; Symbol: ER_IB_MSG_LOG_FILE_SIZE_INVALID; SQLSTATE: HY000

    Message: The redo log file %s size %llu is not a multiple of innodb_page_size

  • Error number: MY-012963; Symbol: ER_IB_MSG_LOG_FILES_DIFFERENT_SIZES; SQLSTATE: HY000

    Message: The redo log file %s is of different size %llu bytes than other log files %llu bytes!

  • Error number: MY-012964; Symbol: ER_IB_MSG_1139; SQLSTATE: HY000

    Message: Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)

  • Error number: MY-012965; Symbol: ER_IB_MSG_RECOVERY_CORRUPT; SQLSTATE: HY000

    Message: The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!

  • Error number: MY-012967; Symbol: ER_IB_MSG_1142; SQLSTATE: HY000

    Message: Cannot open DD tablespace.

  • Error number: MY-012968; Symbol: ER_IB_MSG_LOG_FILES_REWRITING; SQLSTATE: HY000

    Message: Starting to delete and rewrite redo log files.

  • Error number: MY-012969; Symbol: ER_IB_MSG_1144; SQLSTATE: HY000

    Message: Undo from 5.7 found. It will be purged

  • Error number: MY-012970; Symbol: ER_IB_MSG_1145; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012971; Symbol: ER_IB_MSG_1146; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012972; Symbol: ER_IB_MSG_1147; SQLSTATE: HY000

    Message: Tablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pages

  • Error number: MY-012973; Symbol: ER_IB_MSG_1148; SQLSTATE: HY000

    Message: Cannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.

  • Error number: MY-012974; Symbol: ER_IB_MSG_1149; SQLSTATE: HY000

    Message: Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pages

  • Error number: MY-012975; Symbol: ER_IB_MSG_1150; SQLSTATE: HY000

    Message: Cannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.

  • Error number: MY-012976; Symbol: ER_IB_MSG_1151; SQLSTATE: HY000

    Message: %s started; log sequence number %llu

  • Error number: MY-012977; Symbol: ER_IB_MSG_1152; SQLSTATE: HY000

    Message: Waiting for purge to complete

  • Error number: MY-012979; Symbol: ER_IB_MSG_1154; SQLSTATE: HY000

    Message: Query counter shows %lld queries still inside InnoDB at shutdown

  • Error number: MY-012980; Symbol: ER_IB_MSG_1155; SQLSTATE: HY000

    Message: Shutdown completed; log sequence number %llu

  • Error number: MY-012981; Symbol: ER_IB_MSG_1156; SQLSTATE: HY000

    Message: Cannot continue operation.

  • Error number: MY-012982; Symbol: ER_IB_MSG_1157; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012983; Symbol: ER_IB_MSG_1158; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012984; Symbol: ER_IB_MSG_1159; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012985; Symbol: ER_IB_MSG_1160; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012986; Symbol: ER_IB_MSG_1161; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012987; Symbol: ER_IB_MSG_1162; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012988; Symbol: ER_IB_MSG_1163; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012989; Symbol: ER_IB_MSG_1164; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012990; Symbol: ER_IB_MSG_1165; SQLSTATE: HY000

    Message: %s

  • Error number: MY-012991; Symbol: ER_IB_MSG_UNDO_TRUNCATE_FAIL_TO_READ_LOG_FILE; SQLSTATE: HY000

    Message: Unable to read the existing undo truncate log file '%s'. The error is %s

  • Error number: MY-012992; Symbol: ER_IB_MSG_UNDO_MARKED_FOR_TRUNCATE; SQLSTATE: HY000

    Message: Undo tablespace %s is marked for truncate

  • Error number: MY-012994; Symbol: ER_IB_MSG_UNDO_TRUNCATE_START; SQLSTATE: HY000

    Message: Truncating UNDO tablespace %s

  • Error number: MY-012996; Symbol: ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_LOG_CREATE; SQLSTATE: HY000

    Message: Cannot create truncate log for undo tablespace '%s'.

  • Error number: MY-012998; Symbol: ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_FAILURE; SQLSTATE: HY000

    Message: Failed to truncate undo tablespace '%s'.

  • Error number: MY-013000; Symbol: ER_IB_MSG_UNDO_TRUNCATE_COMPLETE; SQLSTATE: HY000

    Message: Completed truncate of undo tablespace %s.

  • Error number: MY-013002; Symbol: ER_IB_MSG_1177; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013003; Symbol: ER_IB_MSG_1178; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013004; Symbol: ER_IB_MSG_1179; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013005; Symbol: ER_IB_MSG_1180; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013006; Symbol: ER_IB_MSG_1181; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013007; Symbol: ER_IB_MSG_1182; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013008; Symbol: ER_IB_MSG_1183; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013009; Symbol: ER_IB_ERR_ACCESSING_OUT_OF_BOUND_FIELD_IN_INDEX; SQLSTATE: HY000

    Message: Trying to access update undo rec field %llu in index %s of table %s but index has only %llu fields. %s. Run also CHECK TABLE %s. n_fields = %llu, i = %llu, ptr = %p.

  • Error number: MY-013010; Symbol: ER_IB_MSG_1185; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013011; Symbol: ER_IB_MSG_1186; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013012; Symbol: ER_IB_MSG_1187; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013013; Symbol: ER_IB_MSG_1188; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013014; Symbol: ER_IB_MSG_1189; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013015; Symbol: ER_IB_MSG_TRX_RECOVERY_ROLLBACK_COMPLETED; SQLSTATE: HY000

    Message: Rollback of non-prepared transactions completed

  • Error number: MY-013016; Symbol: ER_IB_MSG_1191; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013017; Symbol: ER_IB_MSG_1192; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013018; Symbol: ER_IB_MSG_1193; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013019; Symbol: ER_IB_MSG_1194; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013020; Symbol: ER_IB_MSG_1195; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013021; Symbol: ER_IB_MSG_1196; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013022; Symbol: ER_IB_MSG_1197; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013023; Symbol: ER_IB_MSG_1198; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013024; Symbol: ER_IB_MSG_1199; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013025; Symbol: ER_IB_MSG_1200; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013026; Symbol: ER_IB_MSG_1201; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013027; Symbol: ER_IB_MSG_1202; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013028; Symbol: ER_IB_MSG_1203; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013029; Symbol: ER_IB_MSG_1204; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013030; Symbol: ER_IB_MSG_1205; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013031; Symbol: ER_IB_MSG_1206; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013032; Symbol: ER_IB_MSG_1207; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013033; Symbol: ER_IB_MSG_1208; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013034; Symbol: ER_IB_MSG_1209; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013035; Symbol: ER_IB_MSG_1210; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013036; Symbol: ER_IB_MSG_1211; SQLSTATE: HY000

    Message: Blocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.

  • Error number: MY-013037; Symbol: ER_IB_MSG_1212; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013038; Symbol: ER_IB_MSG_1213; SQLSTATE: HY000

    Message: gettimeofday() failed: %s

  • Error number: MY-013039; Symbol: ER_IB_MSG_1214; SQLSTATE: HY000

    Message: Can't create UNDO tablespace %s %s

  • Error number: MY-013040; Symbol: ER_IB_MSG_1215; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013041; Symbol: ER_IB_MSG_LOG_FILES_RESIZE_ON_START; SQLSTATE: HY000

    Message: Resizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.

  • Error number: MY-013042; Symbol: ER_IB_MSG_1217; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013043; Symbol: ER_IB_MSG_1218; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013044; Symbol: ER_IB_MSG_1219; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013045; Symbol: ER_IB_MSG_1220; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013046; Symbol: ER_IB_MSG_1221; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013047; Symbol: ER_IB_MSG_1222; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013048; Symbol: ER_IB_MSG_1223; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013049; Symbol: ER_IB_MSG_1224; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013050; Symbol: ER_IB_MSG_1225; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013051; Symbol: ER_IB_MSG_1226; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013052; Symbol: ER_IB_MSG_1227; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013053; Symbol: ER_IB_MSG_1228; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013054; Symbol: ER_IB_MSG_1229; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013056; Symbol: ER_IB_MSG_1231; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013058; Symbol: ER_IB_MSG_1233; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013059; Symbol: ER_IB_MSG_LOG_WRITER_OUT_OF_SPACE; SQLSTATE: HY000

    Message: Out of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.

  • Error number: MY-013060; Symbol: ER_IB_MSG_1235; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013061; Symbol: ER_IB_MSG_LOG_WRITER_ABORTS_LOG_ARCHIVER; SQLSTATE: HY000

    Message: Log writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.

  • Error number: MY-013062; Symbol: ER_IB_MSG_LOG_WRITER_WAITING_FOR_ARCHIVER; SQLSTATE: HY000

    Message: Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.

  • Error number: MY-013063; Symbol: ER_IB_MSG_1238; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013064; Symbol: ER_IB_MSG_1239; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013066; Symbol: ER_IB_MSG_1241; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013067; Symbol: ER_IB_MSG_LOG_FILES_CANNOT_ENCRYPT_IN_READ_ONLY; SQLSTATE: HY000

    Message: Can't set redo log files to be encrypted in read-only mode.

  • Error number: MY-013068; Symbol: ER_IB_MSG_LOG_FILES_ENCRYPTION_INIT_FAILED; SQLSTATE: HY000

    Message: Can't set redo log files to be encrypted.

  • Error number: MY-013070; Symbol: ER_IB_MSG_1245; SQLSTATE: HY000

    Message: Redo log encryption is enabled.

  • Error number: MY-013071; Symbol: ER_IB_MSG_1246; SQLSTATE: HY000

    Message: Waiting for archiver to finish archiving page and log

  • Error number: MY-013072; Symbol: ER_IB_MSG_1247; SQLSTATE: HY000

    Message: Starting shutdown...

  • Error number: MY-013073; Symbol: ER_IB_MSG_1248; SQLSTATE: HY000

    Message: Waiting for %s to exit.

  • Error number: MY-013074; Symbol: ER_IB_MSG_1249; SQLSTATE: HY000

    Message: Waiting for rollback of %zu recovered transactions, before shutdown.

  • Error number: MY-013075; Symbol: ER_IB_MSG_1250; SQLSTATE: HY000

    Message: Waiting for master thread to be suspended.

  • Error number: MY-013076; Symbol: ER_IB_MSG_1251; SQLSTATE: HY000

    Message: Waiting for page_cleaner to finish flushing of buffer pool.

  • Error number: MY-013077; Symbol: ER_IB_MSG_BUF_PENDING_IO_ON_SHUTDOWN; SQLSTATE: HY000

    Message: Shutdown is waiting for %zu buffer page I/Os to complete.

  • Error number: MY-013078; Symbol: ER_IB_MSG_1253; SQLSTATE: HY000

    Message: MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!

  • Error number: MY-013080; Symbol: ER_IB_MSG_1255; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013081; Symbol: ER_IB_MSG_1256; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013082; Symbol: ER_IB_MSG_1257; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013083; Symbol: ER_IB_MSG_1258; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013084; Symbol: ER_IB_MSG_1259; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013085; Symbol: ER_IB_MSG_1260; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013086; Symbol: ER_IB_MSG_1261; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013087; Symbol: ER_IB_MSG_1262; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013088; Symbol: ER_IB_MSG_1263; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013089; Symbol: ER_IB_MSG_LOG_FILE_HEADER_INVALID_CHECKSUM; SQLSTATE: HY000

    Message: Invalid redo log header checksum.

  • Error number: MY-013090; Symbol: ER_IB_MSG_LOG_FORMAT_BEFORE_5_7_9; SQLSTATE: HY000

    Message: Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9

  • Error number: MY-013091; Symbol: ER_IB_MSG_1266; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013092; Symbol: ER_IB_MSG_LOG_PARAMS_CONCURRENCY_MARGIN_UNSAFE; SQLSTATE: HY000

    Message: Cannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s

  • Error number: MY-013093; Symbol: ER_IB_MSG_1268; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013094; Symbol: ER_IB_MSG_1269; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013095; Symbol: ER_IB_MSG_THREAD_CONCURRENCY_CHANGED; SQLSTATE: HY000

    Message: User has set innodb_thread_concurrency to %lu.

  • Error number: MY-013096; Symbol: ER_RPL_REPLICA_SQL_THREAD_STOP_CMD_EXEC_TIMEOUT; SQLSTATE: HY000

    Message: STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.

  • Error number: MY-013097; Symbol: ER_RPL_REPLICA_IO_THREAD_STOP_CMD_EXEC_TIMEOUT; SQLSTATE: HY000

    Message: STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.

  • Error number: MY-013098; Symbol: ER_RPL_GTID_UNSAFE_STMT_ON_NON_TRANS_TABLE; SQLSTATE: HY000

    Message: Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

  • Error number: MY-013099; Symbol: ER_RPL_GTID_UNSAFE_STMT_CREATE_SELECT; SQLSTATE: HY000

    Message: Statement violates GTID consistency: CREATE TABLE ... SELECT.

  • Error number: MY-013101; Symbol: ER_BINLOG_ROW_VALUE_OPTION_IGNORED; SQLSTATE: HY000

    Message: When %s, the option binlog_row_value_options=%s will be ignored and updates will be written in full format to binary log.

  • Error number: MY-013103; Symbol: ER_BINLOG_ROW_VALUE_OPTION_USED_ONLY_FOR_AFTER_IMAGES; SQLSTATE: HY000

    Message: When %s, the option binlog_row_value_options=%s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.

  • Error number: MY-013104; Symbol: ER_CONNECTION_ABORTED; SQLSTATE: HY000

    Message: Aborted connection %u to db: '%s' user: '%s' host: '%s' (%s).

  • Error number: MY-013105; Symbol: ER_NORMAL_SERVER_SHUTDOWN; SQLSTATE: HY000

    Message: %s: Normal shutdown.

  • Error number: MY-013106; Symbol: ER_KEYRING_MIGRATE_FAILED; SQLSTATE: HY000

    Message: Can not perform keyring migration : %s.

  • Error number: MY-013107; Symbol: ER_GRP_RPL_LOWER_CASE_TABLE_NAMES_DIFF_FROM_GRP; SQLSTATE: HY000

    Message: The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.

  • Error number: MY-013108; Symbol: ER_OOM_SAVE_GTIDS; SQLSTATE: HY000

    Message: An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed table

  • Error number: MY-013109; Symbol: ER_LCTN_NOT_FOUND; SQLSTATE: HY000

    Message: The lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.

  • Error number: MY-013111; Symbol: ER_COMPONENT_FILTER_WRONG_VALUE; SQLSTATE: HY000

    Message: Variable '%s' can't be set to the value of '%s'

  • Error number: MY-013112; Symbol: ER_XPLUGIN_FAILED_TO_STOP_SERVICES; SQLSTATE: HY000

    Message: Stopping services failed with error "%s"

  • Error number: MY-013113; Symbol: ER_INCONSISTENT_ERROR; SQLSTATE: HY000

    Message: Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'

  • Error number: MY-013114; Symbol: ER_SERVER_SOURCE_FATAL_ERROR_READING_BINLOG; SQLSTATE: HY000

    Message: Got fatal error %d from source when reading data from binary log: '%s'

  • Error number: MY-013115; Symbol: ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE; SQLSTATE: HY000

    Message: Replication event checksum verification failed while reading from network.

  • Error number: MY-013116; Symbol: ER_REPLICA_CREATE_EVENT_FAILURE; SQLSTATE: HY000

    Message: Failed to create %s

  • Error number: MY-013117; Symbol: ER_REPLICA_FATAL_ERROR; SQLSTATE: HY000

    Message: Fatal error: %s

  • Error number: MY-013118; Symbol: ER_REPLICA_HEARTBEAT_FAILURE; SQLSTATE: HY000

    Message: Unexpected source's heartbeat data: %s

  • Error number: MY-013119; Symbol: ER_REPLICA_INCIDENT; SQLSTATE: HY000

    Message: The incident %s occurred on the source. Message: %s

  • Error number: MY-013120; Symbol: ER_REPLICA_SOURCE_COM_FAILURE; SQLSTATE: HY000

    Message: Source command %s failed: %s

  • Error number: MY-013121; Symbol: ER_REPLICA_RELAY_LOG_READ_FAILURE; SQLSTATE: HY000

    Message: Relay log read failure: %s

  • Error number: MY-013122; Symbol: ER_REPLICA_RELAY_LOG_WRITE_FAILURE; SQLSTATE: HY000

    Message: Relay log write failure: %s

  • Error number: MY-013123; Symbol: ER_SERVER_REPLICA_CM_INIT_REPOSITORY; SQLSTATE: HY000

    Message: Replica failed to initialize connection metadata structure from the repository

  • Error number: MY-013124; Symbol: ER_SERVER_REPLICA_AM_INIT_REPOSITORY; SQLSTATE: HY000

    Message: Replica failed to initialize applier metadata structure from the repository

  • Error number: MY-013125; Symbol: ER_SERVER_NET_PACKET_TOO_LARGE; SQLSTATE: HY000

    Message: Got a packet bigger than 'max_allowed_packet' bytes

  • Error number: MY-013126; Symbol: ER_SERVER_NO_SYSTEM_TABLE_ACCESS; SQLSTATE: HY000

    Message: Access to %s '%s.%s' is rejected.

  • Error number: MY-013128; Symbol: ER_SERVER_UNKNOWN_SYSTEM_VARIABLE; SQLSTATE: HY000

    Message: Unknown system variable '%s'

  • Error number: MY-013129; Symbol: ER_SERVER_NO_SESSION_TO_SEND_TO; SQLSTATE: HY000

    Message: A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %s

  • Error number: MY-013130; Symbol: ER_SERVER_NEW_ABORTING_CONNECTION; SQLSTATE: 08S01

    Message: Aborted connection %u to db: '%s' user: '%s' host: '%s' (%s; diagnostics area: MY-%06d - %s)

  • Error number: MY-013131; Symbol: ER_SERVER_OUT_OF_SORTMEMORY; SQLSTATE: HY000

    Message: Out of sort memory, consider increasing server sort buffer size!

  • Error number: MY-013132; Symbol: ER_SERVER_RECORD_FILE_FULL; SQLSTATE: HY000

    Message: The table '%s' is full!

  • Error number: MY-013133; Symbol: ER_SERVER_DISK_FULL_NOWAIT; SQLSTATE: HY000

    Message: Create table/tablespace '%s' failed, as disk is full.

  • Error number: MY-013134; Symbol: ER_SERVER_HANDLER_ERROR; SQLSTATE: HY000

    Message: Handler reported error %d - %s

  • Error number: MY-013135; Symbol: ER_SERVER_NOT_FORM_FILE; SQLSTATE: HY000

    Message: Incorrect information in file: '%s'

  • Error number: MY-013136; Symbol: ER_SERVER_CANT_OPEN_FILE; SQLSTATE: HY000

    Message: Can't open file: '%s' (OS errno: %d - %s)

  • Error number: MY-013137; Symbol: ER_SERVER_FILE_NOT_FOUND; SQLSTATE: HY000

    Message: Can't find file: '%s' (OS errno: %d - %s)

  • Error number: MY-013138; Symbol: ER_SERVER_FILE_USED; SQLSTATE: HY000

    Message: '%s' is locked against change (OS errno: %d - %s)

  • Error number: MY-013139; Symbol: ER_SERVER_CANNOT_LOAD_FROM_TABLE_V2; SQLSTATE: HY000

    Message: Cannot load from %s.%s. The table is probably corrupted!

  • Error number: MY-013140; Symbol: ER_ERROR_INFO_FROM_DA; SQLSTATE: HY000

    Message: Error in diagnostics area: MY-%06d - %s

  • Error number: MY-013141; Symbol: ER_SERVER_TABLE_CHECK_FAILED; SQLSTATE: HY000

    Message: Incorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.

  • Error number: MY-013142; Symbol: ER_SERVER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2; SQLSTATE: HY000

    Message: The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.

  • Error number: MY-013143; Symbol: ER_SERVER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2; SQLSTATE: HY000

    Message: Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted.

  • Error number: MY-013144; Symbol: ER_SERVER_ACL_TABLE_ERROR; SQLSTATE: HY000

    Message:

  • Error number: MY-013145; Symbol: ER_SERVER_REPLICA_INIT_QUERY_FAILED; SQLSTATE: HY000

    Message: Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'

  • Error number: MY-013146; Symbol: ER_SERVER_REPLICA_CONVERSION_FAILED; SQLSTATE: HY000

    Message: Column %d (counting the first column as number 1) of table '%s.%s' cannot be converted from type '%s' to type '%s'

  • Error number: MY-013147; Symbol: ER_SERVER_REPLICA_IGNORED_TABLE; SQLSTATE: HY000

    Message: Replica SQL thread ignored the query because of replicate-*-table rules

  • Error number: MY-013148; Symbol: ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION; SQLSTATE: HY000

    Message: Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %s, position %lld.

  • Error number: MY-013149; Symbol: ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON; SQLSTATE: HY000

    Message: Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %s, position %lld.

  • Error number: MY-013150; Symbol: ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF; SQLSTATE: HY000

    Message: Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %s, position %lld.

  • Error number: MY-013151; Symbol: ER_SERVER_TEST_MESSAGE; SQLSTATE: HY000

    Message: Simulated error

  • Error number: MY-013152; Symbol: ER_AUDIT_LOG_JSON_FILTER_PARSING_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013153; Symbol: ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED; SQLSTATE: HY000

    Message: Audit Log filtering has not been installed.

  • Error number: MY-013154; Symbol: ER_PLUGIN_FAILED_TO_OPEN_TABLES; SQLSTATE: HY000

    Message: Failed to open the %s filter tables.

  • Error number: MY-013155; Symbol: ER_PLUGIN_FAILED_TO_OPEN_TABLE; SQLSTATE: HY000

    Message: Failed to open '%s.%s' %s table.

  • Error number: MY-013156; Symbol: ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY; SQLSTATE: HY000

    Message: Filter name cannot be empty.

  • Error number: MY-013157; Symbol: ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER; SQLSTATE: HY000

    Message: Invalid character in the user name.

  • Error number: MY-013158; Symbol: ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE; SQLSTATE: HY000

    Message: Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operation

  • Error number: MY-013159; Symbol: ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED; SQLSTATE: HY000

    Message: No keyring installed.

  • Error number: MY-013160; Symbol: ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER; SQLSTATE: HY000

    Message: Invalid character in the host name.

  • Error number: MY-013161; Symbol: ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET; SQLSTATE: HY000

    Message: Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.

  • Error number: MY-013162; Symbol: ER_AUDIT_LOG_COULD_NOT_CREATE_AES_KEY; SQLSTATE: HY000

    Message: Could not create AES key. OpenSSL's EVP_BytesToKey function failed.

  • Error number: MY-013163; Symbol: ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED; SQLSTATE: HY000

    Message: Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.

  • Error number: MY-013164; Symbol: ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS; SQLSTATE: HY000

    Message: Could not reinitialize audit log filters.

  • Error number: MY-013165; Symbol: ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY; SQLSTATE: HY000

    Message: User cannot be empty.

  • Error number: MY-013166; Symbol: ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC; SQLSTATE: HY000

    Message: First character of the user name must be alphanumeric.

  • Error number: MY-013167; Symbol: ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Specified filter has not been found.

  • Error number: MY-013169; Symbol: ER_STARTING_INIT; SQLSTATE: HY000

    Message: %s (mysqld %s) initializing of server in progress as process %lu

  • Error number: MY-013170; Symbol: ER_ENDING_INIT; SQLSTATE: HY000

    Message: %s (mysqld %s) initializing of server has completed

  • Error number: MY-013171; Symbol: ER_IB_MSG_1272; SQLSTATE: HY000

    Message: Cannot boot server version %lu on data directory built by version %llu. Downgrade is not supported

  • Error number: MY-013172; Symbol: ER_SERVER_SHUTDOWN_INFO; SQLSTATE: HY000

    Message: Received SHUTDOWN from user %s. Shutting down mysqld (Version: %s).

  • Error number: MY-013173; Symbol: ER_GRP_RPL_PLUGIN_ABORT; SQLSTATE: HY000

    Message: The plugin encountered a critical error and will abort: %s

  • Error number: MY-013177; Symbol: ER_AUDIT_LOG_TABLE_DEFINITION_NOT_UPDATED; SQLSTATE: HY000

    Message: '%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.

  • Error number: MY-013178; Symbol: ER_DD_INITIALIZE_SQL_ERROR; SQLSTATE: HY000

    Message: Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.

  • Error number: MY-013179; Symbol: ER_NO_PATH_FOR_SHARED_LIBRARY; SQLSTATE: HY000

    Message: No paths allowed for shared library.

  • Error number: MY-013180; Symbol: ER_UDF_ALREADY_EXISTS; SQLSTATE: HY000

    Message: Function '%s' already exists.

  • Error number: MY-013181; Symbol: ER_SET_EVENT_FAILED; SQLSTATE: HY000

    Message: Got Error: %ld from SetEvent.

  • Error number: MY-013182; Symbol: ER_FAILED_TO_ALLOCATE_SSL_BIO; SQLSTATE: HY000

    Message: Error allocating SSL BIO.

  • Error number: MY-013183; Symbol: ER_IB_MSG_1273; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013184; Symbol: ER_PID_FILEPATH_LOCATIONS_INACCESSIBLE; SQLSTATE: HY000

    Message: One or several locations were inaccessible while checking PID filepath.

  • Error number: MY-013185; Symbol: ER_UNKNOWN_VARIABLE_IN_PERSISTED_CONFIG_FILE; SQLSTATE: HY000

    Message: Currently unknown variable '%s' was read from the persisted config file.

  • Error number: MY-013186; Symbol: ER_FAILED_TO_HANDLE_DEFAULTS_FILE; SQLSTATE: HY000

    Message: Fatal error in defaults handling. Program aborted!

  • Error number: MY-013187; Symbol: ER_DUPLICATE_SYS_VAR; SQLSTATE: HY000

    Message: Duplicate variable name '%s'.

  • Error number: MY-013188; Symbol: ER_FAILED_TO_INIT_SYS_VAR; SQLSTATE: HY000

    Message: Failed to initialize system variables.

  • Error number: MY-013189; Symbol: ER_SYS_VAR_NOT_FOUND; SQLSTATE: HY000

    Message: Variable name '%s' not found.

  • Error number: MY-013190; Symbol: ER_IB_MSG_1274; SQLSTATE: HY000

    Message: Some (%d) threads are still active

  • Error number: MY-013191; Symbol: ER_IB_MSG_1275; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013193; Symbol: ER_IB_MSG_WAIT_FOR_ENCRYPT_THREAD; SQLSTATE: HY000

    Message: Waiting for tablespace_alter_encrypt_thread to exit

  • Error number: MY-013194; Symbol: ER_IB_MSG_1277; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013195; Symbol: ER_IB_MSG_NO_ENCRYPT_PROGRESS_FOUND; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013196; Symbol: ER_IB_MSG_RESUME_OP_FOR_SPACE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013197; Symbol: ER_IB_MSG_1280; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013198; Symbol: ER_IB_MSG_1281; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013199; Symbol: ER_IB_MSG_1282; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013200; Symbol: ER_IB_MSG_1283; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013201; Symbol: ER_IB_MSG_1284; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013202; Symbol: ER_CANT_SET_ERROR_SUPPRESSION_LIST_FROM_COMMAND_LINE; SQLSTATE: HY000

    Message: %s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.

  • Error number: MY-013203; Symbol: ER_INVALID_VALUE_OF_BIND_ADDRESSES; SQLSTATE: HY000

    Message: Invalid value for command line option bind-addresses: '%s'

  • Error number: MY-013204; Symbol: ER_RELAY_LOG_SPACE_LIMIT_DISABLED; SQLSTATE: HY000

    Message: Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.

  • Error number: MY-013205; Symbol: ER_GRP_RPL_ERROR_GTID_SET_EXTRACTION; SQLSTATE: HY000

    Message: Error when extracting GTID execution information: %s

  • Error number: MY-013206; Symbol: ER_GRP_RPL_MISSING_GRP_RPL_ACTION_COORDINATOR; SQLSTATE: HY000

    Message: Message received without a proper group coordinator module.

  • Error number: MY-013207; Symbol: ER_GRP_RPL_JOIN_WHEN_GROUP_ACTION_RUNNING; SQLSTATE: HY000

    Message: A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.

  • Error number: MY-013208; Symbol: ER_GRP_RPL_JOINER_EXIT_WHEN_GROUP_ACTION_RUNNING; SQLSTATE: HY000

    Message: A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.

  • Error number: MY-013209; Symbol: ER_GRP_RPL_CHANNEL_THREAD_WHEN_GROUP_ACTION_RUNNING; SQLSTATE: HY000

    Message: Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.

  • Error number: MY-013210; Symbol: ER_GRP_RPL_APPOINTED_PRIMARY_NOT_PRESENT; SQLSTATE: HY000

    Message: A primary election was invoked but the requested primary member is not in the group. Request ignored.

  • Error number: MY-013211; Symbol: ER_GRP_RPL_ERROR_ON_MESSAGE_SENDING; SQLSTATE: HY000

    Message: Error while sending message. Context: %s

  • Error number: MY-013212; Symbol: ER_GRP_RPL_CONFIGURATION_ACTION_ERROR; SQLSTATE: HY000

    Message: Error while executing a group configuration operation: %s

  • Error number: MY-013213; Symbol: ER_GRP_RPL_CONFIGURATION_ACTION_LOCAL_TERMINATION; SQLSTATE: HY000

    Message: Configuration operation '%s' terminated. %s

  • Error number: MY-013214; Symbol: ER_GRP_RPL_CONFIGURATION_ACTION_START; SQLSTATE: HY000

    Message: Starting group operation local execution: %s

  • Error number: MY-013215; Symbol: ER_GRP_RPL_CONFIGURATION_ACTION_END; SQLSTATE: HY000

    Message: Termination of group operation local execution: %s

  • Error number: MY-013216; Symbol: ER_GRP_RPL_CONFIGURATION_ACTION_KILLED_ERROR; SQLSTATE: HY000

    Message: A configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.

  • Error number: MY-013217; Symbol: ER_GRP_RPL_PRIMARY_ELECTION_PROCESS_ERROR; SQLSTATE: HY000

    Message: There was an issue on the primary election process: %s The member will now leave the group.

  • Error number: MY-013218; Symbol: ER_GRP_RPL_PRIMARY_ELECTION_STOP_ERROR; SQLSTATE: HY000

    Message: There was an issue when stopping a previous election process: %s

  • Error number: MY-013219; Symbol: ER_GRP_RPL_NO_STAGE_SERVICE; SQLSTATE: HY000

    Message: It was not possible to initialize stage logging for this task. The operation will still run without stage tracking.

  • Error number: MY-013220; Symbol: ER_GRP_RPL_UDF_REGISTER_ERROR; SQLSTATE: HY000

    Message: Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove it

  • Error number: MY-013221; Symbol: ER_GRP_RPL_UDF_UNREGISTER_ERROR; SQLSTATE: HY000

    Message: Could not uninstall Group Replication UDF functions. Try to remove them manually if present.

  • Error number: MY-013222; Symbol: ER_GRP_RPL_UDF_REGISTER_SERVICE_ERROR; SQLSTATE: HY000

    Message: Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the plugin

  • Error number: MY-013223; Symbol: ER_GRP_RPL_SERVER_UDF_ERROR; SQLSTATE: HY000

    Message: The function '%s' failed. %s

  • Error number: MY-013227; Symbol: ER_SERVER_WRONG_VALUE_FOR_VAR; SQLSTATE: HY000

    Message: Variable '%s' can't be set to the value of '%s'

  • Error number: MY-013228; Symbol: ER_COULD_NOT_CREATE_WINDOWS_REGISTRY_KEY; SQLSTATE: HY000

    Message: %s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.

  • Error number: MY-013229; Symbol: ER_SERVER_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRX_IN_SBR; SQLSTATE: HY000

    Message: Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.

  • Error number: MY-013233; Symbol: ER_XPLUGIN_FAILED_TO_SWITCH_SECURITY_CTX; SQLSTATE: HY000

    Message: Unable to switch security context to user: %s

  • Error number: MY-013234; Symbol: ER_RPL_GTID_UNSAFE_ALTER_ADD_COL_WITH_DEFAULT_EXPRESSION; SQLSTATE: HY000

    Message: Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.

  • Error number: MY-013235; Symbol: ER_UPGRADE_PARSE_ERROR; SQLSTATE: HY000

    Message: Error in parsing %s '%s'.'%s' during upgrade. %s

  • Error number: MY-013236; Symbol: ER_DATA_DIRECTORY_UNUSABLE; SQLSTATE: HY000

    Message: The designated data directory %s is unusable. You can remove all files that the server added to it.

  • Error number: MY-013237; Symbol: ER_LDAP_AUTH_USER_GROUP_SEARCH_ROOT_BIND; SQLSTATE: HY000

    Message: Group search rebinding via root DN: %s

  • Error number: MY-013238; Symbol: ER_PLUGIN_INSTALL_ERROR; SQLSTATE: HY000

    Message: Error installing plugin '%s': %s

  • Error number: MY-013239; Symbol: ER_PLUGIN_UNINSTALL_ERROR; SQLSTATE: HY000

    Message: Error uninstalling plugin '%s': %s

  • Error number: MY-013240; Symbol: ER_SHARED_TABLESPACE_USED_BY_PARTITIONED_TABLE; SQLSTATE: HY000

    Message: Partitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.

  • Error number: MY-013241; Symbol: ER_UNKNOWN_TABLESPACE_TYPE; SQLSTATE: HY000

    Message: Cannot determine the type of the tablespace named '%s'.

  • Error number: MY-013242; Symbol: ER_WARN_DEPRECATED_UTF8_ALIAS_OPTION; SQLSTATE: HY000

    Message: %s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.

  • Error number: MY-013243; Symbol: ER_WARN_DEPRECATED_UTF8MB3_CHARSET_OPTION; SQLSTATE: HY000

    Message: %s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.

  • Error number: MY-013244; Symbol: ER_WARN_DEPRECATED_UTF8MB3_COLLATION_OPTION; SQLSTATE: HY000

    Message: %s: '%s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.

  • Error number: MY-013245; Symbol: ER_SSL_MEMORY_INSTRUMENTATION_INIT_FAILED; SQLSTATE: HY000

    Message: The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.

  • Error number: MY-013246; Symbol: ER_IB_MSG_MADV_DONTDUMP_UNSUPPORTED; SQLSTATE: HY000

    Message: Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platform

  • Error number: MY-013247; Symbol: ER_IB_MSG_MADVISE_FAILED; SQLSTATE: HY000

    Message: Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %s

  • Error number: MY-013249; Symbol: ER_WARN_REMOVED_SQL_MODE; SQLSTATE: HY000

    Message: sql_mode=0x%08x has been removed and will be ignored

  • Error number: MY-013250; Symbol: ER_IB_MSG_FAILED_TO_ALLOCATE_WAIT; SQLSTATE: HY000

    Message: Failed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.

  • Error number: MY-013252; Symbol: ER_IB_MSG_USING_UNDO_SPACE; SQLSTATE: HY000

    Message: Using undo tablespace '%s'.

  • Error number: MY-013253; Symbol: ER_IB_MSG_FAIL_TO_SAVE_SPACE_STATE; SQLSTATE: HY000

    Message: %s Unable to save the current state of tablespace '%s' to the data dictionary

  • Error number: MY-013254; Symbol: ER_IB_MSG_MAX_UNDO_SPACES_REACHED; SQLSTATE: HY000

    Message: Cannot create undo tablespace %s at %s because %d undo tablespaces already exist.

  • Error number: MY-013255; Symbol: ER_IB_MSG_ERROR_OPENING_NEW_UNDO_SPACE; SQLSTATE: HY000

    Message: Error %d opening newly created undo tablespace %s.

  • Error number: MY-013256; Symbol: ER_IB_MSG_FAILED_SDI_Z_BUF_ERROR; SQLSTATE: HY000

    Message: SDI Compression failed, Z_BUF_ERROR

  • Error number: MY-013257; Symbol: ER_IB_MSG_FAILED_SDI_Z_MEM_ERROR; SQLSTATE: HY000

    Message: SDI Compression failed, Z_MEM_ERROR

  • Error number: MY-013258; Symbol: ER_IB_MSG_SDI_Z_STREAM_ERROR; SQLSTATE: HY000

    Message: SDI Compression failed, Z_STREAM_ERROR

  • Error number: MY-013259; Symbol: ER_IB_MSG_SDI_Z_UNKNOWN_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013260; Symbol: ER_IB_MSG_FOUND_WRONG_UNDO_SPACE; SQLSTATE: HY000

    Message: Expected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead! Did you change innodb_undo_directory?

  • Error number: MY-013261; Symbol: ER_IB_MSG_NOT_END_WITH_IBU; SQLSTATE: HY000

    Message: Cannot use %s as an undo tablespace because it does not end with '.ibu'.

  • Error number: MY-013266; Symbol: ER_IB_MSG_FAILED_TO_FINISH_TRUNCATE; SQLSTATE: HY000

    Message: %s Failed to finish truncating Undo Tablespace '%s'

  • Error number: MY-013267; Symbol: ER_IB_MSG_DEPRECATED_INNODB_UNDO_TABLESPACES; SQLSTATE: HY000

    Message: The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used. InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.

  • Error number: MY-013268; Symbol: ER_IB_MSG_WRONG_TABLESPACE_DIR; SQLSTATE: HY000

    Message: The directory for tablespace %s does not exist or is incorrect.

  • Error number: MY-013269; Symbol: ER_IB_MSG_LOCK_FREE_HASH_USAGE_STATS; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013270; Symbol: ER_CLONE_DONOR_TRACE; SQLSTATE: HY000

    Message: Clone donor reported : %s.

  • Error number: MY-013271; Symbol: ER_CLONE_PROTOCOL_TRACE; SQLSTATE: HY000

    Message: Clone received unexpected response from donor : %s.

  • Error number: MY-013272; Symbol: ER_CLONE_CLIENT_TRACE; SQLSTATE: HY000

    Message: Client: %s.

  • Error number: MY-013273; Symbol: ER_CLONE_SERVER_TRACE; SQLSTATE: HY000

    Message: Server: %s.

  • Error number: MY-013274; Symbol: ER_THREAD_POOL_PFS_TABLES_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to initialize the performance schema tables service.

  • Error number: MY-013275; Symbol: ER_THREAD_POOL_PFS_TABLES_ADD_FAILED; SQLSTATE: HY000

    Message: Failed to add thread pool performance schema tables.

  • Error number: MY-013276; Symbol: ER_CANT_SET_DATA_DIR; SQLSTATE: HY000

    Message: Failed to set datadir to \'%s\' (OS errno: %d - %s)

  • Error number: MY-013277; Symbol: ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY_LOCATION; SQLSTATE: HY000

    Message: The innodb_undo_directory is not allowed to be an ancestor of the datadir.

  • Error number: MY-013278; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_FETCH_KEY; SQLSTATE: HY000

    Message: Failed to fetch key from keyring, please check if keyring is loaded.

  • Error number: MY-013279; Symbol: ER_SERVER_RPL_ENCRYPTION_KEY_NOT_FOUND; SQLSTATE: HY000

    Message: Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.

  • Error number: MY-013280; Symbol: ER_SERVER_RPL_ENCRYPTION_KEYRING_INVALID_KEY; SQLSTATE: HY000

    Message: Fetched an invalid key from keyring.

  • Error number: MY-013281; Symbol: ER_SERVER_RPL_ENCRYPTION_HEADER_ERROR; SQLSTATE: HY000

    Message: Error reading a replication log encryption header: %s.

  • Error number: MY-013282; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ROTATE_LOGS; SQLSTATE: HY000

    Message: Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.

  • Error number: MY-013283; Symbol: ER_SERVER_RPL_ENCRYPTION_KEY_EXISTS_UNEXPECTED; SQLSTATE: HY000

    Message: Key %s exists unexpected.

  • Error number: MY-013284; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_GENERATE_KEY; SQLSTATE: HY000

    Message: Failed to generate key, please check if keyring is loaded.

  • Error number: MY-013285; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_STORE_KEY; SQLSTATE: HY000

    Message: Failed to store key, please check if keyring is loaded.

  • Error number: MY-013286; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_REMOVE_KEY; SQLSTATE: HY000

    Message: Failed to remove key, please check if keyring is loaded.

  • Error number: MY-013287; Symbol: ER_SERVER_RPL_ENCRYPTION_MASTER_KEY_RECOVERY_FAILED; SQLSTATE: HY000

    Message: Unable to recover binlog encryption master key, please check if keyring is loaded.

  • Error number: MY-013288; Symbol: ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_INITIALIZE; SQLSTATE: HY000

    Message: Failed to initialize binlog encryption, please check if keyring is loaded.

  • Error number: MY-013289; Symbol: ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_ROTATE_MASTER_KEY_AT_STARTUP; SQLSTATE: HY000

    Message: Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.

  • Error number: MY-013290; Symbol: ER_SERVER_RPL_ENCRYPTION_IGNORE_ROTATE_MASTER_KEY_AT_STARTUP; SQLSTATE: HY000

    Message: Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.

  • Error number: MY-013291; Symbol: ER_INVALID_ADMIN_ADDRESS; SQLSTATE: HY000

    Message: Invalid value for command line option admin-address: '%s'

  • Error number: MY-013292; Symbol: ER_SERVER_STARTUP_ADMIN_INTERFACE; SQLSTATE: HY000

    Message: Admin interface ready for connections, address: '%s' port: %d

  • Error number: MY-013293; Symbol: ER_CANT_CREATE_ADMIN_THREAD; SQLSTATE: HY000

    Message: Can't create thread to handle admin connections (errno= %d)

  • Error number: MY-013294; Symbol: ER_WARNING_RETAIN_CURRENT_PASSWORD_CLAUSE_VOID; SQLSTATE: HY000

    Message: RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.

  • Error number: MY-013295; Symbol: ER_WARNING_DISCARD_OLD_PASSWORD_CLAUSE_VOID; SQLSTATE: HY000

    Message: DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.

  • Error number: MY-013299; Symbol: ER_WARNING_AUTHCACHE_INVALID_USER_ATTRIBUTES; SQLSTATE: HY000

    Message: Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.

  • Error number: MY-013300; Symbol: ER_MYSQL_NATIVE_PASSWORD_SECOND_PASSWORD_USED_INFORMATION; SQLSTATE: HY000

    Message: Second password was used for login by user: '%s'@'%s'.

  • Error number: MY-013301; Symbol: ER_SHA256_PASSWORD_SECOND_PASSWORD_USED_INFORMATION; SQLSTATE: HY000

    Message: Second password was used for login by user: '%s'@'%s'.

  • Error number: MY-013302; Symbol: ER_CACHING_SHA2_PASSWORD_SECOND_PASSWORD_USED_INFORMATION; SQLSTATE: HY000

    Message: Second password was used for login by user: '%s'@'%s'.

  • Error number: MY-013303; Symbol: ER_GRP_RPL_SEND_TRX_PREPARED_MESSAGE_FAILED; SQLSTATE: HY000

    Message: Error sending transaction '%s:%lld' prepared message from session '%u'.

  • Error number: MY-013304; Symbol: ER_GRP_RPL_RELEASE_COMMIT_AFTER_GROUP_PREPARE_FAILED; SQLSTATE: HY000

    Message: Error releasing transaction '%s:%lld' for commit on session '%u' after being prepared on all group members.

  • Error number: MY-013305; Symbol: ER_GRP_RPL_TRX_ALREADY_EXISTS_ON_TCM_ON_AFTER_CERTIFICATION; SQLSTATE: HY000

    Message: Transaction '%s:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.

  • Error number: MY-013306; Symbol: ER_GRP_RPL_FAILED_TO_INSERT_TRX_ON_TCM_ON_AFTER_CERTIFICATION; SQLSTATE: HY000

    Message: Error registering transaction '%s:%lld' on Group Replication consistency manager after conflict detection.

  • Error number: MY-013307; Symbol: ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_GROUP_PREPARE_FAILED; SQLSTATE: HY000

    Message: Error registering transaction '%s:%lld' from session '%u' to wait for being prepared on all group members.

  • Error number: MY-013308; Symbol: ER_GRP_RPL_TRX_WAIT_FOR_GROUP_PREPARE_FAILED; SQLSTATE: HY000

    Message: Error on transaction '%s:%lld' from session '%u' while waiting for being prepared on all group members.

  • Error number: MY-013309; Symbol: ER_GRP_RPL_TRX_DOES_NOT_EXIST_ON_TCM_ON_HANDLE_REMOTE_PREPARE; SQLSTATE: HY000

    Message: Transaction '%s:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.

  • Error number: MY-013310; Symbol: ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_DEPENDENCIES_COMMIT_FAILED; SQLSTATE: HY000

    Message: Error releasing transaction '%s:%lld' for execution on session '%u' after its dependencies did complete commit.

  • Error number: MY-013311; Symbol: ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_DEPENDENCIES_FAILED; SQLSTATE: HY000

    Message: Error registering transaction from session '%u' to wait for its dependencies to complete commit.

  • Error number: MY-013312; Symbol: ER_GRP_RPL_WAIT_FOR_DEPENDENCIES_FAILED; SQLSTATE: HY000

    Message: Error on session '%u' while waiting for its dependencies to complete commit.

  • Error number: MY-013313; Symbol: ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED; SQLSTATE: HY000

    Message: Error registering transaction from session '%u' to wait for sync before execution.

  • Error number: MY-013314; Symbol: ER_GRP_RPL_SEND_TRX_SYNC_BEFORE_EXECUTION_FAILED; SQLSTATE: HY000

    Message: Error sending sync before execution message from session '%u'.

  • Error number: MY-013315; Symbol: ER_GRP_RPL_TRX_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED; SQLSTATE: HY000

    Message: Error on transaction from session '%u' while waiting for sync before execution.

  • Error number: MY-013316; Symbol: ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_WAIT_FOR_SYNC_BEFORE_EXEC; SQLSTATE: HY000

    Message: Error releasing transaction for execution on session '%u' after wait for sync before execution.

  • Error number: MY-013317; Symbol: ER_GRP_RPL_TRX_WAIT_FOR_GROUP_GTID_EXECUTED; SQLSTATE: HY000

    Message: Error waiting for group executed transactions commit on session '%u'.

  • Error number: MY-013320; Symbol: ER_WARN_PROPERTY_STRING_PARSE_FAILED; SQLSTATE: HY000

    Message: Could not parse key-value pairs in property string '%s'

  • Error number: MY-013321; Symbol: ER_INVALID_PROPERTY_KEY; SQLSTATE: HY000

    Message: Property key '%s' is invalid.

  • Error number: MY-013322; Symbol: ER_GRP_RPL_GTID_SET_EXTRACT_ERROR_DURING_RECOVERY; SQLSTATE: HY000

    Message: Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.

  • Error number: MY-013323; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ENCRYPT; SQLSTATE: HY000

    Message: Failed to encrypt content to write into binlog file: %s.

  • Error number: MY-013324; Symbol: ER_CANNOT_GET_SERVER_VERSION_FROM_TABLESPACE_HEADER; SQLSTATE: HY000

    Message: Cannot get the server version number from the dictionary tablespace header.

  • Error number: MY-013325; Symbol: ER_CANNOT_SET_SERVER_VERSION_IN_TABLESPACE_HEADER; SQLSTATE: HY000

    Message: Cannot set the server version number in the dictionary tablespace header.

  • Error number: MY-013326; Symbol: ER_SERVER_UPGRADE_VERSION_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Upgrading the server from server version '%u' is not supported.

  • Error number: MY-013327; Symbol: ER_SERVER_UPGRADE_FROM_VERSION; SQLSTATE: HY000

    Message: MySQL server upgrading from version '%u' to '%u'.

  • Error number: MY-013328; Symbol: ER_GRP_RPL_ERROR_ON_CERT_DB_INSTALL; SQLSTATE: HY000

    Message: The certification information could not be set in this server: '%s'

  • Error number: MY-013329; Symbol: ER_GRP_RPL_FORCE_MEMBERS_WHEN_LEAVING; SQLSTATE: HY000

    Message: A request to force a new group membership was issued when the member is leaving the group.

  • Error number: MY-013330; Symbol: ER_TRG_WRONG_ORDER; SQLSTATE: HY000

    Message: Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.

  • Error number: MY-013332; Symbol: ER_LDAP_AUTH_GRP_SEARCH_NOT_SPECIAL_HDL; SQLSTATE: HY000

    Message: Special handling for group search, {GA} not found

  • Error number: MY-013333; Symbol: ER_LDAP_AUTH_GRP_USER_OBJECT_HAS_GROUP_INFO; SQLSTATE: HY000

    Message: User group retrieval: User object has group information

  • Error number: MY-013334; Symbol: ER_LDAP_AUTH_GRP_INFO_FOUND_IN_MANY_OBJECTS; SQLSTATE: HY000

    Message: Group information found in multiple user objects. Search filter configuration is incorrect.

  • Error number: MY-013335; Symbol: ER_LDAP_AUTH_GRP_INCORRECT_ATTRIBUTE; SQLSTATE: HY000

    Message: User group retrieval: no group attribute found. Incorrect group search attribute.

  • Error number: MY-013336; Symbol: ER_LDAP_AUTH_GRP_NULL_ATTRIBUTE_VALUE; SQLSTATE: HY000

    Message: User group retrieval: Group attribute values is NULL.

  • Error number: MY-013337; Symbol: ER_LDAP_AUTH_GRP_DN_PARSING_FAILED; SQLSTATE: HY000

    Message: User group retrieval: parsing DN failed.

  • Error number: MY-013338; Symbol: ER_LDAP_AUTH_GRP_OBJECT_HAS_USER_INFO; SQLSTATE: HY000

    Message: User group retrieval: Group object has user information

  • Error number: MY-013339; Symbol: ER_LDAP_AUTH_LDAPS; SQLSTATE: HY000

    Message: Reserved port for ldaps using ldaps

  • Error number: MY-013340; Symbol: ER_LDAP_MAPPING_GET_USER_PROXY; SQLSTATE: HY000

    Message: Get user proxy

  • Error number: MY-013341; Symbol: ER_LDAP_MAPPING_USER_DONT_BELONG_GROUP; SQLSTATE: HY000

    Message: Get user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.

  • Error number: MY-013342; Symbol: ER_LDAP_MAPPING_INFO; SQLSTATE: HY000

    Message: Get user proxy: configured mapping info: %s

  • Error number: MY-013343; Symbol: ER_LDAP_MAPPING_EMPTY_MAPPING; SQLSTATE: HY000

    Message: Get user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.

  • Error number: MY-013344; Symbol: ER_LDAP_MAPPING_PROCESS_MAPPING; SQLSTATE: HY000

    Message: Process group proxy mapping

  • Error number: MY-013345; Symbol: ER_LDAP_MAPPING_CHECK_DELIMI_QUOTE; SQLSTATE: HY000

    Message: Check delimiter after quote

  • Error number: MY-013346; Symbol: ER_LDAP_MAPPING_PROCESS_DELIMITER; SQLSTATE: HY000

    Message: Processing delimiter

  • Error number: MY-013347; Symbol: ER_LDAP_MAPPING_PROCESS_DELIMITER_EQUAL_NOT_FOUND; SQLSTATE: HY000

    Message: Processing delimiter, separator = not found, resetting position

  • Error number: MY-013348; Symbol: ER_LDAP_MAPPING_PROCESS_DELIMITER_TRY_COMMA; SQLSTATE: HY000

    Message: Processing delimiter, failed to get data for = separator try for separator ,.

  • Error number: MY-013349; Symbol: ER_LDAP_MAPPING_PROCESS_DELIMITER_COMMA_NOT_FOUND; SQLSTATE: HY000

    Message: Processing delimiter, separator , not found, resetting position

  • Error number: MY-013350; Symbol: ER_LDAP_MAPPING_NO_SEPEARATOR_END_OF_GROUP; SQLSTATE: HY000

    Message: Processing delimiter: No mapping separator is found, end of group information

  • Error number: MY-013351; Symbol: ER_LDAP_MAPPING_GETTING_NEXT_MAPPING; SQLSTATE: HY000

    Message: Getting next mapping information

  • Error number: MY-013352; Symbol: ER_LDAP_MAPPING_PARSING_CURRENT_STATE; SQLSTATE: HY000

    Message: Parsing mapping, current state: %d delimiter char: %c

  • Error number: MY-013353; Symbol: ER_LDAP_MAPPING_PARSING_MAPPING_INFO; SQLSTATE: HY000

    Message: Parsing mapping info, LDAP group: %s MySQL proxy: %s

  • Error number: MY-013354; Symbol: ER_LDAP_MAPPING_PARSING_ERROR; SQLSTATE: HY000

    Message: Mapping parsing error

  • Error number: MY-013355; Symbol: ER_LDAP_MAPPING_TRIMMING_SPACES; SQLSTATE: HY000

    Message: Trimming left spaces

  • Error number: MY-013356; Symbol: ER_LDAP_MAPPING_IS_QUOTE; SQLSTATE: HY000

    Message: Checking if current characters is quote

  • Error number: MY-013357; Symbol: ER_LDAP_MAPPING_NON_DESIRED_STATE; SQLSTATE: HY000

    Message: Not desired state or un-defined states.

  • Error number: MY-013358; Symbol: ER_INVALID_NAMED_PIPE_FULL_ACCESS_GROUP; SQLSTATE: HY000

    Message: Invalid value for named_pipe_full_access_group.

  • Error number: MY-013359; Symbol: ER_PREPARE_FOR_SECONDARY_ENGINE; SQLSTATE: HY000

    Message: Retry the statement using a secondary storage engine.

  • Error number: MY-013360; Symbol: ER_SERVER_WARN_DEPRECATED; SQLSTATE: HY000

    Message: '%s' is deprecated and will be removed in a future release. Please use %s instead

  • Error number: MY-013361; Symbol: ER_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES; SQLSTATE: HY000

    Message: Cannot set mandatory_roles: AuthId `%s`@`%s` has '%s' privilege.

  • Error number: MY-013362; Symbol: ER_SERVER_BINLOG_MASTER_KEY_RECOVERY_OUT_OF_COMBINATION; SQLSTATE: HY000

    Message: Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.

  • Error number: MY-013363; Symbol: ER_SERVER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_AUX_KEY; SQLSTATE: HY000

    Message: Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.

  • Error number: MY-013368; Symbol: ER_TURNING_ON_PARTIAL_REVOKES; SQLSTATE: HY000

    Message: At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.

  • Error number: MY-013369; Symbol: ER_WARN_PARTIAL_REVOKE_AND_DB_GRANT; SQLSTATE: HY000

    Message: For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.

  • Error number: MY-013370; Symbol: ER_WARN_INCORRECT_PRIVILEGE_FOR_DB_RESTRICTIONS; SQLSTATE: HY000

    Message: For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.

  • Error number: MY-013371; Symbol: ER_WARN_INVALID_DB_RESTRICTIONS; SQLSTATE: HY000

    Message: For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.

  • Error number: MY-013372; Symbol: ER_GRP_RPL_INVALID_COMMUNICATION_PROTOCOL; SQLSTATE: HY000

    Message: '%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's version

  • Error number: MY-013373; Symbol: ER_GRP_RPL_STARTED_AUTO_REJOIN; SQLSTATE: HY000

    Message: Started auto-rejoin procedure attempt %lu of %lu

  • Error number: MY-013374; Symbol: ER_GRP_RPL_TIMEOUT_RECEIVED_VC_ON_REJOIN; SQLSTATE: HY000

    Message: Timeout while waiting for a view change event during the auto-rejoin procedure

  • Error number: MY-013375; Symbol: ER_GRP_RPL_FINISHED_AUTO_REJOIN; SQLSTATE: HY000

    Message: Auto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.

  • Error number: MY-013376; Symbol: ER_GRP_RPL_DEFAULT_TABLE_ENCRYPTION_DIFF_FROM_GRP; SQLSTATE: HY000

    Message: The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.

  • Error number: MY-013377; Symbol: ER_SERVER_UPGRADE_OFF; SQLSTATE: HY000

    Message: Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.

  • Error number: MY-013378; Symbol: ER_SERVER_UPGRADE_SKIP; SQLSTATE: HY000

    Message: Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.

  • Error number: MY-013379; Symbol: ER_SERVER_UPGRADE_PENDING; SQLSTATE: HY000

    Message: Server upgrade started with version %d, but server upgrade of version %d is still pending.

  • Error number: MY-013380; Symbol: ER_SERVER_UPGRADE_FAILED; SQLSTATE: HY000

    Message: Failed to upgrade server.

  • Error number: MY-013381; Symbol: ER_SERVER_UPGRADE_STATUS; SQLSTATE: HY000

    Message: Server upgrade from '%d' to '%d' %s.

  • Error number: MY-013382; Symbol: ER_SERVER_UPGRADE_REPAIR_REQUIRED; SQLSTATE: HY000

    Message: Table '%s' requires repair.

  • Error number: MY-013383; Symbol: ER_SERVER_UPGRADE_REPAIR_STATUS; SQLSTATE: HY000

    Message: Table '%s' repair %s.

  • Error number: MY-013384; Symbol: ER_SERVER_UPGRADE_INFO_FILE; SQLSTATE: HY000

    Message: Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.

  • Error number: MY-013385; Symbol: ER_SERVER_UPGRADE_SYS_SCHEMA; SQLSTATE: HY000

    Message: Upgrading the sys schema.

  • Error number: MY-013386; Symbol: ER_SERVER_UPGRADE_MYSQL_TABLES; SQLSTATE: HY000

    Message: Running queries to upgrade MySQL server.

  • Error number: MY-013387; Symbol: ER_SERVER_UPGRADE_SYSTEM_TABLES; SQLSTATE: HY000

    Message: Upgrading system table data.

  • Error number: MY-013388; Symbol: ER_SERVER_UPGRADE_EMPTY_SYS; SQLSTATE: HY000

    Message: Found empty sys database. Installing the sys schema.

  • Error number: MY-013389; Symbol: ER_SERVER_UPGRADE_NO_SYS_VERSION; SQLSTATE: HY000

    Message: A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.

  • Error number: MY-013390; Symbol: ER_SERVER_UPGRADE_SYS_VERSION_EMPTY; SQLSTATE: HY000

    Message: A sys schema exists with a sys.version view, but it returns no results.

  • Error number: MY-013391; Symbol: ER_SERVER_UPGRADE_SYS_SCHEMA_OUTDATED; SQLSTATE: HY000

    Message: Found outdated sys schema version %s.

  • Error number: MY-013392; Symbol: ER_SERVER_UPGRADE_SYS_SCHEMA_UP_TO_DATE; SQLSTATE: HY000

    Message: The sys schema is already up to date (version %s).

  • Error number: MY-013393; Symbol: ER_SERVER_UPGRADE_SYS_SCHEMA_OBJECT_COUNT; SQLSTATE: HY000

    Message: Found %d sys %s, but expected %d. Re-installing the sys schema.

  • Error number: MY-013394; Symbol: ER_SERVER_UPGRADE_CHECKING_DB; SQLSTATE: HY000

    Message: Checking '%s' schema.

  • Error number: MY-013395; Symbol: ER_IB_MSG_DDL_LOG_DELETE_BY_ID_TMCT; SQLSTATE: HY000

    Message: Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.

  • Error number: MY-013396; Symbol: ER_IB_MSG_POST_RECOVER_DDL_LOG_RECOVER; SQLSTATE: HY000

    Message: Error in DDL Log recovery during Post-Recovery processing.

  • Error number: MY-013397; Symbol: ER_IB_MSG_POST_RECOVER_POST_TS_ENCRYPT; SQLSTATE: HY000

    Message: Error in Post-Tablespace-Encryption during Post-Recovery processing.

  • Error number: MY-013398; Symbol: ER_IB_MSG_DDL_LOG_FAIL_POST_DDL; SQLSTATE: HY000

    Message: Error in DLL Log cleanup during Post-DDL processing.

  • Error number: MY-013399; Symbol: ER_SERVER_BINLOG_UNSAFE_SYSTEM_FUNCTION; SQLSTATE: HY000

    Message: '%s' statement is unsafe because it uses a system function that may return a different value on the replica.

  • Error number: MY-013400; Symbol: ER_SERVER_UPGRADE_HELP_TABLE_STATUS; SQLSTATE: HY000

    Message: Upgrade of help tables %s.

  • Error number: MY-013404; Symbol: ER_BINLOG_UNABLE_TO_ROTATE_GTID_TABLE_READONLY; SQLSTATE: HY000

    Message: Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %s

  • Error number: MY-013405; Symbol: ER_NETWORK_NAMESPACES_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Network Namespaces is not supported on this platform

  • Error number: MY-013406; Symbol: ER_UNKNOWN_NETWORK_NAMESPACE; SQLSTATE: HY000

    Message: Unknown network namespace '%s'

  • Error number: MY-013407; Symbol: ER_NETWORK_NAMESPACE_NOT_ALLOWED_FOR_WILDCARD_ADDRESS; SQLSTATE: HY000

    Message: Network namespace not allowed for wildcard interface address

  • Error number: MY-013408; Symbol: ER_SETNS_FAILED; SQLSTATE: HY000

    Message: setns() failed with error '%s'

  • Error number: MY-013409; Symbol: ER_WILDCARD_NOT_ALLOWED_FOR_MULTIADDRESS_BIND; SQLSTATE: HY000

    Message: Wildcard address value not allowed for multivalued bind address

  • Error number: MY-013410; Symbol: ER_NETWORK_NAMESPACE_FILE_PATH_TOO_LONG; SQLSTATE: HY000

    Message: The path to a special network namespace file is too long. (got %u > max %u)

  • Error number: MY-013411; Symbol: ER_IB_MSG_TOO_LONG_PATH; SQLSTATE: HY000

    Message: Cannot create tablespace '%s'. The filepath is too long for this OS.

  • Error number: MY-013412; Symbol: ER_IB_RECV_FIRST_REC_GROUP_INVALID; SQLSTATE: HY000

    Message: The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).

  • Error number: MY-013413; Symbol: ER_DD_UPGRADE_COMPLETED; SQLSTATE: HY000

    Message: Data dictionary upgrade from version '%u' to '%u' completed.

  • Error number: MY-013415; Symbol: ER_PERSIST_OPTION_USER_TRUNCATED; SQLSTATE: HY000

    Message: Truncated a user name for %s that was too long while reading the persisted variables file

  • Error number: MY-013416; Symbol: ER_PERSIST_OPTION_HOST_TRUNCATED; SQLSTATE: HY000

    Message: Truncated a host name for %s that was too long while reading the persisted variables file

  • Error number: MY-013417; Symbol: ER_NET_WAIT_ERROR; SQLSTATE: HY000

    Message: The wait_timeout period was exceeded, the idle time since last command was too long.

  • Error number: MY-013418; Symbol: ER_IB_MSG_1285; SQLSTATE: HY000

    Message: '%s' found not encrypted while '%s' is ON. Trying to encrypt it now.

  • Error number: MY-013419; Symbol: ER_IB_MSG_CLOCK_MONOTONIC_UNSUPPORTED; SQLSTATE: HY000

    Message: CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !

  • Error number: MY-013420; Symbol: ER_IB_MSG_CLOCK_GETTIME_FAILED; SQLSTATE: HY000

    Message: clock_gettime() failed: %s

  • Error number: MY-013421; Symbol: ER_PLUGIN_NOT_EARLY_DUP; SQLSTATE: HY000

    Message: Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.

  • Error number: MY-013422; Symbol: ER_PLUGIN_NO_INSTALL_DUP; SQLSTATE: HY000

    Message: Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.

  • Error number: MY-013425; Symbol: ER_BINLOG_UNSAFE_DEFAULT_EXPRESSION_IN_SUBSTATEMENT; SQLSTATE: HY000

    Message: The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.

  • Error number: MY-013426; Symbol: ER_GRP_RPL_MEMBER_VER_READ_COMPATIBLE; SQLSTATE: HY000

    Message: Member version is read compatible with the group.

  • Error number: MY-013427; Symbol: ER_LOCK_ORDER_INIT_FAILED; SQLSTATE: HY000

    Message: Lock order disabled (reason: init failed).

  • Error number: MY-013428; Symbol: ER_AUDIT_LOG_KEYRING_ID_TIMESTAMP_VALUE_IS_INVALID; SQLSTATE: HY000

    Message: Keyring ID timestamp value is invalid: '%s'

  • Error number: MY-013429; Symbol: ER_AUDIT_LOG_FILE_NAME_TIMESTAMP_VALUE_IS_MISSING_OR_INVALID; SQLSTATE: HY000

    Message: File name timestamp value is missing or invalid: '%s'

  • Error number: MY-013430; Symbol: ER_AUDIT_LOG_FILE_NAME_DOES_NOT_HAVE_REQUIRED_FORMAT; SQLSTATE: HY000

    Message: Cannot process audit log file. File name does not have required format: '%s'

  • Error number: MY-013431; Symbol: ER_AUDIT_LOG_FILE_NAME_KEYRING_ID_VALUE_IS_MISSING; SQLSTATE: HY000

    Message: Cannot process audit log file. File name keyring ID value is missing: '%s'

  • Error number: MY-013432; Symbol: ER_AUDIT_LOG_FILE_HAS_BEEN_SUCCESSFULLY_PROCESSED; SQLSTATE: HY000

    Message: Audit log file has been successfully processed: '%s'

  • Error number: MY-013433; Symbol: ER_AUDIT_LOG_COULD_NOT_OPEN_FILE_FOR_READING; SQLSTATE: HY000

    Message: Could not open audit log file for reading: '%s'

  • Error number: MY-013434; Symbol: ER_AUDIT_LOG_INVALID_FILE_CONTENT; SQLSTATE: HY000

    Message: Invalid audit log file content: '%s'

  • Error number: MY-013435; Symbol: ER_AUDIT_LOG_CANNOT_READ_PASSWORD; SQLSTATE: HY000

    Message: Cannot read password: '%s'.

  • Error number: MY-013436; Symbol: ER_AUDIT_LOG_CANNOT_STORE_PASSWORD; SQLSTATE: HY000

    Message: Cannot store password: '%s'.

  • Error number: MY-013437; Symbol: ER_AUDIT_LOG_CANNOT_REMOVE_PASSWORD; SQLSTATE: HY000

    Message: Cannot remove password: '%s'.

  • Error number: MY-013438; Symbol: ER_AUDIT_LOG_PASSWORD_HAS_BEEN_COPIED; SQLSTATE: HY000

    Message: 'audit_log' password has been copied into '%s' and will be removed with first purged password.

  • Error number: MY-013447; Symbol: ER_LDAP_EMPTY_USERDN_PASSWORD; SQLSTATE: HY000

    Message: Empty user dn or password is not allowed, not attempting LDAP bind.

  • Error number: MY-013449; Symbol: ER_ACL_WRONG_OR_MISSING_ACL_TABLES_LOG; SQLSTATE: HY000

    Message: The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.

  • Error number: MY-013450; Symbol: ER_LOCK_ORDER_FAILED_WRITE_FILE; SQLSTATE: HY000

    Message: LOCK_ORDER: Failed to write to file <%s>.

  • Error number: MY-013451; Symbol: ER_LOCK_ORDER_FAILED_READ_FILE; SQLSTATE: HY000

    Message: LOCK_ORDER: Failed to read from file <%s>.

  • Error number: MY-013452; Symbol: ER_LOCK_ORDER_MESSAGE; SQLSTATE: HY000

    Message: LOCK_ORDER message: %s

  • Error number: MY-013453; Symbol: ER_LOCK_ORDER_DEPENDENCIES_SYNTAX; SQLSTATE: HY000

    Message: Lock order dependencies file <%s> (%d:%d) - (%d:%d) : %s

  • Error number: MY-013454; Symbol: ER_LOCK_ORDER_SCANNER_SYNTAX; SQLSTATE: HY000

    Message: Lock order scanner: (%d:%d) - (%d:%d) : %s

  • Error number: MY-013455; Symbol: ER_DATA_DIRECTORY_UNUSABLE_DELETABLE; SQLSTATE: HY000

    Message: The newly created data directory %s by --initialize is unusable. You can remove it.

  • Error number: MY-013456; Symbol: ER_IB_MSG_BTREE_LEVEL_LIMIT_EXCEEDED; SQLSTATE: HY000

    Message: No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.

  • Error number: MY-013457; Symbol: ER_IB_CLONE_START_STOP; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013458; Symbol: ER_IB_CLONE_OPERATION; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013459; Symbol: ER_IB_CLONE_RESTART; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013460; Symbol: ER_IB_CLONE_USER_DATA; SQLSTATE: HY000

    Message: Clone removing all user data for provisioning: %s

  • Error number: MY-013461; Symbol: ER_IB_CLONE_NON_INNODB_TABLE; SQLSTATE: HY000

    Message: Non innodb table: %s.%s is not cloned and is empty.

  • Error number: MY-013462; Symbol: ER_CLONE_SHUTDOWN_TRACE; SQLSTATE: HY000

    Message: Clone shutting down server as RESTART failed. Please start server to complete clone operation.

  • Error number: MY-013463; Symbol: ER_GRP_RPL_GTID_PURGED_EXTRACT_ERROR; SQLSTATE: HY000

    Message: Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.

  • Error number: MY-013464; Symbol: ER_GRP_RPL_CLONE_PROCESS_PREPARE_ERROR; SQLSTATE: HY000

    Message: There was an issue when configuring the remote cloning process: %s

  • Error number: MY-013465; Symbol: ER_GRP_RPL_CLONE_PROCESS_EXEC_ERROR; SQLSTATE: HY000

    Message: There was an issue when cloning from another server: %s

  • Error number: MY-013466; Symbol: ER_GRP_RPL_RECOVERY_EVAL_ERROR; SQLSTATE: HY000

    Message: There was an issue when trying to evaluate the best distributed recovery strategy while joining.%s

  • Error number: MY-013467; Symbol: ER_GRP_RPL_NO_POSSIBLE_RECOVERY; SQLSTATE: HY000

    Message: No valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.

  • Error number: MY-013468; Symbol: ER_GRP_RPL_CANT_KILL_THREAD; SQLSTATE: HY000

    Message: The group replication plugin could not kill the plugin routine for %s. %s

  • Error number: MY-013469; Symbol: ER_GRP_RPL_RECOVERY_STRAT_CLONE_THRESHOLD; SQLSTATE: HY000

    Message: This member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.

  • Error number: MY-013470; Symbol: ER_GRP_RPL_RECOVERY_STRAT_CLONE_PURGED; SQLSTATE: HY000

    Message: This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.

  • Error number: MY-013471; Symbol: ER_GRP_RPL_RECOVERY_STRAT_CHOICE; SQLSTATE: HY000

    Message: Distributed recovery will transfer data using: %s

  • Error number: MY-013472; Symbol: ER_GRP_RPL_RECOVERY_STRAT_FALLBACK; SQLSTATE: HY000

    Message: Due to some issue on the previous step distributed recovery is now executing: %s

  • Error number: MY-013473; Symbol: ER_GRP_RPL_RECOVERY_STRAT_NO_FALLBACK; SQLSTATE: HY000

    Message: Due to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.

  • Error number: MY-013474; Symbol: ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_CLONE; SQLSTATE: HY000

    Message: The '%s' thread of channel '%s' will error out as the server will attempt to clone another server

  • Error number: MY-013475; Symbol: ER_UNKNOWN_TABLE_IN_UPGRADE; SQLSTATE: HY000

    Message: Unknown table '%s'

  • Error number: MY-013476; Symbol: ER_IDENT_CAUSES_TOO_LONG_PATH_IN_UPGRADE; SQLSTATE: HY000

    Message: Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.

  • Error number: MY-013477; Symbol: ER_XA_CANT_CREATE_MDL_BACKUP; SQLSTATE: HY000

    Message: XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.

  • Error number: MY-013478; Symbol: ER_AUDIT_LOG_SUPER_PRIVILEGE_REQUIRED; SQLSTATE: HY000

    Message: SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.

  • Error number: MY-013479; Symbol: ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_TYPE; SQLSTATE: HY000

    Message: Invalid argument type

  • Error number: MY-013480; Symbol: ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT; SQLSTATE: HY000

    Message: Invalid argument count

  • Error number: MY-013481; Symbol: ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED; SQLSTATE: HY000

    Message: audit_log plugin has not been installed using INSTALL PLUGIN syntax.

  • Error number: MY-013482; Symbol: ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE; SQLSTATE: HY000

    Message: Invalid "max_array_length" argument type.

  • Error number: MY-013483; Symbol: ER_LOG_CANNOT_WRITE_EXTENDED; SQLSTATE: HY000

    Message: Failed to write to %s: %s (%s)

  • Error number: MY-013485; Symbol: ER_KEYRING_AWS_INCORRECT_PROXY; SQLSTATE: HY000

    Message: Incorrect environment variable %s, invalid port: %s

  • Error number: MY-013486; Symbol: ER_GRP_RPL_SERVER_SET_TO_OFFLINE_MODE_DUE_TO_ERRORS; SQLSTATE: HY000

    Message: The server was automatically set into offline mode after an error was detected.

  • Error number: MY-013487; Symbol: ER_GRP_RPL_MESSAGE_SERVICE_FATAL_ERROR; SQLSTATE: HY000

    Message: A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.

  • Error number: MY-013488; Symbol: ER_WARN_WRONG_COMPRESSION_ALGORITHM_LOG; SQLSTATE: HY000

    Message: Invalid SOURCE_COMPRESSION_ALGORITHMS '%s' found in repository for channel '%s'. Resetting to 'uncompressed' (no compression).

  • Error number: MY-013489; Symbol: ER_WARN_WRONG_COMPRESSION_LEVEL_LOG; SQLSTATE: HY000

    Message: Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%s'. Resetting to %u.

  • Error number: MY-013490; Symbol: ER_PROTOCOL_COMPRESSION_RESET_LOG; SQLSTATE: HY000

    Message: Option --protocol-compression-algorithms is reset to default value.

  • Error number: MY-013491; Symbol: ER_XPLUGIN_COMPRESSION_ERROR; SQLSTATE: HY000

    Message: Fatal error while compressing outgoing data - %s

  • Error number: MY-013492; Symbol: ER_MYSQLBACKUP_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013493; Symbol: ER_WARN_UNKNOWN_KEYRING_AWS_REGION; SQLSTATE: HY000

    Message: Unknown keyring_aws_region '%s'. Connection to AWS KMS may fail.

  • Error number: MY-013494; Symbol: ER_WARN_LOG_PRIVILEGE_CHECKS_USER_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this is not an existing user. Correct this before starting replication threads.

  • Error number: MY-013495; Symbol: ER_WARN_LOG_PRIVILEGE_CHECKS_USER_CORRUPT; SQLSTATE: HY000

    Message: Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.

  • Error number: MY-013496; Symbol: ER_WARN_LOG_PRIVILEGE_CHECKS_USER_NEEDS_RPL_APPLIER_PRIV; SQLSTATE: HY000

    Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.

  • Error number: MY-013497; Symbol: ER_OBSOLETE_FILE_PRIVILEGE_FOR_REPLICATION_CHECKS; SQLSTATE: HY000

    Message: The PRIVILEGE_CHECKS_USER for channel '%s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.

  • Error number: MY-013498; Symbol: ER_RPL_REPLICA_SQL_THREAD_STARTING_WITH_PRIVILEGE_CHECKS; SQLSTATE: HY000

    Message: Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%s'@'%s', roles: %s

  • Error number: MY-013499; Symbol: ER_AUDIT_LOG_CANNOT_GENERATE_PASSWORD; SQLSTATE: HY000

    Message: Cannot generate password: '%s'

  • Error number: MY-013500; Symbol: ER_INIT_FAILED_TO_GENERATE_ROOT_PASSWORD; SQLSTATE: HY000

    Message: Failed to generate a random password for root. Probabably not enough enthropy.

  • Error number: MY-013501; Symbol: ER_PLUGIN_LOAD_OPTIONS_IGNORED; SQLSTATE: HY000

    Message: Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).

  • Error number: MY-013502; Symbol: ER_WARN_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES; SQLSTATE: HY000

    Message: Cannot set mandatory_roles: AuthId `%s`@`%s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.

  • Error number: MY-013503; Symbol: ER_IB_MSG_SKIP_HIDDEN_DIR; SQLSTATE: HY000

    Message: Directory '%s' will not be scanned because it is a hidden directory.

  • Error number: MY-013504; Symbol: ER_WARN_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE_EOF; SQLSTATE: HY000

    Message: Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.

  • Error number: MY-013505; Symbol: ER_IB_LOB_ROLLBACK_INDEX_LEN; SQLSTATE: HY000

    Message: Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)

  • Error number: MY-013506; Symbol: ER_CANT_PROCESS_EXPRESSION_FOR_GENERATED_COLUMN_TO_DD; SQLSTATE: HY000

    Message: Error in processing (possibly deprecated) expression or function '%s' for generated column %s.%s.%s

  • Error number: MY-013507; Symbol: ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_NON_ROW_FORMAT; SQLSTATE: HY000

    Message: The queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.

  • Error number: MY-013508; Symbol: ER_OBSOLETE_REQUIRE_ROW_FORMAT_VIOLATION; SQLSTATE: HY000

    Message: The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.

  • Error number: MY-013509; Symbol: ER_LOG_PRIV_CHECKS_REQUIRE_ROW_FORMAT_NOT_SET; SQLSTATE: HY000

    Message: PRIVILEGE_CHECKS_USER for replication channel '%s' can't be set to `%s`@`%s` unless REQUIRE_ROW_FORMAT is also set to %d.

  • Error number: MY-013510; Symbol: ER_RPL_REPLICA_SQL_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE; SQLSTATE: HY000

    Message: An unexpected event sequence was detected by the SQL thread while applying an event.

  • Error number: MY-013511; Symbol: ER_IB_MSG_UPGRADE_PARTITION_FILE; SQLSTATE: HY000

    Message: Updating partition file name '%s' to '%s' and all other partition files during upgrade

  • Error number: MY-013512; Symbol: ER_IB_MSG_DOWNGRADE_PARTITION_FILE; SQLSTATE: HY000

    Message: Updating partition file name '%s' to '%s' and all other partition files during downgrade

  • Error number: MY-013513; Symbol: ER_IB_MSG_UPGRADE_PARTITION_FILE_IMPORT; SQLSTATE: HY000

    Message: Updating partition file name '%s' to '%s' for import

  • Error number: MY-013514; Symbol: ER_IB_WARN_OPEN_PARTITION_FILE; SQLSTATE: HY000

    Message: Unable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths

  • Error number: MY-013515; Symbol: ER_IB_MSG_FIL_STATE_MOVED_CORRECTED; SQLSTATE: HY000

    Message: %s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'

  • Error number: MY-013516; Symbol: ER_IB_MSG_FIL_STATE_MOVED_CHANGED_PATH; SQLSTATE: HY000

    Message: %s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'

  • Error number: MY-013517; Symbol: ER_IB_MSG_FIL_STATE_MOVED_CHANGED_NAME; SQLSTATE: HY000

    Message: %s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'

  • Error number: MY-013518; Symbol: ER_IB_MSG_FIL_STATE_MOVED_TOO_MANY; SQLSTATE: HY000

    Message: %s Too many files have been moved, disabling logging of detailed messages

  • Error number: MY-013519; Symbol: ER_GR_ELECTED_PRIMARY_GTID_INFORMATION; SQLSTATE: HY000

    Message: Elected primary member %s: %s

  • Error number: MY-013520; Symbol: ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED; SQLSTATE: HY000

    Message: Schema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.

  • Error number: MY-013521; Symbol: ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED; SQLSTATE: HY000

    Message: Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.

  • Error number: MY-013522; Symbol: ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK; SQLSTATE: HY000

    Message: Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.

  • Error number: MY-013523; Symbol: ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK; SQLSTATE: HY000

    Message: Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.

  • Error number: MY-013524; Symbol: ER_IB_MSG_DICT_PARTITION_NOT_FOUND; SQLSTATE: HY000

    Message: Table Partition: %s is not found in InnoDB dictionary

  • Error number: MY-013525; Symbol: ER_ACCESS_DENIED_FOR_USER_ACCOUNT_BLOCKED_BY_PASSWORD_LOCK; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.

  • Error number: MY-013526; Symbol: ER_INNODB_OUT_OF_RESOURCES; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013528; Symbol: ER_MIGRATE_TABLE_TO_DD_OOM; SQLSTATE: HY000

    Message: Could not allocate memory for key_info when migrating table %s.%s

  • Error number: MY-013529; Symbol: ER_RPL_RELAY_LOG_RECOVERY_INFO_AFTER_CLONE; SQLSTATE: HY000

    Message: Applier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'

  • Error number: MY-013530; Symbol: ER_IB_MSG_57_UNDO_SPACE_DELETE_FAIL; SQLSTATE: HY000

    Message: Failed to delete 5.7 undo tablespace: %s during upgrade

  • Error number: MY-013531; Symbol: ER_IB_MSG_DBLWR_1285; SQLSTATE: HY000

    Message: Empty doublewrite file: %s

  • Error number: MY-013532; Symbol: ER_IB_MSG_DBLWR_1286; SQLSTATE: HY000

    Message: Using '%s' for doublewrite

  • Error number: MY-013533; Symbol: ER_IB_MSG_DBLWR_1287; SQLSTATE: HY000

    Message: Error reading doublewrite buffer from the system tablespace

  • Error number: MY-013534; Symbol: ER_IB_MSG_DBLWR_1288; SQLSTATE: HY000

    Message: Cannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.

  • Error number: MY-013535; Symbol: ER_IB_MSG_DBLWR_1290; SQLSTATE: HY000

    Message: The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6

  • Error number: MY-013536; Symbol: ER_IB_MSG_BAD_DBLWR_FILE_NAME; SQLSTATE: HY000

    Message: The doublewrite filename '%s' is incorrect.

  • Error number: MY-013538; Symbol: ER_IB_MSG_DBLWR_1293; SQLSTATE: HY000

    Message: Doublewrite file create failed: %s

  • Error number: MY-013539; Symbol: ER_IB_MSG_DBLWR_1294; SQLSTATE: HY000

    Message: DBLWRThread: pthread_setaffinity() failed!

  • Error number: MY-013540; Symbol: ER_IB_MSG_DBLWR_1295; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013541; Symbol: ER_IB_MSG_DBLWR_1296; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013542; Symbol: ER_IB_MSG_DBLWR_1297; SQLSTATE: HY000

    Message: Doublewrite file read failed: %s

  • Error number: MY-013543; Symbol: ER_IB_MSG_DBLWR_1298; SQLSTATE: HY000

    Message: Dump of the data file page:

  • Error number: MY-013544; Symbol: ER_IB_MSG_DBLWR_1300; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013545; Symbol: ER_IB_MSG_DBLWR_1301; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013546; Symbol: ER_IB_MSG_DBLWR_1304; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013547; Symbol: ER_IB_MSG_DBLWR_1305; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013548; Symbol: ER_IB_MSG_DBLWR_1306; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013549; Symbol: ER_IB_MSG_DBLWR_1307; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013550; Symbol: ER_IB_MSG_DBLWR_1308; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013551; Symbol: ER_IB_MSG_DBLWR_1309; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013552; Symbol: ER_IB_MSG_DBLWR_1310; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013553; Symbol: ER_IB_MSG_DBLWR_1311; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013554; Symbol: ER_IB_MSG_DBLWR_1312; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013555; Symbol: ER_IB_MSG_DBLWR_1313; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013556; Symbol: ER_IB_MSG_DBLWR_1314; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013557; Symbol: ER_IB_MSG_DBLWR_1315; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013558; Symbol: ER_IB_MSG_DBLWR_1316; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013559; Symbol: ER_IB_MSG_DBLWR_1317; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013560; Symbol: ER_IB_MSG_DBLWR_1318; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013561; Symbol: ER_IB_MSG_DBLWR_LOAD_WRONG_SIZE; SQLSTATE: HY000

    Message: Doublewrite load file %s size %llu is not a multiple of the configured page size %zu

  • Error number: MY-013562; Symbol: ER_IB_MSG_DBLWR_1320; SQLSTATE: HY000

    Message: Doublewrite file %s truncate failed

  • Error number: MY-013563; Symbol: ER_IB_MSG_DBLWR_1321; SQLSTATE: HY000

    Message: Doublewrite file %s failed to writ zeros

  • Error number: MY-013564; Symbol: ER_IB_MSG_DBLWR_OPEN_OR_CREATE_WRONG_SIZE; SQLSTATE: HY000

    Message: Doublewrite open or create file %s size %llu is not a multiple of the configured page size %zu

  • Error number: MY-013565; Symbol: ER_IB_MSG_DBLWR_1323; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013566; Symbol: ER_IB_MSG_DBLWR_1324; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013567; Symbol: ER_IB_MSG_DBLWR_1325; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013568; Symbol: ER_IB_MSG_DBLWR_1326; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013569; Symbol: ER_IB_MSG_DBLWR_1327; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013570; Symbol: ER_IB_MSG_GTID_FLUSH_AT_SHUTDOWN; SQLSTATE: HY000

    Message: Could not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.

  • Error number: MY-013571; Symbol: ER_IB_MSG_57_STAT_SPACE_DELETE_FAIL; SQLSTATE: HY000

    Message: Failed to delete 5.7 stat tablespace: %s during upgrade

  • Error number: MY-013572; Symbol: ER_NDBINFO_UPGRADING_SCHEMA; SQLSTATE: HY000

    Message: Installing ndbinfo schema version %s

  • Error number: MY-013573; Symbol: ER_NDBINFO_NOT_UPGRADING_SCHEMA; SQLSTATE: HY000

    Message: Installed ndbinfo schema is current. Not upgrading.

  • Error number: MY-013574; Symbol: ER_NDBINFO_UPGRADING_SCHEMA_FAIL; SQLSTATE: HY000

    Message: Failed to upgrade ndbinfo schema.

  • Error number: MY-013576; Symbol: ER_IB_MSG_INNODB_START_INITIALIZE; SQLSTATE: HY000

    Message: InnoDB initialization has started.

  • Error number: MY-013577; Symbol: ER_IB_MSG_INNODB_END_INITIALIZE; SQLSTATE: HY000

    Message: InnoDB initialization has ended.

  • Error number: MY-013578; Symbol: ER_IB_MSG_PAGE_ARCH_NO_RESET_POINTS; SQLSTATE: HY000

    Message: Could not find appropriate reset points.

  • Error number: MY-013579; Symbol: ER_IB_WRN_PAGE_ARCH_FLUSH_DATA; SQLSTATE: HY000

    Message: Unable to flush. Page archiving data may be corrupt in case of a crash.

  • Error number: MY-013580; Symbol: ER_IB_ERR_PAGE_ARCH_INVALID_DOUBLE_WRITE_BUF; SQLSTATE: HY000

    Message: Page archiver's doublewrite buffer for %ld is not valid.

  • Error number: MY-013581; Symbol: ER_IB_ERR_PAGE_ARCH_RECOVERY_FAILED; SQLSTATE: HY000

    Message: Page archiver system's recovery failed.

  • Error number: MY-013582; Symbol: ER_IB_ERR_PAGE_ARCH_INVALID_FORMAT; SQLSTATE: HY000

    Message: Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.

  • Error number: MY-013583; Symbol: ER_INVALID_XPLUGIN_SOCKET_SAME_AS_SERVER; SQLSTATE: HY000

    Message: X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket

  • Error number: MY-013584; Symbol: ER_INNODB_UNABLE_TO_ACQUIRE_DD_OBJECT; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013586; Symbol: ER_IB_MSG_UNDO_TRUNCATE_TOO_OFTEN; SQLSTATE: HY000

    Message: Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.

  • Error number: MY-013587; Symbol: ER_GRP_RPL_IS_STARTING; SQLSTATE: HY000

    Message: Plugin 'group_replication' is starting.

  • Error number: MY-013588; Symbol: ER_IB_MSG_INVALID_LOCATION_FOR_TABLESPACE; SQLSTATE: HY000

    Message: Cannot create tablespace %s because the directory is not a valid location. %s

  • Error number: MY-013589; Symbol: ER_IB_MSG_INVALID_LOCATION_WRONG_DB; SQLSTATE: HY000

    Message: Scanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.

  • Error number: MY-013590; Symbol: ER_IB_MSG_CANNOT_FIND_DD_UNDO_SPACE; SQLSTATE: HY000

    Message: Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.

  • Error number: MY-013591; Symbol: ER_GRP_RPL_RECOVERY_ENDPOINT_FORMAT; SQLSTATE: HY000

    Message: Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port).

  • Error number: MY-013592; Symbol: ER_GRP_RPL_RECOVERY_ENDPOINT_INVALID; SQLSTATE: HY000

    Message: The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.

  • Error number: MY-013593; Symbol: ER_GRP_RPL_RECOVERY_ENDPOINT_INVALID_DONOR_ENDPOINT; SQLSTATE: HY000

    Message: Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.

  • Error number: MY-013594; Symbol: ER_GRP_RPL_RECOVERY_ENDPOINT_INTERFACES_IPS; SQLSTATE: HY000

    Message: Failed to retrieve IP addresses from enabled host network interfaces.

  • Error number: MY-013595; Symbol: ER_WARN_TLS_CHANNEL_INITIALIZATION_ERROR; SQLSTATE: HY000

    Message: Failed to initialize TLS for channel: %s. See below for the description of exact issue.

  • Error number: MY-013596; Symbol: ER_XPLUGIN_FAILED_TO_VALIDATE_ADDRESS; SQLSTATE: HY000

    Message: Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.

  • Error number: MY-013597; Symbol: ER_XPLUGIN_FAILED_TO_BIND_INTERFACE_ADDRESS; SQLSTATE: HY000

    Message: Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.

  • Error number: MY-013598; Symbol: ER_IB_ERR_RECOVERY_REDO_DISABLED; SQLSTATE: HY000

    Message: Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6

  • Error number: MY-013599; Symbol: ER_IB_WRN_FAST_SHUTDOWN_REDO_DISABLED; SQLSTATE: HY000

    Message: InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.

  • Error number: MY-013600; Symbol: ER_IB_WRN_REDO_DISABLED; SQLSTATE: HY000

    Message: InnoDB redo logging is disabled. All data could be lost in case of a server crash.

  • Error number: MY-013601; Symbol: ER_IB_WRN_REDO_ENABLED; SQLSTATE: HY000

    Message: InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.

  • Error number: MY-013602; Symbol: ER_TLS_CONFIGURED_FOR_CHANNEL; SQLSTATE: HY000

    Message: Channel %s configured to support TLS. Encrypted connections are now supported for this channel.

  • Error number: MY-013603; Symbol: ER_TLS_CONFIGURATION_REUSED; SQLSTATE: HY000

    Message: No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.

  • Error number: MY-013604; Symbol: ER_IB_TABLESPACE_PATH_VALIDATION_SKIPPED; SQLSTATE: HY000

    Message: Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!

  • Error number: MY-013605; Symbol: ER_IB_CANNOT_UPGRADE_WITH_DISCARDED_TABLESPACES; SQLSTATE: HY000

    Message: Upgrade failed because database contains discarded tablespaces.

  • Error number: MY-013606; Symbol: ER_USERNAME_TRUNKATED; SQLSTATE: HY000

    Message: The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.

  • Error number: MY-013607; Symbol: ER_HOSTNAME_TRUNKATED; SQLSTATE: HY000

    Message: The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.

  • Error number: MY-013608; Symbol: ER_IB_MSG_TRX_RECOVERY_ROLLBACK_NOT_COMPLETED; SQLSTATE: HY000

    Message: Rollback of non-prepared transactions not completed, due to fast shutdown

  • Error number: MY-013609; Symbol: ER_AUTHCACHE_ROLE_EDGES_IGNORED_EMPTY_NAME; SQLSTATE: HY000

    Message: Found an entry in the 'role_edges' table with empty authorization ID; Skipped

  • Error number: MY-013610; Symbol: ER_AUTHCACHE_ROLE_EDGES_UNKNOWN_AUTHORIZATION_ID; SQLSTATE: HY000

    Message: Found an entry in the 'role_edges' table with unknown authorization ID '%s'; Skipped

  • Error number: MY-013611; Symbol: ER_AUTHCACHE_DEFAULT_ROLES_IGNORED_EMPTY_NAME; SQLSTATE: HY000

    Message: Found an entry in the 'default_roles' table with empty authorization ID; Skipped

  • Error number: MY-013612; Symbol: ER_AUTHCACHE_DEFAULT_ROLES_UNKNOWN_AUTHORIZATION_ID; SQLSTATE: HY000

    Message: Found an entry in the 'default_roles' table with unknown authorization ID '%s'; Skipped

  • Error number: MY-013613; Symbol: ER_IB_ERR_DDL_LOG_INSERT_FAILURE; SQLSTATE: HY000

    Message: Couldn't insert entry in ddl log for ddl.

  • Error number: MY-013614; Symbol: ER_IB_LOCK_VALIDATE_LATCH_ORDER_VIOLATION; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013615; Symbol: ER_IB_RELOCK_LATCH_ORDER_VIOLATION; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013621; Symbol: ER_IB_MSG_1357; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013622; Symbol: ER_IB_MSG_1358; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013623; Symbol: ER_IB_MSG_1359; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013624; Symbol: ER_IB_FAILED_TO_DELETE_TABLESPACE_FILE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013625; Symbol: ER_IB_UNABLE_TO_EXPAND_TEMPORARY_TABLESPACE_POOL; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013626; Symbol: ER_IB_TMP_TABLESPACE_CANNOT_CREATE_DIRECTORY; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013627; Symbol: ER_IB_MSG_SCANNING_TEMP_TABLESPACE_DIR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013628; Symbol: ER_IB_ERR_TEMP_TABLESPACE_DIR_DOESNT_EXIST; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013629; Symbol: ER_IB_ERR_TEMP_TABLESPACE_DIR_EMPTY; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013630; Symbol: ER_IB_ERR_TEMP_TABLESPACE_DIR_CONTAINS_SEMICOLON; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013631; Symbol: ER_IB_ERR_TEMP_TABLESPACE_DIR_SUBDIR_OF_DATADIR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013632; Symbol: ER_IB_ERR_SCHED_SETAFFNINITY_FAILED; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013633; Symbol: ER_IB_ERR_UNKNOWN_PAGE_FETCH_MODE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013634; Symbol: ER_IB_ERR_LOG_PARSING_BUFFER_OVERFLOW; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013635; Symbol: ER_IB_ERR_NOT_ENOUGH_MEMORY_FOR_PARSE_BUFFER; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013636; Symbol: ER_IB_MSG_1372; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013637; Symbol: ER_IB_MSG_1373; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013638; Symbol: ER_IB_MSG_1374; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013639; Symbol: ER_IB_MSG_1375; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013640; Symbol: ER_IB_ERR_ZLIB_UNCOMPRESS_FAILED; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013641; Symbol: ER_IB_ERR_ZLIB_BUF_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013642; Symbol: ER_IB_ERR_ZLIB_MEM_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013643; Symbol: ER_IB_ERR_ZLIB_DATA_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013644; Symbol: ER_IB_ERR_ZLIB_UNKNOWN_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013645; Symbol: ER_IB_MSG_1381; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013646; Symbol: ER_IB_ERR_INDEX_RECORDS_WRONG_ORDER; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013647; Symbol: ER_IB_ERR_INDEX_DUPLICATE_KEY; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013648; Symbol: ER_IB_ERR_FOUND_N_DUPLICATE_KEYS; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013649; Symbol: ER_IB_ERR_FOUND_N_RECORDS_WRONG_ORDER; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013650; Symbol: ER_IB_ERR_PARALLEL_READ_OOM; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013651; Symbol: ER_IB_MSG_UNDO_MARKED_ACTIVE; SQLSTATE: HY000

    Message: The state of undo tablespace %s is set to active implicitly.

  • Error number: MY-013652; Symbol: ER_IB_MSG_UNDO_ALTERED_ACTIVE; SQLSTATE: HY000

    Message: The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.

  • Error number: MY-013653; Symbol: ER_IB_MSG_UNDO_ALTERED_INACTIVE; SQLSTATE: HY000

    Message: The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.

  • Error number: MY-013654; Symbol: ER_IB_MSG_UNDO_MARKED_EMPTY; SQLSTATE: HY000

    Message: The state of undo tablespace %s is set to 'empty'.

  • Error number: MY-013655; Symbol: ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_CLONE; SQLSTATE: HY000

    Message: Delaying truncate of undo tablespace %s due to clone activity.

  • Error number: MY-013656; Symbol: ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_MDL; SQLSTATE: HY000

    Message: Delaying truncate of undo tablespace %s due to a metadata lock.

  • Error number: MY-013657; Symbol: ER_IB_MSG_INJECT_CRASH; SQLSTATE: HY000

    Message: Injected debug crash point: %s

  • Error number: MY-013658; Symbol: ER_IB_MSG_INJECT_FAILURE; SQLSTATE: HY000

    Message: Injected debug failure point: %s

  • Error number: MY-013659; Symbol: ER_GRP_RPL_TIMEOUT_RECEIVED_VC_LEAVE_ON_REJOIN; SQLSTATE: HY000

    Message: Timeout while waiting for a view change event during the leave step before a auto-rejoin attempt.

  • Error number: MY-013660; Symbol: ER_RPL_ASYNC_RECONNECT_FAIL_NO_SOURCE; SQLSTATE: HY000

    Message: Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.

  • Error number: MY-013661; Symbol: ER_UDF_REGISTER_SERVICE_ERROR; SQLSTATE: HY000

    Message: Could not execute the installation of UDF functions. Check for other errors in the log

  • Error number: MY-013662; Symbol: ER_UDF_REGISTER_ERROR; SQLSTATE: HY000

    Message: Could not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.

  • Error number: MY-013663; Symbol: ER_UDF_UNREGISTER_ERROR; SQLSTATE: HY000

    Message: Could not uninstall UDF functions. Try to remove them manually if present.

  • Error number: MY-013664; Symbol: ER_EMPTY_PRIVILEGE_NAME_IGNORED; SQLSTATE: HY000

    Message: An empty or illegal privilege identifier was ignored when global privileges were read from disk.

  • Error number: MY-013665; Symbol: ER_IB_MSG_INCORRECT_SIZE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013666; Symbol: ER_TMPDIR_PATH_TOO_LONG; SQLSTATE: HY000

    Message: A tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.

  • Error number: MY-013667; Symbol: ER_ERROR_LOG_DESTINATION_NOT_A_FILE; SQLSTATE: HY000

    Message: Error-log destination "%s" is not a file. Can not restore error log messages from previous run.

  • Error number: MY-013668; Symbol: ER_NO_ERROR_LOG_PARSER_CONFIGURED; SQLSTATE: HY000

    Message: None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.

  • Error number: MY-013669; Symbol: ER_UPGRADE_NONEXISTENT_SCHEMA; SQLSTATE: HY000

    Message: The schema "%s" referenced by %s "%s" does not exist. Please clean up any orphan %s before upgrading.

  • Error number: MY-013670; Symbol: ER_IB_MSG_CREATED_UNDO_SPACE; SQLSTATE: HY000

    Message: Created undo tablespace '%s'.

  • Error number: MY-013671; Symbol: ER_IB_MSG_DROPPED_UNDO_SPACE; SQLSTATE: HY000

    Message: Dropped undo tablespace '%s'.

  • Error number: MY-013672; Symbol: ER_IB_MSG_MASTER_KEY_ROTATED; SQLSTATE: HY000

    Message: The InnoDB Encryption Master Key has been rotated in %d tablespaces.

  • Error number: MY-013673; Symbol: ER_IB_DBLWR_DECOMPRESS_FAILED; SQLSTATE: HY000

    Message: Failed to decompress a DBLWR page (err=%d). The original size is %d. Reporting the dblwr page as corrupted.

  • Error number: MY-013674; Symbol: ER_IB_DBLWR_DECRYPT_FAILED; SQLSTATE: HY000

    Message: Decrypting a page in doublewrite file failed: %s.

  • Error number: MY-013675; Symbol: ER_IB_DBLWR_KEY_MISSING; SQLSTATE: HY000

    Message: Encryption key missing: %s.

  • Error number: MY-013676; Symbol: ER_INNODB_IO_WRITE_ERROR_RETRYING; SQLSTATE: HY000

    Message: I/O error while writing to file: %s. Retrying ...

  • Error number: MY-013677; Symbol: ER_INNODB_IO_WRITE_FAILED; SQLSTATE: HY000

    Message: Failed to write data to file: %s

  • Error number: MY-013678; Symbol: ER_LOG_COMPONENT_CANNOT_INIT; SQLSTATE: HY000

    Message: Log component %s failed to initialize.

  • Error number: MY-013679; Symbol: ER_RPL_ASYNC_CHANNEL_CANT_CONNECT; SQLSTATE: HY000

    Message: The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.

  • Error number: MY-013680; Symbol: ER_RPL_ASYNC_SENDER_ADDED; SQLSTATE: HY000

    Message: The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.

  • Error number: MY-013681; Symbol: ER_RPL_ASYNC_SENDER_REMOVED; SQLSTATE: HY000

    Message: The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.

  • Error number: MY-013682; Symbol: ER_RPL_ASYNC_CHANNEL_STOPPED_QUORUM_LOST; SQLSTATE: HY000

    Message: The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.

  • Error number: MY-013683; Symbol: ER_RPL_ASYNC_CHANNEL_CANT_CONNECT_NO_QUORUM; SQLSTATE: HY000

    Message: The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.

  • Error number: MY-013685; Symbol: ER_RPL_REPLICA_MONITOR_IO_THREAD_EXITING; SQLSTATE: HY000

    Message: Replica Monitor IO thread exiting.

  • Error number: MY-013686; Symbol: ER_RPL_ASYNC_MANAGED_NAME_REMOVED; SQLSTATE: HY000

    Message: The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.

  • Error number: MY-013687; Symbol: ER_RPL_ASYNC_MANAGED_NAME_ADDED; SQLSTATE: HY000

    Message: The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.

  • Error number: MY-013688; Symbol: ER_RPL_ASYNC_READ_FAILOVER_TABLE; SQLSTATE: HY000

    Message: Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.

  • Error number: MY-013689; Symbol: ER_RPL_REPLICA_MONITOR_IO_THREAD_RECONNECT_CHANNEL; SQLSTATE: HY000

    Message: Error %s the channel '%s', the operation will be automatically retried.

  • Error number: MY-013690; Symbol: ER_REPLICA_ANON_TO_GTID_IS_LOCAL_OR_UUID_AND_GTID_MODE_NOT_ON; SQLSTATE: HY000

    Message: Replication channel '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.

  • Error number: MY-013691; Symbol: ER_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_GROUP_NAME; SQLSTATE: HY000

    Message: Replication channel '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.

  • Error number: MY-013692; Symbol: ER_GRP_RPL_GRP_NAME_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID; SQLSTATE: HY000

    Message: The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel

  • Error number: MY-013693; Symbol: ER_WARN_GTID_THRESHOLD_BREACH; SQLSTATE: HY000

    Message: The integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.

  • Error number: MY-013694; Symbol: ER_HEALTH_INFO; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013695; Symbol: ER_HEALTH_WARNING; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013696; Symbol: ER_HEALTH_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013697; Symbol: ER_HEALTH_WARNING_DISK_USAGE_LEVEL_1; SQLSTATE: HY000

    Message: %s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB

  • Error number: MY-013698; Symbol: ER_HEALTH_WARNING_DISK_USAGE_LEVEL_2; SQLSTATE: HY000

    Message: %s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB

  • Error number: MY-013699; Symbol: ER_HEALTH_WARNING_DISK_USAGE_LEVEL_3; SQLSTATE: HY000

    Message: %s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB

  • Error number: MY-013700; Symbol: ER_IB_INNODB_TBSP_OUT_OF_SPACE; SQLSTATE: HY000

    Message: InnoDB: Size of tablespace %s is more than the maximum size allowed.

  • Error number: MY-013701; Symbol: ER_GRP_RPL_APPLIER_CHANNEL_STILL_RUNNING; SQLSTATE: HY000

    Message: The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.

  • Error number: MY-013702; Symbol: ER_RPL_ASYNC_RECONNECT_GTID_MODE_OFF_CHANNEL; SQLSTATE: HY000

    Message: Detected misconfiguration: replication channel \'%s\' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL \'%s\', or change GTID_MODE to value ON, before starting the replica receiver thread.

  • Error number: MY-013703; Symbol: ER_FIREWALL_SERVICES_NOT_ACQUIRED; SQLSTATE: HY000

    Message: Could not acquire required component services.

  • Error number: MY-013704; Symbol: ER_FIREWALL_UDF_REGISTER_FAILED; SQLSTATE: HY000

    Message: Automatic registration of function(s) failed.

  • Error number: MY-013705; Symbol: ER_FIREWALL_PFS_TABLE_REGISTER_FAILED; SQLSTATE: HY000

    Message: Automatic registration of Performance schema table(s) failed.

  • Error number: MY-013706; Symbol: ER_IB_MSG_STATS_SAMPLING_TOO_LARGE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013707; Symbol: ER_AUDIT_LOG_FILE_PRUNE_FAILED; SQLSTATE: HY000

    Message: Failed to auto-prune file '%s', Error (%d): %s

  • Error number: MY-013708; Symbol: ER_AUDIT_LOG_FILE_AUTO_PRUNED; SQLSTATE: HY000

    Message: File '%s' auto-pruned

  • Error number: MY-013709; Symbol: ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_INIT; SQLSTATE: HY000

    Message: Received an error while processing components from manifest file: %s

  • Error number: MY-013710; Symbol: ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_DEINIT; SQLSTATE: HY000

    Message: Received an error while unloading components read from manifest file: %s

  • Error number: MY-013711; Symbol: ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_NOT_RO; SQLSTATE: HY000

    Message: Manifest file '%s' is not read-only. For better security, please make sure that the file is read-only.

  • Error number: MY-013712; Symbol: ER_WARN_NO_KEYRING_COMPONENT_SERVICE_FOUND; SQLSTATE: HY000

    Message: No suitable '%s' service implementation found to fulfill the request.

  • Error number: MY-013713; Symbol: ER_NOTE_KEYRING_COMPONENT_INITIALIZED; SQLSTATE: HY000

    Message: Keyring component initialized successfully.

  • Error number: MY-013714; Symbol: ER_KEYRING_COMPONENT_NOT_INITIALIZED; SQLSTATE: HY000

    Message: The component is not initialized properly. Error: %s. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.

  • Error number: MY-013715; Symbol: ER_KEYRING_COMPONENT_EXCEPTION; SQLSTATE: HY000

    Message: Keyring component encountered an exception while executing : '%s' API of service: '%s'

  • Error number: MY-013716; Symbol: ER_KEYRING_COMPONENT_MEMORY_ALLOCATION_ERROR; SQLSTATE: HY000

    Message: Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'

  • Error number: MY-013717; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_INVALID_MODE_BLOCK_SIZE; SQLSTATE: HY000

    Message: Empty or 0 values for AES encryption mode and/or block size are not permitted.

  • Error number: MY-013718; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_DATA_IDENTIFIER_EMPTY; SQLSTATE: HY000

    Message: A valid data identifier is required in order to fetch the key required for the AES operation.

  • Error number: MY-013719; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_INVALID_KEY; SQLSTATE: HY000

    Message: Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.

  • Error number: MY-013720; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_OPERATION_ERROR; SQLSTATE: HY000

    Message: Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.

  • Error number: MY-013721; Symbol: ER_NOTE_KEYRING_COMPONENT_READ_DATA_NOT_FOUND; SQLSTATE: HY000

    Message: Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.

  • Error number: MY-013722; Symbol: ER_NOTE_KEYRING_COMPONENT_WRITE_MAXIMUM_DATA_LENGTH; SQLSTATE: HY000

    Message: Maximum permissible size of data is '%zu' bits

  • Error number: MY-013723; Symbol: ER_NOTE_KEYRING_COMPONENT_STORE_FAILED; SQLSTATE: HY000

    Message: Error writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.

  • Error number: MY-013724; Symbol: ER_NOTE_KEYRING_COMPONENT_REMOVE_FAILED; SQLSTATE: HY000

    Message: Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.

  • Error number: MY-013725; Symbol: ER_NOTE_KEYRING_COMPONENT_GENERATE_FAILED; SQLSTATE: HY000

    Message: Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.

  • Error number: MY-013726; Symbol: ER_NOTE_KEYRING_COMPONENT_KEYS_METADATA_ITERATOR_FETCH_FAILED; SQLSTATE: HY000

    Message: Failed to get metadata from current keys metadata iterator position.

  • Error number: MY-013727; Symbol: ER_NOTE_KEYRING_COMPONENT_METADATA_ITERATOR_INVALID_OUT_PARAM; SQLSTATE: HY000

    Message: Key and value length parameters must not be null.

  • Error number: MY-013728; Symbol: ER_IB_WRN_FAILED_TO_ACQUIRE_SERVICE; SQLSTATE: HY000

    Message: Innodb could not acquire service : %s

  • Error number: MY-013729; Symbol: ER_IB_WRN_OLD_GEOMETRY_TYPE; SQLSTATE: HY000

    Message: Column %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.

  • Error number: MY-013730; Symbol: ER_NET_WAIT_ERROR2; SQLSTATE: HY000

    Message: 'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.

  • Error number: MY-013731; Symbol: ER_GRP_RPL_MEMBER_ACTION_TRIGGERED; SQLSTATE: HY000

    Message: The member action "%s" for event "%s" with priority "%u" will be run.

  • Error number: MY-013732; Symbol: ER_GRP_RPL_MEMBER_ACTION_FAILURE_IGNORE; SQLSTATE: HY000

    Message: The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.

  • Error number: MY-013733; Symbol: ER_GRP_RPL_MEMBER_ACTION_FAILURE; SQLSTATE: HY000

    Message: The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.

  • Error number: MY-013734; Symbol: ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_RECEIVE; SQLSTATE: HY000

    Message: Unable to parse the member actions configuration sent by the primary.

  • Error number: MY-013735; Symbol: ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS; SQLSTATE: HY000

    Message: Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.

  • Error number: MY-013736; Symbol: ER_GRP_RPL_MEMBER_ACTION_GET_EXCHANGEABLE_DATA; SQLSTATE: HY000

    Message: Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.

  • Error number: MY-013737; Symbol: ER_GRP_RPL_MEMBER_ACTION_DEFAULT_CONFIGURATION; SQLSTATE: HY000

    Message: This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.

  • Error number: MY-013738; Symbol: ER_GRP_RPL_MEMBER_ACTION_UNABLE_TO_SET_DEFAULT_CONFIGURATION; SQLSTATE: HY000

    Message: Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.

  • Error number: MY-013739; Symbol: ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_MEMBER_JOIN; SQLSTATE: HY000

    Message: Unable to parse the member actions configuration sent by the group on member join.

  • Error number: MY-013740; Symbol: ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS_ON_MEMBER_JOIN; SQLSTATE: HY000

    Message: Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.

  • Error number: MY-013741; Symbol: ER_GRP_RPL_MEMBER_ACTION_INVALID_ACTIONS_ON_MEMBER_JOIN; SQLSTATE: HY000

    Message: The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.

  • Error number: MY-013742; Symbol: ER_GRP_RPL_MEMBER_ACTION_ENABLED; SQLSTATE: HY000

    Message: Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".

  • Error number: MY-013743; Symbol: ER_GRP_RPL_MEMBER_ACTION_DISABLED; SQLSTATE: HY000

    Message: Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".

  • Error number: MY-013744; Symbol: ER_GRP_RPL_MEMBER_ACTIONS_RESET; SQLSTATE: HY000

    Message: Member actions configuration was reset.

  • Error number: MY-013747; Symbol: ER_FIREWALL_DEPRECATED_USER_PROFILE; SQLSTATE: HY000

    Message: User profile \'%s\' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.

  • Error number: MY-013748; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_INVALID; SQLSTATE: HY000

    Message: Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.

  • Error number: MY-013749; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_SAME_AS_GROUP_NAME; SQLSTATE: HY000

    Message: Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.

  • Error number: MY-013750; Symbol: ER_GRP_RPL_GROUP_NAME_SAME_AS_VIEW_CHANGE_UUID; SQLSTATE: HY000

    Message: group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATIC

  • Error number: MY-013751; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID; SQLSTATE: HY000

    Message: The group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel

  • Error number: MY-013752; Symbol: ER_GRP_RPL_GRP_VIEW_CHANGE_UUID_IS_INCOMPATIBLE_WITH_SERVER_UUID; SQLSTATE: HY000

    Message: group_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.

  • Error number: MY-013753; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_DIFF_FROM_GRP; SQLSTATE: HY000

    Message: The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.

  • Error number: MY-013754; Symbol: ER_WARN_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_VIEW_CHANGE_UUID; SQLSTATE: HY000

    Message: Replication channel '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.

  • Error number: MY-013755; Symbol: ER_GRP_RPL_FAILED_TO_PARSE_THE_VIEW_CHANGE_UUID; SQLSTATE: HY000

    Message: Unable to parse the group_replication_view_change_uuid.

  • Error number: MY-013756; Symbol: ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_VIEW_CHANGE_UUID; SQLSTATE: HY000

    Message: Unable to generate sidno for group_replication_view_change_uuid.

  • Error number: MY-013757; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_PARSE_ERROR; SQLSTATE: HY000

    Message: Unable to parse the group_replication_view_change_uuid during the Certification module initialization.

  • Error number: MY-013758; Symbol: ER_GRP_RPL_UPDATE_GRPGTID_VIEW_CHANGE_UUID_EXECUTED_ERROR; SQLSTATE: HY000

    Message: Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.

  • Error number: MY-013759; Symbol: ER_GRP_RPL_ADD_VIEW_CHANGE_UUID_TO_GRP_SID_MAP_ERROR; SQLSTATE: HY000

    Message: Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.

  • Error number: MY-013760; Symbol: ER_GRP_RPL_DONOR_VIEW_CHANGE_UUID_TRANS_INFO_ERROR; SQLSTATE: HY000

    Message: Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.

  • Error number: MY-013761; Symbol: ER_WARN_GRP_RPL_VIEW_CHANGE_UUID_FAIL_GET_VARIABLE; SQLSTATE: HY000

    Message: Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.

  • Error number: MY-013762; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_AND_PRUNE_SECONDS_LOG; SQLSTATE: HY000

    Message: Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignored

  • Error number: MY-013763; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_CLOSE_TO_ROTATE_ON_SIZE_LOG; SQLSTATE: HY000

    Message: audit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.

  • Error number: MY-013764; Symbol: ER_PLUGIN_INVALID_TABLE_DEFINITION; SQLSTATE: HY000

    Message: Invalid table definition for '%s.%s'.

  • Error number: MY-013765; Symbol: ER_AUTH_KERBEROS_LOGGER_GENERIC_MSG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013766; Symbol: ER_INSTALL_PLUGIN_CONFLICT_LOG; SQLSTATE: HY000

    Message: Cannot install the %s plugin when the %s plugin is installed.

  • Error number: MY-013767; Symbol: ER_DEPRECATED_PERSISTED_VARIABLE_WITH_ALIAS; SQLSTATE: HY000

    Message: The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.

  • Error number: MY-013768; Symbol: ER_LOG_COMPONENT_FLUSH_FAILED; SQLSTATE: HY000

    Message: %d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.

  • Error number: MY-013769; Symbol: ER_IB_MSG_REENCRYPTED_TABLESPACE_KEY; SQLSTATE: HY000

    Message: Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.

  • Error number: MY-013770; Symbol: ER_IB_MSG_REENCRYPTED_GENERAL_TABLESPACE_KEY; SQLSTATE: HY000

    Message: Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.

  • Error number: MY-013771; Symbol: ER_IB_ERR_PAGE_ARCH_DBLWR_INIT_FAILED; SQLSTATE: HY000

    Message: Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.

  • Error number: MY-013772; Symbol: ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__SKIP_IBUF_MERGES; SQLSTATE: HY000

    Message: There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.

  • Error number: MY-013773; Symbol: ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__UNEXPECTED; SQLSTATE: HY000

    Message: There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).

  • Error number: MY-013774; Symbol: ER_WARN_AUDIT_LOG_FORMAT_UNIX_TIMESTAMP_ONLY_WHEN_JSON_LOG; SQLSTATE: HY000

    Message: audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.

  • Error number: MY-013775; Symbol: ER_PREPARE_FOR_PRIMARY_ENGINE; SQLSTATE: HY000

    Message: Retry the statement using the primary storage engine.

  • Error number: MY-013776; Symbol: ER_IB_MSG_PAR_RSEG_INIT_COMPLETE_MSG; SQLSTATE: HY000

    Message: Parallel initialization of rseg complete

  • Error number: MY-013777; Symbol: ER_IB_MSG_PAR_RSEG_INIT_TIME_MSG; SQLSTATE: HY000

    Message: Time taken to initialize rseg using %u thread: %u ms.

  • Error number: MY-013778; Symbol: ER_DDL_MSG_1; SQLSTATE: HY000

    Message: DDL failed to create a thread to load an index, fall back to single thread

  • Error number: MY-013779; Symbol: ER_MTR_MSG_1; SQLSTATE: HY000

    Message: Debug_check_no_latching failed, slot->type=%d

  • Error number: MY-013780; Symbol: ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_CONN_ERR; SQLSTATE: HY000

    Message: Failed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.

  • Error number: MY-013781; Symbol: ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_COMMAND_ERR; SQLSTATE: HY000

    Message: Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.

  • Error number: MY-013782; Symbol: ER_GRP_RPL_FAILOVER_CONF_GET_EXCHANGEABLE_DATA; SQLSTATE: HY000

    Message: Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.

  • Error number: MY-013783; Symbol: ER_GRP_RPL_FAILOVER_CONF_DEFAULT_CONFIGURATION; SQLSTATE: HY000

    Message: This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.

  • Error number: MY-013784; Symbol: ER_GRP_RPL_FAILOVER_CONF_UNABLE_TO_SET_DEFAULT_CONFIGURATION; SQLSTATE: HY000

    Message: Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.

  • Error number: MY-013785; Symbol: ER_GRP_RPL_FAILOVER_CONF_PARSE_ON_MEMBER_JOIN; SQLSTATE: HY000

    Message: Unable to parse the replication failover channels configuration sent by the group on member join.

  • Error number: MY-013786; Symbol: ER_GRP_RPL_FAILOVER_CONF_CHANNEL_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.

  • Error number: MY-013787; Symbol: ER_GRP_RPL_FAILOVER_REGISTER_MESSAGE_LISTENER_SERVICE; SQLSTATE: HY000

    Message: Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.

  • Error number: MY-013788; Symbol: ER_GRP_RPL_FAILOVER_PRIMARY_WITHOUT_MAJORITY; SQLSTATE: HY000

    Message: This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.

  • Error number: MY-013789; Symbol: ER_GRP_RPL_FAILOVER_PRIMARY_BACK_TO_MAJORITY; SQLSTATE: HY000

    Message: This server is back to the group majority. Replication failover channels handling is resumed.

  • Error number: MY-013790; Symbol: ER_RPL_INCREMENTING_MEMBER_ACTION_VERSION; SQLSTATE: HY000

    Message: Error incrementing member action configuration version for %s.%s table.

  • Error number: MY-013791; Symbol: ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_SECONDARY_MEMBER; SQLSTATE: HY000

    Message: The '%s' thread of channel '%s' will error out as this server is a group secondary.

  • Error number: MY-013792; Symbol: ER_IB_MSG_CLONE_DDL_NTFN; SQLSTATE: HY000

    Message: Clone DDL Notification: %s

  • Error number: MY-013793; Symbol: ER_IB_MSG_CLONE_DDL_APPLY; SQLSTATE: HY000

    Message: Clone DDL APPLY: %s

  • Error number: MY-013794; Symbol: ER_IB_MSG_CLONE_DDL_INVALIDATE; SQLSTATE: HY000

    Message: Clone DDL Invalidate : %s

  • Error number: MY-013795; Symbol: ER_IB_MSG_UNDO_ENCRYPTION_INFO_LOADED; SQLSTATE: HY000

    Message: Encryption key is loaded for undo tablespace '%s'.

  • Error number: MY-013796; Symbol: ER_IB_WRN_ENCRYPTION_INFO_SIZE_MISMATCH; SQLSTATE: HY000

    Message: Ignoring encryption INFO size in redo log: %zu, expected: %zu

  • Error number: MY-013797; Symbol: ER_INVALID_AUTHENTICATION_POLICY; SQLSTATE: HY000

    Message: Option --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.

  • Error number: MY-013798; Symbol: ER_AUTHENTICATION_PLUGIN_REGISTRATION_FAILED; SQLSTATE: HY000

    Message: Signature verification failed during registration.

  • Error number: MY-013799; Symbol: ER_AUTHENTICATION_PLUGIN_REGISTRATION_INSUFFICIENT_BUFFER; SQLSTATE: HY000

    Message: Buffer too small to hold registration challenge response.

  • Error number: MY-013800; Symbol: ER_AUTHENTICATION_PLUGIN_AUTH_DATA_CORRUPT; SQLSTATE: HY000

    Message: FIDO device authenticator data corrupt.

  • Error number: MY-013801; Symbol: ER_AUTHENTICATION_PLUGIN_SIGNATURE_CORRUPT; SQLSTATE: HY000

    Message: FIDO device signature corrupt.

  • Error number: MY-013802; Symbol: ER_AUTHENTICATION_PLUGIN_VERIFY_SIGNATURE_FAILED; SQLSTATE: HY000

    Message: Signature verification failed during authentication.

  • Error number: MY-013803; Symbol: ER_AUTHENTICATION_PLUGIN_OOM; SQLSTATE: HY000

    Message: Out of memory.

  • Error number: MY-013804; Symbol: ER_AUTHENTICATION_PLUGIN_LOG; SQLSTATE: HY000

    Message: Can't initialize logging service.

  • Error number: MY-013805; Symbol: ER_WARN_REPLICA_GTID_ONLY_AND_GTID_MODE_NOT_ON; SQLSTATE: HY000

    Message: Replication channel '%s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.

  • Error number: MY-013806; Symbol: ER_WARN_L_DISABLE_GTID_ONLY_WITH_SOURCE_AUTO_POS_INVALID_POS; SQLSTATE: HY000

    Message: The replication positions relative to the source may be out-of-date on channel '%s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.

  • Error number: MY-013807; Symbol: ER_RPL_CANNOT_OPEN_RELAY_LOG; SQLSTATE: HY000

    Message: Could not open relay log: %s

  • Error number: MY-013808; Symbol: ER_AUTHENTICATION_OCI_PLUGIN_NOT_INITIALIZED; SQLSTATE: HY000

    Message: Authentication plugin not initialized.

  • Error number: MY-013809; Symbol: ER_AUTHENTICATION_OCI_PRIVATE_KEY_ERROR; SQLSTATE: HY000

    Message: Cannot use the generated private key file.

  • Error number: MY-013810; Symbol: ER_AUTHENTICATION_OCI_DOWNLOAD_PUBLIC_KEY; SQLSTATE: HY000

    Message: Unavailable public key with fingerprint %s for user %s in tenancy %s .

  • Error number: MY-013811; Symbol: ER_AUTHENTICATION_OCI_IMDS; SQLSTATE: HY000

    Message: Cannot obtain the OCI configuration from the IMDS service.

  • Error number: MY-013812; Symbol: ER_AUTHENTICATION_OCI_IAM; SQLSTATE: HY000

    Message: Cannot initialize the IAM service.

  • Error number: MY-013813; Symbol: ER_AUTHENTICATION_OCI_INVALID_AUTHENTICATION_STRING; SQLSTATE: HY000

    Message: Invalid authentication string details for user: `%s`@`%s`.

  • Error number: MY-013814; Symbol: ER_AUTHENTICATION_OCI_NO_MATCHING_GROUPS; SQLSTATE: HY000

    Message: None of the groups returned by IAM matches any of the entries from authentication string.

  • Error number: MY-013815; Symbol: ER_AUTHENTICATION_OCI_NO_GROUPS_FOUND; SQLSTATE: HY000

    Message: User is not part of any groups. However, account is configured to use group mapping.

  • Error number: MY-013816; Symbol: ER_AUTHENTICATION_OCI_NONCE; SQLSTATE: HY000

    Message: Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .

  • Error number: MY-013817; Symbol: ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_1; SQLSTATE: HY000

    Message: %s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB

  • Error number: MY-013818; Symbol: ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_2; SQLSTATE: HY000

    Message: %s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB

  • Error number: MY-013819; Symbol: ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_3; SQLSTATE: HY000

    Message: %s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB

  • Error number: MY-013820; Symbol: ER_GRP_RPL_SET_SINGLE_CONSENSUS_LEADER; SQLSTATE: HY000

    Message: The member %s:%u, with UUID: %s, was set as the single preferred consensus leader.

  • Error number: MY-013821; Symbol: ER_GRP_RPL_ERROR_SET_SINGLE_CONSENSUS_LEADER; SQLSTATE: HY000

    Message: Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.

  • Error number: MY-013822; Symbol: ER_GRP_RPL_SET_MULTI_CONSENSUS_LEADER; SQLSTATE: HY000

    Message: All members were set as consensus leaders.

  • Error number: MY-013823; Symbol: ER_GRP_RPL_ERROR_SET_MULTI_CONSENSUS_LEADER; SQLSTATE: HY000

    Message: Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.

  • Error number: MY-013824; Symbol: ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_GRP; SQLSTATE: HY000

    Message: This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.

  • Error number: MY-013825; Symbol: ER_MFA_USER_ATTRIBUTES_CORRUPT; SQLSTATE: HY000

    Message: Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".

  • Error number: MY-013826; Symbol: ER_MFA_PLUGIN_NOT_LOADED; SQLSTATE: HY000

    Message: Plugin \'%s\' is not loaded; Ignoring user

  • Error number: MY-013827; Symbol: ER_WARN_DEPRECATED_CHARSET_OPTION; SQLSTATE: HY000

    Message: %s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.

  • Error number: MY-013828; Symbol: ER_WARN_DEPRECATED_COLLATION_OPTION; SQLSTATE: HY000

    Message: %s: '%s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.

  • Error number: MY-013829; Symbol: ER_REGEXP_MISSING_ICU_DATADIR; SQLSTATE: HY000

    Message: Missing data directory for ICU regular expressions: %s.

  • Error number: MY-013830; Symbol: ER_IB_WARN_MANY_NON_LRU_FILES_OPENED; SQLSTATE: HY000

    Message: More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.

  • Error number: MY-013831; Symbol: ER_IB_MSG_TRYING_TO_OPEN_FILE_FOR_LONG_TIME; SQLSTATE: HY000

    Message: Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.

  • Error number: MY-013832; Symbol: ER_GLOBAL_CONN_LIMIT; SQLSTATE: HY000

    Message: Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.

  • Error number: MY-013833; Symbol: ER_CONN_LIMIT; SQLSTATE: HY000

    Message: Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.

  • Error number: MY-013834; Symbol: ER_WARN_AUDIT_LOG_DISABLED; SQLSTATE: HY000

    Message: Audit Log is disabled. Enable it with audit_log_disable = false.

  • Error number: MY-013835; Symbol: ER_INVALID_TLS_VERSION; SQLSTATE: HY000

    Message: Option --tls-version or --admin-tls-version is set to an invalid value %s.

  • Error number: MY-013836; Symbol: ER_RPL_RELAY_LOG_RECOVERY_GTID_ONLY; SQLSTATE: HY000

    Message: Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.

  • Error number: MY-013837; Symbol: ER_KEYRING_OKV_STANDBY_SERVER_COUNT_EXCEEDED; SQLSTATE: HY000

    Message: Number of STANDBY_SERVER values exceeded maximum limit of 64.

  • Error number: MY-013838; Symbol: ER_WARN_MIGRATION_EMPTY_SOURCE_KEYRING; SQLSTATE: HY000

    Message: Source keyring does not have any keys to migrate.

  • Error number: MY-013839; Symbol: ER_WARN_CANNOT_PERSIST_SENSITIVE_VARIABLES; SQLSTATE: HY000

    Message: Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.

  • Error number: MY-013840; Symbol: ER_CANNOT_INTERPRET_PERSISTED_SENSITIVE_VARIABLES; SQLSTATE: HY000

    Message: Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.

  • Error number: MY-013841; Symbol: ER_PERSISTED_VARIABLES_KEYRING_SUPPORT_REQUIRED; SQLSTATE: HY000

    Message: Keyring has to be loaded through manifest file in order to support secure storage for persisted variables

  • Error number: MY-013842; Symbol: ER_PERSISTED_VARIABLES_MASTER_KEY_NOT_FOUND; SQLSTATE: HY000

    Message: Could not find master key %s in keyring

  • Error number: MY-013843; Symbol: ER_PERSISTED_VARIABLES_MASTER_KEY_CANNOT_BE_GENERATED; SQLSTATE: HY000

    Message: A new master key %s could not be generated

  • Error number: MY-013844; Symbol: ER_PERSISTED_VARIABLES_ENCRYPTION_FAILED; SQLSTATE: HY000

    Message: Failed to encrypt %s using %s

  • Error number: MY-013845; Symbol: ER_PERSISTED_VARIABLES_DECRYPTION_FAILED; SQLSTATE: HY000

    Message: Failed to decrypt %s using %s

  • Error number: MY-013846; Symbol: ER_PERSISTED_VARIABLES_LACK_KEYRING_SUPPORT; SQLSTATE: HY000

    Message: Persisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.

  • Error number: MY-013847; Symbol: ER_MY_MALLOC_USING_JEMALLOC; SQLSTATE: HY000

    Message: Using jemalloc.dll for my_malloc and ut::malloc etc.

  • Error number: MY-013848; Symbol: ER_MY_MALLOC_USING_STD_MALLOC; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-013849; Symbol: ER_MY_MALLOC_LOADLIBRARY_FAILED; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-013850; Symbol: ER_MY_MALLOC_GETPROCADDRESS_FAILED; SQLSTATE: HY000

    Message: %s.

  • Error number: MY-013851; Symbol: ER_ACCOUNT_WITH_EXPIRED_PASSWORD; SQLSTATE: HY000

    Message: Password for the account '%s'@'%s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.

  • Error number: MY-013852; Symbol: ER_THREAD_POOL_PLUGIN_STARTED; SQLSTATE: HY000

    Message: Thread pool plugin started successfully with parameters: %s

  • Error number: MY-013853; Symbol: ER_THREAD_POOL_DEDICATED_LISTENERS_INVALID; SQLSTATE: HY000

    Message: thread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0

  • Error number: MY-013854; Symbol: ER_IB_DBLWR_BYTES_INFO; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013855; Symbol: ER_IB_RDBLWR_BYTES_INFO; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013856; Symbol: ER_IB_MSG_LOG_FILE_IS_EMPTY; SQLSTATE: HY000

    Message: The redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.

  • Error number: MY-013857; Symbol: ER_IB_MSG_LOG_FILE_TOO_SMALL; SQLSTATE: HY000

    Message: The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.

  • Error number: MY-013858; Symbol: ER_IB_MSG_LOG_FILE_TOO_BIG; SQLSTATE: HY000

    Message: The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.

  • Error number: MY-013859; Symbol: ER_IB_MSG_LOG_FILE_HEADER_READ_FAILED; SQLSTATE: HY000

    Message: Failed to read header of the redo log file %s

  • Error number: MY-013860; Symbol: ER_IB_MSG_LOG_INIT_DIR_NOT_EMPTY_WONT_INITIALIZE; SQLSTATE: HY000

    Message: --initialize specified but the redo log directory %s has redo log files inside. Aborting.

  • Error number: MY-013861; Symbol: ER_IB_MSG_LOG_INIT_DIR_LIST_FAILED; SQLSTATE: HY000

    Message: Failed to list redo log files in the redo log directory %s

  • Error number: MY-013862; Symbol: ER_IB_MSG_LOG_INIT_DIR_MISSING_SUBDIR; SQLSTATE: HY000

    Message: Neither found %s subdirectory, nor %s* files in %s

  • Error number: MY-013863; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_CLONE_AND_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Cannot restore cloned data directory, InnoDB running in read-only mode!

  • Error number: MY-013864; Symbol: ER_IB_MSG_LOG_WRITER_WRITE_FAILED; SQLSTATE: HY000

    Message: Error %d encountered when writing to the redo log file: %s.

  • Error number: MY-013865; Symbol: ER_IB_MSG_LOG_WRITER_WAIT_ON_NEW_LOG_FILE; SQLSTATE: HY000

    Message: Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.

  • Error number: MY-013866; Symbol: ER_IB_MSG_RECOVERY_CHECKPOINT_OUTSIDE_LOG_FILE; SQLSTATE: HY000

    Message: Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.

  • Error number: MY-013867; Symbol: ER_IB_MSG_LOG_WRITER_ENTERED_EXTRA_MARGIN; SQLSTATE: HY000

    Message: Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.

  • Error number: MY-013868; Symbol: ER_IB_MSG_LOG_WRITER_EXITED_EXTRA_MARGIN; SQLSTATE: HY000

    Message: Redo log reclaimed some free space, resuming user threads.

  • Error number: MY-013869; Symbol: ER_IB_MSG_LOG_PARAMS_FILE_SIZE_UNUSED; SQLSTATE: HY000

    Message: Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.

  • Error number: MY-013870; Symbol: ER_IB_MSG_LOG_PARAMS_N_FILES_UNUSED; SQLSTATE: HY000

    Message: Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.

  • Error number: MY-013871; Symbol: ER_IB_MSG_LOG_UPGRADE_FORCED_RECV; SQLSTATE: HY000

    Message: Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.

  • Error number: MY-013872; Symbol: ER_IB_MSG_LOG_UPGRADE_IN_READ_ONLY_MODE; SQLSTATE: HY000

    Message: Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).

  • Error number: MY-013873; Symbol: ER_IB_MSG_LOG_UPGRADE_CLONED_DB; SQLSTATE: HY000

    Message: Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).

  • Error number: MY-013874; Symbol: ER_IB_MSG_LOG_UPGRADE_UNINITIALIZED_FILES; SQLSTATE: HY000

    Message: Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).

  • Error number: MY-013875; Symbol: ER_IB_MSG_LOG_UPGRADE_CORRUPTION__UNEXPECTED; SQLSTATE: HY000

    Message: Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).

  • Error number: MY-013879; Symbol: ER_IB_MSG_LOG_FILE_FOREIGN_UUID; SQLSTATE: HY000

    Message: The redo log file %s comes from other data directory than redo log file %s.

  • Error number: MY-013880; Symbol: ER_IB_MSG_LOG_FILE_INVALID_START_LSN; SQLSTATE: HY000

    Message: The redo log file %s has invalid start_lsn %llu.

  • Error number: MY-013881; Symbol: ER_IB_MSG_LOG_FILE_INVALID_LSN_RANGES; SQLSTATE: HY000

    Message: The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).

  • Error number: MY-013882; Symbol: ER_IB_MSG_LOG_FILE_MISSING_FOR_ID; SQLSTATE: HY000

    Message: Missing redo log file %s (with start_lsn = %llu).

  • Error number: MY-013883; Symbol: ER_IB_MSG_LOG_CHECKPOINT_FOUND; SQLSTATE: HY000

    Message: The latest found checkpoint is at lsn = %llu in redo log file %s.

  • Error number: MY-013884; Symbol: ER_IB_MSG_LOG_FILES_CAPACITY_CHANGED; SQLSTATE: HY000

    Message: User has set innodb_redo_log_capacity to %lluM.

  • Error number: MY-013885; Symbol: ER_IB_MSG_LOG_FILES_RESIZE_REQUESTED; SQLSTATE: HY000

    Message: Redo log has been requested to resize from %lluM to %lluM.

  • Error number: MY-013886; Symbol: ER_IB_MSG_LOG_FILES_RESIZE_CANCELLED; SQLSTATE: HY000

    Message: Redo log resize has been cancelled.

  • Error number: MY-013887; Symbol: ER_IB_MSG_LOG_FILES_RESIZE_FINISHED; SQLSTATE: HY000

    Message: Redo log has been resized to %lluM.

  • Error number: MY-013888; Symbol: ER_IB_MSG_LOG_FILES_UPGRADE; SQLSTATE: HY000

    Message: Upgrading redo log: %lluM, LSN=%llu.

  • Error number: MY-013889; Symbol: ER_IB_MSG_LOG_FILE_MARK_CURRENT_AS_INCOMPLETE; SQLSTATE: HY000

    Message: Marked the current redo log file %s as incomplete.

  • Error number: MY-013890; Symbol: ER_IB_MSG_LOG_FILE_REMOVE_FAILED; SQLSTATE: HY000

    Message: Failed to remove redo log file %s.

  • Error number: MY-013891; Symbol: ER_IB_MSG_LOG_FILE_RENAME_ON_CREATE_FAILED; SQLSTATE: HY000

    Message: Failed to rename %s when creating redo log file %s (error: %d)

  • Error number: MY-013892; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_UNKNOWN_CREATOR; SQLSTATE: HY000

    Message: Redo log files created by unknown creator %s.

  • Error number: MY-013893; Symbol: ER_IB_MSG_LOG_FILES_FOUND_MISSING; SQLSTATE: HY000

    Message: Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.

  • Error number: MY-013894; Symbol: ER_IB_MSG_LOG_FILE_FORMAT_TOO_NEW; SQLSTATE: HY000

    Message: Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.

  • Error number: MY-013895; Symbol: ER_IB_MSG_LOG_FILE_FORMAT_TOO_OLD; SQLSTATE: HY000

    Message: Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.

  • Error number: MY-013896; Symbol: ER_IB_MSG_LOG_FILE_DIFFERENT_FORMATS; SQLSTATE: HY000

    Message: Found redo log files with different formats: %s has format v%lu, %s has format v%lu.

  • Error number: MY-013897; Symbol: ER_IB_MSG_LOG_PRE_8_0_30_MISSING_FILE0; SQLSTATE: HY000

    Message: Missing ib_logfile0 in the directory %s.

  • Error number: MY-013898; Symbol: ER_IB_MSG_LOG_PFS_ACQUIRE_SERVICES_FAILED; SQLSTATE: HY000

    Message: Failed to initialize services required to handle redo log PFS tables.

  • Error number: MY-013899; Symbol: ER_IB_MSG_LOG_PFS_CREATE_TABLES_FAILED; SQLSTATE: HY000

    Message: Failed to create redo log PFS tables.

  • Error number: MY-013900; Symbol: ER_IB_MSG_LOG_FILE_TRUNCATE; SQLSTATE: HY000

    Message: Truncating redo log file %s...

  • Error number: MY-013901; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_RESIZE_FAILED; SQLSTATE: HY000

    Message: Failed to resize unused redo log file %s to %llu MB (%s).

  • Error number: MY-013902; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_REMOVE_FAILED; SQLSTATE: HY000

    Message: Failed to remove unused redo log file %s.

  • Error number: MY-013903; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_RENAME_FAILED; SQLSTATE: HY000

    Message: Failed to rename unused redo log file %s to %s.

  • Error number: MY-013904; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_MARK_AS_IN_USE_FAILED; SQLSTATE: HY000

    Message: Failed to mark unused redo log file %s as in use (by renaming to %s).

  • Error number: MY-013905; Symbol: ER_IB_MSG_LOG_FILE_MARK_AS_UNUSED_FAILED; SQLSTATE: HY000

    Message: Failed to mark redo log file %s as unused (by renaming to %s).

  • Error number: MY-013906; Symbol: ER_IB_MSG_LOG_PARAMS_DEDICATED_SERVER_IGNORED; SQLSTATE: HY000

    Message: Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.

  • Error number: MY-013907; Symbol: ER_IB_MSG_LOG_PARAMS_LEGACY_USAGE; SQLSTATE: HY000

    Message: Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.

  • Error number: MY-013908; Symbol: ER_GRP_RPL_FAILED_TO_LOG_VIEW_CHANGE; SQLSTATE: HY000

    Message: This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.

  • Error number: MY-013909; Symbol: ER_BINLOG_CRASH_RECOVERY_MALFORMED_LOG; SQLSTATE: HY000

    Message: Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.

  • Error number: MY-013910; Symbol: ER_BINLOG_CRASH_RECOVERY_ERROR_RETURNED_SE; SQLSTATE: HY000

    Message: Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.

  • Error number: MY-013911; Symbol: ER_BINLOG_CRASH_RECOVERY_ENGINE_RESULTS; SQLSTATE: HY000

    Message: Crash recovery finished in %s engine. %s

  • Error number: MY-013912; Symbol: ER_BINLOG_CRASH_RECOVERY_COMMIT_FAILED; SQLSTATE: HY000

    Message: Failed to commit %s in %s, with failure code %s.

  • Error number: MY-013913; Symbol: ER_BINLOG_CRASH_RECOVERY_ROLLBACK_FAILED; SQLSTATE: HY000

    Message: Failed to rollback %s in %s, with failure code %s.

  • Error number: MY-013914; Symbol: ER_BINLOG_CRASH_RECOVERY_PREPARE_FAILED; SQLSTATE: HY000

    Message: Failed to prepare %s in %s, with failure code %s.

  • Error number: MY-013915; Symbol: ER_COMPONENT_EE_SYS_VAR_REGISTRATION_FAILURE; SQLSTATE: HY000

    Message: Cannot register variable '%s'. Please check if it is not already registered by another component.

  • Error number: MY-013916; Symbol: ER_COMPONENT_EE_SYS_VAR_DEREGISTRATION_FAILURE; SQLSTATE: HY000

    Message: Cannot unregister variable '%s'. Please check if it was registered properly in the first place.

  • Error number: MY-013917; Symbol: ER_COMPONENT_EE_FUNCTION_REGISTRATION_FAILURE; SQLSTATE: HY000

    Message: Cannot register function '%s'. Please check if it is not already registered.

  • Error number: MY-013918; Symbol: ER_COMPONENT_EE_FUNCTION_DEREGISTRATION_FAILURE; SQLSTATE: HY000

    Message: Cannot unregister function '%s'. Please check if it was registered properly in the first place.

  • Error number: MY-013919; Symbol: ER_COMPONENT_EE_FUNCTION_INVALID_ARGUMENTS; SQLSTATE: HY000

    Message: Invalid arguments to function '%s'. Expected values: %s.

  • Error number: MY-013920; Symbol: ER_COMPONENT_EE_FUNCTION_INVALID_ALGORITHM; SQLSTATE: HY000

    Message: Invalid algorithm value '%s' in function %s.

  • Error number: MY-013921; Symbol: ER_COMPONENT_EE_FUNCTION_KEY_LENGTH_OUT_OF_RANGE; SQLSTATE: HY000

    Message: Invalid key length '%d' for function '%s' with algorithm '%s'. Please provide a value between [%d, %d].

  • Error number: MY-013922; Symbol: ER_COMPONENT_EE_FUNCTION_PRIVATE_KEY_GENERATION_FAILURE; SQLSTATE: HY000

    Message: Failed to generate private key of length '%d' with algorithm '%s' in function '%s'. More details about the error would have been logged before this message.

  • Error number: MY-013923; Symbol: ER_COMPONENT_EE_FUNCTION_PUBLIC_KEY_GENERATION_FAILURE; SQLSTATE: HY000

    Message: Failed to generate public key with algorithm '%s' for given private key in function '%s'. More details about the error would have been logged before this message.

  • Error number: MY-013924; Symbol: ER_COMPONENT_EE_DATA_LENGTH_OUT_OF_RAGE; SQLSTATE: HY000

    Message: Invalid data length '%d' (in bytes) for function '%s' with algorithm '%s'. The maximum support data length for given private key is %d (in bytes).

  • Error number: MY-013925; Symbol: ER_COMPONENT_EE_DATA_ENCRYPTION_ERROR; SQLSTATE: HY000

    Message: Could not encrypt data in function '%s' using algorithm '%s'. Data length was '%d' bytes. More details about the error would have been logged before this message.

  • Error number: MY-013926; Symbol: ER_COMPONENT_EE_DATA_DECRYPTION_ERROR; SQLSTATE: HY000

    Message: Could not decrypt data in function '%s' using algorithm '%s'. Data length was '%d' bytes. More details about the error would have been logged before this message.

  • Error number: MY-013927; Symbol: ER_COMPONENT_EE_DATA_SIGN_ERROR; SQLSTATE: HY000

    Message: Could not sign data in function '%s' using algorithm '%s' and digest type '%s'. More details about the error would have logged before this message.

  • Error number: MY-013928; Symbol: ER_COMPONENT_EE_OPENSSL_ERROR; SQLSTATE: HY000

    Message: Received OpenSSL error in function '%s' for algorithm '%s': '%s'

  • Error number: MY-013929; Symbol: ER_COMPONENT_EE_INSUFFICIENT_LENGTH; SQLSTATE: HY000

    Message: In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.

  • Error number: MY-013930; Symbol: ER_SYSTEMD_NOTIFY_DEBUG; SQLSTATE: HY000

    Message: %s%s

  • Error number: MY-013931; Symbol: ER_TMP_SESSION_FOR_VAR; SQLSTATE: HY000

    Message: Setting session values for system variables only makes sense in a user session (failed to set '%s').

  • Error number: MY-013932; Symbol: ER_BUILD_ID; SQLSTATE: HY000

    Message: BuildID[sha1]=%s

  • Error number: MY-013933; Symbol: ER_THREAD_POOL_CANNOT_REGISTER_DYNAMIC_PRIVILEGE; SQLSTATE: HY000

    Message: Failed to register dynamic privilege %s.

  • Error number: MY-013934; Symbol: ER_IB_MSG_LOG_WRITER_WAIT_ON_CONSUMER; SQLSTATE: HY000

    Message: Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.

  • Error number: MY-013935; Symbol: ER_CONDITIONAL_DEBUG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013936; Symbol: ER_IB_MSG_PARSE_OLD_REDO_INDEX_VERSION; SQLSTATE: HY000

    Message: Recovery: Generating index information for INSTANT DDL Table in 8.0.29 format

  • Error number: MY-013941; Symbol: ER_IB_MSG_CLEAR_INSTANT_DROP_COLUMN_METADATA; SQLSTATE: HY000

    Message: Failed to clear instant drop column metadata for table %s

  • Error number: MY-013942; Symbol: ER_COMPONENT_KEYRING_OCI_OPEN_KEY_FILE; SQLSTATE: HY000

    Message: Cannot open signing key file %s.

  • Error number: MY-013943; Symbol: ER_COMPONENT_KEYRING_OCI_CREATE_PRIVATE_KEY; SQLSTATE: HY000

    Message: Out of memory! Cannot create private key.

  • Error number: MY-013944; Symbol: ER_COMPONENT_KEYRING_OCI_READ_KEY_FILE; SQLSTATE: HY000

    Message: Cannot read signing key file %s.

  • Error number: MY-013945; Symbol: ER_NOTE_COMPONENT_KEYRING_OCI_MISSING_NAME_OR_TYPE; SQLSTATE: HY000

    Message: Incomplete key: missing Name/Type for the Key: %s.

  • Error number: MY-013946; Symbol: ER_WARN_COMPONENT_KEYRING_OCI_DUPLICATE_KEY; SQLSTATE: HY000

    Message: Duplicate key found in keyring with Name: %s and Owner: %s.

  • Error number: MY-013947; Symbol: ER_KEYRING_OCI_PARSE_JSON; SQLSTATE: HY000

    Message: Error parsing JSON response %s.

  • Error number: MY-013948; Symbol: ER_KEYRING_OCI_INVALID_JSON; SQLSTATE: HY000

    Message: Invalid JSON response!

  • Error number: MY-013949; Symbol: ER_KEYRING_OCI_HTTP_REQUEST; SQLSTATE: HY000

    Message: HTTP request failed with error: '%s'

  • Error number: MY-013950; Symbol: ER_THREAD_POOL_SYSVAR_CHANGE; SQLSTATE: HY000

    Message: Variable thread_pool.%s was updated: %s

  • Error number: MY-013951; Symbol: ER_STACK_BACKTRACE; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013952; Symbol: ER_IB_MSG_BUF_POOL_RESIZE_COMPLETE_CUR_CODE; SQLSTATE: HY000

    Message: Status code %u: Completed

  • Error number: MY-013953; Symbol: ER_IB_MSG_BUF_POOL_RESIZE_PROGRESS_UPDATE; SQLSTATE: HY000

    Message: Status code %u: %u%% complete

  • Error number: MY-013954; Symbol: ER_IB_MSG_BUF_POOL_RESIZE_CODE_STATUS; SQLSTATE: HY000

    Message: Status code %u: %s

  • Error number: MY-013955; Symbol: ER_THREAD_POOL_QUERY_THREADS_PER_GROUP_INVALID; SQLSTATE: HY000

    Message: Invalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.

  • Error number: MY-013956; Symbol: ER_THREAD_POOL_QUERY_THRS_PER_GRP_EXCEEDS_TXN_THR_LIMIT; SQLSTATE: HY000

    Message: Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per group

  • Error number: MY-013957; Symbol: ER_IB_MSG_INVALID_PAGE_TYPE; SQLSTATE: HY000

    Message: Found page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lu

  • Error number: MY-013958; Symbol: ER_IB_PARALLEL_READER_WORKER_INFO; SQLSTATE: HY000

    Message: preader: thread_id=%zu, n_threads=%zu, n_ctx=%zu, one_range_per_thread=%s, n_index=%zu, index_list=%s, err=%zu

  • Error number: MY-013959; Symbol: ER_IB_BULK_LOAD_SUBTREE_INFO; SQLSTATE: HY000

    Message: bulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zu

  • Error number: MY-013960; Symbol: ER_IB_BULK_FLUSHER_INFO; SQLSTATE: HY000

    Message: bulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu

  • Error number: MY-013961; Symbol: ER_IB_BUFFER_POOL_OVERUSE; SQLSTATE: HY000

    Message: %s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.

  • Error number: MY-013962; Symbol: ER_IB_BUFFER_POOL_FULL; SQLSTATE: HY000

    Message: %s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!

  • Error number: MY-013963; Symbol: ER_IB_DUPLICATE_KEY; SQLSTATE: HY000

    Message: %s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)

  • Error number: MY-013964; Symbol: ER_REPLICATION_INCOMPATIBLE_TABLE_WITH_GIPK; SQLSTATE: HY000

    Message: Failed to apply row event with %d columns, originating from a server of version %s on table '%s.%s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.

  • Error number: MY-013965; Symbol: ER_BULK_EXECUTOR_INFO; SQLSTATE: HY000

    Message: Bulk executor: %s

  • Error number: MY-013966; Symbol: ER_BULK_LOADER_INFO; SQLSTATE: HY000

    Message: Bulk loader: %s

  • Error number: MY-013967; Symbol: ER_BULK_LOADER_FILE_CONTAINS_LESS_LINES_THAN_IGNORE_CLAUSE_LOG; SQLSTATE: HY000

    Message: The first file being loaded contained less lines than the ignore clause

  • Error number: MY-013968; Symbol: ER_BULK_READER_INFO; SQLSTATE: HY000

    Message: Bulk reader: %s

  • Error number: MY-013969; Symbol: ER_BULK_READER_LIBCURL_INIT_FAILED_LOG; SQLSTATE: HY000

    Message: Bulk reader failed to initialize libcurl

  • Error number: MY-013970; Symbol: ER_BULK_READER_LIBCURL_ERROR_LOG; SQLSTATE: HY000

    Message: Bulk reader got libcurl error: %s

  • Error number: MY-013971; Symbol: ER_BULK_READER_SERVER_ERROR_LOG; SQLSTATE: HY000

    Message: Bulk reader got error response from server: %ld

  • Error number: MY-013972; Symbol: ER_BULK_READER_COMMUNICATION_ERROR_LOG; SQLSTATE: HY000

    Message: Bulk reader got error in communication with source server, check the error log for additional details

  • Error number: MY-013973; Symbol: ER_BULK_PARSER_MISSING_ENCLOSED_BY_LOG; SQLSTATE: HY000

    Message: Missing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.

  • Error number: MY-013974; Symbol: ER_BULK_PARSER_ROW_BUFFER_MAX_TOTAL_COLS_EXCEEDED_LOG; SQLSTATE: HY000

    Message: The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.

  • Error number: MY-013975; Symbol: ER_BULK_PARSER_COPY_BUFFER_SIZE_EXCEEDED_LOG; SQLSTATE: HY000

    Message: The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.

  • Error number: MY-013976; Symbol: ER_BULK_PARSER_UNEXPECTED_END_OF_INPUT_LOG; SQLSTATE: HY000

    Message: Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.

  • Error number: MY-013977; Symbol: ER_BULK_PARSER_UNEXPECTED_ROW_TERMINATOR_LOG; SQLSTATE: HY000

    Message: Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.

  • Error number: MY-013978; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_ENDING_ENCLOSED_BY_LOG; SQLSTATE: HY000

    Message: Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.

  • Error number: MY-013979; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_NULL_ESCAPE_LOG; SQLSTATE: HY000

    Message: Unexpected characters after NULL escape (\\N) found at row %ld in file '%s'.

  • Error number: MY-013980; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_COLUMN_TERMINATOR_LOG; SQLSTATE: HY000

    Message: Unexpected characters after column terminator found at row %ld in file '%s'.

  • Error number: MY-013981; Symbol: ER_BULK_PARSER_INCOMPLETE_ESCAPE_SEQUENCE_LOG; SQLSTATE: HY000

    Message: Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.

  • Error number: MY-013982; Symbol: ER_LOAD_BULK_DATA_WRONG_VALUE_FOR_FIELD_LOG; SQLSTATE: HY000

    Message: Incorrect %s value: '%s' for column '%s' at row %ld in file '%s'

  • Error number: MY-013983; Symbol: ER_LOAD_BULK_DATA_WARN_NULL_TO_NOTNULL_LOG; SQLSTATE: HY000

    Message: NULL supplied to NOT NULL column '%s' at row %ld in file '%s'

  • Error number: MY-013984; Symbol: ER_IB_BULK_LOAD_THREAD_FAIL; SQLSTATE: HY000

    Message: %s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s

  • Error number: MY-013985; Symbol: ER_IB_BULK_LOAD_MERGE_FAIL; SQLSTATE: HY000

    Message: %s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%s

  • Error number: MY-013986; Symbol: ER_IB_LOAD_BULK_CONCURRENCY_REDUCED; SQLSTATE: HY000

    Message: LOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.

  • Error number: MY-013987; Symbol: ER_PLUGIN_EXCEPTION_OPERATION_FAILED; SQLSTATE: HY000

    Message: C++ Exception caught while %s the %s plugin: [%s]

  • Error number: MY-013988; Symbol: ER_REQUIRE_TABLE_PRIMARY_KEY_CHECK_GENERATE_WITH_GR_IN_REPO; SQLSTATE: HY000

    Message: Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.

  • Error number: MY-013989; Symbol: ER_CHECK_TABLE_INSTANT_VERSION_BIT_SET; SQLSTATE: HY000

    Message: Record has both instant and version bit set.

  • Error number: MY-013990; Symbol: ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_OLD_GRP; SQLSTATE: HY000

    Message: This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.

  • Error number: MY-013991; Symbol: ER_IB_WRN_IGNORE_REDO_LOG_CAPACITY; SQLSTATE: HY000

    Message: Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.

  • Error number: MY-013992; Symbol: ER_IB_PRIMARY_KEY_IS_INSTANT; SQLSTATE: HY000

    Message: Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging

  • Error number: MY-013993; Symbol: ER_THREAD_POOL_IDLE_CONNECTION_CLOSED; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013994; Symbol: ER_IB_HIDDEN_NAME_CONFLICT; SQLSTATE: HY000

    Message: Column name %s and internally generated INSTANT DROP column name %s is causing a conflict.

  • Error number: MY-013995; Symbol: ER_IB_DICT_INVALID_COLUMN_POSITION; SQLSTATE: HY000

    Message: Field number: %llu too large, Total fields in Record: %zu.

  • Error number: MY-013996; Symbol: ER_IB_DICT_LOG_TABLE_INFO; SQLSTATE: HY000

    Message: %s

  • Error number: MY-013997; Symbol: ER_RPL_ASYNC_NEXT_FAILOVER_CHANNEL_SELECTED; SQLSTATE: HY000

    Message: The connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'

  • Error number: MY-013998; Symbol: ER_RPL_REPLICA_SOURCE_UUID_HAS_NOT_CHANGED; SQLSTATE: HY000

    Message: The Replica which was connected to source \'%s:%d\', is now connected to new source \'%s:%d\', but still has the same server_uuid %s.

  • Error number: MY-013999; Symbol: ER_RPL_REPLICA_SOURCE_UUID_HAS_CHANGED_HOST_PORT_UNCHANGED; SQLSTATE: HY000

    Message: The server_uuid for source server \'%s:%d\' has changed from %s to %s. This should not happen unless you have changed it manually.

  • Error number: MY-014000; Symbol: ER_RPL_REPLICA_SOURCE_UUID_HOST_PORT_HAS_CHANGED; SQLSTATE: HY000

    Message: The source server has changed from \'%s:%d\' with server_uuid %s, to \'%s:%d\' with server_uuid %s.

  • Error number: MY-014001; Symbol: ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_FILE_BASED; SQLSTATE: HY000

    Message: Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.

  • Error number: MY-014002; Symbol: ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_GTID_BASED; SQLSTATE: HY000

    Message: Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting GTID-based replication.

  • Error number: MY-014003; Symbol: ER_IB_INDEX_LOADER_DONE; SQLSTATE: HY000

    Message: Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.

  • Error number: MY-014004; Symbol: ER_IB_INDEX_BUILDER_DONE; SQLSTATE: HY000

    Message: Builder::finish(): Completed building index=%s of table=%s, err=%zu.

  • Error number: MY-014005; Symbol: ER_WARN_DEPRECATED_USER_DEFINED_COLLATIONS_OPTION; SQLSTATE: HY000

    Message: %s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.

  • Error number: MY-014006; Symbol: ER_IB_INDEX_BUILDER_INIT; SQLSTATE: HY000

    Message: Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.

  • Error number: MY-014007; Symbol: ER_IB_SELECT_COUNT_STAR; SQLSTATE: HY000

    Message: SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.

  • Error number: MY-014008; Symbol: ER_IB_INDEX_LOG_VERSION_MISMATCH; SQLSTATE: HY000

    Message: Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.

  • Error number: MY-014009; Symbol: ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_MULTIPLE_KEYRING; SQLSTATE: HY000

    Message: Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.

  • Error number: MY-014010; Symbol: ER_GRP_RPL_HAS_STARTED; SQLSTATE: HY000

    Message: Plugin 'group_replication' has been started.

  • Error number: MY-014011; Symbol: ER_CHECK_TABLE_MIN_REC_FLAG_SET; SQLSTATE: HY000

    Message: Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.

  • Error number: MY-014012; Symbol: ER_CHECK_TABLE_MIN_REC_FLAG_NOT_SET; SQLSTATE: HY000

    Message: Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.

  • Error number: MY-014013; Symbol: ER_NOTE_COMPONENT_SLOT_REGISTRATION_SUCCESS; SQLSTATE: HY000

    Message: Successfully registered slot '%d' for component '%s'.

  • Error number: MY-014014; Symbol: ER_NOTE_COMPONENT_SLOT_DEREGISTRATION_SUCCESS; SQLSTATE: HY000

    Message: Successfully de-registered slot '%d' from component '%s'.

  • Error number: MY-014015; Symbol: ER_WARN_CANNOT_FREE_COMPONENT_DATA_DEALLOCATION_FAILED; SQLSTATE: HY000

    Message: Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.

  • Error number: MY-014016; Symbol: ER_IB_RESURRECT_TRX_INSERT; SQLSTATE: HY000

    Message: Transaction ID: %lu found for resurrecting inserts

  • Error number: MY-014017; Symbol: ER_IB_RESURRECT_TRX_UPDATE; SQLSTATE: HY000

    Message: Transaction ID: %lu found for resurrecting updates

  • Error number: MY-014018; Symbol: ER_IB_RESURRECT_IDENTIFY_TABLE_TO_LOCK; SQLSTATE: HY000

    Message: Identified table ID: %lu to acquire lock

  • Error number: MY-014019; Symbol: ER_IB_RESURRECT_ACQUIRE_TABLE_LOCK; SQLSTATE: HY000

    Message: Acquired lock on table ID: %lu, name: %s

  • Error number: MY-014020; Symbol: ER_IB_RESURRECT_RECORD_PROGRESS; SQLSTATE: HY000

    Message: Records read: %lu - Pages read: %lu

  • Error number: MY-014021; Symbol: ER_IB_RESURRECT_RECORD_COMPLETE; SQLSTATE: HY000

    Message: Total records resurrected: %lu - Total pages read: %lu - Total tables acquired: %lu

  • Error number: MY-014022; Symbol: ER_IB_RESURRECT_TRX_INSERT_COMPLETE; SQLSTATE: HY000

    Message: Resurrected %lu transactions doing inserts.

  • Error number: MY-014023; Symbol: ER_IB_RESURRECT_TRX_UPDATE_COMPLETE; SQLSTATE: HY000

    Message: Resurrected %lu transactions doing updates.

  • Error number: MY-014024; Symbol: ER_AUTHENTICATION_OCI_INVALID_TOKEN; SQLSTATE: HY000

    Message: Invalid security token provided by '%s' for '%s'@'%s': %s.

  • Error number: MY-014025; Symbol: ER_AUTHENTICATION_OCI_TOKEN_DETAILS_MISMATCH; SQLSTATE: HY000

    Message: Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.

  • Error number: MY-014026; Symbol: ER_AUTHENTICATION_OCI_TOKEN_NOT_VERIFIED; SQLSTATE: HY000

    Message: Verification failed for security token provided by '%s' for '%s'@'%s' : %s.

  • Error number: MY-014027; Symbol: ER_AUTHENTICATION_OCI_DOWNLOAD_IDDP_PUBLIC_KEY; SQLSTATE: HY000

    Message: Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.

  • Error number: MY-014029; Symbol: ER_SYS_VAR_REGISTRATION; SQLSTATE: HY000

    Message: Cannot register variable '%s'. Please check if it is not already registered by another component.

  • Error number: MY-014030; Symbol: ER_SYS_VAR_DEREGISTRATION; SQLSTATE: HY000

    Message: Cannot unregister variable '%s'. Please check if it was registered properly in the first place.

  • Error number: MY-014031; Symbol: ER_UDF_REGISTRATION; SQLSTATE: HY000

    Message: Cannot register function '%s'. Please check if it is not already registered by another component.

  • Error number: MY-014032; Symbol: ER_UDF_DEREGISTRATION; SQLSTATE: HY000

    Message: Cannot unregister function '%s'. Please check if it was registered properly in the first place.

  • Error number: MY-014033; Symbol: ER_PRIVILEGE_REGISTRATION; SQLSTATE: HY000

    Message: Cannot register privilege '%s'. Please check if it is not already registered.

  • Error number: MY-014034; Symbol: ER_PRIVILEGE_DEREGISTRATION; SQLSTATE: HY000

    Message: Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.

  • Error number: MY-014035; Symbol: ER_UDF_EXEC_FAILURE; SQLSTATE: HY000

    Message: Error while executing UDF %s.

  • Error number: MY-014036; Symbol: ER_UDF_EXEC_FAILURE_REASON; SQLSTATE: HY000

    Message: Error while executing UDF %s: %s.

  • Error number: MY-014037; Symbol: ER_COMPONENT_SERVICE_CALL; SQLSTATE: HY000

    Message: %s failed.

  • Error number: MY-014038; Symbol: ER_COMPONENT_SERVICE_CALL_RESULT; SQLSTATE: HY000

    Message: %s failed with %u.

  • Error number: MY-014039; Symbol: ER_COMPONENT_LOCK; SQLSTATE: HY000

    Message: Lock failed at %s : %u.

  • Error number: MY-014040; Symbol: ER_COMPONENT_UNLOCK; SQLSTATE: HY000

    Message: Lock from %s : %u failed to unlock.

  • Error number: MY-014041; Symbol: ER_COMPONENT_MASKING_OTHER_ERROR; SQLSTATE: HY000

    Message: Masking component error: '%s'.

  • Error number: MY-014042; Symbol: ER_COMPONENT_MASKING_ABI; SQLSTATE: HY000

    Message: %s failed.

  • Error number: MY-014043; Symbol: ER_COMPONENT_MASKING_ABI_REASON; SQLSTATE: HY000

    Message: %s failed because %s.

  • Error number: MY-014044; Symbol: ER_COMPONENT_MASKING_RANDOM_CREATE; SQLSTATE: HY000

    Message: Creation of random context failed.

  • Error number: MY-014045; Symbol: ER_COMPONENT_MASKING_RANDOM_CREATE_REASON; SQLSTATE: HY000

    Message: Creation of random context failed because %s.

  • Error number: MY-014046; Symbol: ER_COMPONENT_MASKING_CANNOT_ACCESS_TABLE; SQLSTATE: HY000

    Message: Cannot access %s.%s table.

  • Error number: MY-014047; Symbol: ER_REDUCED_DBLWR_FILE_CORRUPTED; SQLSTATE: HY000

    Message: Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.

  • Error number: MY-014048; Symbol: ER_REDUCED_DBLWR_PAGE_FOUND; SQLSTATE: HY000

    Message: Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.

  • Error number: MY-014049; Symbol: ER_CONN_INIT_CONNECT_IGNORED_MFA; SQLSTATE: HY000

    Message: init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxing

  • Error number: MY-014050; Symbol: ER_SECONDARY_ENGINE_DDL_FAILED; SQLSTATE: HY000

    Message: Execution of alter table %s %s failed because %s.

  • Error number: MY-014052; Symbol: ER_WARN_SCHEDULED_TASK_RUN_FAILED; SQLSTATE: HY000

    Message: Scheduled run of task %s failed

  • Error number: MY-014053; Symbol: ER_AUDIT_LOG_INVALID_FLUSH_INTERVAL_VALUE; SQLSTATE: HY000

    Message: Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d

  • Error number: MY-014054; Symbol: ER_LOG_CANNOT_PURGE_BINLOG_WITH_BACKUP_LOCK; SQLSTATE: HY000

    Message: Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.

  • Error number: MY-014055; Symbol: ER_CONVERT_MULTI_VALUE; SQLSTATE: HY000

    Message: Multi-values cannot be converted to MySQL format: %s

  • Error number: MY-014056; Symbol: ER_IB_DDL_CONVERT_HEAP_NOT_FOUND; SQLSTATE: HY000

    Message: Heap required to convert columns is not present.

  • Error number: MY-014057; Symbol: ER_SERVER_DOWNGRADE_FROM_VERSION; SQLSTATE: HY000

    Message: MySQL server downgrading from version '%u' to '%u'.

  • Error number: MY-014058; Symbol: ER_BEYOND_SERVER_DOWNGRADE_THRESHOLD; SQLSTATE: HY000

    Message: Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.

  • Error number: MY-014059; Symbol: ER_BEYOND_SERVER_UPGRADE_THRESHOLD; SQLSTATE: HY000

    Message: Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.

  • Error number: MY-014060; Symbol: ER_INVALID_SERVER_UPGRADE_NOT_LTS; SQLSTATE: HY000

    Message: Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.

  • Error number: MY-014061; Symbol: ER_INVALID_SERVER_DOWNGRADE_NOT_PATCH; SQLSTATE: HY000

    Message: Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.

  • Error number: MY-014062; Symbol: ER_FAILED_GET_DD_PROPERTY; SQLSTATE: HY000

    Message: Failed to get the data dictionary property %s.

  • Error number: MY-014063; Symbol: ER_FAILED_SET_DD_PROPERTY; SQLSTATE: HY000

    Message: Failed to set the data dictionary property %s.

  • Error number: MY-014064; Symbol: ER_SERVER_DOWNGRADE_STATUS; SQLSTATE: HY000

    Message: Server downgrade from '%d' to '%d' %s.

  • Error number: MY-014065; Symbol: ER_INFORMATION_SCHEMA_VERSION_CHANGE; SQLSTATE: HY000

    Message: %s information schema from version %u to %u.

  • Error number: MY-014066; Symbol: ER_PERFORMANCE_SCHEMA_VERSION_CHANGE; SQLSTATE: HY000

    Message: %s performance schema from version %u to %u.

  • Error number: MY-014067; Symbol: ER_WARN_DEPRECATED_OR_BLOCKED_CIPHER; SQLSTATE: HY000

    Message: Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.

  • Error number: MY-014068; Symbol: ER_IB_MSG_DDL_FAIL_NO_BUILDER; SQLSTATE: HY000

    Message: DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.

  • Error number: MY-014069; Symbol: ER_GRP_RPL_MEMBER_INFO_DOES_NOT_EXIST; SQLSTATE: HY000

    Message: Member identified %s: '%s' does not exist on Group Replication membership during %s.

  • Error number: MY-014070; Symbol: ER_USAGE_DEPRECATION_COUNTER; SQLSTATE: HY000

    Message: Deprecated '%s' used %s times, last time used '%s'.

  • Error number: MY-014071; Symbol: ER_WAITING_FOR_NO_CONNECTIONS; SQLSTATE: HY000

    Message: Waiting for %u connections to be closed.

  • Error number: MY-014072; Symbol: ER_WAITING_FOR_NO_THDS; SQLSTATE: HY000

    Message: Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.

  • Error number: MY-014073; Symbol: ER_IB_INDEX_PART_TOO_LONG; SQLSTATE: HY000

    Message: Index %s of %s.%s exceeds limit of %lu bytes per column.

  • Error number: MY-015000; Symbol: ER_LANGUAGE_COMPONENT_INFO; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015001; Symbol: ER_LANGUAGE_COMPONENT_WARNING; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015002; Symbol: ER_LANGUAGE_COMPONENT_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015003; Symbol: ER_IB_BULK_FLUSHER_PUNCH_HOLE; SQLSTATE: HY000

    Message: bulkflusher: Failed to punch hole: table=%s, index=%s, space_id=%zu, page_no=%zu, disk_page_size=%zu, hole_size=%zu, file=%s, err=%zu

  • Error number: MY-015004; Symbol: ER_GRP_RPL_CONN_KILLED; SQLSTATE: HY000

    Message: %s as the client session was killed.

  • Error number: MY-015005; Symbol: ER_WARN_CANT_OPEN_CERTIFICATE; SQLSTATE: HY000

    Message: Cannot open certificate %s. Please check the cerificate

  • Error number: MY-015006; Symbol: ER_FAILED_TO_VALIDATE_CERTIFICATES_SERVER_EXIT; SQLSTATE: HY000

    Message: Certificate validation has failed. Stopping the server as tls-certificates-enforced-validation is enabled

  • Error number: MY-015007; Symbol: ER_WARN_CA_CERT_VERIFY_FAILED; SQLSTATE: HY000

    Message: CA certificate/certficates is invalid. Please check logs for more details.

  • Error number: MY-015008; Symbol: ER_WARN_FAILED_TO_SETUP_TLS; SQLSTATE: HY000

    Message: Internal TLS error %s:%s:%d:%s

  • Error number: MY-015009; Symbol: ER_TLS_LIBRARY_ERROR_INTERNAL; SQLSTATE: HY000

    Message: Failed to set up TLS. Check logs for details

  • Error number: MY-015010; Symbol: ER_SERVER_CERT_VERIFY_FAILED; SQLSTATE: HY000

    Message: Server certificate %s verification has failed. Check logs for more details

  • Error number: MY-015011; Symbol: ER_WARN_CERTIFICATE_ERROR_STRING; SQLSTATE: HY000

    Message: Failed to validate certificate %s because %s

  • Error number: MY-015012; Symbol: ER_TELEMETRY_INFO; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015013; Symbol: ER_TELEMETRY_WARNING; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015014; Symbol: ER_TELEMETRY_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015015; Symbol: ER_SRV_START; SQLSTATE: HY000

    Message: MySQL Server - start.

  • Error number: MY-015016; Symbol: ER_SRV_END; SQLSTATE: HY000

    Message: MySQL Server - end.

  • Error number: MY-015017; Symbol: ER_SRV_INIT_START; SQLSTATE: HY000

    Message: MySQL Server Initialization - start.

  • Error number: MY-015018; Symbol: ER_SRV_INIT_END; SQLSTATE: HY000

    Message: MySQL Server Initialization - end.

  • Error number: MY-015019; Symbol: ER_PLUGINS_SHUTDOWN_START; SQLSTATE: HY000

    Message: MySQL Server: Plugins Shutdown - start.

  • Error number: MY-015020; Symbol: ER_PLUGINS_SHUTDOWN_END; SQLSTATE: HY000

    Message: MySQL Server: Plugins Shutdown - end.

  • Error number: MY-015021; Symbol: ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN_START; SQLSTATE: HY000

    Message: MySQL Server: Components Shutdown - start.

  • Error number: MY-015022; Symbol: ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN_END; SQLSTATE: HY000

    Message: MySQL Server: Components Shutdown - end (with return value = %d).

  • Error number: MY-015023; Symbol: ER_CONNECTIONS_SHUTDOWN_START; SQLSTATE: HY000

    Message: MySQL Server: Closing Connections - start.

  • Error number: MY-015024; Symbol: ER_CONNECTIONS_SHUTDOWN_END; SQLSTATE: HY000

    Message: MySQL Server: Closing Connections - end.

  • Error number: MY-015025; Symbol: ER_THREAD_STILL_ALIVE; SQLSTATE: HY000

    Message: Waiting for forceful disconnection of Thread (ID %ld) to end.

  • Error number: MY-015026; Symbol: ER_NUM_THREADS_STILL_ALIVE; SQLSTATE: HY000

    Message: Waiting for forceful disconnection of %ld thread(s) to end.

  • Error number: MY-015027; Symbol: ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_SERVER_ERROR_COMMAND_ERR; SQLSTATE: HY000

    Message: Failed to accept a MySQL connection for Group Replication. %s. Please retry.

  • Error number: MY-015028; Symbol: ER_COMPONENT_KEYRING_OCI_INVALID_CONFIG_VAR; SQLSTATE: HY000

    Message: Invalid value of argument %s (%s).

  • Error number: MY-015029; Symbol: ER_WARN_OPTION_RESET_AND_IGNORED_DURING_INITIALIZE; SQLSTATE: HY000

    Message: Ignoring a non-default value for %s during --initialize.

  • Error number: MY-015030; Symbol: ER_FIREWALL_SCHEDULER_REGISTER_FAILED; SQLSTATE: HY000

    Message: Automatic registration of the scheduler failed.

  • Error number: MY-015031; Symbol: ER_FIREWALL_INVALID_RELOAD_INTERVAL_VALUE; SQLSTATE: HY000

    Message: Invalid reload interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d.

  • Error number: MY-015032; Symbol: ER_WARN_DEPRECATED_DYNAMIC_PRIV_FOR_USER; SQLSTATE: HY000

    Message: '%s' (granted to '%s@%s') is deprecated and will be removed in a future release.

  • Error number: MY-015033; Symbol: ER_BULK_MULTI_READER_INFO; SQLSTATE: HY000

    Message: Bulk Multi Reader: %s

  • Error number: MY-015034; Symbol: ER_BULK_MERGE_LOADER_INFO; SQLSTATE: HY000

    Message: Bulk Merge Loader: %s

  • Error number: MY-015035; Symbol: ER_BULK_SORTING_LOADER_INFO; SQLSTATE: HY000

    Message: Bulk Sorting Loader: %s

  • Error number: MY-015036; Symbol: ER_BULK_WRITER_INFO; SQLSTATE: HY000

    Message: Bulk Writer: %s

  • Error number: MY-015037; Symbol: ER_BULK_WRITER_LIBCURL_INIT_FAILED_LOG; SQLSTATE: HY000

    Message: Bulk writer failed to initialize libcurl

  • Error number: MY-015038; Symbol: ER_BULK_WRITER_LIBCURL_ERROR_LOG; SQLSTATE: HY000

    Message: Bulk writer got libcurl error: %s

  • Error number: MY-015039; Symbol: ER_IB_WRONG_PAGE_ID; SQLSTATE: HY000

    Message: Detected wrong page_id: buf_block_t[space_id=%zu, page_no=%zu], buf_frame_t[space_id=%zu, page_no=%zu], file=%s

  • Error number: MY-015040; Symbol: ER_IB_FIXED_PAGE_ID; SQLSTATE: HY000

    Message: Fixed wrong page_id with sync read: buf_block_t[space_id=%zu, page_no=%zu], buf_frame_t[space_id=%zu, page_no=%zu], file=%s, retry=%zu

  • Error number: MY-015041; Symbol: ER_IB_WRONG_PAGEID_AFTER_SYNC_READ; SQLSTATE: HY000

    Message: Wrong page_id after sync read: buf_block_t[space_id=%zu, page_no=%zu], buf_frame_t[space_id=%zu, page_no=%zu], file=%s, retry=%zu

  • Error number: MY-015042; Symbol: ER_IB_SYNC_READ_FAILED; SQLSTATE: HY000

    Message: Sync read to fix wrong page_id failed: buf_block_t[space_id=%zu, page_no=%zu], file=%s, err=%zu, retry=%zu

  • Error number: MY-015043; Symbol: ER_START_REPLICA_CHANNEL_INVALID_CONFIGURATION_LOG; SQLSTATE: HY000

    Message: Cannot start replication channel '%s' because %s.

  • Error number: MY-015044; Symbol: ER_GROUP_REPLICATION_CERTIFIER_MESSAGE_LARGE; SQLSTATE: HY000

    Message: The certification information, part of the required information to the new member join the group, is too big and cannot be send. Please wait until the value of the column COUNT_TRANSACTIONS_ROWS_VALIDATING of the table performance_schema.replication_group_member_stats decreases and try to join the new member again.

  • Error number: MY-015045; Symbol: ER_GROUP_REPLICATION_METADATA_SENDER_IS_REMOTE; SQLSTATE: HY000

    Message: The member %s:%u will be the one sending the recovery metadata message.

  • Error number: MY-015046; Symbol: ER_GROUP_REPLICATION_METADATA_SENDER; SQLSTATE: HY000

    Message: This member %s:%u will be the one sending the recovery metadata message.

  • Error number: MY-015047; Symbol: ER_GROUP_REPLICATION_ERROR_COMPRESS_INITIALIZE; SQLSTATE: HY000

    Message: Error initializing the %s compression context. Data cannot be compressed.

  • Error number: MY-015048; Symbol: ER_GROUP_REPLICATION_COMPRESS_PROCESS; SQLSTATE: HY000

    Message: Error while compressing data using %s compression. Data cannot be decompressed.

  • Error number: MY-015049; Symbol: ER_GROUP_REPLICATION_UNKOWN_COMPRESSION_TYPE; SQLSTATE: HY000

    Message: Error unknown Compression Library requested.

  • Error number: MY-015050; Symbol: ER_GROUP_REPLICATION_COMPRESS_EXCEEDS_MAX_SIZE; SQLSTATE: HY000

    Message: Error while compressing data using %s compression. The operation could not be performed as buffer size exceeded configured maximum size. Please wait until the value of the column COUNT_TRANSACTIONS_ROWS_VALIDATING of the table performance_schema.replication_group_member_stats decreases and try to join the new member again.

  • Error number: MY-015051; Symbol: ER_GROUP_REPLICATION_COMPRESS_OUT_OF_MEMORY; SQLSTATE: HY000

    Message: Error while compressing data using %s compression. The operation could not be performed as memory allocation failed.

  • Error number: MY-015052; Symbol: ER_GROUP_REPLICATION_ERROR_DECOMPRESS_INITIALIZE; SQLSTATE: HY000

    Message: Error initializing the %s decompression context. Data cannot be decompressed.

  • Error number: MY-015053; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_EXCEEDS_MAX_SIZE; SQLSTATE: HY000

    Message: Error while decompressing data using %s compression. The operation could not be performed as buffer size exceeded configured maximum size. Please wait until the value of the column COUNT_TRANSACTIONS_ROWS_VALIDATING of the table performance_schema.replication_group_member_stats decreases and try to join the new member again.

  • Error number: MY-015054; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_OUT_OF_MEMORY; SQLSTATE: HY000

    Message: Error while decompressing data using %s compression. The operation could not be performed as memory allocation failed.

  • Error number: MY-015055; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_TRUNCATED; SQLSTATE: HY000

    Message: Error while decompressing data using %s compression. The operation could not be performed as all the input provided to decompress is consumed, but the decompressed output produced is less than required.

  • Error number: MY-015056; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_CORRUPTED; SQLSTATE: HY000

    Message: Error while decompressing data using %s compression. The operation could not be performed as the compression library reported an error.

  • Error number: MY-015057; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_END; SQLSTATE: HY000

    Message: Error while decompressing data using %s compression. The operation could not be performed as no more input bytes remaining to decompress. The decompressed output has not been changed.

  • Error number: MY-015058; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_PROCESS; SQLSTATE: HY000

    Message: Error while decompressing data using %s compression. Data cannot be decompressed.

  • Error number: MY-015059; Symbol: ER_GRP_RPL_VCLE_NOT_BEING_LOGGED; SQLSTATE: HY000

    Message: View_change_log_event will not be logged further on the binary log, as all members of the group are 8.3.0 or greater.

  • Error number: MY-015060; Symbol: ER_GROUP_REPLICATION_METADATA_PROTOBUF_PARSING; SQLSTATE: HY000

    Message: Error while parsing serialzed Certification_info from received Recovery Metadata to Protobuf format using Protobuf library.

  • Error number: MY-015061; Symbol: ER_GROUP_REPLICATION_PROTOBUF_SERIALIZING_ERROR; SQLSTATE: HY000

    Message: Error while serializing % data using Protobuf library.

  • Error number: MY-015062; Symbol: ER_GROUP_REPLICATION_ERROR_RECEIVED_WAITING_METADATA; SQLSTATE: HY000

    Message: Error received while the Recovery thread was waiting for the Recovery Metadata. The Recovery will be terminated.

  • Error number: MY-015063; Symbol: ER_GROUP_REPLICATION_TIMEOUT_ERROR_FETCHING_METADATA; SQLSTATE: HY000

    Message: Error fetching AFTER_GTIDS from Recovery Metadata by Recovery thread. The Recovery thread timeout after waiting for %d seconds. The Recovery will be terminated.

  • Error number: MY-015064; Symbol: ER_GROUP_REPLICATION_METADATA_PAYLOAD_EMPTY; SQLSTATE: HY000

    Message: Error while decoding the received Recovery Metadata Message. The received payload is empty which could be due to error in decoding of received Recovery Metadata Message. The joining member will leave the group.

  • Error number: MY-015065; Symbol: ER_GROUP_REPLICATION_METADATA_MESSAGE_PAYLOAD_EMPTY; SQLSTATE: HY000

    Message: The %s payload type of the received Recovery Metadata Message is empty.

  • Error number: MY-015066; Symbol: ER_GROUP_REPLICATION_METADATA_READ_GTID_EXECUTED; SQLSTATE: HY000

    Message: Error reading gtid_executed from the received Recovery Metadata Message.

  • Error number: MY-015067; Symbol: ER_GROUP_REPLICATION_METADATA_PAYLOAD_DECODING; SQLSTATE: HY000

    Message: Error while decoding the received Recovery Metadata Message.

  • Error number: MY-015068; Symbol: ER_GROUP_REPLICATION_METADATA_SEND_ERROR; SQLSTATE: HY000

    Message: The group was unable to send the Recovery Metadata to a joining member.

  • Error number: MY-015069; Symbol: ER_GROUP_REPLICATION_METADATA_SAVE_RECOVERY_COPY; SQLSTATE: HY000

    Message: Error while saving copy of Recovery Metadata Message.

  • Error number: MY-015070; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_ERROR_PROCESSING; SQLSTATE: HY000

    Message: Error while processing received Certification Information from the Recovery Metadata Message.

  • Error number: MY-015071; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_PACKET_EMPTY; SQLSTATE: HY000

    Message: Error Certification Information packet from the received Recovery Metadata Message is empty.

  • Error number: MY-015072; Symbol: ER_GROUP_REPLICATION_METADATA_ERROR_ON_SEND_ERROR_MESSAGE; SQLSTATE: HY000

    Message: Error while sending Recovery metadata error message. If this is a temporary failure of send message and member itself hasn't left the group, then joiner will timeout waiting for Recovery metadata message. If this is a permanent failure, the member will leave the group and another member will send the Recovery metadata message.

  • Error number: MY-015073; Symbol: ER_GROUP_REPLICATION_METADATA_SET_IN_RECOVERY_FAILED; SQLSTATE: HY000

    Message: Error when transferring Recovery Metadata Message to Recovery. The joining member will leave the group.

  • Error number: MY-015074; Symbol: ER_GROUP_REPLICATION_CERTIFICATION_MODULE_FAILURE; SQLSTATE: HY000

    Message: Error Certification module wasn't properly initialized.

  • Error number: MY-015075; Symbol: ER_GROUP_REPLICATION_METADATA_INITIALIZATION_FAILURE; SQLSTATE: HY000

    Message: Error Recovery Metadata Message module wasn't properly initialized.

  • Error number: MY-015076; Symbol: ER_GROUP_REPLICATION_METADATA_MEMORY_ALLOC; SQLSTATE: HY000

    Message: Error while %s. The operation could not be performed as memory allocation failed.

  • Error number: MY-015077; Symbol: ER_GROUP_REPLICATION_RECOVERY_SKIPPED_GTID_PRESENT; SQLSTATE: HY000

    Message: The group replication recovery is skipped as the joiner's gtid executed set %s already has all the transactions of the donor's gtid set %s.

  • Error number: MY-015078; Symbol: ER_GROUP_REPLICATION_RECOVERY_FETCHING_GTID_EXECUTED_SET; SQLSTATE: HY000

    Message: Error in Group Replication Recovery while getting member's global GTID executed set.

  • Error number: MY-015079; Symbol: ER_GROUP_REPLICATION_RECOVERY_ERROR_ADD_GTID_EXECUTED; SQLSTATE: HY000

    Message: Error in Group Replication Recovery while adding GTIDs in string format to Gtid_set.

  • Error number: MY-015080; Symbol: ER_GROUP_REPLICATION_RECOVERY_METADATA_SENDER_NOT_FOUND; SQLSTATE: HY000

    Message: Error computing the current Recovery metadata sender. Check if this MEMBER is not leaving the group and the joiner is able to successfully fetch the recovery metadata or not.

  • Error number: MY-015081; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_PACKET_COUNT_ERROR; SQLSTATE: HY000

    Message: Error in the received Recovery Metadata Message the number of compressed Certification Information packet count mismatch with the number of sent compressed Certification Information packets.

  • Error number: MY-015082; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_ENCODING_ERROR; SQLSTATE: HY000

    Message: Error while encoding Certification Information for the Recovery Metadata Message.

  • Error number: MY-015083; Symbol: ER_GROUP_REPLICATION_METADATA_NO_VALID_DONOR; SQLSTATE: HY000

    Message: There are no valid recovery metadata donors. The joining member will leave the group.

  • Error number: MY-015084; Symbol: ER_GROUP_REPLICATION_NO_CERTIFICATION_DONOR_AVAILABLE; SQLSTATE: HY000

    Message: No donor available to provide the certification information, part of the required information to the new member join the group. Please wait until there are ONLINE members on the group and try to join the new member again.

  • Error number: MY-015085; Symbol: ER_GROUP_REPLICATION_RECOVERY_STOPPED_GTID_PRESENT; SQLSTATE: HY000

    Message: The group replication recovery is complete, joiner gtid executed set has all the transactions of the donor's gtid set %s.

  • Error number: MY-015086; Symbol: ER_RPL_ASYNC_CHECK_CONNECTION_ERROR; SQLSTATE: HY000

    Message: The Monitor IO thread encountered an error while executing the query to check connection to the source server. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'.

  • Error number: MY-015087; Symbol: ER_RPL_ASYNC_MONITOR_IO_THD_FETCH_GROUP_MAJORITY_ERROR; SQLSTATE: HY000

    Message: The Monitor IO thread failed to detect if the source belongs to the group majority. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'.

  • Error number: MY-015088; Symbol: ER_RPL_ASYNC_REPLICA_IO_THD_FETCH_GROUP_MAJORITY_ERROR; SQLSTATE: HY000

    Message: The replica IO thread failed to detect if the source belongs to the group majority. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'.

  • Error number: MY-015089; Symbol: ER_RPL_ASYNC_GET_GROUP_MEMBERSHIP_DETAILS_ERROR; SQLSTATE: HY000

    Message: The Monitor IO thread failed to get group membership details. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'.

  • Error number: MY-015090; Symbol: ER_IB_ERR_CORRUPT_TABLESPACE_UNRECOVERABLE; SQLSTATE: HY000

    Message: Tablespace '%u' mentioned in the redo log is corrupted in a way it is unrecoverable by double-write buffer, so further redo log recovery is not possible!

  • Error number: MY-015091; Symbol: ER_IB_BULK_LOAD_STATS_WARN; SQLSTATE: HY000

    Message: %s: Failed to save statistics for table=%s err=%zu trx_err=%zu

  • Error number: MY-015092; Symbol: ER_COMPONENT_MASKING_INVALID_FLUSH_INTERVAL_VALUE; SQLSTATE: HY000

    Message: Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d.

  • Error number: MY-015093; Symbol: ER_COMPONENT_MASKING_VAR_REGISTRATION_FAILURE; SQLSTATE: HY000

    Message: Cannot register variable '%s'.'%s'.

  • Error number: MY-015094; Symbol: ER_COMPONENT_MASKING_NOTIFICATION_REGISTRATION_FAILURE; SQLSTATE: HY000

    Message: Masking component failed to register notification service. Periodical masking dictionaries flush will not work.

  • Error number: MY-015095; Symbol: ER_GRP_RPL_MSG_DECODING_FAILED; SQLSTATE: HY000

    Message: Failed to decode Group Replication message: %s. Reason : %s

  • Error number: MY-015096; Symbol: ER_GRP_RPL_APPLIER_ERROR_PACKET_RECEIVED; SQLSTATE: HY000

    Message: The Applier process of Group Replication found an error and was requested to stop: %s

  • Error number: MY-015097; Symbol: ER_LANGUAGE_COMPONENT_INSTALL_ERROR; SQLSTATE: HY000

    Message: Cannot install the component.

  • Error number: MY-015098; Symbol: ER_WARN_LANGUAGE_COMPONENT_CANNOT_UNINSTALL; SQLSTATE: HY000

    Message: Cannot uninstall the language component: %s.

  • Error number: MY-015099; Symbol: ER_LANGUAGE_COMPONENT_SERVER_ERROR; SQLSTATE: HY000

    Message: Calling component service: %s.

  • Error number: MY-015100; Symbol: ER_LANGUAGE_COMPONENT_INTERNAL_ERROR; SQLSTATE: HY000

    Message: Internal error while %s.

  • Error number: MY-015101; Symbol: ER_LANGUAGE_COMPONENT_VM_API_FUNCTION_ERROR; SQLSTATE: HY000

    Message: Internal VM API function failed: %s.

  • Error number: MY-015102; Symbol: ER_LANGUAGE_COMPONENT_VM_INTERNAL_ERROR; SQLSTATE: HY000

    Message: Internal VM error while %s.

  • Error number: MY-015103; Symbol: ER_WARN_LANGUAGE_COMPONENT_RESOURCE_LIMIT; SQLSTATE: HY000

    Message: The resource limit has been exceeded. Details: %s.

  • Error number: MY-015104; Symbol: ER_BLOCKED_CIPHER; SQLSTATE: HY000

    Message: Value for option '%s' contains cipher '%s' that is blocked. Please refer to the documentation for allowed ciphers.

  • Error number: MY-015105; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_NAME_EMPTY; SQLSTATE: HY000

    Message: Keyring file path is empty in configuration file.

  • Error number: MY-015106; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_READ_FAILED; SQLSTATE: HY000

    Message: Failed to read keyring file: %s.

  • Error number: MY-015107; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_DECRYPT_FAILED; SQLSTATE: HY000

    Message: Failed to decrypt keyring file: %s.

  • Error number: MY-015108; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_INVALID_FORMAT; SQLSTATE: HY000

    Message: The keyring file content is not in a valid JSON format.

  • Error number: MY-015109; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_JSON_EXTRACT_FAILED; SQLSTATE: HY000

    Message: Failed to extract a valid JSON data from keyring file.

  • Error number: MY-015110; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_KEY_EXTRACT_FAILED; SQLSTATE: HY000

    Message: Failed to extract key from keyring file JSON data.

  • Error number: MY-015111; Symbol: ER_NOTE_KEYRING_COMPONENT_NOT_INITIALIZED; SQLSTATE: HY000

    Message: Keyring component is not initialized.

  • Error number: MY-015112; Symbol: ER_NOTE_KEYRING_COMPONENT_EMPTY_DATA_ID; SQLSTATE: HY000

    Message: Provided Data ID is empty.

  • Error number: MY-015113; Symbol: ER_NOTE_KEYRING_COMPONENT_KEYS_METADATA_ITERATOR_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to initialize metadata iterator.

  • Error number: MY-015114; Symbol: ER_NOTE_KEYRING_COMPONENT_KEY_READ_ITERATOR_INIT_FAILED; SQLSTATE: HY000

    Message: Failed to initialize key reader iterator.

  • Error number: MY-015115; Symbol: ER_NOTE_KEYRING_COMPONENT_KEY_READ_ITERATOR_FETCH_FAILED; SQLSTATE: HY000

    Message: Failed to read key from key reader iterator.

  • Error number: MY-015116; Symbol: ER_BACKGROUND_HISTOGRAM_UPDATE; SQLSTATE: HY000

    Message: %*s

  • Error number: MY-015117; Symbol: ER_IB_MSG_SUBMIT_DETAILED_BUG_REPORT; SQLSTATE: HY000

    Message: Submit a detailed bug report to http://bugs.mysql.com

  • Error number: MY-015118; Symbol: ER_AUTO_INCREMENT_NOT_SUPPORTED_FOR_FLOAT_DOUBLE; SQLSTATE: HY000

    Message: AUTO_INCREMENT is not supported with DOUBLE/FLOAT field. Please consider fixing (Schema:%s, Table:%s, Column:%s).

  • Error number: MY-015119; Symbol: ER_SERVER_DOWNGRADE_SYS_SCHEMA; SQLSTATE: HY000

    Message: Downgrading the sys schema.

  • Error number: MY-015120; Symbol: ER_SERVER_DOWNGRADE_HELP_TABLE_STATUS; SQLSTATE: HY000

    Message: Downgrade of help tables %s.

  • Error number: MY-015121; Symbol: ER_KEYRING_MIGRATE_SKIPPED_KEY; SQLSTATE: HY000

    Message: Could not find data pointed by data_id: %s, auth_id: %s. Skipping.

  • Error number: MY-015122; Symbol: ER_KEYRING_MIGRATE_MEMORY_DEALLOCATION_FAILED; SQLSTATE: HY000

    Message: Failed to deallocate reader_object.

  • Error number: MY-015123; Symbol: ER_LOG_CLIENT_INTERACTION_TIMEOUT; SQLSTATE: HY000

    Message: A connection from %s was closed by the server due to a timeout in the communication layer (vio:%d, packet:%d) %ld seconds after the last command started. Currently configured wait_timeout is %ld seconds.

  • Error number: MY-015124; Symbol: ER_GRP_RPL_PREEMPTIVE_GARBAGE_COLLECTION_DIFF_FROM_GRP; SQLSTATE: HY000

    Message: The member is configured with a group_replication_preemptive_garbage_collection option value '%d' different from the group '%d'. The member will now exit the group.

  • Error number: MY-015125; Symbol: ER_IB_LONG_ROLLBACK_FULL; SQLSTATE: HY000

    Message: Still rolling back transaction %llu; %llu undo records rolled back out of %llu total (%lu%% complete). Transaction info: last state: %s

  • Error number: MY-015126; Symbol: ER_IB_LONG_ROLLBACK; SQLSTATE: HY000

    Message: Still rolling back transaction %llu; %llu undo records rolled back out of %llu total (%lu%% complete).

  • Error number: MY-015127; Symbol: ER_INVALID_FILE_FORMAT; SQLSTATE: HY000

    Message: Invalid format of file '%s'.

  • Error number: MY-015128; Symbol: ER_LOG_SANITIZATION; SQLSTATE: HY000

    Message: Relay log sanitization: %s

  • Error number: MY-015129; Symbol: ER_WARN_LOG_DEPRECATED_NON_STANDARD_KEY; SQLSTATE: HY000

    Message: Foreign key '%s' on table '%s'.'%s' refers to non-unique key or partial key. This is deprecated and will be removed in a future release.

  • Error number: MY-015130; Symbol: ER_THREAD_POOL_MTL_DISABLE; SQLSTATE: HY000

    Message: Disabling MTL in thread group %u since it has %u (=MTL per group) long running transactions.

  • Error number: MY-015131; Symbol: ER_THREAD_POOL_MTL_REENABLE; SQLSTATE: HY000

    Message: Re-enabling MTL in thread group %u since it is down to %u long running transactions.

  • Error number: MY-015132; Symbol: ER_LOG_PARTITION_PREFIX_KEY_NOT_SUPPORTED; SQLSTATE: HY000

    Message: Column '%s.%s.%s' having prefix key part '%s(%u)' in the PARTITION BY KEY() clause is not supported.

  • Error number: MY-015133; Symbol: ER_LDAP_AUTH_INFO_USER_MAP; SQLSTATE: HY000

    Message: Login user: %s@%s (external: %s) authenticated as: %s

  • Error number: MY-015134; Symbol: ER_ACCESS_DENIED_NO_PROXY_GRANT_WITH_NAME; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s', missing proxy privilege to '%s'.

  • Error number: MY-015135; Symbol: ER_ACCESS_DENIED_NO_PROXY_WITH_NAME; SQLSTATE: HY000

    Message: Access denied for user '%s'@'%s', proxied user '%s' doesn't exist.

  • Error number: MY-015136; Symbol: ER_GRP_RPL_RECOVERY_WAIT_APPLIER_BACKLOG_START; SQLSTATE: HY000

    Message: Distributed recovery will wait until the transactions '%s' contained on the 'group_replication_applier' channel are applied.

  • Error number: MY-015137; Symbol: ER_GRP_RPL_RECOVERY_WAIT_APPLIER_BACKLOG_FINISH; SQLSTATE: HY000

    Message: Distributed recovery finished applying the transactions '%s' contained on the 'group_replication_applier' channel.

  • Error number: MY-015138; Symbol: ER_BULK_READER_ZSTD_ERROR_LOG; SQLSTATE: HY000

    Message: ZSTD decompression failed: %s

  • Error number: MY-015139; Symbol: ER_SECONDARY_ENGINE_DDL_TRACK_PROGRESS; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015140; Symbol: ER_IB_MSG_INNODB_FLUSH_METHOD; SQLSTATE: HY000

    Message: Using innodb_flush_method=%s

  • Error number: MY-015141; Symbol: ER_BULK_SCANNER_INFO; SQLSTATE: HY000

    Message: Bulk Scanner: %s

  • Error number: MY-015142; Symbol: ER_LOG_DEPRECATE_NON_COMPOSABLE_MULTIPLE_ENGINE; SQLSTATE: HY000

    Message: Combining the storage engines %s and %s is deprecated, but the statement or transaction updates both the %s table %s.%s and the %s table %s.%s.

  • Error number: MY-015143; Symbol: ER_DD_UPDATE_DATADIR_FLAG_FAIL; SQLSTATE: HY000

    Message: Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown

  • Error number: MY-015144; Symbol: ER_IB_MSG_FIL_STATE_MOVED_PREV_OR_HAS_DATADIR; SQLSTATE: HY000

    Message: %s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory. It is either moved or is created with 'DATA DIRECTORY'

  • Error number: MY-015145; Symbol: ER_LOAD_BULK_JSON_ERROR; SQLSTATE: HY000

    Message: Bulk CSV parser reports JSON error: %s at %zu

  • Error number: MY-015146; Symbol: ER_IB_BULK_LOAD_STATS_INFO; SQLSTATE: HY000

    Message: %s: %s: Saving statistics for table=%s err=%zu trx_err=%zu

  • Error number: MY-015147; Symbol: ER_AUTHENTICATION_OPENID_INVALID_TOKEN; SQLSTATE: HY000

    Message: Invalid identity token provided by '%s' for '%s'@'%s': %s.

  • Error number: MY-015148; Symbol: ER_AUTHENTICATION_OPENID_ISSUER_MISMATCH; SQLSTATE: HY000

    Message: Issuer (%s) found in identity token provided by '%s' for '%s'@'%s' does not match the issuer in the configuration.

  • Error number: MY-015149; Symbol: ER_AUTHENTICATION_OPENID_USER_MISMATCH; SQLSTATE: HY000

    Message: Unknown subject (%s) found in identity token provided by '%s' for '%s'@'%s'.

  • Error number: MY-015150; Symbol: ER_AUTHENTICATION_OPENID_INVALID_CONFIGURATION; SQLSTATE: HY000

    Message: The configuration for authentication_openid_connect is invalid. %s.

  • Error number: MY-015151; Symbol: ER_AUTHENTICATION_OPENID_TOKEN_NOT_VERIFIED; SQLSTATE: HY000

    Message: Verification failed for identity token provided by '%s' for '%s'@'%s' : %s.

  • Error number: MY-015152; Symbol: ER_AUTHENTICATION_OPENID_INSECURE_CONNECTION; SQLSTATE: HY000

    Message: The Client-Server connection is not secure. Please make sure either a TLS, socket or shared memory connection is established between the client and the server.

  • Error number: MY-015153; Symbol: ER_AUTHENTICATION_OPENID_READ_PACKET; SQLSTATE: HY000

    Message: An error occurred during the client server handshake.

  • Error number: MY-015154; Symbol: ER_AUTHENTICATION_OPENID_INVALID_TOKEN_SIZE; SQLSTATE: HY000

    Message: The ID token is not acceptable. Token size should be less than 10k.

  • Error number: MY-015155; Symbol: ER_AUTHENTICATION_OPENID_INVALID_IDENTITY_PROVIDER; SQLSTATE: HY000

    Message: The provided identity provider in the auth string is not supported.

  • Error number: MY-015156; Symbol: ER_AUTHENTICATION_OPENID_CONFIGURATION_NOT_SET; SQLSTATE: HY000

    Message: The configuration for the plugin is not set. Please set authentication_openid_connect_configuration before a login attempt or user creation.

  • Error number: MY-015157; Symbol: ER_AUTHENTICATION_OPENID_FAILED_TO_UPDATE_CONFIGURATION; SQLSTATE: HY000

    Message: Failed to update authentication_openid_connect_configuration to a new value and the old value is lost too. Please set it to avoid unexpected results.

  • Error number: MY-015158; Symbol: ER_SIMPLE_ERROR_LOG_COMPONENT_STATUS; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015500; Symbol: ER_INVALID_METER; SQLSTATE: HY000

    Message: Invalid meter name or value for performance_schema_meter '%s'.

  • Error number: MY-015501; Symbol: ER_INVALID_LOGGER; SQLSTATE: HY000

    Message: Invalid logger name or value for performance_schema_logger '%s'.

  • Error number: MY-015502; Symbol: ER_IB_DELETE_SCHEMA_DIR; SQLSTATE: HY000

    Message: deleted the schema directory: %s

  • Error number: MY-015503; Symbol: ER_IB_INSERT_DELETE_SCHEMA_DIRECTORY_DDL_LOG; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015504; Symbol: ER_IMDS_OCI_INFO; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015505; Symbol: ER_IMDS_OCI_WARNING; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015506; Symbol: ER_IMDS_OCI_ERROR; SQLSTATE: HY000

    Message: %s

  • Error number: MY-015507; Symbol: ER_THREAD_POOL_CONNECTION_INIT_REPORT; SQLSTATE: HY000

    Message: TP conn (init: in, queue, auth, err, ok. port: managed(delta), active, opened, closed, added, dropped): %s

  • Error number: MY-015508; Symbol: ER_THREAD_POOL_ALLOC_FAILED; SQLSTATE: HY000

    Message: Thread pool failed to allocate %s.

  • Error number: MY-015509; Symbol: ER_THREAD_POOL_SOCKETPAIR_FAILED; SQLSTATE: HY000

    Message: socketpair() failed with errno: %d

  • Error number: MY-015510; Symbol: ER_THREAD_POOL_LOW_LEVEL_INIT_FAILED; SQLSTATE: HY000

    Message: tp_client_low_level_init() failed

  • Error number: MY-015511; Symbol: ER_THREAD_POOL_LOW_LEVEL_ARM_FAILED; SQLSTATE: HY000

    Message: tp_client_low_level_arm() failed

  • Error number: MY-015512; Symbol: ER_THREAD_POOL_LOW_LEVEL_ARM_FAILED_WITH_ERRNO; SQLSTATE: HY000

    Message: tp_client_low_level_arm() failed with %d

  • Error number: MY-015513; Symbol: ER_THREAD_POOL_CREATE_THREAD_FAILED; SQLSTATE: HY000

    Message: Can't create pool thread (error %d, errno: %d)

  • Error number: MY-015514; Symbol: ER_THREAD_POOL_LOW_LEVEL_INIT_ALLOC_FAILED; SQLSTATE: HY000

    Message: tp_client_low_level_init() for wait context failed to allocate memory

  • Error number: MY-015515; Symbol: ER_THREAD_POOL_CREATE_EPOLL_FAILED; SQLSTATE: HY000

    Message: epoll_create() failed with %d

  • Error number: MY-015516; Symbol: ER_THREAD_POOL_EPOLL_WAIT_ERROR; SQLSTATE: HY000

    Message: Thread pool epoll_wait() error: errno=%d.

  • Error number: MY-015517; Symbol: ER_THREAD_POOL_POLL_WAIT_ERROR; SQLSTATE: HY000

    Message: Thread pool poll_wait() error: errno=%d.

  • Error number: MY-015518; Symbol: ER_KEYRING_COMPONENT_AWS_FILE_PATH_EMPTY; SQLSTATE: HY000

    Message: Keyring data file path is empty in configuration file.

  • Error number: MY-015519; Symbol: ER_KEYRING_COMPONENT_AWS_FILE_OPEN_FAILED; SQLSTATE: HY000

    Message: Failed to open keyring data file: %s.

  • Error number: MY-015520; Symbol: ER_KEYRING_COMPONENT_AWS_FILE_READ_FAILED; SQLSTATE: HY000

    Message: Failed to read data from keyring data file: %s.

  • Error number: MY-015521; Symbol: ER_KEYRING_COMPONENT_AWS_FILE_WRITE_FAILED; SQLSTATE: HY000

    Message: Failed to write data to keyring data file: %s.

  • Error number: MY-015522; Symbol: ER_KEYRING_COMPONENT_AWS_FILE_PARSE_FAILED; SQLSTATE: HY000

    Message: The keyring file content is not in a valid JSON format.

  • Error number: MY-015523; Symbol: ER_KEYRING_COMPONENT_AWS_KEY_EXTRACT_FAILED; SQLSTATE: HY000

    Message: Failed to extract %d. element from keyring file content.

  • Error number: MY-015524; Symbol: ER_KEYRING_COMPONENT_AWS_CLIENT_CREATE_FAILED; SQLSTATE: HY000

    Message: Failed to create AWS KMS client.

  • Error number: MY-015525; Symbol: ER_KEYRING_COMPONENT_AWS_CLIENT_OPERATION_FAILED; SQLSTATE: HY000

    Message: Failed AWS KMS operation %s: %s.

  • Error number: MY-015526; Symbol: ER_KEYRING_COMPONENT_AWS_GENERATE_KEY_INVALID_PARAMETER; SQLSTATE: HY000

    Message: Invalid key generate parameter: %s = %s, must be %s.

  • Error number: MY-015527; Symbol: ER_KEYRING_COMPONENT_AWS_BACKEND_OPERATION_FAILED; SQLSTATE: HY000

    Message: Failed operation %s on key %s owned by %s.

  • Error number: MY-015528; Symbol: ER_KEYRING_COMPONENT_AWS_CACHE_OPERATION_FAILED; SQLSTATE: HY000

    Message: Failed keyring cache operation %s.

  • Error number: MY-015529; Symbol: ER_KEYRING_COMPONENT_AWS_ADD_TO_DOC_FAILED; SQLSTATE: HY000

    Message: Failed to add key %s for %s to JSON document.

  • Error number: MY-015530; Symbol: ER_KEYRING_COMPONENT_AWS_WRITE_AFTER_REENCRYPTION_FAILED; SQLSTATE: HY000

    Message: Failed to write the data after reencryption.

  • Error number: MY-015531; Symbol: ER_KEYRING_COMPONENT_AWS_READ_ONLY_LIMIT; SQLSTATE: HY000

    Message: Cannot %s, the keyring is read only.

  • Error number: MY-015532; Symbol: ER_KEYRING_COMPONENT_AWS_CANNOT_ENCRYPT_READ_ONLY; SQLSTATE: HY000

    Message: CMK was changed and the keyring must be re-encrypted, but the keyring is read only. Set the read_only config parameter to false for re-encryption and reload the component.

  • Error number: MY-015533; Symbol: ER_AUTHENTICATION_OPENID_OPTION_REGISTER; SQLSTATE: HY000

    Message: Option registration failed.

  • Error number: MY-015534; Symbol: ER_AUTHENTICATION_OPENID_OPTION_DEREGISTER; SQLSTATE: HY000

    Message: Option deregistration failed.


PREV   HOME   UP   NEXT
Download this Manual
PDF (US Ltr) - 6.4Mb
PDF (A4) - 6.4Mb