mysql-5.7 Server Error Codes and Messages

Message: hashchk

Unused.

Message: isamchk

Unused.

Message: NO

Used in the construction of other messages.

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.

Message: Can’t create file ’%s’ (errno: %d – %s)

Occurs for failure to copy an .frm file to a new location, during execution of a CREATE TABLE dst LIKE src statement when the server tries to copy the source table.frm file to the destination table .frm file.

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

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

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.

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

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.

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

Message: Error dropping database (can’t delete ’%s’, errno: %d)

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

Message: Error on delete of ’%s’ (errno: %d – %s)

Message: Can’t read record in system table

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

Message: Can’t get status of ’%s’ (errno: %d – %s)

Message: Can’t get working directory (errno: %d – %s)

Message: Can’t lock file (errno: %d – %s)

Message: Can’t open file: ’%s’ (errno: %d – %s)

InnoDB reports this error when the table from the InnoDB data files cannot be found, even though the .frm file for the table exists. See Section 14.19.3, “Troubleshooting InnoDB Data Dictionary Operations”.

Message: Can’t find file: ’%s’ (errno: %d – %s)

Message: Can’t read dir of ’%s’ (errno: %d – %s)

Message: Can’t change dir to ’%s’ (errno: %d – %s)

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

Message: Disk full (%s); waiting for someone to free some space… (errno: %d – %s)

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

Message: Error on close of ’%s’ (errno: %d – %s)

Message: Error reading file ’%s’ (errno: %d – %s)

Message: Error on rename of ’%s’ to ’%s’ (errno: %d – %s)

Message: Error writing file ’%s’ (errno: %d – %s)

Message: ’%s’ is locked against change

Message: Sort aborted

Message: View ’%s’ doesn’t exist for ’%s’

Message: Got error %d 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.

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

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

Message: Incorrect information in file: ’%s’

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

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

Message: Table ’%s’ is read only

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

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

Message: Unexpected EOF found when reading file ’%s’ (errno: %d – %s)

Message: Too many connections

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

Message: Can’t get hostname for your address

Message: Bad handshake

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

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

Message: No database selected

Message: Unknown command

Message: Column ’%s’ cannot be null

Message: Unknown database ’%s’

Message: Table ’%s’ already exists

Message: Unknown table ’%s’

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:

Message: Server shutdown in progress

Message: Unknown column ’%s’ in ’%s’

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

Message: Can’t group on ’%s’

Message: Statement has sum functions and columns in same statement

Message: Column count doesn’t match value count

Message: Identifier name ’%s’ is too long

Message: Duplicate column name ’%s’

Message: Duplicate key name ’%s’

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

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

Message: Incorrect column specifier for column ’%s’

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

Message: Query was empty

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

Message: Invalid default value for ’%s’

Message: Multiple primary key defined

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

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

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

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

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

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

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

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

Message: %s: Normal shutdown

Message: %s: Got signal %d. Aborting!

Message: %s: Shutdown complete

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

Message: Can’t create IP socket

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

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

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

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

Message: File ’%s’ already exists

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

Message: Records: %ld Duplicates: %ld

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

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

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

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

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

Message: Unknown thread id: %lu

Message: You are not owner of thread %lu

Message: No tables used

Message: Too many strings for column %s and SET

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

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

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

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

Message: Incorrect database name ’%s’

Message: Incorrect table name ’%s’

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

Message: Unknown error

Message: Unknown procedure ’%s’

Message: Incorrect parameter count to procedure ’%s’

Message: Incorrect parameters to procedure ’%s’

Message: Unknown table ’%s’ in %s

Message: Column ’%s’ specified twice

Message: Invalid use of group function

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

Message: A table must have at least 1 column

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.

Message: Unknown character set: ’%s’

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

Message: Too many columns

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

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

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

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

Message: Can’t load function ’%s’

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

Message: No paths allowed for shared library

Message: Function ’%s’ already exists

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

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

Message: Function ’%s’ is not defined

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

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

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

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

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

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

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

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

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

Message: Invalid use of NULL value

Message: Got error ’%s’ from regexp

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

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

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

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

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

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

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

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

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

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

Message: Delayed insert thread couldn’t get requested lock for table %s

Message: Too many delayed threads in use

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

Message: Got a packet bigger than ’max_allowed_packet’ bytes

Message: Got a read error from the connection pipe

Message: Got an error from fcntl()

Message: Got packets out of order

Message: Couldn’t uncompress communication packet

Message: Got an error reading communication packets

Message: Got timeout reading communication packets

Message: Got an error writing communication packets

Message: Got timeout writing communication packets

Message: Result string is longer than ’max_allowed_packet’ bytes

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

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

Message: INSERT DELAYED can’t be used with table ’%s’ because it is locked with LOCK TABLES

Message: Incorrect column name ’%s’

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

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

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

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

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

Message: Result consisted of more than one row

Message: This table type requires a primary key

Message: This version of MySQL is not compiled with RAID support

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

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

Message: Can’t open table

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

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

Message: Got error %d during COMMIT

Message: Got error %d during ROLLBACK

Message: Got error %d during FLUSH_LOGS

Message: Got error %d during CHECKPOINT

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

Message: The storage engine for the table does not support binary table dump

Message: Binlog closed, cannot RESET MASTER

Message: Failed rebuilding the index of dumped table ’%s’

Message: Error from master: ’%s’

Message: Net error reading from master

Message: Net error writing to master

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

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

Message: Unknown system variable ’%s’

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

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

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

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

Message: This operation cannot be performed with a running slave; run STOP SLAVE first

Message: This operation requires a running slave; configure slave and do START SLAVE

Message: The server is not configured as slave; fix in config file or with CHANGE MASTER TO

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

Message: Could not create slave thread; check system resources

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

Message: You may only use constant expressions with SET

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 theinnodb_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.

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 ofinnodb_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.

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

Message: DROP DATABASE not allowed while thread is holding global read lock

Message: CREATE DATABASE not allowed while thread is holding global read lock

Message: Incorrect arguments to %s

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

Message: Incorrect table definition; all MERGE tables must be in the same database

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 Section 14.3.10, “How to Cope with Deadlocks” for details.

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

Message: Cannot add foreign key constraint

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.

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.

Message: Error connecting to master: %s

Message: Error running query on master: %s

Message: Error when executing command %s: %s

Message: Incorrect usage of %s and %s

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

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

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

Message: Option ’%s’ used twice in statement

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

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

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

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

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

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

Message: Incorrect argument type to variable ’%s’

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

Message: Incorrect usage/placement of ’%s’

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

Message: Got fatal error %d from master when reading data from binary log: ’%s’

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

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

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

Message: Key reference and table reference don’t match

Message: Operand should contain %d column(s)

Message: Subquery returns more than 1 row

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

Message: Help database is corrupt or does not exist

Message: Cyclic reference on subqueries

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

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

Message: Every derived table must have its own alias

Message: Select %u was reduced during optimization

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

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

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

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

Message: Slave is already running

Message: Slave already has been stopped

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

Message: ZLIB: Not enough memory

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

Message: ZLIB: Input data corrupted

Message: Row %u was cut by GROUP_CONCAT()

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

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

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

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

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

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

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

Message: Cannot drop one or more of the requested users

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

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

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

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

Message: Unknown collation: ’%s’

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

Message: Server is running in –secure-auth mode, but ’%s’@’%s’ has a password in the old format; please change the password to the new format

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

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

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

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

Message: Incorrect index name ’%s’

Message: Incorrect catalog name ’%s’

Message: Query cache failed to set size %lu; new query cache size is %lu

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

Message: Unknown key cache ’%s’

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

Message: Unknown storage engine ’%s’

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

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

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

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

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

Message: Truncated incorrect %s value: ’%s’

Message: Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause

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

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

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

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

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

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

Message: Invalid %s character string: ’%s’

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

Message: Conflicting declarations: ’%s%s’ and ’%s%s’

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

Message: %s %s already exists

Message: %s %s does not exist

Message: Failed to DROP %s %s

Message: Failed to CREATE %s %s

Message: %s with no matching label: %s

Message: Redefining label %s

Message: End-label %s without match

Message: Referring to uninitialized variable %s

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

Message: RETURN is only allowed in a FUNCTION

Message: %s is not allowed in stored procedures

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

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

Message: Query execution was interrupted

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

Message: Undefined CONDITION: %s

Message: No RETURN found in FUNCTION %s

Message: FUNCTION %s ended without RETURN

Message: Cursor statement must be a SELECT

Message: Cursor SELECT must not have INTO

Message: Undefined CURSOR: %s

Message: Cursor is already open

Message: Cursor is not open

Message: Undeclared variable: %s

Message: Incorrect number of FETCH variables

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

Message: Duplicate parameter: %s

Message: Duplicate variable: %s

Message: Duplicate condition: %s

Message: Duplicate cursor: %s

Message: Failed to ALTER %s %s

Message: Subquery value not supported

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

Message: Variable or condition declaration after cursor or handler declaration

Message: Cursor declaration after handler declaration

Message: Case not found for CASE statement

Message: Configuration file ’%s’ is too big

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

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

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

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

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

Message: File ’%s’ has unknown type ’%s’ in its header

Message: ’%s.%s’ is not %s

Message: Column ’%s’ is not updatable

Message: View’s SELECT contains a subquery in the FROM clause

ER_VIEW_SELECT_DERIVED was removed after 5.7.6.

Message: View’s SELECT contains a subquery in the FROM clause

ER_VIEW_SELECT_DERIVED_UNUSED was added in 5.7.7.

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

Message: View’s SELECT contains a variable or parameter

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

Message: View’s SELECT and view’s field list have different column counts

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

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

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

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

Message: GOTO is not allowed in a stored procedure handler

Message: Trigger already exists

Message: Trigger does not exist

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

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

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

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

Message: Division by 0

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

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

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

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

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

Message: Failed purging old relay logs: %s

Message: Password hash should be a %d-digit hexadecimal number

Message: Target log not found in binlog index

Message: I/O error reading log index file

Message: Server configuration does not permit binlog purge

Message: Failed on fseek()

Message: Fatal error during log purge

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

Message: Unknown error during log purge

Message: Failed initializing relay log position: %s

Message: You are not using binary logging

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

Message: WSAStartup Failed

Message: Can’t handle procedures with different groups yet

Message: Select must have a group with this procedure

Message: Can’t use ORDER clause with this procedure

Message: Binary logging and replication forbid changing the global server %s

Message: Can’t map file: %s, errno: %d

Message: Wrong magic in %s

Message: Prepared statement contains too many placeholders

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

Message: View text checksum failed

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

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

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

Message: Operation %s failed for %s

Message: XAER_NOTA: Unknown XID

Message: XAER_INVAL: Invalid arguments (or unsupported command)

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

Message: XAER_OUTSIDE: Some work is done outside global transaction

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

Message: XA_RBROLLBACK: Transaction branch was rolled back

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

Message: Failed to grant EXECUTE and ALTER ROUTINE privileges

Message: Failed to revoke all privileges to dropped routine

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

Message: Bad SQLSTATE: ’%s’

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

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

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

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

Message: Table definition has changed, please retry transaction

Message: Duplicate handler declared in the same block

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

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

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

Message: A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes

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)

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)

Message: You can’t execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.

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

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

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

Message: Recursive stored functions and triggers are not allowed.

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

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

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

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

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

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

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

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

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

Message: Can’t create federated table. Foreign data src error: %s

Message: Trigger in wrong schema

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.

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

Message: Cannot drop default keycache

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

Message: XAER_DUPID: The XID already exists

Message: Datetime function: %s field overflow

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

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

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

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

Message: Definer is not fully qualified

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

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

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

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

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

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

Message: Variable ’%s’ must be quoted with `…`, or renamed

Message: No definer attribute for trigger ’%s’.’%s’. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.

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

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

Message: Failed to load routine %s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)

Message: Incorrect routine name ’%s’

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

Message: AGGREGATE is not supported for stored functions

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

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

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

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

Message: Triggers can not be created on system tables

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

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

Message: user name

Message: host name

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

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

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

Message: Too high level of nesting for select

Message: Name ’%s’ has become ’’

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

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

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

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

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

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

Message: MAXVALUE can only be used in last partition definition

Message: Subpartitions can only be hash partitions and by key

Message: Must define subpartitions on all partitions if on one partition

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

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

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

Message: Expression in RANGE/LIST VALUES must be constant

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

Message: List of fields is only allowed in KEY partitions

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

Message: The %s function returns the wrong type

Message: For %s partitions each partition must be defined

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

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

Message: Multiple definition of same constant in list partitioning

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

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

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

Message: Too many partitions (including subpartitions) were defined

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

Message: Failed to create specific handler file

Message: A BLOB field is not allowed in partition function

Message: A %s must include all columns in the table’s partitioning function

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

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

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

Message: Error in list of partitions to %s

Message: Cannot remove all partitions, use DROP TABLE instead

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

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

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

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

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

Message: At least one partition must be added

Message: At least one partition must be coalesced

Message: More partitions to reorganize than there are partitions

Message: Duplicate partition name %s

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

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

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

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

Message: Partition state cannot be defined from CREATE/ALTER TABLE

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

Message: Plugin ’%s’ is not loaded

Message: Incorrect %s value: ’%s’

Message: Table has no partition for value %s

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

Message: Failed to create %s

Message: Failed to drop %s

Message: The handler doesn’t support autoextend of tablespaces

Message: A size parameter was incorrectly specified, either number or on the form 10M

Message: The size number was correct but we don’t allow the digit part to be more than 2 billion

Message: Failed to alter: %s

Message: Writing one row to the row-based binary log failed

Message: Table definition on master and slave does not match: %s

Message: Slave running with –log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events

Message: Event ’%s’ already exists

Message: Failed to store event %s. Error code %d from storage engine.

Message: Unknown event ’%s’

Message: Failed to alter event ’%s’

Message: Failed to drop %s

Message: INTERVAL is either not positive or too big

Message: ENDS is either invalid or before STARTS

Message: Event execution time is in the past. Event has been disabled

Message: Failed to open mysql.event

Message: No datetime expression provided

Message: Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted

Message: Cannot load from mysql.%s. The table is probably corrupted

Message: Failed to delete the event from mysql.event

Message: Error during compilation of event’s body

Message: Same old and new event name

Message: Data for column ’%s’ too long

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.

Message: The syntax ’%s’ is deprecated and will be removed in MySQL %s. Please use %s instead

Message: You can’t write-lock a log table. Only read access is possible

Message: You can’t use locks with log tables.

Message: Upholding foreign key constraints for table ’%s’, entry ’%s’, key %d would lead to a duplicate entry

Message: Column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.

Message: Cannot switch out of the row-based binary log format when the session has open temporary tables

Message: Cannot change the binary logging format inside a stored function or trigger

Message: The NDB cluster engine does not support changing the binlog format on the fly yet

Message: Cannot create temporary table with partitions

Message: Partition constant is out of partition function domain

Message: This partition function is not allowed

Message: Error in DDL log

Message: Not allowed to use NULL value in VALUES LESS THAN

Message: Incorrect partition name

Message: Transaction characteristics can’t be changed while a transaction is in progress

Message: ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry ’%s’ for key ’%s’

Message: Internal scheduler error %d

Message: Error during starting/stopping of the scheduler. Error code %u

Message: Engine cannot be used in partitioned tables

Message: Cannot activate ’%s’ log

Message: The server was not built with row-based replication

Message: Decoding of base64 string failed

Message: Recursion of EVENT DDL statements is forbidden when body is present

Message: Cannot proceed because system tables used by Event Scheduler were found damaged at server start

To address this issue, try running mysql_upgrade.

Message: Only integers allowed as number here

Message: This storage engine cannot be used for log tables”

Message: You cannot ’%s’ a log table if logging is enabled

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’

Message: Incorrect parameter count in the call to native function ’%s’

Message: Incorrect parameters in the call to native function ’%s’

Message: Incorrect parameters in the call to stored function %s

Message: This function ’%s’ has the same name as a native function

Message: Duplicate entry ’%s’ for key ’%s’

The format string for this error is also used with ER_DUP_ENTRY.

Message: Too many files opened, please execute the command again

Message: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.

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.

Message: The incident %s occured on the master. Message: %s

Message: Table has no partition for some existing values

Message: Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s

Message: Fatal error: %s

Message: Relay log read failure: %s

Message: Relay log write failure: %s

Message: Failed to create %s

Message: Master command %s failed: %s

Message: Binary logging not possible. Message: %s

Message: View `%s`.`%s` has no creation context

Message: Creation context of view `%s`.`%s’ is invalid

Message: Creation context of stored routine `%s`.`%s` is invalid

Message: Corrupted TRG file for table `%s`.`%s`

Message: Triggers for table `%s`.`%s` have no creation context

Message: Trigger creation context of table `%s`.`%s` is invalid

Message: Creation context of event `%s`.`%s` is invalid

Message: Cannot open table for trigger `%s`.`%s`

Message: Cannot create stored routine `%s`. Check warnings

Message: Ambiguous slave modes combination. %s

Message: The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.

Message: Corrupted replication event was detected

Message: Invalid column reference (%s) in LOAD DATA

ER_LOAD_DATA_INVALID_COLUMN was removed after 5.7.7.

Message: Invalid column reference (%s) in LOAD DATA

ER_LOAD_DATA_INVALID_COLUMN_UNUSED was added in 5.7.8.

Message: Being purged log %s was not found

Message: XA_RBTIMEOUT: Transaction branch was rolled back: took too long

Message: XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected

Message: Prepared statement needs to be re-prepared

Message: DELAYED option not supported for table ’%s’

Message: The master info structure does not exist

Message: <%s> option ignored

Message: Built-in plugins cannot be deleted

WARN_PLUGIN_DELETE_BUILTIN was removed after 5.7.4.

Message: Built-in plugins cannot be deleted

ER_PLUGIN_DELETE_BUILTIN was added in 5.7.5.

Message: Plugin is busy and will be uninstalled on shutdown

Message: %s variable ’%s’ is read-only. Use SET %s to assign the value

Message: Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted

Message: Unexpected master’s heartbeat data: %s

Message: The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).

Message: Bad schema for mysql.ndb_replication table. Message: %s

Message: Error in parsing conflict function. Message: %s

Message: Write to exceptions table failed. Message: %s”

Message: Comment for table ’%s’ is too long (max = %lu)

Message: Comment for field ’%s’ is too long (max = %lu)

Message: FUNCTION %s does not exist. Check the ’Function Name Parsing and Resolution’ section in the Reference Manual

Message: Database

Message: Table

Message: Partition

Message: Subpartition

Message: Temporary

Message: Renamed

Message: Too many active concurrent transactions

Message: Non-ASCII separator arguments are not fully supported

Message: debug sync point wait timed out

Message: debug sync point hit limit reached

Message: Duplicate condition information item ’%s’

Message: Unhandled user-defined warning condition

Message: Unhandled user-defined not found condition

Message: Unhandled user-defined exception condition

Message: RESIGNAL when handler not active

Message: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE

Message: Data truncated for condition item ’%s’

Message: Data too long for condition item ’%s’

Message: Unknown locale: ’%s’

Message: The requested server id %d clashes with the slave startup option –replicate-same-server-id

Message: Query cache is disabled; restart the server with query_cache_type=1 to enable it

Message: Duplicate partition field name ’%s’

Message: Inconsistency in usage of column lists for partitioning

Message: Partition column values of incorrect type

Message: Too many fields in ’%s’

Message: Cannot use MAXVALUE as value in VALUES IN

Message: Cannot have more than one value for this type of %s partitioning

Message: Row expressions in VALUES IN only allowed for multi-field column partitioning

Message: Field ’%s’ is of a not allowed type for this type of partitioning

Message: The total length of the partitioning fields is too large

Message: Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.

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.

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

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.

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

Message: Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.

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.

Message: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.

Message: The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.

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 slaves.

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.

Message: Statement is unsafe because it uses a UDF which may not return the same value on the slave.

Message: Statement is unsafe because it uses a system variable that may have a different value on the slave.

Message: Statement is unsafe because it uses a system function that may return a different value on the slave.

Message: Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.

Message: %s Statement: %s

Message: Column %d of table ’%s.%s’ cannot be converted from type ’%s’ to type ’%s’

Message: Can’t create conversion table for table ’%s.%s’

Message: Cannot modify @@session.binlog_format inside a transaction

Message: The path specified for %s is too long.

Message: ’%s’ is deprecated and will be removed in a future release.

Message: Native table ’%s’.’%s’ has the wrong structure

Message: Invalid performance_schema usage.

Message: Table ’%s’.’%s’ was skipped since its definition is being modified by concurrent DDL statement

Message: Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction

Message: Cannot change the binlog direct flag inside a stored function or trigger

Message: A SPATIAL index may only contain a geometrical type column

Message: Comment for index ’%s’ is too long (max = %lu)

Message: Wait on a lock was aborted due to a pending exclusive lock

Message: %s value is out of range in ’%s’

Message: A variable of a non-integer based type in LIMIT clause

Message: Mixing self-logging and non-self-logging engines in a statement is unsafe.

Message: Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.

Message: Cannot modify @@session.sql_log_bin inside a transaction

Message: Cannot change the sql_log_bin inside a stored function or trigger

Message: Failed to read from the .par file

Message: VALUES value for partition ’%s’ must have type INT

Message: Access denied for user ’%s’@’%s’

Message: SET PASSWORD has no significance for users authenticating via plugins

Message: GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists

Message: Cannot truncate a table referenced in a foreign key constraint (%s)

Message: Plugin ’%s’ is force_plus_permanent and can not be unloaded

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.

Message: The requested value for the heartbeat period exceeds the value of `slave_net_timeout’ seconds. A sensible value for the period should be less than the timeout.

Message: Multi-row statements required more than ’max_binlog_stmt_cache_size’ bytes of storage; increase this mysqld variable and try again

Message: Primary key/partition key update is not allowed since the table is updated both as ’%s’ and ’%s’.

Message: Table rebuild required. Please do ”ALTER TABLE `%s` FORCE” or dump/reload to fix it!

Message: The value of ’%s’ should be no less than the value of ’%s’

Message: Index column size too large. The maximum column size is %lu bytes.

Message: Trigger ’%s’ has an error in its body: ’%s’

Message: Unknown trigger has an error in its body: ’%s’

Message: Index %s is corrupted

Message: Undo log record is too big.

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 master and the slave.

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 master and the slave.

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 master and the slave.

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 master and the slave.

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 master and the slave.

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 master and the slave.

Message: Plugin ’%s’ is marked as not dynamically uninstallable. You have to stop the server to uninstall it.

Message: Plugin ’%s’ is marked as not dynamically installable. You have to stop the server to install it.

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 master and the slave.

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 master and the slave.

Message: INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe

Message: Table is being used in foreign key check.

Message: Storage engine ’%s’ does not support system tables. [%s.%s]

Message: INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.

Message: Cannot load from %s.%s. The table is probably corrupted

Message: The requested value %s for the master delay exceeds the maximum %u

Message: Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)

Message: Non matching attribute ’%s’ between partition and table

Message: Table to exchange with partition is partitioned: ’%s’

Message: Table to exchange with partition is temporary: ’%s’

Message: Subpartitioned table, use subpartition instead of partition

Message: Unknown partition ’%s’ in table ’%s’

Message: Tables have different definitions

Message: Found a row that does not match the partition

Message: Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.

Message: Cannot use %s access on index ’%s’ due to type or collation conversion on field ’%s’

Message: Table to exchange with partition has foreign key references: ’%s’

Message: Key value ’%s’ was not found in table ’%s.%s’

Message: Data for column ’%s’ too long

Message: Replication event checksum verification failed while reading from network.

Message: Replication event checksum verification failed while reading from a log file.

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.

Message: Can’t update table ’%s’ while ’%s’ is being created.

Message: PARTITION () clause on non partitioned table

Message: Found a row not matching the given partition set

Message: partition ’%s’ doesn’t exist

Message: Failure while changing the type of replication repository: %s.

Message: The creation of some temporary tables could not be rolled back.

Message: Some temporary tables were dropped, but these operations could not be rolled back.

Message: %s is not supported in multi-threaded slave mode. %s

Message: The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.

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.

Message: %s

Message: FULLTEXT index is not supported for partitioned tables.

Message: Invalid condition number

Message: Sending passwords in plain text without SSL/TLS is extremely insecure.

Message: Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the ’START SLAVE Syntax’ in the MySQL Manual for more information.

Message: Foreign key constraint for table ’%s’, record ’%s’ would lead to a duplicate entry in table ’%s’, key ’%s’

Message: Foreign key constraint for table ’%s’, record ’%s’ would lead to a duplicate entry in a child table

Message: Setting authentication options is not possible when only the Slave SQL Thread is being started.

Message: The table does not have FULLTEXT index to support this query

Message: The system variable %s cannot be set in stored functions or triggers.

Message: The system variable %s cannot be set when there is an ongoing transaction.

Message: The system variable @@SESSION.GTID_NEXT has the value %s, which is not listed in @@SESSION.GTID_NEXT_LIST.

Message: The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.

ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION_WHEN_GTID_NEXT_LIST_IS_NULL was removed after 5.7.5.

Message: The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.

ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION was added in 5.7.6.

Message: The statement ’SET %s’ cannot invoke a stored function.

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

Message: Skipping transaction %s because it has already been executed and logged.

Message: Malformed GTID set specification ’%s’.

Message: Malformed GTID set encoding.

Message: Malformed GTID specification ’%s’.

Message: Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid.

Message: Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.

Message: CHANGE MASTER TO MASTER_AUTO_POSITION = 1 can only be executed when @@GLOBAL.GTID_MODE = ON.

ER_AUTO_POSITION_REQUIRES_GTID_MODE_ON was removed after 5.7.5.

Message: CHANGE MASTER TO MASTER_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.

ER_AUTO_POSITION_REQUIRES_GTID_MODE_NOT_OFF was added in 5.7.6.

Message: Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == ’UUID:NUMBER’.

Message: @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_2 requires @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.

ER_GTID_MODE_2_OR_3_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON was removed after 5.7.5.

Message: GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.

ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON was added in 5.7.6.

Message: @@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires –log-bin and –log-slave-updates.

Message: @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.

Message: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.

Message: @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.

Message: Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF.

ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF was removed after 5.7.5.

Message: Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.

ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF__UNUSED was added in 5.7.6.

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.

Message: Statement violates GTID consistency: CREATE TABLE … SELECT.

Message: Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.

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.

Message: The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.

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.

Message: Unknown EXPLAIN format name: ’%s’

Message: Cannot execute statement in a READ ONLY transaction.

Message: Comment for table partition ’%s’ is too long (max = %lu)

Message: Slave is not configured or failed to initialize properly. You must at least set –server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.

Message: InnoDB presently supports one FULLTEXT index creation at a time

Message: Cannot create FULLTEXT index on temporary InnoDB table

Message: Column ’%s’ is of wrong type for an InnoDB FULLTEXT index

Message: Index ’%s’ is of wrong type for an InnoDB FULLTEXT index

Message: Creating index ’%s’ required more than ’innodb_online_alter_log_max_size’ bytes of modification log. Please try again.

Message: Unknown ALGORITHM ’%s’

Message: Unknown LOCK type ’%s’

Message: CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL.

Message: Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.

Message: Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.

Message: Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted

Message: Slave must silently retry current transaction

Message: There is a foreign key check running on table ’%s’. Cannot discard the table.

Message: Schema mismatch (%s)

Message: Table ’%s’ in system tablespace

Message: IO Read error: (%lu, %s) %s

Message: IO Write error: (%lu, %s) %s

Message: Tablespace is missing for table %s.

Message: Tablespace ’%s’ exists.

Message: Tablespace has been discarded for table ’%s’

Message: Internal error: %s

Message: ALTER TABLE %s IMPORT TABLESPACE failed with error %lu : ’%s’

Message: Index corrupt: %s

Message: Supports only YEAR or YEAR(4) column.

Message: Your password does not satisfy the current policy requirements

Message: You must reset your password using ALTER USER statement before executing this statement.

Message: Failed to add the foreign key constaint. Missing index for constraint ’%s’ in the foreign table ’%s’

Message: Failed to add the foreign key constaint. Missing index for constraint ’%s’ in the referenced table ’%s’

Message: Failed to add the foreign key constraint ’%s’ to system tables

Message: Failed to open the referenced table ’%s’

Message: Failed to add the foreign key constraint on table ’%s’. Incorrect options in FOREIGN KEY constraint ’%s’

Message: Duplicate foreign key constraint name ’%s’

Message: The password hash doesn’t have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function.

Message: Cannot drop column ’%s’: needed in a foreign key constraint ’%s’

Message: Cannot drop column ’%s’: needed in a foreign key constraint ’%s’ of table ’%s’

Message: Column ’%s’ cannot be NOT NULL: needed in a foreign key constraint ’%s’ SET NULL

Message: Duplicate index ’%s’ defined on the table ’%s.%s’. This is deprecated and will be disallowed in a future release.

Message: Cannot change column ’%s’: used in a foreign key constraint ’%s’

Message: Cannot change column ’%s’: used in a foreign key constraint ’%s’ of table ’%s’

Message: Cannot delete rows from table which is parent in a foreign key constraint ’%s’ of table ’%s’

ER_FK_CANNOT_DELETE_PARENT was removed after 5.7.3.

Message: Cannot delete rows from table which is parent in a foreign key constraint ’%s’ of table ’%s’

ER_UNUSED5 was added in 5.7.4.

Message: Malformed communication packet.

Message: Running in read-only mode

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’.

Message: The system variable %s cannot be set in stored procedures.

Message: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.

Message: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.

Message: @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).

Message: @@GLOBAL.GTID_PURGED was changed from ’%s’ to ’%s’.

Message: @@GLOBAL.GTID_EXECUTED was changed from ’%s’ to ’%s’.

Message: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.

Message: %s is not supported for this operation. Try %s.

ER_ALTER_OPERATION_NOT_SUPPORTED was added in 5.7.1.

Message: %s is not supported. Reason: %s. Try %s.

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON was added in 5.7.1.

Message: COPY algorithm requires a lock

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY was added in 5.7.1.

Message: Partition specific operations do not yet support LOCK/ALGORITHM

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION was added in 5.7.1.

Message: Columns participating in a foreign key are renamed

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME was added in 5.7.1.

Message: Cannot change column type INPLACE

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE was added in 5.7.1.

Message: Adding foreign keys needs foreign_key_checks=OFF

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK was added in 5.7.1.

Message: Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_IGNORE was added in 5.7.1, removed after 5.7.3.