Table of Contents
This appendix lists common problems and errors that may occur and potential resolutions, in addition to listing the errors that may appear when you call MySQL from any host language. The first section covers problems and resolutions. Detailed information on errors is provided: One list displays server error messages. Another list displays client program messages.
There are several sources of error information in MySQL:
Each SQL statement executed results in an error code, an SQLSTATE value, and an error message, as described in Section B.2, “Types of Error Values”. These errors are returned from the server side; see Section B.3, “Server Error Codes and Messages”.
Errors can occur on the client side, usually involving problems communicating with the server; see Section B.4, “Client Error Codes and Messages”.
SQL statement warning and error information is available
through the SHOW WARNINGS
and
SHOW ERRORS
statements. The
warning_count
system variable
indicates the number of errors, warnings, and notes. The
error_count
system variable
indicates the number of errors. Its value excludes warnings
and notes.
The GET DIAGNOSTICS
statement
may be used to inspect the diagnostic information in the
diagnostics area. See Section 13.6.7.3, “GET DIAGNOSTICS Syntax”.
SHOW SLAVE STATUS
statement
output includes information about replication errors occurring
on the slave side.
SHOW ENGINE
INNODB STATUS
statement output includes information
about the most recent foreign key error if a
CREATE TABLE
statement for an
InnoDB
table fails.
The perror program provides information from the command line about error numbers. See Section 4.8.2, “perror — Explain Error Codes”.
Descriptions of server and client errors are provided later in
this Appendix. For information about errors related to
InnoDB
, see
Section 15.20.4, “InnoDB Error Handling”.
When an error occurs in MySQL, the server returns two types of error values:
A MySQL-specific error code. This value is numeric. It is not portable to other database systems.
An SQLSTATE value. The value is a five-character string (for
example, '42S02'
). The values are taken
from ANSI SQL and ODBC and are more standardized.
A message string that provides a textual description of the error is also available.
When an error occurs, the MySQL error code, SQLSTATE value, and message string are available using C API functions:
MySQL error code: Call
mysql_errno()
SQLSTATE value: Call
mysql_sqlstate()
Error message: Call
mysql_error()
For prepared statements, the corresponding error functions are
mysql_stmt_errno()
,
mysql_stmt_sqlstate()
, and
mysql_stmt_error()
. All error
functions are described in Section 27.7, “MySQL C API”.
The number of errors, warnings, and notes for the previous
statement can be obtained by calling
mysql_warning_count()
. See
Section 27.7.7.80, “mysql_warning_count()”.
The first two characters of an SQLSTATE value indicate the error class:
Class = '00'
indicates success.
Class = '01'
indicates a warning.
Class = '02'
indicates “not
found.” This is relevant within the context of cursors
and is used to control what happens when a cursor reaches the
end of a data set. This condition also occurs for
SELECT ... INTO
statements that
retrieve no rows.
var_list
Class > '02'
indicates an exception.
MySQL programs have access to several types of error information when the server returns an error. For example, the mysql client program displays errors using the following format:
shell> SELECT * FROM no_such_table;
ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist
The message displayed contains three types of information:
A numeric error code (1146
). This number is
MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value ('42S02'
).
The values are taken from ANSI SQL and ODBC and are more
standardized. Not all MySQL error numbers have corresponding
SQLSTATE values. In these cases, 'HY000'
(general error) is used.
A message string that provides a textual description of the error.
For error checking, use error codes, not error messages. Error messages do not change often, but it is possible. Also if the database administrator changes the language setting, that affects the language of error messages.
Error codes are stable across GA releases of a given MySQL series. Before a series reaches GA status, new codes may still be under development and subject to change.
Server error information comes from the following source files. For details about the way that error information is defined, see the MySQL Internals Manual.
Error message information is listed in the
share/errmsg-utf8.txt
file.
%d
and %s
represent
numbers and strings, respectively, that are substituted into
the Message values when they are displayed.
The Error values listed in
share/errmsg-utf8.txt
are used to
generate the definitions in the
include/mysqld_error.h
and
include/mysqld_ername.h
MySQL source
files.
The SQLSTATE values listed in
share/errmsg-utf8.txt
are used to
generate the definitions in the
include/sql_state.h
MySQL source file.
Because updates are frequent, it is possible that those files will contain additional error information not listed here.
Error: 1002
SQLSTATE: HY000
(ER_NO
)
Message: NO
Used in the construction of other messages.
Error: 1003
SQLSTATE: HY000
(ER_YES
)
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: 1004
SQLSTATE: HY000
(ER_CANT_CREATE_FILE
)
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: 1005
SQLSTATE: HY000
(ER_CANT_CREATE_TABLE
)
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: 1006
SQLSTATE: HY000
(ER_CANT_CREATE_DB
)
Message: Can't create database '%s' (errno: %d - %s)
Error: 1007
SQLSTATE: HY000
(ER_DB_CREATE_EXISTS
)
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: 1008
SQLSTATE: HY000
(ER_DB_DROP_EXISTS
)
Message: Can't drop database '%s'; database doesn't exist
Error: 1010
SQLSTATE: HY000
(ER_DB_DROP_RMDIR
)
Message: Error dropping database (can't rmdir '%s', errno: %d - %s)
Error: 1012
SQLSTATE: HY000
(ER_CANT_FIND_SYSTEM_REC
)
Message: Can't read record in system table
Returned by InnoDB
for attempts to access
InnoDB
INFORMATION_SCHEMA
tables when InnoDB
is unavailable.
Error: 1013
SQLSTATE: HY000
(ER_CANT_GET_STAT
)
Message: Can't get status of '%s' (errno: %d - %s)
Error: 1015
SQLSTATE: HY000
(ER_CANT_LOCK
)
Message: Can't lock file (errno: %d - %s)
Error: 1016
SQLSTATE: HY000
(ER_CANT_OPEN_FILE
)
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: 1017
SQLSTATE: HY000
(ER_FILE_NOT_FOUND
)
Message: Can't find file: '%s' (errno: %d - %s)
Error: 1018
SQLSTATE: HY000
(ER_CANT_READ_DIR
)
Message: Can't read dir of '%s' (errno: %d - %s)
Error: 1020
SQLSTATE: HY000
(ER_CHECKREAD
)
Message: Record has changed since last read in table '%s'
Error: 1022
SQLSTATE: 23000
(ER_DUP_KEY
)
Message: Can't write; duplicate key in table '%s'
Error: 1024
SQLSTATE: HY000
(ER_ERROR_ON_READ
)
Message: Error reading file '%s' (errno: %d - %s)
Error: 1025
SQLSTATE: HY000
(ER_ERROR_ON_RENAME
)
Message: Error on rename of '%s' to '%s' (errno: %d - %s)
Error: 1026
SQLSTATE: HY000
(ER_ERROR_ON_WRITE
)
Message: Error writing file '%s' (errno: %d - %s)
Error: 1027
SQLSTATE: HY000
(ER_FILE_USED
)
Message: '%s' is locked against change
Error: 1028
SQLSTATE: HY000
(ER_FILSORT_ABORT
)
Message: Sort aborted
Error: 1030
SQLSTATE: HY000
(ER_GET_ERRNO
)
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: 1031
SQLSTATE: HY000
(ER_ILLEGAL_HA
)
Message: Table storage engine for '%s' doesn't have this option
Error: 1032
SQLSTATE: HY000
(ER_KEY_NOT_FOUND
)
Message: Can't find record in '%s'
Error: 1033
SQLSTATE: HY000
(ER_NOT_FORM_FILE
)
Message: Incorrect information in file: '%s'
Error: 1034
SQLSTATE: HY000
(ER_NOT_KEYFILE
)
Message: Incorrect key file for table '%s'; try to repair it
Error: 1035
SQLSTATE: HY000
(ER_OLD_KEYFILE
)
Message: Old key file for table '%s'; repair it!
Error: 1036
SQLSTATE: HY000
(ER_OPEN_AS_READONLY
)
Message: Table '%s' is read only
Error: 1037
SQLSTATE: HY001
(ER_OUTOFMEMORY
)
Message: Out of memory; restart server and try again (needed %d bytes)
Error: 1038
SQLSTATE: HY001
(ER_OUT_OF_SORTMEMORY
)
Message: Out of sort memory, consider increasing server sort buffer size
Error: 1040
SQLSTATE: 08004
(ER_CON_COUNT_ERROR
)
Message: Too many connections
Error: 1041
SQLSTATE: HY000
(ER_OUT_OF_RESOURCES
)
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: 1042
SQLSTATE: 08S01
(ER_BAD_HOST_ERROR
)
Message: Can't get hostname for your address
Error: 1043
SQLSTATE: 08S01
(ER_HANDSHAKE_ERROR
)
Message: Bad handshake
Error: 1044
SQLSTATE: 42000
(ER_DBACCESS_DENIED_ERROR
)
Message: Access denied for user '%s'@'%s' to database '%s'
Error: 1045
SQLSTATE: 28000
(ER_ACCESS_DENIED_ERROR
)
Message: Access denied for user '%s'@'%s' (using password: %s)
Error: 1046
SQLSTATE: 3D000
(ER_NO_DB_ERROR
)
Message: No database selected
Error: 1047
SQLSTATE: 08S01
(ER_UNKNOWN_COM_ERROR
)
Message: Unknown command
Error: 1048
SQLSTATE: 23000
(ER_BAD_NULL_ERROR
)
Message: Column '%s' cannot be null
Error: 1049
SQLSTATE: 42000
(ER_BAD_DB_ERROR
)
Message: Unknown database '%s'
Error: 1050
SQLSTATE: 42S01
(ER_TABLE_EXISTS_ERROR
)
Message: Table '%s' already exists
Error: 1051
SQLSTATE: 42S02
(ER_BAD_TABLE_ERROR
)
Message: Unknown table '%s'
Error: 1052
SQLSTATE: 23000
(ER_NON_UNIQ_ERROR
)
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: 1053
SQLSTATE: 08S01
(ER_SERVER_SHUTDOWN
)
Message: Server shutdown in progress
Error: 1054
SQLSTATE: 42S22
(ER_BAD_FIELD_ERROR
)
Message: Unknown column '%s' in '%s'
Error: 1055
SQLSTATE: 42000
(ER_WRONG_FIELD_WITH_GROUP
)
Message: '%s' isn't in GROUP BY
Error: 1056
SQLSTATE: 42000
(ER_WRONG_GROUP_FIELD
)
Message: Can't group on '%s'
Error: 1057
SQLSTATE: 42000
(ER_WRONG_SUM_SELECT
)
Message: Statement has sum functions and columns in same statement
Error: 1058
SQLSTATE: 21S01
(ER_WRONG_VALUE_COUNT
)
Message: Column count doesn't match value count
Error: 1059
SQLSTATE: 42000
(ER_TOO_LONG_IDENT
)
Message: Identifier name '%s' is too long
Error: 1060
SQLSTATE: 42S21
(ER_DUP_FIELDNAME
)
Message: Duplicate column name '%s'
Error: 1061
SQLSTATE: 42000
(ER_DUP_KEYNAME
)
Message: Duplicate key name '%s'
Error: 1062
SQLSTATE: 23000
(ER_DUP_ENTRY
)
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: 1063
SQLSTATE: 42000
(ER_WRONG_FIELD_SPEC
)
Message: Incorrect column specifier for column '%s'
Error: 1064
SQLSTATE: 42000
(ER_PARSE_ERROR
)
Message: %s near '%s' at line %d
Error: 1065
SQLSTATE: 42000
(ER_EMPTY_QUERY
)
Message: Query was empty
Error: 1066
SQLSTATE: 42000
(ER_NONUNIQ_TABLE
)
Message: Not unique table/alias: '%s'
Error: 1067
SQLSTATE: 42000
(ER_INVALID_DEFAULT
)
Message: Invalid default value for '%s'
Error: 1068
SQLSTATE: 42000
(ER_MULTIPLE_PRI_KEY
)
Message: Multiple primary key defined
Error: 1069
SQLSTATE: 42000
(ER_TOO_MANY_KEYS
)
Message: Too many keys specified; max %d keys allowed
Error: 1070
SQLSTATE: 42000
(ER_TOO_MANY_KEY_PARTS
)
Message: Too many key parts specified; max %d parts allowed
Error: 1071
SQLSTATE: 42000
(ER_TOO_LONG_KEY
)
Message: Specified key was too long; max key length is %d bytes
Error: 1072
SQLSTATE: 42000
(ER_KEY_COLUMN_DOES_NOT_EXITS
)
Message: Key column '%s' doesn't exist in table
Error: 1073
SQLSTATE: 42000
(ER_BLOB_USED_AS_KEY
)
Message: BLOB column '%s' can't be used in key specification with the used table type
Error: 1074
SQLSTATE: 42000
(ER_TOO_BIG_FIELDLENGTH
)
Message: Column length too big for column '%s' (max = %lu); use BLOB or TEXT instead
Error: 1075
SQLSTATE: 42000
(ER_WRONG_AUTO_KEY
)
Message: Incorrect table definition; there can be only one auto column and it must be defined as a key
Error: 1076
SQLSTATE: HY000
(ER_READY
)
Message: %s: ready for connections. Version: '%s' socket: '%s' port: %d
Error: 1077
SQLSTATE: HY000
(ER_NORMAL_SHUTDOWN
)
Message: %s: Normal shutdown
Error: 1079
SQLSTATE: HY000
(ER_SHUTDOWN_COMPLETE
)
Message: %s: Shutdown complete
Error: 1080
SQLSTATE: 08S01
(ER_FORCING_CLOSE
)
Message: %s: Forcing close of thread %ld user: '%s'
Error: 1081
SQLSTATE: 08S01
(ER_IPSOCK_ERROR
)
Message: Can't create IP socket
Error: 1082
SQLSTATE: 42S12
(ER_NO_SUCH_INDEX
)
Message: Table '%s' has no index like the one used in CREATE INDEX; recreate the table
Error: 1083
SQLSTATE: 42000
(ER_WRONG_FIELD_TERMINATORS
)
Message: Field separator argument is not what is expected; check the manual
Error: 1084
SQLSTATE: 42000
(ER_BLOBS_AND_NO_TERMINATED
)
Message: You can't use fixed rowlength with BLOBs; please use 'fields terminated by'
Error: 1085
SQLSTATE: HY000
(ER_TEXTFILE_NOT_READABLE
)
Message: The file '%s' must be in the database directory or be readable by all
Error: 1086
SQLSTATE: HY000
(ER_FILE_EXISTS_ERROR
)
Message: File '%s' already exists
Error: 1087
SQLSTATE: HY000
(ER_LOAD_INFO
)
Message: Records: %ld Deleted: %ld Skipped: %ld Warnings: %ld
Error: 1088
SQLSTATE: HY000
(ER_ALTER_INFO
)
Message: Records: %ld Duplicates: %ld
Error: 1089
SQLSTATE: HY000
(ER_WRONG_SUB_KEY
)
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: 1090
SQLSTATE: 42000
(ER_CANT_REMOVE_ALL_FIELDS
)
Message: You can't delete all columns with ALTER TABLE; use DROP TABLE instead
Error: 1091
SQLSTATE: 42000
(ER_CANT_DROP_FIELD_OR_KEY
)
Message: Can't DROP '%s'; check that column/key exists
Error: 1092
SQLSTATE: HY000
(ER_INSERT_INFO
)
Message: Records: %ld Duplicates: %ld Warnings: %ld
Error: 1093
SQLSTATE: HY000
(ER_UPDATE_TABLE_USED
)
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 Section 8.2.2.3, “Optimizing Derived Tables, View References, and Common Table Expressions”.
Error: 1094
SQLSTATE: HY000
(ER_NO_SUCH_THREAD
)
Message: Unknown thread id: %lu
Error: 1095
SQLSTATE: HY000
(ER_KILL_DENIED_ERROR
)
Message: You are not owner of thread %lu
Error: 1096
SQLSTATE: HY000
(ER_NO_TABLES_USED
)
Message: No tables used
Error: 1097
SQLSTATE: HY000
(ER_TOO_BIG_SET
)
Message: Too many strings for column %s and SET
Error: 1098
SQLSTATE: HY000
(ER_NO_UNIQUE_LOGFILE
)
Message: Can't generate a unique log-filename %s.(1-999)
Error: 1099
SQLSTATE: HY000
(ER_TABLE_NOT_LOCKED_FOR_WRITE
)
Message: Table '%s' was locked with a READ lock and can't be updated
Error: 1100
SQLSTATE: HY000
(ER_TABLE_NOT_LOCKED
)
Message: Table '%s' was not locked with LOCK TABLES
Error: 1101
SQLSTATE: 42000
(ER_BLOB_CANT_HAVE_DEFAULT
)
Message: BLOB, TEXT, GEOMETRY or JSON column '%s' can't have a default value
Error: 1102
SQLSTATE: 42000
(ER_WRONG_DB_NAME
)
Message: Incorrect database name '%s'
Error: 1103
SQLSTATE: 42000
(ER_WRONG_TABLE_NAME
)
Message: Incorrect table name '%s'
Error: 1104
SQLSTATE: 42000
(ER_TOO_BIG_SELECT
)
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: 1105
SQLSTATE: HY000
(ER_UNKNOWN_ERROR
)
Message: Unknown error
Error: 1106
SQLSTATE: 42000
(ER_UNKNOWN_PROCEDURE
)
Message: Unknown procedure '%s'
Error: 1107
SQLSTATE: 42000
(ER_WRONG_PARAMCOUNT_TO_PROCEDURE
)
Message: Incorrect parameter count to procedure '%s'
Error: 1108
SQLSTATE: HY000
(ER_WRONG_PARAMETERS_TO_PROCEDURE
)
Message: Incorrect parameters to procedure '%s'
Error: 1109
SQLSTATE: 42S02
(ER_UNKNOWN_TABLE
)
Message: Unknown table '%s' in %s
Error: 1110
SQLSTATE: 42000
(ER_FIELD_SPECIFIED_TWICE
)
Message: Column '%s' specified twice
Error: 1111
SQLSTATE: HY000
(ER_INVALID_GROUP_FUNC_USE
)
Message: Invalid use of group function
Error: 1112
SQLSTATE: 42000
(ER_UNSUPPORTED_EXTENSION
)
Message: Table '%s' uses an extension that doesn't exist in this MySQL version
Error: 1113
SQLSTATE: 42000
(ER_TABLE_MUST_HAVE_COLUMNS
)
Message: A table must have at least 1 column
Error: 1114
SQLSTATE: HY000
(ER_RECORD_FILE_FULL
)
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: 1115
SQLSTATE: 42000
(ER_UNKNOWN_CHARACTER_SET
)
Message: Unknown character set: '%s'
Error: 1116
SQLSTATE: HY000
(ER_TOO_MANY_TABLES
)
Message: Too many tables; MySQL can only use %d tables in a join
Error: 1117
SQLSTATE: HY000
(ER_TOO_MANY_FIELDS
)
Message: Too many columns
Error: 1118
SQLSTATE: 42000
(ER_TOO_BIG_ROWSIZE
)
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: 1119
SQLSTATE: HY000
(ER_STACK_OVERRUN
)
Message: Thread stack overrun: Used: %ld of a %ld stack. Use 'mysqld --thread_stack=#' to specify a bigger stack if needed
Error: 1120
SQLSTATE: 42000
(ER_WRONG_OUTER_JOIN
)
Message: Cross dependency found in OUTER JOIN; examine your ON conditions
ER_WRONG_OUTER_JOIN
was removed
after 8.0.0.
Error: 1120
SQLSTATE: 42000
(ER_WRONG_OUTER_JOIN_UNUSED
)
Message: Cross dependency found in OUTER JOIN; examine your ON conditions
ER_WRONG_OUTER_JOIN_UNUSED
was
added in 8.0.1.
Error: 1121
SQLSTATE: 42000
(ER_NULL_COLUMN_IN_INDEX
)
Message: Table handler doesn't support NULL in given index. Please change column '%s' to be NOT NULL or use another handler
Error: 1122
SQLSTATE: HY000
(ER_CANT_FIND_UDF
)
Message: Can't load function '%s'
Error: 1123
SQLSTATE: HY000
(ER_CANT_INITIALIZE_UDF
)
Message: Can't initialize function '%s'; %s
Error: 1124
SQLSTATE: HY000
(ER_UDF_NO_PATHS
)
Message: No paths allowed for shared library
Error: 1125
SQLSTATE: HY000
(ER_UDF_EXISTS
)
Message: Function '%s' already exists
Error: 1126
SQLSTATE: HY000
(ER_CANT_OPEN_LIBRARY
)
Message: Can't open shared library '%s' (errno: %d %s)
Error: 1127
SQLSTATE: HY000
(ER_CANT_FIND_DL_ENTRY
)
Message: Can't find symbol '%s' in library
Error: 1128
SQLSTATE: HY000
(ER_FUNCTION_NOT_DEFINED
)
Message: Function '%s' is not defined
Error: 1129
SQLSTATE: HY000
(ER_HOST_IS_BLOCKED
)
Message: Host '%s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
Error: 1130
SQLSTATE: HY000
(ER_HOST_NOT_PRIVILEGED
)
Message: Host '%s' is not allowed to connect to this MySQL server
Error: 1131
SQLSTATE: 42000
(ER_PASSWORD_ANONYMOUS_USER
)
Message: You are using MySQL as an anonymous user and anonymous users are not allowed to change passwords
Error: 1132
SQLSTATE: 42000
(ER_PASSWORD_NOT_ALLOWED
)
Message: You must have privileges to update tables in the mysql database to be able to change passwords for others
Error: 1133
SQLSTATE: 42000
(ER_PASSWORD_NO_MATCH
)
Message: Can't find any matching row in the user table
Error: 1134
SQLSTATE: HY000
(ER_UPDATE_INFO
)
Message: Rows matched: %ld Changed: %ld Warnings: %ld
Error: 1135
SQLSTATE: HY000
(ER_CANT_CREATE_THREAD
)
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: 1136
SQLSTATE: 21S01
(ER_WRONG_VALUE_COUNT_ON_ROW
)
Message: Column count doesn't match value count at row %ld
Error: 1137
SQLSTATE: HY000
(ER_CANT_REOPEN_TABLE
)
Message: Can't reopen table: '%s'
Error: 1138
SQLSTATE: 22004
(ER_INVALID_USE_OF_NULL
)
Message: Invalid use of NULL value
Error: 1139
SQLSTATE: 42000
(ER_REGEXP_ERROR
)
Message: Got error '%s' from regexp
Error: 1140
SQLSTATE: 42000
(ER_MIX_OF_GROUP_FUNC_AND_FIELDS
)
Message: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause
Error: 1141
SQLSTATE: 42000
(ER_NONEXISTING_GRANT
)
Message: There is no such grant defined for user '%s' on host '%s'
Error: 1142
SQLSTATE: 42000
(ER_TABLEACCESS_DENIED_ERROR
)
Message: %s command denied to user '%s'@'%s' for table '%s'
Error: 1143
SQLSTATE: 42000
(ER_COLUMNACCESS_DENIED_ERROR
)
Message: %s command denied to user '%s'@'%s' for column '%s' in table '%s'
Error: 1144
SQLSTATE: 42000
(ER_ILLEGAL_GRANT_FOR_TABLE
)
Message: Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used
Error: 1145
SQLSTATE: 42000
(ER_GRANT_WRONG_HOST_OR_USER
)
Message: The host or user argument to GRANT is too long
Error: 1146
SQLSTATE: 42S02
(ER_NO_SUCH_TABLE
)
Message: Table '%s.%s' doesn't exist
Error: 1147
SQLSTATE: 42000
(ER_NONEXISTING_TABLE_GRANT
)
Message: There is no such grant defined for user '%s' on host '%s' on table '%s'
Error: 1148
SQLSTATE: 42000
(ER_NOT_ALLOWED_COMMAND
)
Message: The used command is not allowed with this MySQL version
Error: 1149
SQLSTATE: 42000
(ER_SYNTAX_ERROR
)
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: 1152
SQLSTATE: 08S01
(ER_ABORTING_CONNECTION
)
Message: Aborted connection %ld to db: '%s' user: '%s' (%s)
Error: 1153
SQLSTATE: 08S01
(ER_NET_PACKET_TOO_LARGE
)
Message: Got a packet bigger than 'max_allowed_packet' bytes
Error: 1154
SQLSTATE: 08S01
(ER_NET_READ_ERROR_FROM_PIPE
)
Message: Got a read error from the connection pipe
Error: 1155
SQLSTATE: 08S01
(ER_NET_FCNTL_ERROR
)
Message: Got an error from fcntl()
Error: 1156
SQLSTATE: 08S01
(ER_NET_PACKETS_OUT_OF_ORDER
)
Message: Got packets out of order
Error: 1157
SQLSTATE: 08S01
(ER_NET_UNCOMPRESS_ERROR
)
Message: Couldn't uncompress communication packet
Error: 1158
SQLSTATE: 08S01
(ER_NET_READ_ERROR
)
Message: Got an error reading communication packets
Error: 1159
SQLSTATE: 08S01
(ER_NET_READ_INTERRUPTED
)
Message: Got timeout reading communication packets
Error: 1160
SQLSTATE: 08S01
(ER_NET_ERROR_ON_WRITE
)
Message: Got an error writing communication packets
Error: 1161
SQLSTATE: 08S01
(ER_NET_WRITE_INTERRUPTED
)
Message: Got timeout writing communication packets
Error: 1162
SQLSTATE: 42000
(ER_TOO_LONG_STRING
)
Message: Result string is longer than 'max_allowed_packet' bytes
Error: 1163
SQLSTATE: 42000
(ER_TABLE_CANT_HANDLE_BLOB
)
Message: The used table type doesn't support BLOB/TEXT columns
Error: 1164
SQLSTATE: 42000
(ER_TABLE_CANT_HANDLE_AUTO_INCREMENT
)
Message: The used table type doesn't support AUTO_INCREMENT columns
Error: 1166
SQLSTATE: 42000
(ER_WRONG_COLUMN_NAME
)
Message: Incorrect column name '%s'
Error: 1167
SQLSTATE: 42000
(ER_WRONG_KEY_COLUMN
)
Message: The used storage engine can't index column '%s'
Error: 1168
SQLSTATE: HY000
(ER_WRONG_MRG_TABLE
)
Message: Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist
Error: 1169
SQLSTATE: 23000
(ER_DUP_UNIQUE
)
Message: Can't write, because of unique constraint, to table '%s'
Error: 1170
SQLSTATE: 42000
(ER_BLOB_KEY_WITHOUT_LENGTH
)
Message: BLOB/TEXT column '%s' used in key specification without a key length
Error: 1171
SQLSTATE: 42000
(ER_PRIMARY_CANT_HAVE_NULL
)
Message: All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead
Error: 1172
SQLSTATE: 42000
(ER_TOO_MANY_ROWS
)
Message: Result consisted of more than one row
Error: 1173
SQLSTATE: 42000
(ER_REQUIRES_PRIMARY_KEY
)
Message: This table type requires a primary key
Error: 1175
SQLSTATE: HY000
(ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE
)
Message: You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column
Error: 1176
SQLSTATE: 42000
(ER_KEY_DOES_NOT_EXITS
)
Message: Key '%s' doesn't exist in table '%s'
Error: 1177
SQLSTATE: 42000
(ER_CHECK_NO_SUCH_TABLE
)
Message: Can't open table
Error: 1178
SQLSTATE: 42000
(ER_CHECK_NOT_IMPLEMENTED
)
Message: The storage engine for the table doesn't support %s
Error: 1179
SQLSTATE: 25000
(ER_CANT_DO_THIS_DURING_AN_TRANSACTION
)
Message: You are not allowed to execute this command in a transaction
Error: 1180
SQLSTATE: HY000
(ER_ERROR_DURING_COMMIT
)
Message: Got error %d - '%s' during COMMIT
Error: 1181
SQLSTATE: HY000
(ER_ERROR_DURING_ROLLBACK
)
Message: Got error %d - '%s' during ROLLBACK
Error: 1182
SQLSTATE: HY000
(ER_ERROR_DURING_FLUSH_LOGS
)
Message: Got error %d during FLUSH_LOGS
Error: 1184
SQLSTATE: 08S01
(ER_NEW_ABORTING_CONNECTION
)
Message: Aborted connection %u to db: '%s' user: '%s' host: '%s' (%s)
Error: 1188
SQLSTATE: HY000
(ER_MASTER
)
Message: Error from master: '%s'
Error: 1189
SQLSTATE: 08S01
(ER_MASTER_NET_READ
)
Message: Net error reading from master
Error: 1190
SQLSTATE: 08S01
(ER_MASTER_NET_WRITE
)
Message: Net error writing to master
Error: 1191
SQLSTATE: HY000
(ER_FT_MATCHING_KEY_NOT_FOUND
)
Message: Can't find FULLTEXT index matching the column list
Error: 1192
SQLSTATE: HY000
(ER_LOCK_OR_ACTIVE_TRANSACTION
)
Message: Can't execute the given command because you have active locked tables or an active transaction
Error: 1193
SQLSTATE: HY000
(ER_UNKNOWN_SYSTEM_VARIABLE
)
Message: Unknown system variable '%s'
Error: 1194
SQLSTATE: HY000
(ER_CRASHED_ON_USAGE
)
Message: Table '%s' is marked as crashed and should be repaired
Error: 1195
SQLSTATE: HY000
(ER_CRASHED_ON_REPAIR
)
Message: Table '%s' is marked as crashed and last (automatic?) repair failed
Error: 1196
SQLSTATE: HY000
(ER_WARNING_NOT_COMPLETE_ROLLBACK
)
Message: Some non-transactional changed tables couldn't be rolled back
Error: 1197
SQLSTATE: HY000
(ER_TRANS_CACHE_FULL
)
Message: Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again
Error: 1199
SQLSTATE: HY000
(ER_SLAVE_NOT_RUNNING
)
Message: This operation requires a running slave; configure slave and do START SLAVE
Error: 1200
SQLSTATE: HY000
(ER_BAD_SLAVE
)
Message: The server is not configured as slave; fix in config file or with CHANGE MASTER TO
Error: 1201
SQLSTATE: HY000
(ER_MASTER_INFO
)
Message: Could not initialize master info structure; more error messages can be found in the MySQL error log
Error: 1202
SQLSTATE: HY000
(ER_SLAVE_THREAD
)
Message: Could not create slave thread; check system resources
Error: 1203
SQLSTATE: 42000
(ER_TOO_MANY_USER_CONNECTIONS
)
Message: User %s already has more than 'max_user_connections' active connections
Error: 1204
SQLSTATE: HY000
(ER_SET_CONSTANTS_ONLY
)
Message: You may only use constant expressions with SET
Error: 1205
SQLSTATE: HY000
(ER_LOCK_WAIT_TIMEOUT
)
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: 1206
SQLSTATE: HY000
(ER_LOCK_TABLE_FULL
)
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: 1207
SQLSTATE: 25000
(ER_READ_ONLY_TRANSACTION
)
Message: Update locks cannot be acquired during a READ UNCOMMITTED transaction
Error: 1210
SQLSTATE: HY000
(ER_WRONG_ARGUMENTS
)
Message: Incorrect arguments to %s
Error: 1211
SQLSTATE: 42000
(ER_NO_PERMISSION_TO_CREATE_USER
)
Message: '%s'@'%s' is not allowed to create new users
Error: 1213
SQLSTATE: 40001
(ER_LOCK_DEADLOCK
)
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 15.5.5, “Deadlocks in InnoDB” for details.
Error: 1214
SQLSTATE: HY000
(ER_TABLE_CANT_HANDLE_FT
)
Message: The used table type doesn't support FULLTEXT indexes
Error: 1215
SQLSTATE: HY000
(ER_CANNOT_ADD_FOREIGN
)
Message: Cannot add foreign key constraint
Error: 1216
SQLSTATE: 23000
(ER_NO_REFERENCED_ROW
)
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: 1217
SQLSTATE: 23000
(ER_ROW_IS_REFERENCED
)
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: 1218
SQLSTATE: 08S01
(ER_CONNECT_TO_MASTER
)
Message: Error connecting to master: %s
Error: 1220
SQLSTATE: HY000
(ER_ERROR_WHEN_EXECUTING_COMMAND
)
Message: Error when executing command %s: %s
Error: 1221
SQLSTATE: HY000
(ER_WRONG_USAGE
)
Message: Incorrect usage of %s and %s
Error: 1222
SQLSTATE: 21000
(ER_WRONG_NUMBER_OF_COLUMNS_IN_SELECT
)
Message: The used SELECT statements have a different number of columns
Error: 1223
SQLSTATE: HY000
(ER_CANT_UPDATE_WITH_READLOCK
)
Message: Can't execute the query because you have a conflicting read lock
Error: 1224
SQLSTATE: HY000
(ER_MIXING_NOT_ALLOWED
)
Message: Mixing of transactional and non-transactional tables is disabled
Error: 1225
SQLSTATE: HY000
(ER_DUP_ARGUMENT
)
Message: Option '%s' used twice in statement
Error: 1226
SQLSTATE: 42000
(ER_USER_LIMIT_REACHED
)
Message: User '%s' has exceeded the '%s' resource (current value: %ld)
Error: 1227
SQLSTATE: 42000
(ER_SPECIFIC_ACCESS_DENIED_ERROR
)
Message: Access denied; you need (at least one of) the %s privilege(s) for this operation
Error: 1228
SQLSTATE: HY000
(ER_LOCAL_VARIABLE
)
Message: Variable '%s' is a SESSION variable and can't be used with SET GLOBAL
Error: 1229
SQLSTATE: HY000
(ER_GLOBAL_VARIABLE
)
Message: Variable '%s' is a GLOBAL variable and should be set with SET GLOBAL
Error: 1230
SQLSTATE: 42000
(ER_NO_DEFAULT
)
Message: Variable '%s' doesn't have a default value
Error: 1231
SQLSTATE: 42000
(ER_WRONG_VALUE_FOR_VAR
)
Message: Variable '%s' can't be set to the value of '%s'
Error: 1232
SQLSTATE: 42000
(ER_WRONG_TYPE_FOR_VAR
)
Message: Incorrect argument type to variable '%s'
Error: 1233
SQLSTATE: HY000
(ER_VAR_CANT_BE_READ
)
Message: Variable '%s' can only be set, not read
Error: 1234
SQLSTATE: 42000
(ER_CANT_USE_OPTION_HERE
)
Message: Incorrect usage/placement of '%s'
Error: 1235
SQLSTATE: 42000
(ER_NOT_SUPPORTED_YET
)
Message: This version of MySQL doesn't yet support '%s'
Error: 1236
SQLSTATE: HY000
(ER_MASTER_FATAL_ERROR_READING_BINLOG
)
Message: Got fatal error %d from master when reading data from binary log: '%s'
Error: 1237
SQLSTATE: HY000
(ER_SLAVE_IGNORED_TABLE
)
Message: Slave SQL thread ignored the query because of replicate-*-table rules
Error: 1238
SQLSTATE: HY000
(ER_INCORRECT_GLOBAL_LOCAL_VAR
)
Message: Variable '%s' is a %s variable
Error: 1239
SQLSTATE: 42000
(ER_WRONG_FK_DEF
)
Message: Incorrect foreign key definition for '%s': %s
Error: 1240
SQLSTATE: HY000
(ER_KEY_REF_DO_NOT_MATCH_TABLE_REF
)
Message: Key reference and table reference don't match
Error: 1241
SQLSTATE: 21000
(ER_OPERAND_COLUMNS
)
Message: Operand should contain %d column(s)
Error: 1242
SQLSTATE: 21000
(ER_SUBQUERY_NO_1_ROW
)
Message: Subquery returns more than 1 row
Error: 1243
SQLSTATE: HY000
(ER_UNKNOWN_STMT_HANDLER
)
Message: Unknown prepared statement handler (%.*s) given to %s
Error: 1244
SQLSTATE: HY000
(ER_CORRUPT_HELP_DB
)
Message: Help database is corrupt or does not exist
Error: 1246
SQLSTATE: HY000
(ER_AUTO_CONVERT
)
Message: Converting column '%s' from %s to %s
Error: 1247
SQLSTATE: 42S22
(ER_ILLEGAL_REFERENCE
)
Message: Reference '%s' not supported (%s)
Error: 1248
SQLSTATE: 42000
(ER_DERIVED_MUST_HAVE_ALIAS
)
Message: Every derived table must have its own alias
Error: 1249
SQLSTATE: 01000
(ER_SELECT_REDUCED
)
Message: Select %u was reduced during optimization
Error: 1250
SQLSTATE: 42000
(ER_TABLENAME_NOT_ALLOWED_HERE
)
Message: Table '%s' from one of the SELECTs cannot be used in %s
Error: 1251
SQLSTATE: 08004
(ER_NOT_SUPPORTED_AUTH_MODE
)
Message: Client does not support authentication protocol requested by server; consider upgrading MySQL client
Error: 1252
SQLSTATE: 42000
(ER_SPATIAL_CANT_HAVE_NULL
)
Message: All parts of a SPATIAL index must be NOT NULL
Error: 1253
SQLSTATE: 42000
(ER_COLLATION_CHARSET_MISMATCH
)
Message: COLLATION '%s' is not valid for CHARACTER SET '%s'
Error: 1256
SQLSTATE: HY000
(ER_TOO_BIG_FOR_UNCOMPRESS
)
Message: Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)
Error: 1257
SQLSTATE: HY000
(ER_ZLIB_Z_MEM_ERROR
)
Message: ZLIB: Not enough memory
Error: 1258
SQLSTATE: HY000
(ER_ZLIB_Z_BUF_ERROR
)
Message: ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)
Error: 1259
SQLSTATE: HY000
(ER_ZLIB_Z_DATA_ERROR
)
Message: ZLIB: Input data corrupted
Error: 1260
SQLSTATE: HY000
(ER_CUT_VALUE_GROUP_CONCAT
)
Message: Row %u was cut by GROUP_CONCAT()
Error: 1261
SQLSTATE: 01000
(ER_WARN_TOO_FEW_RECORDS
)
Message: Row %ld doesn't contain data for all columns
Error: 1262
SQLSTATE: 01000
(ER_WARN_TOO_MANY_RECORDS
)
Message: Row %ld was truncated; it contained more data than there were input columns
Error: 1263
SQLSTATE: 22004
(ER_WARN_NULL_TO_NOTNULL
)
Message: Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld
Error: 1264
SQLSTATE: 22003
(ER_WARN_DATA_OUT_OF_RANGE
)
Message: Out of range value for column '%s' at row %ld
Error: 1265
SQLSTATE: 01000
(WARN_DATA_TRUNCATED
)
Message: Data truncated for column '%s' at row %ld
Error: 1266
SQLSTATE: HY000
(ER_WARN_USING_OTHER_HANDLER
)
Message: Using storage engine %s for table '%s'
Error: 1267
SQLSTATE: HY000
(ER_CANT_AGGREGATE_2COLLATIONS
)
Message: Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'
Error: 1269
SQLSTATE: HY000
(ER_REVOKE_GRANTS
)
Message: Can't revoke all privileges for one or more of the requested users
Error: 1270
SQLSTATE: HY000
(ER_CANT_AGGREGATE_3COLLATIONS
)
Message: Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'
Error: 1271
SQLSTATE: HY000
(ER_CANT_AGGREGATE_NCOLLATIONS
)
Message: Illegal mix of collations for operation '%s'
Error: 1272
SQLSTATE: HY000
(ER_VARIABLE_IS_NOT_STRUCT
)
Message: Variable '%s' is not a variable component (can't be used as XXXX.variable_name)
Error: 1273
SQLSTATE: HY000
(ER_UNKNOWN_COLLATION
)
Message: Unknown collation: '%s'
Error: 1274
SQLSTATE: HY000
(ER_SLAVE_IGNORED_SSL_PARAMS
)
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
Error: 1275
SQLSTATE: HY000
(ER_SERVER_IS_IN_SECURE_AUTH_MODE
)
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
Error: 1276
SQLSTATE: HY000
(ER_WARN_FIELD_RESOLVED
)
Message: Field or reference '%s%s%s%s%s' of SELECT #%d was resolved in SELECT #%d
Error: 1277
SQLSTATE: HY000
(ER_BAD_SLAVE_UNTIL_COND
)
Message: Incorrect parameter or combination of parameters for START SLAVE UNTIL
Error: 1278
SQLSTATE: HY000
(ER_MISSING_SKIP_SLAVE
)
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
Error: 1279
SQLSTATE: HY000
(ER_UNTIL_COND_IGNORED
)
Message: SQL thread is not to be started so UNTIL options are ignored
Error: 1280
SQLSTATE: 42000
(ER_WRONG_NAME_FOR_INDEX
)
Message: Incorrect index name '%s'
Error: 1281
SQLSTATE: 42000
(ER_WRONG_NAME_FOR_CATALOG
)
Message: Incorrect catalog name '%s'
Error: 1282
SQLSTATE: HY000
(ER_WARN_QC_RESIZE
)
Message: Query cache failed to set size %lu; new query cache size is %lu
ER_WARN_QC_RESIZE
was removed
after 8.0.2.
Error: 1283
SQLSTATE: HY000
(ER_BAD_FT_COLUMN
)
Message: Column '%s' cannot be part of FULLTEXT index
Error: 1284
SQLSTATE: HY000
(ER_UNKNOWN_KEY_CACHE
)
Message: Unknown key cache '%s'
Error: 1285
SQLSTATE: HY000
(ER_WARN_HOSTNAME_WONT_WORK
)
Message: MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work
Error: 1286
SQLSTATE: 42000
(ER_UNKNOWN_STORAGE_ENGINE
)
Message: Unknown storage engine '%s'
Error: 1287
SQLSTATE: HY000
(ER_WARN_DEPRECATED_SYNTAX
)
Message: '%s' is deprecated and will be removed in a future release. Please use %s instead
Error: 1288
SQLSTATE: HY000
(ER_NON_UPDATABLE_TABLE
)
Message: The target table %s of the %s is not updatable
Error: 1289
SQLSTATE: HY000
(ER_FEATURE_DISABLED
)
Message: The '%s' feature is disabled; you need MySQL built with '%s' to have it working
Error: 1290
SQLSTATE: HY000
(ER_OPTION_PREVENTS_STATEMENT
)
Message: The MySQL server is running with the %s option so it cannot execute this statement
Error: 1291
SQLSTATE: HY000
(ER_DUPLICATED_VALUE_IN_TYPE
)
Message: Column '%s' has duplicated value '%s' in %s
Error: 1292
SQLSTATE: 22007
(ER_TRUNCATED_WRONG_VALUE
)
Message: Truncated incorrect %s value: '%s'
Error: 1294
SQLSTATE: HY000
(ER_INVALID_ON_UPDATE
)
Message: Invalid ON UPDATE clause for '%s' column
Error: 1295
SQLSTATE: HY000
(ER_UNSUPPORTED_PS
)
Message: This command is not supported in the prepared statement protocol yet
Error: 1296
SQLSTATE: HY000
(ER_GET_ERRMSG
)
Message: Got error %d '%s' from %s
Error: 1297
SQLSTATE: HY000
(ER_GET_TEMPORARY_ERRMSG
)
Message: Got temporary error %d '%s' from %s
Error: 1298
SQLSTATE: HY000
(ER_UNKNOWN_TIME_ZONE
)
Message: Unknown or incorrect time zone: '%s'
Error: 1299
SQLSTATE: HY000
(ER_WARN_INVALID_TIMESTAMP
)
Message: Invalid TIMESTAMP value in column '%s' at row %ld
Error: 1300
SQLSTATE: HY000
(ER_INVALID_CHARACTER_STRING
)
Message: Invalid %s character string: '%s'
Error: 1301
SQLSTATE: HY000
(ER_WARN_ALLOWED_PACKET_OVERFLOWED
)
Message: Result of %s() was larger than max_allowed_packet (%ld) - truncated
Error: 1302
SQLSTATE: HY000
(ER_CONFLICTING_DECLARATIONS
)
Message: Conflicting declarations: '%s%s' and '%s%s'
Error: 1303
SQLSTATE: 2F003
(ER_SP_NO_RECURSIVE_CREATE
)
Message: Can't create a %s from within another stored routine
Error: 1304
SQLSTATE: 42000
(ER_SP_ALREADY_EXISTS
)
Message: %s %s already exists
Error: 1305
SQLSTATE: 42000
(ER_SP_DOES_NOT_EXIST
)
Message: %s %s does not exist
Error: 1306
SQLSTATE: HY000
(ER_SP_DROP_FAILED
)
Message: Failed to DROP %s %s
Error: 1307
SQLSTATE: HY000
(ER_SP_STORE_FAILED
)
Message: Failed to CREATE %s %s
Error: 1308
SQLSTATE: 42000
(ER_SP_LILABEL_MISMATCH
)
Message: %s with no matching label: %s
Error: 1309
SQLSTATE: 42000
(ER_SP_LABEL_REDEFINE
)
Message: Redefining label %s
Error: 1310
SQLSTATE: 42000
(ER_SP_LABEL_MISMATCH
)
Message: End-label %s without match
Error: 1311
SQLSTATE: 01000
(ER_SP_UNINIT_VAR
)
Message: Referring to uninitialized variable %s
Error: 1312
SQLSTATE: 0A000
(ER_SP_BADSELECT
)
Message: PROCEDURE %s can't return a result set in the given context
Error: 1313
SQLSTATE: 42000
(ER_SP_BADRETURN
)
Message: RETURN is only allowed in a FUNCTION
Error: 1314
SQLSTATE: 0A000
(ER_SP_BADSTATEMENT
)
Message: %s is not allowed in stored procedures
Error: 1315
SQLSTATE: 42000
(ER_UPDATE_LOG_DEPRECATED_IGNORED
)
Message: The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.
Error: 1316
SQLSTATE: 42000
(ER_UPDATE_LOG_DEPRECATED_TRANSLATED
)
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: 1317
SQLSTATE: 70100
(ER_QUERY_INTERRUPTED
)
Message: Query execution was interrupted
Error: 1318
SQLSTATE: 42000
(ER_SP_WRONG_NO_OF_ARGS
)
Message: Incorrect number of arguments for %s %s; expected %u, got %u
Error: 1319
SQLSTATE: 42000
(ER_SP_COND_MISMATCH
)
Message: Undefined CONDITION: %s
Error: 1320
SQLSTATE: 42000
(ER_SP_NORETURN
)
Message: No RETURN found in FUNCTION %s
Error: 1321
SQLSTATE: 2F005
(ER_SP_NORETURNEND
)
Message: FUNCTION %s ended without RETURN
Error: 1322
SQLSTATE: 42000
(ER_SP_BAD_CURSOR_QUERY
)
Message: Cursor statement must be a SELECT
Error: 1323
SQLSTATE: 42000
(ER_SP_BAD_CURSOR_SELECT
)
Message: Cursor SELECT must not have INTO
Error: 1324
SQLSTATE: 42000
(ER_SP_CURSOR_MISMATCH
)
Message: Undefined CURSOR: %s
Error: 1325
SQLSTATE: 24000
(ER_SP_CURSOR_ALREADY_OPEN
)
Message: Cursor is already open
Error: 1326
SQLSTATE: 24000
(ER_SP_CURSOR_NOT_OPEN
)
Message: Cursor is not open
Error: 1327
SQLSTATE: 42000
(ER_SP_UNDECLARED_VAR
)
Message: Undeclared variable: %s
Error: 1328
SQLSTATE: HY000
(ER_SP_WRONG_NO_OF_FETCH_ARGS
)
Message: Incorrect number of FETCH variables
Error: 1329
SQLSTATE: 02000
(ER_SP_FETCH_NO_DATA
)
Message: No data - zero rows fetched, selected, or processed
Error: 1330
SQLSTATE: 42000
(ER_SP_DUP_PARAM
)
Message: Duplicate parameter: %s
Error: 1331
SQLSTATE: 42000
(ER_SP_DUP_VAR
)
Message: Duplicate variable: %s
Error: 1332
SQLSTATE: 42000
(ER_SP_DUP_COND
)
Message: Duplicate condition: %s
Error: 1333
SQLSTATE: 42000
(ER_SP_DUP_CURS
)
Message: Duplicate cursor: %s
Error: 1334
SQLSTATE: HY000
(ER_SP_CANT_ALTER
)
Message: Failed to ALTER %s %s
Error: 1335
SQLSTATE: 0A000
(ER_SP_SUBSELECT_NYI
)
Message: Subquery value not supported
Error: 1336
SQLSTATE: 0A000
(ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
)
Message: %s is not allowed in stored function or trigger
Error: 1337
SQLSTATE: 42000
(ER_SP_VARCOND_AFTER_CURSHNDLR
)
Message: Variable or condition declaration after cursor or handler declaration
Error: 1338
SQLSTATE: 42000
(ER_SP_CURSOR_AFTER_HANDLER
)
Message: Cursor declaration after handler declaration
Error: 1339
SQLSTATE: 20000
(ER_SP_CASE_NOT_FOUND
)
Message: Case not found for CASE statement
Error: 1340
SQLSTATE: HY000
(ER_FPARSER_TOO_BIG_FILE
)
Message: Configuration file '%s' is too big
Error: 1341
SQLSTATE: HY000
(ER_FPARSER_BAD_HEADER
)
Message: Malformed file type header in file '%s'
Error: 1342
SQLSTATE: HY000
(ER_FPARSER_EOF_IN_COMMENT
)
Message: Unexpected end of file while parsing comment '%s'
Error: 1343
SQLSTATE: HY000
(ER_FPARSER_ERROR_IN_PARAMETER
)
Message: Error while parsing parameter '%s' (line: '%s')
Error: 1344
SQLSTATE: HY000
(ER_FPARSER_EOF_IN_UNKNOWN_PARAMETER
)
Message: Unexpected end of file while skipping unknown parameter '%s'
Error: 1345
SQLSTATE: HY000
(ER_VIEW_NO_EXPLAIN
)
Message: EXPLAIN/SHOW can not be issued; lacking privileges for underlying table
Error: 1347
SQLSTATE: HY000
(ER_WRONG_OBJECT
)
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: 1348
SQLSTATE: HY000
(ER_NONUPDATEABLE_COLUMN
)
Message: Column '%s' is not updatable
Error: 1350
SQLSTATE: HY000
(ER_VIEW_SELECT_CLAUSE
)
Message: View's SELECT contains a '%s' clause
Error: 1351
SQLSTATE: HY000
(ER_VIEW_SELECT_VARIABLE
)
Message: View's SELECT contains a variable or parameter
Error: 1352
SQLSTATE: HY000
(ER_VIEW_SELECT_TMPTABLE
)
Message: View's SELECT refers to a temporary table '%s'
Error: 1353
SQLSTATE: HY000
(ER_VIEW_WRONG_LIST
)
Message: View's SELECT and view's field list have different column counts
Error: 1354
SQLSTATE: HY000
(ER_WARN_VIEW_MERGE
)
Message: View merge algorithm can't be used here for now (assumed undefined algorithm)
Error: 1355
SQLSTATE: HY000
(ER_WARN_VIEW_WITHOUT_KEY
)
Message: View being updated does not have complete key of underlying table in it
Error: 1356
SQLSTATE: HY000
(ER_VIEW_INVALID
)
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: 1357
SQLSTATE: HY000
(ER_SP_NO_DROP_SP
)
Message: Can't drop or alter a %s from within another stored routine
Error: 1359
SQLSTATE: HY000
(ER_TRG_ALREADY_EXISTS
)
Message: Trigger already exists
Error: 1360
SQLSTATE: HY000
(ER_TRG_DOES_NOT_EXIST
)
Message: Trigger does not exist
Error: 1361
SQLSTATE: HY000
(ER_TRG_ON_VIEW_OR_TEMP_TABLE
)
Message: Trigger's '%s' is view or temporary table
Error: 1362
SQLSTATE: HY000
(ER_TRG_CANT_CHANGE_ROW
)
Message: Updating of %s row is not allowed in %strigger
Error: 1363
SQLSTATE: HY000
(ER_TRG_NO_SUCH_ROW_IN_TRG
)
Message: There is no %s row in %s trigger
Error: 1364
SQLSTATE: HY000
(ER_NO_DEFAULT_FOR_FIELD
)
Message: Field '%s' doesn't have a default value
Error: 1365
SQLSTATE: 22012
(ER_DIVISION_BY_ZERO
)
Message: Division by 0
Error: 1366
SQLSTATE: HY000
(ER_TRUNCATED_WRONG_VALUE_FOR_FIELD
)
Message: Incorrect %s value: '%s' for column '%s' at row %ld
Error: 1367
SQLSTATE: 22007
(ER_ILLEGAL_VALUE_FOR_TYPE
)
Message: Illegal %s '%s' value found during parsing
Error: 1368
SQLSTATE: HY000
(ER_VIEW_NONUPD_CHECK
)
Message: CHECK OPTION on non-updatable view '%s.%s'
Error: 1369
SQLSTATE: HY000
(ER_VIEW_CHECK_FAILED
)
Message: CHECK OPTION failed '%s.%s'
Error: 1370
SQLSTATE: 42000
(ER_PROCACCESS_DENIED_ERROR
)
Message: %s command denied to user '%s'@'%s' for routine '%s'
Error: 1371
SQLSTATE: HY000
(ER_RELAY_LOG_FAIL
)
Message: Failed purging old relay logs: %s
Error: 1373
SQLSTATE: HY000
(ER_UNKNOWN_TARGET_BINLOG
)
Message: Target log not found in binlog index
Error: 1374
SQLSTATE: HY000
(ER_IO_ERR_LOG_INDEX_READ
)
Message: I/O error reading log index file
Error: 1375
SQLSTATE: HY000
(ER_BINLOG_PURGE_PROHIBITED
)
Message: Server configuration does not permit binlog purge
Error: 1376
SQLSTATE: HY000
(ER_FSEEK_FAIL
)
Message: Failed on fseek()
Error: 1377
SQLSTATE: HY000
(ER_BINLOG_PURGE_FATAL_ERR
)
Message: Fatal error during log purge
Error: 1378
SQLSTATE: HY000
(ER_LOG_IN_USE
)
Message: A purgeable log is in use, will not purge
Error: 1379
SQLSTATE: HY000
(ER_LOG_PURGE_UNKNOWN_ERR
)
Message: Unknown error during log purge
Error: 1380
SQLSTATE: HY000
(ER_RELAY_LOG_INIT
)
Message: Failed initializing relay log position: %s
Error: 1381
SQLSTATE: HY000
(ER_NO_BINARY_LOGGING
)
Message: You are not using binary logging
Error: 1382
SQLSTATE: HY000
(ER_RESERVED_SYNTAX
)
Message: The '%s' syntax is reserved for purposes internal to the MySQL server
Error: 1390
SQLSTATE: HY000
(ER_PS_MANY_PARAM
)
Message: Prepared statement contains too many placeholders
Error: 1391
SQLSTATE: HY000
(ER_KEY_PART_0
)
Message: Key part '%s' length cannot be 0
Error: 1392
SQLSTATE: HY000
(ER_VIEW_CHECKSUM
)
Message: View text checksum failed
Error: 1393
SQLSTATE: HY000
(ER_VIEW_MULTIUPDATE
)
Message: Can not modify more than one base table through a join view '%s.%s'
Error: 1394
SQLSTATE: HY000
(ER_VIEW_NO_INSERT_FIELD_LIST
)
Message: Can not insert into join view '%s.%s' without fields list
Error: 1395
SQLSTATE: HY000
(ER_VIEW_DELETE_MERGE_VIEW
)
Message: Can not delete from join view '%s.%s'
Error: 1396
SQLSTATE: HY000
(ER_CANNOT_USER
)
Message: Operation %s failed for %s
Error: 1397
SQLSTATE: XAE04
(ER_XAER_NOTA
)
Message: XAER_NOTA: Unknown XID
Error: 1398
SQLSTATE: XAE05
(ER_XAER_INVAL
)
Message: XAER_INVAL: Invalid arguments (or unsupported command)
Error: 1399
SQLSTATE: XAE07
(ER_XAER_RMFAIL
)
Message: XAER_RMFAIL: The command cannot be executed when global transaction is in the %s state
Error: 1400
SQLSTATE: XAE09
(ER_XAER_OUTSIDE
)
Message: XAER_OUTSIDE: Some work is done outside global transaction
Error: 1401
SQLSTATE: XAE03
(ER_XAER_RMERR
)
Message: XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency
Error: 1402
SQLSTATE: XA100
(ER_XA_RBROLLBACK
)
Message: XA_RBROLLBACK: Transaction branch was rolled back
Error: 1403
SQLSTATE: 42000
(ER_NONEXISTING_PROC_GRANT
)
Message: There is no such grant defined for user '%s' on host '%s' on routine '%s'
Error: 1404
SQLSTATE: HY000
(ER_PROC_AUTO_GRANT_FAIL
)
Message: Failed to grant EXECUTE and ALTER ROUTINE privileges
Error: 1405
SQLSTATE: HY000
(ER_PROC_AUTO_REVOKE_FAIL
)
Message: Failed to revoke all privileges to dropped routine
Error: 1406
SQLSTATE: 22001
(ER_DATA_TOO_LONG
)
Message: Data too long for column '%s' at row %ld
Error: 1407
SQLSTATE: 42000
(ER_SP_BAD_SQLSTATE
)
Message: Bad SQLSTATE: '%s'
Error: 1408
SQLSTATE: HY000
(ER_STARTUP
)
Message: %s: ready for connections. Version: '%s' socket: '%s' port: %d %s
Error: 1409
SQLSTATE: HY000
(ER_LOAD_FROM_FIXED_SIZE_ROWS_TO_VAR
)
Message: Can't load value from file with fixed size rows to variable
Error: 1410
SQLSTATE: 42000
(ER_CANT_CREATE_USER_WITH_GRANT
)
Message: You are not allowed to create a user with GRANT
Error: 1411
SQLSTATE: HY000
(ER_WRONG_VALUE_FOR_TYPE
)
Message: Incorrect %s value: '%s' for function %s
Error: 1412
SQLSTATE: HY000
(ER_TABLE_DEF_CHANGED
)
Message: Table definition has changed, please retry transaction
Error: 1413
SQLSTATE: 42000
(ER_SP_DUP_HANDLER
)
Message: Duplicate handler declared in the same block
Error: 1414
SQLSTATE: 42000
(ER_SP_NOT_VAR_ARG
)
Message: OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger
Error: 1415
SQLSTATE: 0A000
(ER_SP_NO_RETSET
)
Message: Not allowed to return a result set from a %s
Error: 1416
SQLSTATE: 22003
(ER_CANT_CREATE_GEOMETRY_OBJECT
)
Message: Cannot get geometry object from data you send to the GEOMETRY field
Error: 1418
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_ROUTINE
)
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: 1419
SQLSTATE: HY000
(ER_BINLOG_CREATE_ROUTINE_NEED_SUPER
)
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: 1421
SQLSTATE: HY000
(ER_STMT_HAS_NO_OPEN_CURSOR
)
Message: The statement (%lu) has no open cursor.
Error: 1422
SQLSTATE: HY000
(ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG
)
Message: Explicit or implicit commit is not allowed in stored function or trigger.
Error: 1423
SQLSTATE: HY000
(ER_NO_DEFAULT_FOR_VIEW_FIELD
)
Message: Field of view '%s.%s' underlying table doesn't have a default value
Error: 1424
SQLSTATE: HY000
(ER_SP_NO_RECURSION
)
Message: Recursive stored functions and triggers are not allowed.
Error: 1425
SQLSTATE: 42000
(ER_TOO_BIG_SCALE
)
Message: Too big scale %d specified for column '%s'. Maximum is %lu.
Error: 1426
SQLSTATE: 42000
(ER_TOO_BIG_PRECISION
)
Message: Too-big precision %d specified for '%s'. Maximum is %lu.
Error: 1427
SQLSTATE: 42000
(ER_M_BIGGER_THAN_D
)
Message: For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%s').
Error: 1428
SQLSTATE: HY000
(ER_WRONG_LOCK_OF_SYSTEM_TABLE
)
Message: You can't combine write-locking of system tables with other tables or lock types
Error: 1429
SQLSTATE: HY000
(ER_CONNECT_TO_FOREIGN_DATA_SOURCE
)
Message: Unable to connect to foreign data source: %s
Error: 1430
SQLSTATE: HY000
(ER_QUERY_ON_FOREIGN_DATA_SOURCE
)
Message: There was a problem processing the query on the foreign data source. Data source error: %s
Error: 1431
SQLSTATE: HY000
(ER_FOREIGN_DATA_SOURCE_DOESNT_EXIST
)
Message: The foreign data source you are trying to reference does not exist. Data source error: %s
Error: 1432
SQLSTATE: HY000
(ER_FOREIGN_DATA_STRING_INVALID_CANT_CREATE
)
Message: Can't create federated table. The data source connection string '%s' is not in the correct format
Error: 1433
SQLSTATE: HY000
(ER_FOREIGN_DATA_STRING_INVALID
)
Message: The data source connection string '%s' is not in the correct format
Error: 1435
SQLSTATE: HY000
(ER_TRG_IN_WRONG_SCHEMA
)
Message: Trigger in wrong schema
Error: 1436
SQLSTATE: HY000
(ER_STACK_OVERRUN_NEED_MORE
)
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: 1437
SQLSTATE: 42000
(ER_TOO_LONG_BODY
)
Message: Routine body for '%s' is too long
Error: 1438
SQLSTATE: HY000
(ER_WARN_CANT_DROP_DEFAULT_KEYCACHE
)
Message: Cannot drop default keycache
Error: 1439
SQLSTATE: 42000
(ER_TOO_BIG_DISPLAYWIDTH
)
Message: Display width out of range for column '%s' (max = %lu)
Error: 1440
SQLSTATE: XAE08
(ER_XAER_DUPID
)
Message: XAER_DUPID: The XID already exists
Error: 1441
SQLSTATE: 22008
(ER_DATETIME_FUNCTION_OVERFLOW
)
Message: Datetime function: %s field overflow
Error: 1442
SQLSTATE: HY000
(ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
)
Message: Can't update table '%s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.
Error: 1443
SQLSTATE: HY000
(ER_VIEW_PREVENT_UPDATE
)
Message: The definition of table '%s' prevents operation %s on table '%s'.
Error: 1444
SQLSTATE: HY000
(ER_PS_NO_RECURSION
)
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: 1445
SQLSTATE: HY000
(ER_SP_CANT_SET_AUTOCOMMIT
)
Message: Not allowed to set autocommit from a stored function or trigger
Error: 1447
SQLSTATE: HY000
(ER_VIEW_FRM_NO_USER
)
Message: View '%s'.'%s' has no definer information (old table format). Current user is used as definer. Please recreate the view!
Error: 1448
SQLSTATE: HY000
(ER_VIEW_OTHER_USER
)
Message: You need the SUPER privilege for creation view with '%s'@'%s' definer
Error: 1449
SQLSTATE: HY000
(ER_NO_SUCH_USER
)
Message: The user specified as a definer ('%s'@'%s') does not exist
Error: 1450
SQLSTATE: HY000
(ER_FORBID_SCHEMA_CHANGE
)
Message: Changing schema from '%s' to '%s' is not allowed.
Error: 1451
SQLSTATE: 23000
(ER_ROW_IS_REFERENCED_2
)
Message: Cannot delete or update a parent row: a foreign key constraint fails (%s)
Error: 1452
SQLSTATE: 23000
(ER_NO_REFERENCED_ROW_2
)
Message: Cannot add or update a child row: a foreign key constraint fails (%s)
Error: 1453
SQLSTATE: 42000
(ER_SP_BAD_VAR_SHADOW
)
Message: Variable '%s' must be quoted with `...`, or renamed
Error: 1454
SQLSTATE: HY000
(ER_TRG_NO_DEFINER
)
Message: No definer attribute for trigger '%s'.'%s'. It's disallowed to create trigger without definer.
Error: 1455
SQLSTATE: HY000
(ER_OLD_FILE_FORMAT
)
Message: '%s' has an old format, you should re-create the '%s' object(s)
Error: 1456
SQLSTATE: HY000
(ER_SP_RECURSION_LIMIT
)
Message: Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %s
Error: 1458
SQLSTATE: 42000
(ER_SP_WRONG_NAME
)
Message: Incorrect routine name '%s'
Error: 1459
SQLSTATE: HY000
(ER_TABLE_NEEDS_UPGRADE
)
Message: Table upgrade required. Please do "REPAIR TABLE `%s`" or dump/reload to fix it!
Error: 1460
SQLSTATE: 42000
(ER_SP_NO_AGGREGATE
)
Message: AGGREGATE is not supported for stored functions
Error: 1461
SQLSTATE: 42000
(ER_MAX_PREPARED_STMT_COUNT_REACHED
)
Message: Can't create more than max_prepared_stmt_count statements (current value: %lu)
Error: 1462
SQLSTATE: HY000
(ER_VIEW_RECURSIVE
)
Message: `%s`.`%s` contains view recursion
Error: 1463
SQLSTATE: 42000
(ER_NON_GROUPING_FIELD_USED
)
Message: Non-grouping field '%s' is used in %s clause
Error: 1464
SQLSTATE: HY000
(ER_TABLE_CANT_HANDLE_SPKEYS
)
Message: The used table type doesn't support SPATIAL indexes
Error: 1465
SQLSTATE: HY000
(ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA
)
Message: Triggers can not be created on system tables
Error: 1466
SQLSTATE: HY000
(ER_REMOVED_SPACES
)
Message: Leading spaces are removed from name '%s'
Error: 1467
SQLSTATE: HY000
(ER_AUTOINC_READ_FAILED
)
Message: Failed to read auto-increment value from storage engine
Error: 1468
SQLSTATE: HY000
(ER_USERNAME
)
Message: user name
Error: 1469
SQLSTATE: HY000
(ER_HOSTNAME
)
Message: host name
Error: 1470
SQLSTATE: HY000
(ER_WRONG_STRING_LENGTH
)
Message: String '%s' is too long for %s (should be no longer than %d)
Error: 1471
SQLSTATE: HY000
(ER_NON_INSERTABLE_TABLE
)
Message: The target table %s of the %s is not insertable-into
Error: 1472
SQLSTATE: HY000
(ER_ADMIN_WRONG_MRG_TABLE
)
Message: Table '%s' is differently defined or of non-MyISAM type or doesn't exist
Error: 1473
SQLSTATE: HY000
(ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT
)
Message: Too high level of nesting for select
Error: 1474
SQLSTATE: HY000
(ER_NAME_BECOMES_EMPTY
)
Message: Name '%s' has become ''
Error: 1475
SQLSTATE: HY000
(ER_AMBIGUOUS_FIELD_TERM
)
Message: First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY
Error: 1476
SQLSTATE: HY000
(ER_FOREIGN_SERVER_EXISTS
)
Message: The foreign server, %s, you are trying to create already exists.
Error: 1477
SQLSTATE: HY000
(ER_FOREIGN_SERVER_DOESNT_EXIST
)
Message: The foreign server name you are trying to reference does not exist. Data source error: %s
Error: 1478
SQLSTATE: HY000
(ER_ILLEGAL_HA_CREATE_OPTION
)
Message: Table storage engine '%s' does not support the create option '%s'
Error: 1479
SQLSTATE: HY000
(ER_PARTITION_REQUIRES_VALUES_ERROR
)
Message: Syntax error: %s PARTITIONING requires definition of VALUES %s for each partition
Error: 1480
SQLSTATE: HY000
(ER_PARTITION_WRONG_VALUES_ERROR
)
Message: Only %s PARTITIONING can use VALUES %s in partition definition
Error: 1481
SQLSTATE: HY000
(ER_PARTITION_MAXVALUE_ERROR
)
Message: MAXVALUE can only be used in last partition definition
Error: 1484
SQLSTATE: HY000
(ER_PARTITION_WRONG_NO_PART_ERROR
)
Message: Wrong number of partitions defined, mismatch with previous setting
Error: 1485
SQLSTATE: HY000
(ER_PARTITION_WRONG_NO_SUBPART_ERROR
)
Message: Wrong number of subpartitions defined, mismatch with previous setting
Error: 1486
SQLSTATE: HY000
(ER_WRONG_EXPR_IN_PARTITION_FUNC_ERROR
)
Message: Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed
Error: 1488
SQLSTATE: HY000
(ER_FIELD_NOT_FOUND_PART_ERROR
)
Message: Field in list of fields for partition function not found in table
Error: 1490
SQLSTATE: HY000
(ER_INCONSISTENT_PARTITION_INFO_ERROR
)
Message: The partition info in the frm file is not consistent with what can be written into the frm file
Error: 1491
SQLSTATE: HY000
(ER_PARTITION_FUNC_NOT_ALLOWED_ERROR
)
Message: The %s function returns the wrong type
Error: 1492
SQLSTATE: HY000
(ER_PARTITIONS_MUST_BE_DEFINED_ERROR
)
Message: For %s partitions each partition must be defined
Error: 1493
SQLSTATE: HY000
(ER_RANGE_NOT_INCREASING_ERROR
)
Message: VALUES LESS THAN value must be strictly increasing for each partition
Error: 1494
SQLSTATE: HY000
(ER_INCONSISTENT_TYPE_OF_FUNCTIONS_ERROR
)
Message: VALUES value must be of same type as partition function
Error: 1495
SQLSTATE: HY000
(ER_MULTIPLE_DEF_CONST_IN_LIST_PART_ERROR
)
Message: Multiple definition of same constant in list partitioning
Error: 1496
SQLSTATE: HY000
(ER_PARTITION_ENTRY_ERROR
)
Message: Partitioning can not be used stand-alone in query
Error: 1497
SQLSTATE: HY000
(ER_MIX_HANDLER_ERROR
)
Message: The mix of handlers in the partitions is not allowed in this version of MySQL
Error: 1498
SQLSTATE: HY000
(ER_PARTITION_NOT_DEFINED_ERROR
)
Message: For the partitioned engine it is necessary to define all %s
Error: 1499
SQLSTATE: HY000
(ER_TOO_MANY_PARTITIONS_ERROR
)
Message: Too many partitions (including subpartitions) were defined
Error: 1500
SQLSTATE: HY000
(ER_SUBPARTITION_ERROR
)
Message: It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning
Error: 1501
SQLSTATE: HY000
(ER_CANT_CREATE_HANDLER_FILE
)
Message: Failed to create specific handler file
Error: 1502
SQLSTATE: HY000
(ER_BLOB_FIELD_IN_PART_FUNC_ERROR
)
Message: A BLOB field is not allowed in partition function
Error: 1503
SQLSTATE: HY000
(ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF
)
Message: A %s must include all columns in the table's partitioning function
Error: 1504
SQLSTATE: HY000
(ER_NO_PARTS_ERROR
)
Message: Number of %s = 0 is not an allowed value
Error: 1505
SQLSTATE: HY000
(ER_PARTITION_MGMT_ON_NONPARTITIONED
)
Message: Partition management on a not partitioned table is not possible
Error: 1506
SQLSTATE: HY000
(ER_FOREIGN_KEY_ON_PARTITIONED
)
Message: Foreign keys are not yet supported in conjunction with partitioning
Error: 1507
SQLSTATE: HY000
(ER_DROP_PARTITION_NON_EXISTENT
)
Message: Error in list of partitions to %s
Error: 1508
SQLSTATE: HY000
(ER_DROP_LAST_PARTITION
)
Message: Cannot remove all partitions, use DROP TABLE instead
Error: 1509
SQLSTATE: HY000
(ER_COALESCE_ONLY_ON_HASH_PARTITION
)
Message: COALESCE PARTITION can only be used on HASH/KEY partitions
Error: 1510
SQLSTATE: HY000
(ER_REORG_HASH_ONLY_ON_SAME_NO
)
Message: REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers
Error: 1511
SQLSTATE: HY000
(ER_REORG_NO_PARAM_ERROR
)
Message: REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs
Error: 1512
SQLSTATE: HY000
(ER_ONLY_ON_RANGE_LIST_PARTITION
)
Message: %s PARTITION can only be used on RANGE/LIST partitions
Error: 1513
SQLSTATE: HY000
(ER_ADD_PARTITION_SUBPART_ERROR
)
Message: Trying to Add partition(s) with wrong number of subpartitions
Error: 1514
SQLSTATE: HY000
(ER_ADD_PARTITION_NO_NEW_PARTITION
)
Message: At least one partition must be added
Error: 1515
SQLSTATE: HY000
(ER_COALESCE_PARTITION_NO_PARTITION
)
Message: At least one partition must be coalesced
Error: 1516
SQLSTATE: HY000
(ER_REORG_PARTITION_NOT_EXIST
)
Message: More partitions to reorganize than there are partitions
Error: 1517
SQLSTATE: HY000
(ER_SAME_NAME_PARTITION
)
Message: Duplicate partition name %s
Error: 1518
SQLSTATE: HY000
(ER_NO_BINLOG_ERROR
)
Message: It is not allowed to shut off binlog on this command
Error: 1519
SQLSTATE: HY000
(ER_CONSECUTIVE_REORG_PARTITIONS
)
Message: When reorganizing a set of partitions they must be in consecutive order
Error: 1520
SQLSTATE: HY000
(ER_REORG_OUTSIDE_RANGE
)
Message: Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range
Error: 1521
SQLSTATE: HY000
(ER_PARTITION_FUNCTION_FAILURE
)
Message: Partition function not supported in this version for this handler
Error: 1523
SQLSTATE: HY000
(ER_LIMITED_PART_RANGE
)
Message: The %s handler only supports 32 bit integers in VALUES
Error: 1524
SQLSTATE: HY000
(ER_PLUGIN_IS_NOT_LOADED
)
Message: Plugin '%s' is not loaded
Error: 1525
SQLSTATE: HY000
(ER_WRONG_VALUE
)
Message: Incorrect %s value: '%s'
Error: 1526
SQLSTATE: HY000
(ER_NO_PARTITION_FOR_GIVEN_VALUE
)
Message: Table has no partition for value %s
Error: 1527
SQLSTATE: HY000
(ER_FILEGROUP_OPTION_ONLY_ONCE
)
Message: It is not allowed to specify %s more than once
Error: 1528
SQLSTATE: HY000
(ER_CREATE_FILEGROUP_FAILED
)
Message: Failed to create %s
Error: 1529
SQLSTATE: HY000
(ER_DROP_FILEGROUP_FAILED
)
Message: Failed to drop %s
Error: 1530
SQLSTATE: HY000
(ER_TABLESPACE_AUTO_EXTEND_ERROR
)
Message: The handler doesn't support autoextend of tablespaces
Error: 1531
SQLSTATE: HY000
(ER_WRONG_SIZE_NUMBER
)
Message: A size parameter was incorrectly specified, either number or on the form 10M
Error: 1532
SQLSTATE: HY000
(ER_SIZE_OVERFLOW_ERROR
)
Message: The size number was correct but we don't allow the digit part to be more than 2 billion
Error: 1533
SQLSTATE: HY000
(ER_ALTER_FILEGROUP_FAILED
)
Message: Failed to alter: %s
Error: 1534
SQLSTATE: HY000
(ER_BINLOG_ROW_LOGGING_FAILED
)
Message: Writing one row to the row-based binary log failed
Error: 1537
SQLSTATE: HY000
(ER_EVENT_ALREADY_EXISTS
)
Message: Event '%s' already exists
Error: 1539
SQLSTATE: HY000
(ER_EVENT_DOES_NOT_EXIST
)
Message: Unknown event '%s'
Error: 1542
SQLSTATE: HY000
(ER_EVENT_INTERVAL_NOT_POSITIVE_OR_TOO_BIG
)
Message: INTERVAL is either not positive or too big
Error: 1543
SQLSTATE: HY000
(ER_EVENT_ENDS_BEFORE_STARTS
)
Message: ENDS is either invalid or before STARTS
Error: 1544
SQLSTATE: HY000
(ER_EVENT_EXEC_TIME_IN_THE_PAST
)
Message: Event execution time is in the past. Event has been disabled
Error: 1551
SQLSTATE: HY000
(ER_EVENT_SAME_NAME
)
Message: Same old and new event name
Error: 1553
SQLSTATE: HY000
(ER_DROP_INDEX_FK
)
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: 1554
SQLSTATE: HY000
(ER_WARN_DEPRECATED_SYNTAX_WITH_VER
)
Message: The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead
Error: 1556
SQLSTATE: HY000
(ER_CANT_LOCK_LOG_TABLE
)
Message: You can't use locks with log tables.
Error: 1557
SQLSTATE: 23000
(ER_FOREIGN_DUPLICATE_KEY_OLD_UNUSED
)
Message: Upholding foreign key constraints for table '%s', entry '%s', key %d would lead to a duplicate entry
Error: 1558
SQLSTATE: HY000
(ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE
)
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.
Error: 1559
SQLSTATE: HY000
(ER_TEMP_TABLE_PREVENTS_SWITCH_OUT_OF_RBR
)
Message: Cannot switch out of the row-based binary log format when the session has open temporary tables
Error: 1560
SQLSTATE: HY000
(ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT
)
Message: Cannot change the binary logging format inside a stored function or trigger
Error: 1562
SQLSTATE: HY000
(ER_PARTITION_NO_TEMPORARY
)
Message: Cannot create temporary table with partitions
Error: 1563
SQLSTATE: HY000
(ER_PARTITION_CONST_DOMAIN_ERROR
)
Message: Partition constant is out of partition function domain
Error: 1564
SQLSTATE: HY000
(ER_PARTITION_FUNCTION_IS_NOT_ALLOWED
)
Message: This partition function is not allowed
Error: 1565
SQLSTATE: HY000
(ER_DDL_LOG_ERROR
)
Message: Error in DDL log
ER_DDL_LOG_ERROR
was removed after
8.0.1.
Error: 1566
SQLSTATE: HY000
(ER_NULL_IN_VALUES_LESS_THAN
)
Message: Not allowed to use NULL value in VALUES LESS THAN
Error: 1567
SQLSTATE: HY000
(ER_WRONG_PARTITION_NAME
)
Message: Incorrect partition name
Error: 1568
SQLSTATE: 25001
(ER_CANT_CHANGE_TX_CHARACTERISTICS
)
Message: Transaction characteristics can't be changed while a transaction is in progress
Error: 1569
SQLSTATE: HY000
(ER_DUP_ENTRY_AUTOINCREMENT_CASE
)
Message: ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%s' for key '%s'
Error: 1571
SQLSTATE: HY000
(ER_EVENT_SET_VAR_ERROR
)
Message: Error during starting/stopping of the scheduler. Error code %u
Error: 1572
SQLSTATE: HY000
(ER_PARTITION_MERGE_ERROR
)
Message: Engine cannot be used in partitioned tables
Error: 1575
SQLSTATE: HY000
(ER_BASE64_DECODE_ERROR
)
Message: Decoding of base64 string failed
Error: 1576
SQLSTATE: HY000
(ER_EVENT_RECURSION_FORBIDDEN
)
Message: Recursion of EVENT DDL statements is forbidden when body is present
Error: 1578
SQLSTATE: HY000
(ER_ONLY_INTEGERS_ALLOWED
)
Message: Only integers allowed as number here
Error: 1579
SQLSTATE: HY000
(ER_UNSUPORTED_LOG_ENGINE
)
Message: This storage engine cannot be used for log tables
Error: 1580
SQLSTATE: HY000
(ER_BAD_LOG_STATEMENT
)
Message: You cannot '%s' a log table if logging is enabled
Error: 1581
SQLSTATE: HY000
(ER_CANT_RENAME_LOG_TABLE
)
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: 1582
SQLSTATE: 42000
(ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT
)
Message: Incorrect parameter count in the call to native function '%s'
Error: 1583
SQLSTATE: 42000
(ER_WRONG_PARAMETERS_TO_NATIVE_FCT
)
Message: Incorrect parameters in the call to native function '%s'
Error: 1584
SQLSTATE: 42000
(ER_WRONG_PARAMETERS_TO_STORED_FCT
)
Message: Incorrect parameters in the call to stored function %s
Error: 1585
SQLSTATE: HY000
(ER_NATIVE_FCT_NAME_COLLISION
)
Message: This function '%s' has the same name as a native function
Error: 1586
SQLSTATE: 23000
(ER_DUP_ENTRY_WITH_KEY_NAME
)
Message: Duplicate entry '%s' for key '%s'
The format string for this error is also used with
ER_DUP_ENTRY
.
Error: 1587
SQLSTATE: HY000
(ER_BINLOG_PURGE_EMFILE
)
Message: Too many files opened, please execute the command again
Error: 1588
SQLSTATE: HY000
(ER_EVENT_CANNOT_CREATE_IN_THE_PAST
)
Message: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.
Error: 1589
SQLSTATE: HY000
(ER_EVENT_CANNOT_ALTER_IN_THE_PAST
)
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: 1590
SQLSTATE: HY000
(ER_SLAVE_INCIDENT
)
Message: The incident %s occured on the master. Message: %s
Error: 1591
SQLSTATE: HY000
(ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT
)
Message: Table has no partition for some existing values
Error: 1592
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_STATEMENT
)
Message: Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s
Error: 1593
SQLSTATE: HY000
(ER_SLAVE_FATAL_ERROR
)
Message: Fatal error: %s
Error: 1594
SQLSTATE: HY000
(ER_SLAVE_RELAY_LOG_READ_FAILURE
)
Message: Relay log read failure: %s
Error: 1595
SQLSTATE: HY000
(ER_SLAVE_RELAY_LOG_WRITE_FAILURE
)
Message: Relay log write failure: %s
Error: 1596
SQLSTATE: HY000
(ER_SLAVE_CREATE_EVENT_FAILURE
)
Message: Failed to create %s
Error: 1597
SQLSTATE: HY000
(ER_SLAVE_MASTER_COM_FAILURE
)
Message: Master command %s failed: %s
Error: 1598
SQLSTATE: HY000
(ER_BINLOG_LOGGING_IMPOSSIBLE
)
Message: Binary logging not possible. Message: %s
Error: 1599
SQLSTATE: HY000
(ER_VIEW_NO_CREATION_CTX
)
Message: View `%s`.`%s` has no creation context
Error: 1600
SQLSTATE: HY000
(ER_VIEW_INVALID_CREATION_CTX
)
Message: Creation context of view `%s`.`%s' is invalid
Error: 1602
SQLSTATE: HY000
(ER_TRG_CORRUPTED_FILE
)
Message: Corrupted TRG file for table `%s`.`%s`
Error: 1603
SQLSTATE: HY000
(ER_TRG_NO_CREATION_CTX
)
Message: Triggers for table `%s`.`%s` have no creation context
Error: 1604
SQLSTATE: HY000
(ER_TRG_INVALID_CREATION_CTX
)
Message: Trigger creation context of table `%s`.`%s` is invalid
Error: 1605
SQLSTATE: HY000
(ER_EVENT_INVALID_CREATION_CTX
)
Message: Creation context of event `%s`.`%s` is invalid
Error: 1606
SQLSTATE: HY000
(ER_TRG_CANT_OPEN_TABLE
)
Message: Cannot open table for trigger `%s`.`%s`
Error: 1609
SQLSTATE: HY000
(ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT
)
Message: The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.
Error: 1610
SQLSTATE: HY000
(ER_SLAVE_CORRUPT_EVENT
)
Message: Corrupted replication event was detected
Error: 1612
SQLSTATE: HY000
(ER_LOG_PURGE_NO_FILE
)
Message: Being purged log %s was not found
Error: 1613
SQLSTATE: XA106
(ER_XA_RBTIMEOUT
)
Message: XA_RBTIMEOUT: Transaction branch was rolled back: took too long
Error: 1614
SQLSTATE: XA102
(ER_XA_RBDEADLOCK
)
Message: XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected
Error: 1615
SQLSTATE: HY000
(ER_NEED_REPREPARE
)
Message: Prepared statement needs to be re-prepared
Error: 1617
SQLSTATE: HY000
(WARN_NO_MASTER_INFO
)
Message: The master info structure does not exist
Error: 1618
SQLSTATE: HY000
(WARN_OPTION_IGNORED
)
Message: <%s> option ignored
Error: 1619
SQLSTATE: HY000
(ER_PLUGIN_DELETE_BUILTIN
)
Message: Built-in plugins cannot be deleted
Error: 1620
SQLSTATE: HY000
(WARN_PLUGIN_BUSY
)
Message: Plugin is busy and will be uninstalled on shutdown
Error: 1621
SQLSTATE: HY000
(ER_VARIABLE_IS_READONLY
)
Message: %s variable '%s' is read-only. Use SET %s to assign the value
Error: 1622
SQLSTATE: HY000
(ER_WARN_ENGINE_TRANSACTION_ROLLBACK
)
Message: Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted
Error: 1623
SQLSTATE: HY000
(ER_SLAVE_HEARTBEAT_FAILURE
)
Message: Unexpected master's heartbeat data: %s
Error: 1624
SQLSTATE: HY000
(ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE
)
Message: The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).
Error: 1625
SQLSTATE: HY000
(ER_NDB_REPLICATION_SCHEMA_ERROR
)
Message: Bad schema for mysql.ndb_replication table. Message: %s
Error: 1626
SQLSTATE: HY000
(ER_CONFLICT_FN_PARSE_ERROR
)
Message: Error in parsing conflict function. Message: %s
Error: 1627
SQLSTATE: HY000
(ER_EXCEPTIONS_WRITE_ERROR
)
Message: Write to exceptions table failed. Message: %s
Error: 1628
SQLSTATE: HY000
(ER_TOO_LONG_TABLE_COMMENT
)
Message: Comment for table '%s' is too long (max = %lu)
Error: 1629
SQLSTATE: HY000
(ER_TOO_LONG_FIELD_COMMENT
)
Message: Comment for field '%s' is too long (max = %lu)
Error: 1630
SQLSTATE: 42000
(ER_FUNC_INEXISTENT_NAME_COLLISION
)
Message: FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual
Error: 1631
SQLSTATE: HY000
(ER_DATABASE_NAME
)
Message: Database
Error: 1632
SQLSTATE: HY000
(ER_TABLE_NAME
)
Message: Table
Error: 1633
SQLSTATE: HY000
(ER_PARTITION_NAME
)
Message: Partition
Error: 1634
SQLSTATE: HY000
(ER_SUBPARTITION_NAME
)
Message: Subpartition
Error: 1635
SQLSTATE: HY000
(ER_TEMPORARY_NAME
)
Message: Temporary
Error: 1636
SQLSTATE: HY000
(ER_RENAMED_NAME
)
Message: Renamed
Error: 1637
SQLSTATE: HY000
(ER_TOO_MANY_CONCURRENT_TRXS
)
Message: Too many active concurrent transactions
Error: 1638
SQLSTATE: HY000
(WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED
)
Message: Non-ASCII separator arguments are not fully supported
Error: 1639
SQLSTATE: HY000
(ER_DEBUG_SYNC_TIMEOUT
)
Message: debug sync point wait timed out
Error: 1640
SQLSTATE: HY000
(ER_DEBUG_SYNC_HIT_LIMIT
)
Message: debug sync point hit limit reached
Error: 1641
SQLSTATE: 42000
(ER_DUP_SIGNAL_SET
)
Message: Duplicate condition information item '%s'
Error: 1642
SQLSTATE: 01000
(ER_SIGNAL_WARN
)
Message: Unhandled user-defined warning condition
Error: 1643
SQLSTATE: 02000
(ER_SIGNAL_NOT_FOUND
)
Message: Unhandled user-defined not found condition
Error: 1644
SQLSTATE: HY000
(ER_SIGNAL_EXCEPTION
)
Message: Unhandled user-defined exception condition
Error: 1645
SQLSTATE: 0K000
(ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER
)
Message: RESIGNAL when handler not active
Error: 1646
SQLSTATE: HY000
(ER_SIGNAL_BAD_CONDITION_TYPE
)
Message: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE
Error: 1647
SQLSTATE: HY000
(WARN_COND_ITEM_TRUNCATED
)
Message: Data truncated for condition item '%s'
Error: 1648
SQLSTATE: HY000
(ER_COND_ITEM_TOO_LONG
)
Message: Data too long for condition item '%s'
Error: 1649
SQLSTATE: HY000
(ER_UNKNOWN_LOCALE
)
Message: Unknown locale: '%s'
Error: 1650
SQLSTATE: HY000
(ER_SLAVE_IGNORE_SERVER_IDS
)
Message: The requested server id %d clashes with the slave startup option --replicate-same-server-id
Error: 1651
SQLSTATE: HY000
(ER_QUERY_CACHE_DISABLED
)
Message: Query cache is disabled; restart the server with query_cache_type=1 to enable it
ER_QUERY_CACHE_DISABLED
was
removed after 8.0.2.
Error: 1652
SQLSTATE: HY000
(ER_SAME_NAME_PARTITION_FIELD
)
Message: Duplicate partition field name '%s'
Error: 1653
SQLSTATE: HY000
(ER_PARTITION_COLUMN_LIST_ERROR
)
Message: Inconsistency in usage of column lists for partitioning
Error: 1654
SQLSTATE: HY000
(ER_WRONG_TYPE_COLUMN_VALUE_ERROR
)
Message: Partition column values of incorrect type
Error: 1655
SQLSTATE: HY000
(ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR
)
Message: Too many fields in '%s'
Error: 1656
SQLSTATE: HY000
(ER_MAXVALUE_IN_VALUES_IN
)
Message: Cannot use MAXVALUE as value in VALUES IN
Error: 1657
SQLSTATE: HY000
(ER_TOO_MANY_VALUES_ERROR
)
Message: Cannot have more than one value for this type of %s partitioning
Error: 1658
SQLSTATE: HY000
(ER_ROW_SINGLE_PARTITION_FIELD_ERROR
)
Message: Row expressions in VALUES IN only allowed for multi-field column partitioning
Error: 1659
SQLSTATE: HY000
(ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD
)
Message: Field '%s' is of a not allowed type for this type of partitioning
Error: 1660
SQLSTATE: HY000
(ER_PARTITION_FIELDS_TOO_LONG
)
Message: The total length of the partitioning fields is too large
Error: 1661
SQLSTATE: HY000
(ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE
)
Message: Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.
Error: 1662
SQLSTATE: HY000
(ER_BINLOG_ROW_MODE_AND_STMT_ENGINE
)
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: 1663
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_AND_STMT_ENGINE
)
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: 1664
SQLSTATE: HY000
(ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE
)
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: 1665
SQLSTATE: HY000
(ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
)
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: 1666
SQLSTATE: HY000
(ER_BINLOG_ROW_INJECTION_AND_STMT_MODE
)
Message: Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.
Error: 1667
SQLSTATE: HY000
(ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE
)
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: 1668
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_LIMIT
)
Message: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.
Error: 1670
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_SYSTEM_TABLE
)
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.
Error: 1671
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_AUTOINC_COLUMNS
)
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: 1672
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_UDF
)
Message: Statement is unsafe because it uses a UDF which may not return the same value on the slave.
Error: 1673
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_SYSTEM_VARIABLE
)
Message: Statement is unsafe because it uses a system variable that may have a different value on the slave.
Error: 1674
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_SYSTEM_FUNCTION
)
Message: Statement is unsafe because it uses a system function that may return a different value on the slave.
Error: 1675
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS
)
Message: Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.
Error: 1676
SQLSTATE: HY000
(ER_MESSAGE_AND_STATEMENT
)
Message: %s Statement: %s
Error: 1677
SQLSTATE: HY000
(ER_SLAVE_CONVERSION_FAILED
)
Message: Column %d of table '%s.%s' cannot be converted from type '%s' to type '%s'
Error: 1678
SQLSTATE: HY000
(ER_SLAVE_CANT_CREATE_CONVERSION
)
Message: Can't create conversion table for table '%s.%s'
Error: 1679
SQLSTATE: HY000
(ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT
)
Message: Cannot modify @@session.binlog_format inside a transaction
Error: 1680
SQLSTATE: HY000
(ER_PATH_LENGTH
)
Message: The path specified for %s is too long.
Error: 1681
SQLSTATE: HY000
(ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT
)
Message: '%s' is deprecated and will be removed in a future release.
Error: 1682
SQLSTATE: HY000
(ER_WRONG_NATIVE_TABLE_STRUCTURE
)
Message: Native table '%s'.'%s' has the wrong structure
Error: 1683
SQLSTATE: HY000
(ER_WRONG_PERFSCHEMA_USAGE
)
Message: Invalid performance_schema usage.
Error: 1684
SQLSTATE: HY000
(ER_WARN_I_S_SKIPPED_TABLE
)
Message: Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement
Error: 1685
SQLSTATE: HY000
(ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT
)
Message: Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction
Error: 1686
SQLSTATE: HY000
(ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT
)
Message: Cannot change the binlog direct flag inside a stored function or trigger
Error: 1687
SQLSTATE: 42000
(ER_SPATIAL_MUST_HAVE_GEOM_COL
)
Message: A SPATIAL index may only contain a geometrical type column
Error: 1688
SQLSTATE: HY000
(ER_TOO_LONG_INDEX_COMMENT
)
Message: Comment for index '%s' is too long (max = %lu)
Error: 1689
SQLSTATE: HY000
(ER_LOCK_ABORTED
)
Message: Wait on a lock was aborted due to a pending exclusive lock
Error: 1690
SQLSTATE: 22003
(ER_DATA_OUT_OF_RANGE
)
Message: %s value is out of range in '%s'
Error: 1691
SQLSTATE: HY000
(ER_WRONG_SPVAR_TYPE_IN_LIMIT
)
Message: A variable of a non-integer based type in LIMIT clause
Error: 1692
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE
)
Message: Mixing self-logging and non-self-logging engines in a statement is unsafe.
Error: 1693
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_MIXED_STATEMENT
)
Message: Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.
Error: 1694
SQLSTATE: HY000
(ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN
)
Message: Cannot modify @@session.sql_log_bin inside a transaction
Error: 1695
SQLSTATE: HY000
(ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN
)
Message: Cannot change the sql_log_bin inside a stored function or trigger
Error: 1696
SQLSTATE: HY000
(ER_FAILED_READ_FROM_PAR_FILE
)
Message: Failed to read from the .par file
Error: 1697
SQLSTATE: HY000
(ER_VALUES_IS_NOT_INT_TYPE_ERROR
)
Message: VALUES value for partition '%s' must have type INT
Error: 1698
SQLSTATE: 28000
(ER_ACCESS_DENIED_NO_PASSWORD_ERROR
)
Message: Access denied for user '%s'@'%s'
Error: 1699
SQLSTATE: HY000
(ER_SET_PASSWORD_AUTH_PLUGIN
)
Message: SET PASSWORD has no significance for users authenticating via plugins
Error: 1701
SQLSTATE: 42000
(ER_TRUNCATE_ILLEGAL_FK
)
Message: Cannot truncate a table referenced in a foreign key constraint (%s)
Error: 1702
SQLSTATE: HY000
(ER_PLUGIN_IS_PERMANENT
)
Message: Plugin '%s' is force_plus_permanent and can not be unloaded
Error: 1703
SQLSTATE: HY000
(ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN
)
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: 1704
SQLSTATE: HY000
(ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX
)
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.
Error: 1705
SQLSTATE: HY000
(ER_STMT_CACHE_FULL
)
Message: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again
Error: 1706
SQLSTATE: HY000
(ER_MULTI_UPDATE_KEY_CONFLICT
)
Message: Primary key/partition key update is not allowed since the table is updated both as '%s' and '%s'.
Error: 1707
SQLSTATE: HY000
(ER_TABLE_NEEDS_REBUILD
)
Message: Table rebuild required. Please do "ALTER TABLE `%s` FORCE" or dump/reload to fix it!
Error: 1708
SQLSTATE: HY000
(WARN_OPTION_BELOW_LIMIT
)
Message: The value of '%s' should be no less than the value of '%s'
Error: 1709
SQLSTATE: HY000
(ER_INDEX_COLUMN_TOO_LONG
)
Message: Index column size too large. The maximum column size is %lu bytes.
Error: 1710
SQLSTATE: HY000
(ER_ERROR_IN_TRIGGER_BODY
)
Message: Trigger '%s' has an error in its body: '%s'
Error: 1711
SQLSTATE: HY000
(ER_ERROR_IN_UNKNOWN_TRIGGER_BODY
)
Message: Unknown trigger has an error in its body: '%s'
Error: 1712
SQLSTATE: HY000
(ER_INDEX_CORRUPT
)
Message: Index %s is corrupted
Error: 1713
SQLSTATE: HY000
(ER_UNDO_RECORD_TOO_BIG
)
Message: Undo log record is too big.
Error: 1714
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT
)
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.
Error: 1715
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE
)
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.
Error: 1716
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_REPLACE_SELECT
)
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.
Error: 1717
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT
)
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.
Error: 1718
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT
)
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.
Error: 1719
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_UPDATE_IGNORE
)
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.
Error: 1720
SQLSTATE: HY000
(ER_PLUGIN_NO_UNINSTALL
)
Message: Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.
Error: 1721
SQLSTATE: HY000
(ER_PLUGIN_NO_INSTALL
)
Message: Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.
Error: 1722
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT
)
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.
Error: 1723
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC
)
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.
Error: 1724
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_INSERT_TWO_KEYS
)
Message: INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe
Error: 1725
SQLSTATE: HY000
(ER_TABLE_IN_FK_CHECK
)
Message: Table is being used in foreign key check.
Error: 1726
SQLSTATE: HY000
(ER_UNSUPPORTED_ENGINE
)
Message: Storage engine '%s' does not support system tables. [%s.%s]
Error: 1727
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST
)
Message: INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.
Error: 1728
SQLSTATE: HY000
(ER_CANNOT_LOAD_FROM_TABLE_V2
)
Message: Cannot load from %s.%s. The table is probably corrupted
Error: 1729
SQLSTATE: HY000
(ER_MASTER_DELAY_VALUE_OUT_OF_RANGE
)
Message: The requested value %s for the master delay exceeds the maximum %u
Error: 1730
SQLSTATE: HY000
(ER_ONLY_FD_AND_RBR_EVENTS_ALLOWED_IN_BINLOG_STATEMENT
)
Message: Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)
Error: 1731
SQLSTATE: HY000
(ER_PARTITION_EXCHANGE_DIFFERENT_OPTION
)
Message: Non matching attribute '%s' between partition and table
Error: 1732
SQLSTATE: HY000
(ER_PARTITION_EXCHANGE_PART_TABLE
)
Message: Table to exchange with partition is partitioned: '%s'
Error: 1733
SQLSTATE: HY000
(ER_PARTITION_EXCHANGE_TEMP_TABLE
)
Message: Table to exchange with partition is temporary: '%s'
Error: 1734
SQLSTATE: HY000
(ER_PARTITION_INSTEAD_OF_SUBPARTITION
)
Message: Subpartitioned table, use subpartition instead of partition
Error: 1735
SQLSTATE: HY000
(ER_UNKNOWN_PARTITION
)
Message: Unknown partition '%s' in table '%s'
Error: 1736
SQLSTATE: HY000
(ER_TABLES_DIFFERENT_METADATA
)
Message: Tables have different definitions
Error: 1737
SQLSTATE: HY000
(ER_ROW_DOES_NOT_MATCH_PARTITION
)
Message: Found a row that does not match the partition
Error: 1738
SQLSTATE: HY000
(ER_BINLOG_CACHE_SIZE_GREATER_THAN_MAX
)
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: 1739
SQLSTATE: HY000
(ER_WARN_INDEX_NOT_APPLICABLE
)
Message: Cannot use %s access on index '%s' due to type or collation conversion on field '%s'
Error: 1740
SQLSTATE: HY000
(ER_PARTITION_EXCHANGE_FOREIGN_KEY
)
Message: Table to exchange with partition has foreign key references: '%s'
Error: 1742
SQLSTATE: HY000
(ER_RPL_INFO_DATA_TOO_LONG
)
Message: Data for column '%s' too long
Error: 1743
SQLSTATE: HY000
(ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE
)
Message: Replication event checksum verification failed while reading from network.
Error: 1745
SQLSTATE: HY000
(ER_BINLOG_STMT_CACHE_SIZE_GREATER_THAN_MAX
)
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: 1746
SQLSTATE: HY000
(ER_CANT_UPDATE_TABLE_IN_CREATE_TABLE_SELECT
)
Message: Can't update table '%s' while '%s' is being created.
Error: 1747
SQLSTATE: HY000
(ER_PARTITION_CLAUSE_ON_NONPARTITIONED
)
Message: PARTITION () clause on non partitioned table
Error: 1748
SQLSTATE: HY000
(ER_ROW_DOES_NOT_MATCH_GIVEN_PARTITION_SET
)
Message: Found a row not matching the given partition set
Error: 1750
SQLSTATE: HY000
(ER_CHANGE_RPL_INFO_REPOSITORY_FAILURE
)
Message: Failure while changing the type of replication repository: %s.
Error: 1751
SQLSTATE: HY000
(ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_CREATED_TEMP_TABLE
)
Message: The creation of some temporary tables could not be rolled back.
Error: 1752
SQLSTATE: HY000
(ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_DROPPED_TEMP_TABLE
)
Message: Some temporary tables were dropped, but these operations could not be rolled back.
Error: 1753
SQLSTATE: HY000
(ER_MTS_FEATURE_IS_NOT_SUPPORTED
)
Message: %s is not supported in multi-threaded slave mode. %s
Error: 1754
SQLSTATE: HY000
(ER_MTS_UPDATED_DBS_GREATER_MAX
)
Message: The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.
Error: 1755
SQLSTATE: HY000
(ER_MTS_CANT_PARALLEL
)
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: 1756
SQLSTATE: HY000
(ER_MTS_INCONSISTENT_DATA
)
Message: %s
Error: 1757
SQLSTATE: HY000
(ER_FULLTEXT_NOT_SUPPORTED_WITH_PARTITIONING
)
Message: FULLTEXT index is not supported for partitioned tables.
Error: 1758
SQLSTATE: 35000
(ER_DA_INVALID_CONDITION_NUMBER
)
Message: Invalid condition number
Error: 1759
SQLSTATE: HY000
(ER_INSECURE_PLAIN_TEXT
)
Message: Sending passwords in plain text without SSL/TLS is extremely insecure.
Error: 1760
SQLSTATE: HY000
(ER_INSECURE_CHANGE_MASTER
)
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.
Error: 1761
SQLSTATE: 23000
(ER_FOREIGN_DUPLICATE_KEY_WITH_CHILD_INFO
)
Message: Foreign key constraint for table '%s', record '%s' would lead to a duplicate entry in table '%s', key '%s'
Error: 1762
SQLSTATE: 23000
(ER_FOREIGN_DUPLICATE_KEY_WITHOUT_CHILD_INFO
)
Message: Foreign key constraint for table '%s', record '%s' would lead to a duplicate entry in a child table
Error: 1763
SQLSTATE: HY000
(ER_SQLTHREAD_WITH_SECURE_SLAVE
)
Message: Setting authentication options is not possible when only the Slave SQL Thread is being started.
Error: 1764
SQLSTATE: HY000
(ER_TABLE_HAS_NO_FT
)
Message: The table does not have FULLTEXT index to support this query
Error: 1765
SQLSTATE: HY000
(ER_VARIABLE_NOT_SETTABLE_IN_SF_OR_TRIGGER
)
Message: The system variable %s cannot be set in stored functions or triggers.
Error: 1766
SQLSTATE: HY000
(ER_VARIABLE_NOT_SETTABLE_IN_TRANSACTION
)
Message: The system variable %s cannot be set when there is an ongoing transaction.
Error: 1769
SQLSTATE: HY000
(ER_SET_STATEMENT_CANNOT_INVOKE_FUNCTION
)
Message: The statement 'SET %s' cannot invoke a stored function.
Error: 1770
SQLSTATE: HY000
(ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL
)
Message: The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.
Error: 1772
SQLSTATE: HY000
(ER_MALFORMED_GTID_SET_SPECIFICATION
)
Message: Malformed GTID set specification '%s'.
Error: 1773
SQLSTATE: HY000
(ER_MALFORMED_GTID_SET_ENCODING
)
Message: Malformed GTID set encoding.
Error: 1774
SQLSTATE: HY000
(ER_MALFORMED_GTID_SPECIFICATION
)
Message: Malformed GTID specification '%s'.
Error: 1775
SQLSTATE: HY000
(ER_GNO_EXHAUSTED
)
Message: Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid.
Error: 1776
SQLSTATE: HY000
(ER_BAD_SLAVE_AUTO_POSITION
)
Message: Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.
Error: 1777
SQLSTATE: HY000
(ER_AUTO_POSITION_REQUIRES_GTID_MODE_NOT_OFF
)
Message: CHANGE MASTER TO MASTER_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.
Error: 1778
SQLSTATE: HY000
(ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET
)
Message: Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.
Error: 1779
SQLSTATE: HY000
(ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON
)
Message: GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.
Error: 1781
SQLSTATE: HY000
(ER_CANT_SET_GTID_NEXT_TO_GTID_WHEN_GTID_MODE_IS_OFF
)
Message: @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.
Error: 1782
SQLSTATE: HY000
(ER_CANT_SET_GTID_NEXT_TO_ANONYMOUS_WHEN_GTID_MODE_IS_ON
)
Message: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.
Error: 1783
SQLSTATE: HY000
(ER_CANT_SET_GTID_NEXT_LIST_TO_NON_NULL_WHEN_GTID_MODE_IS_OFF
)
Message: @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.
Error: 1785
SQLSTATE: HY000
(ER_GTID_UNSAFE_NON_TRANSACTIONAL_TABLE
)
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: 1786
SQLSTATE: HY000
(ER_GTID_UNSAFE_CREATE_SELECT
)
Message: Statement violates GTID consistency: CREATE TABLE ... SELECT.
Error: 1787
SQLSTATE: HY000
(ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION
)
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.
Error: 1788
SQLSTATE: HY000
(ER_GTID_MODE_CAN_ONLY_CHANGE_ONE_STEP_AT_A_TIME
)
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: 1789
SQLSTATE: HY000
(ER_MASTER_HAS_PURGED_REQUIRED_GTIDS
)
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.
Error: 1790
SQLSTATE: HY000
(ER_CANT_SET_GTID_NEXT_WHEN_OWNING_GTID
)
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: 1791
SQLSTATE: HY000
(ER_UNKNOWN_EXPLAIN_FORMAT
)
Message: Unknown EXPLAIN format name: '%s'
Error: 1792
SQLSTATE: 25006
(ER_CANT_EXECUTE_IN_READ_ONLY_TRANSACTION
)
Message: Cannot execute statement in a READ ONLY transaction.
Error: 1793
SQLSTATE: HY000
(ER_TOO_LONG_TABLE_PARTITION_COMMENT
)
Message: Comment for table partition '%s' is too long (max = %lu)
Error: 1794
SQLSTATE: HY000
(ER_SLAVE_CONFIGURATION
)
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.
Error: 1795
SQLSTATE: HY000
(ER_INNODB_FT_LIMIT
)
Message: InnoDB presently supports one FULLTEXT index creation at a time
Error: 1796
SQLSTATE: HY000
(ER_INNODB_NO_FT_TEMP_TABLE
)
Message: Cannot create FULLTEXT index on temporary InnoDB table
Error: 1797
SQLSTATE: HY000
(ER_INNODB_FT_WRONG_DOCID_COLUMN
)
Message: Column '%s' is of wrong type for an InnoDB FULLTEXT index
Error: 1798
SQLSTATE: HY000
(ER_INNODB_FT_WRONG_DOCID_INDEX
)
Message: Index '%s' is of wrong type for an InnoDB FULLTEXT index
Error: 1799
SQLSTATE: HY000
(ER_INNODB_ONLINE_LOG_TOO_BIG
)
Message: Creating index '%s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.
Error: 1800
SQLSTATE: HY000
(ER_UNKNOWN_ALTER_ALGORITHM
)
Message: Unknown ALGORITHM '%s'
Error: 1801
SQLSTATE: HY000
(ER_UNKNOWN_ALTER_LOCK
)
Message: Unknown LOCK type '%s'
Error: 1802
SQLSTATE: HY000
(ER_MTS_CHANGE_MASTER_CANT_RUN_WITH_GAPS
)
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.
Error: 1803
SQLSTATE: HY000
(ER_MTS_RECOVERY_FAILURE
)
Message: Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.
Error: 1804
SQLSTATE: HY000
(ER_MTS_RESET_WORKERS
)
Message: Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.
Error: 1805
SQLSTATE: HY000
(ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2
)
Message: Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted
Error: 1806
SQLSTATE: HY000
(ER_SLAVE_SILENT_RETRY_TRANSACTION
)
Message: Slave must silently retry current transaction
Error: 1807
SQLSTATE: HY000
(ER_DISCARD_FK_CHECKS_RUNNING
)
Message: There is a foreign key check running on table '%s'. Cannot discard the table.
Error: 1808
SQLSTATE: HY000
(ER_TABLE_SCHEMA_MISMATCH
)
Message: Schema mismatch (%s)
Error: 1809
SQLSTATE: HY000
(ER_TABLE_IN_SYSTEM_TABLESPACE
)
Message: Table '%s' in system tablespace
Error: 1810
SQLSTATE: HY000
(ER_IO_READ_ERROR
)
Message: IO Read error: (%lu, %s) %s
Error: 1811
SQLSTATE: HY000
(ER_IO_WRITE_ERROR
)
Message: IO Write error: (%lu, %s) %s
Error: 1812
SQLSTATE: HY000
(ER_TABLESPACE_MISSING
)
Message: Tablespace is missing for table %s.
Error: 1813
SQLSTATE: HY000
(ER_TABLESPACE_EXISTS
)
Message: Tablespace '%s' exists.
Error: 1814
SQLSTATE: HY000
(ER_TABLESPACE_DISCARDED
)
Message: Tablespace has been discarded for table '%s'
Error: 1815
SQLSTATE: HY000
(ER_INTERNAL_ERROR
)
Message: Internal error: %s
Error: 1816
SQLSTATE: HY000
(ER_INNODB_IMPORT_ERROR
)
Message: ALTER TABLE %s IMPORT TABLESPACE failed with error %lu : '%s'
Error: 1817
SQLSTATE: HY000
(ER_INNODB_INDEX_CORRUPT
)
Message: Index corrupt: %s
Error: 1818
SQLSTATE: HY000
(ER_INVALID_YEAR_COLUMN_LENGTH
)
Message: Supports only YEAR or YEAR(4) column.
Error: 1819
SQLSTATE: HY000
(ER_NOT_VALID_PASSWORD
)
Message: Your password does not satisfy the current policy requirements
Error: 1820
SQLSTATE: HY000
(ER_MUST_CHANGE_PASSWORD
)
Message: You must reset your password using ALTER USER statement before executing this statement.
Error: 1821
SQLSTATE: HY000
(ER_FK_NO_INDEX_CHILD
)
Message: Failed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s'
Error: 1822
SQLSTATE: HY000
(ER_FK_NO_INDEX_PARENT
)
Message: Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s'
Error: 1823
SQLSTATE: HY000
(ER_FK_FAIL_ADD_SYSTEM
)
Message: Failed to add the foreign key constraint '%s' to system tables
Error: 1824
SQLSTATE: HY000
(ER_FK_CANNOT_OPEN_PARENT
)
Message: Failed to open the referenced table '%s'
Error: 1825
SQLSTATE: HY000
(ER_FK_INCORRECT_OPTION
)
Message: Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'
Error: 1826
SQLSTATE: HY000
(ER_FK_DUP_NAME
)
Message: Duplicate foreign key constraint name '%s'
Error: 1827
SQLSTATE: HY000
(ER_PASSWORD_FORMAT
)
Message: The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function.
Error: 1828
SQLSTATE: HY000
(ER_FK_COLUMN_CANNOT_DROP
)
Message: Cannot drop column '%s': needed in a foreign key constraint '%s'
Error: 1829
SQLSTATE: HY000
(ER_FK_COLUMN_CANNOT_DROP_CHILD
)
Message: Cannot drop column '%s': needed in a foreign key constraint '%s' of table '%s'
Error: 1830
SQLSTATE: HY000
(ER_FK_COLUMN_NOT_NULL
)
Message: Column '%s' cannot be NOT NULL: needed in a foreign key constraint '%s' SET NULL
Error: 1831
SQLSTATE: HY000
(ER_DUP_INDEX
)
Message: Duplicate index '%s' defined on the table '%s.%s'. This is deprecated and will be disallowed in a future release.
Error: 1832
SQLSTATE: HY000
(ER_FK_COLUMN_CANNOT_CHANGE
)
Message: Cannot change column '%s': used in a foreign key constraint '%s'
Error: 1833
SQLSTATE: HY000
(ER_FK_COLUMN_CANNOT_CHANGE_CHILD
)
Message: Cannot change column '%s': used in a foreign key constraint '%s' of table '%s'
Error: 1835
SQLSTATE: HY000
(ER_MALFORMED_PACKET
)
Message: Malformed communication packet.
Error: 1836
SQLSTATE: HY000
(ER_READ_ONLY_MODE
)
Message: Running in read-only mode
Error: 1837
SQLSTATE: HY000
(ER_GTID_NEXT_TYPE_UNDEFINED_GROUP
)
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: 1838
SQLSTATE: HY000
(ER_VARIABLE_NOT_SETTABLE_IN_SP
)
Message: The system variable %s cannot be set in stored procedures.
Error: 1840
SQLSTATE: HY000
(ER_CANT_SET_GTID_PURGED_WHEN_GTID_EXECUTED_IS_NOT_EMPTY
)
Message: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.
Error: 1841
SQLSTATE: HY000
(ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY
)
Message: @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).
Error: 1842
SQLSTATE: HY000
(ER_GTID_PURGED_WAS_CHANGED
)
Message: @@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.
Error: 1843
SQLSTATE: HY000
(ER_GTID_EXECUTED_WAS_CHANGED
)
Message: @@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.
Error: 1844
SQLSTATE: HY000
(ER_BINLOG_STMT_MODE_AND_NO_REPL_TABLES
)
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: 1845
SQLSTATE: 0A000
(ER_ALTER_OPERATION_NOT_SUPPORTED
)
Message: %s is not supported for this operation. Try %s.
Error: 1846
SQLSTATE: 0A000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON
)
Message: %s is not supported. Reason: %s. Try %s.
Error: 1847
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY
)
Message: COPY algorithm requires a lock
Error: 1848
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION
)
Message: Partition specific operations do not yet support LOCK/ALGORITHM
Error: 1849
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME
)
Message: Columns participating in a foreign key are renamed
Error: 1850
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE
)
Message: Cannot change column type INPLACE
Error: 1851
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK
)
Message: Adding foreign keys needs foreign_key_checks=OFF
Error: 1853
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK
)
Message: Dropping a primary key is not allowed without also adding a new primary key
Error: 1854
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC
)
Message: Adding an auto-increment column requires a lock
Error: 1855
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS
)
Message: Cannot replace hidden FTS_DOC_ID with a user-visible one
Error: 1856
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS
)
Message: Cannot drop or rename FTS_DOC_ID
Error: 1857
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FTS
)
Message: Fulltext index creation requires a lock
Error: 1858
SQLSTATE: HY000
(ER_SQL_SLAVE_SKIP_COUNTER_NOT_SETTABLE_IN_GTID_MODE
)
Message: sql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transaction
Error: 1859
SQLSTATE: 23000
(ER_DUP_UNKNOWN_IN_INDEX
)
Message: Duplicate entry for key '%s'
Error: 1860
SQLSTATE: HY000
(ER_IDENT_CAUSES_TOO_LONG_PATH
)
Message: Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.
Error: 1861
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL
)
Message: cannot silently convert NULL values, as required in this SQL_MODE
Error: 1862
SQLSTATE: HY000
(ER_MUST_CHANGE_PASSWORD_LOGIN
)
Message: Your password has expired. To log in you must change it using a client that supports expired passwords.
Error: 1863
SQLSTATE: HY000
(ER_ROW_IN_WRONG_PARTITION
)
Message: Found a row in wrong partition %s
Error: 1864
SQLSTATE: HY000
(ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX
)
Message: Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max.
Error: 1866
SQLSTATE: HY000
(ER_BINLOG_LOGICAL_CORRUPTION
)
Message: The binary log file '%s' is logically corrupted: %s
Error: 1867
SQLSTATE: HY000
(ER_WARN_PURGE_LOG_IN_USE
)
Message: file %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.
Error: 1868
SQLSTATE: HY000
(ER_WARN_PURGE_LOG_IS_ACTIVE
)
Message: file %s was not purged because it is the active log file.
Error: 1869
SQLSTATE: HY000
(ER_AUTO_INCREMENT_CONFLICT
)
Message: Auto-increment value in UPDATE conflicts with internally generated values
Error: 1870
SQLSTATE: HY000
(WARN_ON_BLOCKHOLE_IN_RBR
)
Message: Row events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%s'
Error: 1871
SQLSTATE: HY000
(ER_SLAVE_MI_INIT_REPOSITORY
)
Message: Slave failed to initialize master info structure from the repository
Error: 1872
SQLSTATE: HY000
(ER_SLAVE_RLI_INIT_REPOSITORY
)
Message: Slave failed to initialize relay log info structure from the repository
Error: 1873
SQLSTATE: 28000
(ER_ACCESS_DENIED_CHANGE_USER_ERROR
)
Message: Access denied trying to change to user '%s'@'%s' (using password: %s). Disconnecting.
Error: 1874
SQLSTATE: HY000
(ER_INNODB_READ_ONLY
)
Message: InnoDB is in read only mode.
Error: 1875
SQLSTATE: HY000
(ER_STOP_SLAVE_SQL_THREAD_TIMEOUT
)
Message: STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.
Error: 1876
SQLSTATE: HY000
(ER_STOP_SLAVE_IO_THREAD_TIMEOUT
)
Message: STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.
Error: 1877
SQLSTATE: HY000
(ER_TABLE_CORRUPT
)
Message: Operation cannot be performed. The table '%s.%s' is missing, corrupt or contains bad data.
Error: 1878
SQLSTATE: HY000
(ER_TEMP_FILE_WRITE_FAILURE
)
Message: Temporary file write failure.
Error: 1879
SQLSTATE: HY000
(ER_INNODB_FT_AUX_NOT_HEX_ID
)
Message: Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.
Error: 1880
SQLSTATE: HY000
(ER_OLD_TEMPORALS_UPGRADED
)
Message: TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.
Error: 1881
SQLSTATE: HY000
(ER_INNODB_FORCED_RECOVERY
)
Message: Operation not allowed when innodb_forced_recovery > 0.
Error: 1882
SQLSTATE: HY000
(ER_AES_INVALID_IV
)
Message: The initialization vector supplied to %s is too short. Must be at least %d bytes long
Error: 1883
SQLSTATE: HY000
(ER_PLUGIN_CANNOT_BE_UNINSTALLED
)
Message: Plugin '%s' cannot be uninstalled now. %s
Error: 1884
SQLSTATE: HY000
(ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_GTID_GROUP
)
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: 1885
SQLSTATE: HY000
(ER_SLAVE_HAS_MORE_GTIDS_THAN_MASTER
)
Message: Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master but are not included in GTID_EXECUTED.
Error: 3000
SQLSTATE: HY000
(ER_FILE_CORRUPT
)
Message: File %s is corrupted
Error: 3001
SQLSTATE: HY000
(ER_ERROR_ON_MASTER
)
Message: Query partially completed on the master (error on master: %d) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;. Query:'%s'
Error: 3002
SQLSTATE: HY000
(ER_INCONSISTENT_ERROR
)
Message: Query caused different errors on master and slave. Error on master: message (format)='%s' error code=%d; Error on slave:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'
Error: 3003
SQLSTATE: HY000
(ER_STORAGE_ENGINE_NOT_LOADED
)
Message: Storage engine for table '%s'.'%s' is not loaded.
Error: 3004
SQLSTATE: 0Z002
(ER_GET_STACKED_DA_WITHOUT_ACTIVE_HANDLER
)
Message: GET STACKED DIAGNOSTICS when handler not active
Error: 3005
SQLSTATE: HY000
(ER_WARN_LEGACY_SYNTAX_CONVERTED
)
Message: %s is no longer supported. The statement was converted to %s.
Error: 3006
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN
)
Message: Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the slave.
Error: 3007
SQLSTATE: HY000
(ER_CANNOT_DISCARD_TEMPORARY_TABLE
)
Message: Cannot DISCARD/IMPORT tablespace associated with temporary table
Error: 3008
SQLSTATE: HY000
(ER_FK_DEPTH_EXCEEDED
)
Message: Foreign key cascade delete/update exceeds max depth of %d.
Error: 3009
SQLSTATE: HY000
(ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2
)
Message: Column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.
Error: 3010
SQLSTATE: HY000
(ER_WARN_TRIGGER_DOESNT_HAVE_CREATED
)
Message: Trigger %s.%s.%s does not have CREATED attribute.
Error: 3011
SQLSTATE: HY000
(ER_REFERENCED_TRG_DOES_NOT_EXIST
)
Message: Referenced trigger '%s' for the given action time and event type does not exist.
Error: 3012
SQLSTATE: HY000
(ER_EXPLAIN_NOT_SUPPORTED
)
Message: EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE
Error: 3013
SQLSTATE: HY000
(ER_INVALID_FIELD_SIZE
)
Message: Invalid size for column '%s'.
Error: 3014
SQLSTATE: HY000
(ER_MISSING_HA_CREATE_OPTION
)
Message: Table storage engine '%s' found required create option missing
Error: 3015
SQLSTATE: HY000
(ER_ENGINE_OUT_OF_MEMORY
)
Message: Out of memory in storage engine '%s'.
Error: 3016
SQLSTATE: HY000
(ER_PASSWORD_EXPIRE_ANONYMOUS_USER
)
Message: The password for anonymous user cannot be expired.
Error: 3017
SQLSTATE: HY000
(ER_SLAVE_SQL_THREAD_MUST_STOP
)
Message: This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD first
Error: 3018
SQLSTATE: HY000
(ER_NO_FT_MATERIALIZED_SUBQUERY
)
Message: Cannot create FULLTEXT index on materialized subquery
Error: 3019
SQLSTATE: HY000
(ER_INNODB_UNDO_LOG_FULL
)
Message: Undo Log error: %s
Error: 3020
SQLSTATE: 2201E
(ER_INVALID_ARGUMENT_FOR_LOGARITHM
)
Message: Invalid argument for logarithm
Error: 3021
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_IO_THREAD_MUST_STOP
)
Message: This operation cannot be performed with a running slave io thread; run STOP SLAVE IO_THREAD FOR CHANNEL '%s' first.
Error: 3022
SQLSTATE: HY000
(ER_WARN_OPEN_TEMP_TABLES_MUST_BE_ZERO
)
Message: This operation may not be safe when the slave 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 slave_open_temp_tables = 0.
Error: 3023
SQLSTATE: HY000
(ER_WARN_ONLY_MASTER_LOG_FILE_NO_POS
)
Message: CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.
Error: 3024
SQLSTATE: HY000
(ER_QUERY_TIMEOUT
)
Message: Query execution was interrupted, maximum statement execution time exceeded
Error: 3025
SQLSTATE: HY000
(ER_NON_RO_SELECT_DISABLE_TIMER
)
Message: Select is not a read only statement, disabling timer
Error: 3026
SQLSTATE: HY000
(ER_DUP_LIST_ENTRY
)
Message: Duplicate entry '%s'.
Error: 3028
SQLSTATE: HY000
(ER_AGGREGATE_ORDER_FOR_UNION
)
Message: Expression #%u of ORDER BY contains aggregate function and applies to a UNION
Error: 3029
SQLSTATE: HY000
(ER_AGGREGATE_ORDER_NON_AGG_QUERY
)
Message: Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query
Error: 3030
SQLSTATE: HY000
(ER_SLAVE_WORKER_STOPPED_PREVIOUS_THD_ERROR
)
Message: Slave worker has stopped after at least one previous worker encountered an error when slave-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the slave after fixing any failed threads, you should fix this worker as well.
Error: 3031
SQLSTATE: HY000
(ER_DONT_SUPPORT_SLAVE_PRESERVE_COMMIT_ORDER
)
Message: slave_preserve_commit_order is not supported %s.
Error: 3032
SQLSTATE: HY000
(ER_SERVER_OFFLINE_MODE
)
Message: The server is currently in offline mode
Error: 3033
SQLSTATE: HY000
(ER_GIS_DIFFERENT_SRIDS
)
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: 3034
SQLSTATE: HY000
(ER_GIS_UNSUPPORTED_ARGUMENT
)
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: 3035
SQLSTATE: HY000
(ER_GIS_UNKNOWN_ERROR
)
Message: Unknown GIS error occured in function %s.
Error: 3036
SQLSTATE: HY000
(ER_GIS_UNKNOWN_EXCEPTION
)
Message: Unknown exception caught in GIS function %s.
Error: 3037
SQLSTATE: 22023
(ER_GIS_INVALID_DATA
)
Message: Invalid GIS data provided to function %s.
A spatial function was called with an argument not recognized as a valid geometry value.
Error: 3038
SQLSTATE: HY000
(ER_BOOST_GEOMETRY_EMPTY_INPUT_EXCEPTION
)
Message: The geometry has no data in function %s.
Error: 3039
SQLSTATE: HY000
(ER_BOOST_GEOMETRY_CENTROID_EXCEPTION
)
Message: Unable to calculate centroid because geometry is empty in function %s.
Error: 3040
SQLSTATE: HY000
(ER_BOOST_GEOMETRY_OVERLAY_INVALID_INPUT_EXCEPTION
)
Message: Geometry overlay calculation error: geometry data is invalid in function %s.
Error: 3041
SQLSTATE: HY000
(ER_BOOST_GEOMETRY_TURN_INFO_EXCEPTION
)
Message: Geometry turn info calculation error: geometry data is invalid in function %s.
Error: 3042
SQLSTATE: HY000
(ER_BOOST_GEOMETRY_SELF_INTERSECTION_POINT_EXCEPTION
)
Message: Analysis procedures of intersection points interrupted unexpectedly in function %s.
Error: 3043
SQLSTATE: HY000
(ER_BOOST_GEOMETRY_UNKNOWN_EXCEPTION
)
Message: Unknown exception thrown in function %s.
Error: 3044
SQLSTATE: HY000
(ER_STD_BAD_ALLOC_ERROR
)
Message: Memory allocation error: %s in function %s.
Error: 3045
SQLSTATE: HY000
(ER_STD_DOMAIN_ERROR
)
Message: Domain error: %s in function %s.
Error: 3046
SQLSTATE: HY000
(ER_STD_LENGTH_ERROR
)
Message: Length error: %s in function %s.
Error: 3047
SQLSTATE: HY000
(ER_STD_INVALID_ARGUMENT
)
Message: Invalid argument error: %s in function %s.
Error: 3048
SQLSTATE: HY000
(ER_STD_OUT_OF_RANGE_ERROR
)
Message: Out of range error: %s in function %s.
Error: 3049
SQLSTATE: HY000
(ER_STD_OVERFLOW_ERROR
)
Message: Overflow error error: %s in function %s.
Error: 3050
SQLSTATE: HY000
(ER_STD_RANGE_ERROR
)
Message: Range error: %s in function %s.
Error: 3051
SQLSTATE: HY000
(ER_STD_UNDERFLOW_ERROR
)
Message: Underflow error: %s in function %s.
Error: 3052
SQLSTATE: HY000
(ER_STD_LOGIC_ERROR
)
Message: Logic error: %s in function %s.
Error: 3053
SQLSTATE: HY000
(ER_STD_RUNTIME_ERROR
)
Message: Runtime error: %s in function %s.
Error: 3054
SQLSTATE: HY000
(ER_STD_UNKNOWN_EXCEPTION
)
Message: Unknown exception: %s in function %s.
Error: 3055
SQLSTATE: HY000
(ER_GIS_DATA_WRONG_ENDIANESS
)
Message: Geometry byte string must be little endian.
Error: 3056
SQLSTATE: HY000
(ER_CHANGE_MASTER_PASSWORD_LENGTH
)
Message: The password provided for the replication user exceeds the maximum length of 32 characters
Error: 3057
SQLSTATE: 42000
(ER_USER_LOCK_WRONG_NAME
)
Message: Incorrect user-level lock name '%s'.
Error: 3058
SQLSTATE: HY000
(ER_USER_LOCK_DEADLOCK
)
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: 3059
SQLSTATE: HY000
(ER_REPLACE_INACCESSIBLE_ROWS
)
Message: REPLACE cannot be executed as it requires deleting rows that are not in the view
Error: 3060
SQLSTATE: HY000
(ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_GIS
)
Message: Do not support online operation on table with GIS index
Error: 3061
SQLSTATE: 42000
(ER_ILLEGAL_USER_VAR
)
Message: User variable name '%s' is illegal
Error: 3062
SQLSTATE: HY000
(ER_GTID_MODE_OFF
)
Message: Cannot %s when GTID_MODE = OFF.
Error: 3064
SQLSTATE: HY000
(ER_INCORRECT_TYPE
)
Message: Incorrect type for argument %s in function %s.
Error: 3065
SQLSTATE: HY000
(ER_FIELD_IN_ORDER_NOT_SELECT
)
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: 3066
SQLSTATE: HY000
(ER_AGGREGATE_IN_ORDER_NOT_SELECT
)
Message: Expression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %s
Error: 3067
SQLSTATE: HY000
(ER_INVALID_RPL_WILD_TABLE_FILTER_PATTERN
)
Message: Supplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'
Error: 3068
SQLSTATE: 08S01
(ER_NET_OK_PACKET_TOO_LARGE
)
Message: OK packet too large
Error: 3069
SQLSTATE: HY000
(ER_INVALID_JSON_DATA
)
Message: Invalid JSON data provided to function %s: %s
Error: 3070
SQLSTATE: HY000
(ER_INVALID_GEOJSON_MISSING_MEMBER
)
Message: Invalid GeoJSON data provided to function %s: Missing required member '%s'
Error: 3071
SQLSTATE: HY000
(ER_INVALID_GEOJSON_WRONG_TYPE
)
Message: Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'
Error: 3072
SQLSTATE: HY000
(ER_INVALID_GEOJSON_UNSPECIFIED
)
Message: Invalid GeoJSON data provided to function %s
Error: 3073
SQLSTATE: HY000
(ER_DIMENSION_UNSUPPORTED
)
Message: Unsupported number of coordinate dimensions in function %s: Found %u, expected %u
Error: 3074
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_DOES_NOT_EXIST
)
Message: Slave channel '%s' does not exist.
Error: 3076
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_NAME_INVALID_OR_TOO_LONG
)
Message: Couldn't create channel: Channel name is either invalid or too long.
Error: 3077
SQLSTATE: HY000
(ER_SLAVE_NEW_CHANNEL_WRONG_REPOSITORY
)
Message: To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.
Error: 3079
SQLSTATE: HY000
(ER_SLAVE_MULTIPLE_CHANNELS_CMD
)
Message: Multiple channels exist on the slave. Please provide channel name as an argument.
Error: 3080
SQLSTATE: HY000
(ER_SLAVE_MAX_CHANNELS_EXCEEDED
)
Message: Maximum number of replication channels allowed exceeded.
Error: 3081
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_MUST_STOP
)
Message: This operation cannot be performed with running replication threads; run STOP SLAVE FOR CHANNEL '%s' first
Error: 3082
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_NOT_RUNNING
)
Message: This operation requires running replication threads; configure slave and run START SLAVE FOR CHANNEL '%s'
Error: 3083
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_WAS_RUNNING
)
Message: Replication thread(s) for channel '%s' are already runnning.
Error: 3084
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_WAS_NOT_RUNNING
)
Message: Replication thread(s) for channel '%s' are already stopped.
Error: 3085
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_SQL_THREAD_MUST_STOP
)
Message: This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL '%s' first.
Error: 3086
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_SQL_SKIP_COUNTER
)
Message: When sql_slave_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START SLAVE [SQL_THREAD]'. Value of sql_slave_skip_counter can only be used by one SQL thread at a time. Please use 'START SLAVE [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_slave_skip_counter.
Error: 3087
SQLSTATE: HY000
(ER_WRONG_FIELD_WITH_GROUP_V2
)
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: 3088
SQLSTATE: HY000
(ER_MIX_OF_GROUP_FUNC_AND_FIELDS_V2
)
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: 3089
SQLSTATE: HY000
(ER_WARN_DEPRECATED_SYSVAR_UPDATE
)
Message: Updating '%s' is deprecated. It will be made read-only in a future release.
Error: 3090
SQLSTATE: HY000
(ER_WARN_DEPRECATED_SQLMODE
)
Message: Changing sql mode '%s' is deprecated. It will be removed in a future release.
Error: 3091
SQLSTATE: HY000
(ER_CANNOT_LOG_PARTIAL_DROP_DATABASE_WITH_GTID
)
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: 3092
SQLSTATE: HY000
(ER_GROUP_REPLICATION_CONFIGURATION
)
Message: The server is not configured properly to be an active member of the group. Please see more details on error log.
Error: 3093
SQLSTATE: HY000
(ER_GROUP_REPLICATION_RUNNING
)
Message: The START GROUP_REPLICATION command failed since the group is already running.
Error: 3094
SQLSTATE: HY000
(ER_GROUP_REPLICATION_APPLIER_INIT_ERROR
)
Message: The START GROUP_REPLICATION command failed as the applier module failed to start.
Error: 3095
SQLSTATE: HY000
(ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT
)
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: 3096
SQLSTATE: HY000
(ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERROR
)
Message: The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.
Error: 3097
SQLSTATE: HY000
(ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR
)
Message: The START GROUP_REPLICATION command failed as there was an error when joining the communication group.
Error: 3098
SQLSTATE: HY000
(ER_BEFORE_DML_VALIDATION_ERROR
)
Message: The table does not comply with the requirements by an external plugin.
Error: 3099
SQLSTATE: HY000
(ER_PREVENTS_VARIABLE_WITHOUT_RBR
)
Message: Cannot change the value of variable %s without binary log format as ROW.
transaction_write_set_extraction
option value is set and
binlog_format
is not
ROW
.
Error: 3100
SQLSTATE: HY000
(ER_RUN_HOOK_ERROR
)
Message: Error on observer while running replication hook '%s'.
Error: 3101
SQLSTATE: 40000
(ER_TRANSACTION_ROLLBACK_DURING_COMMIT
)
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 Chapter 21, Group Replication.
Error: 3102
SQLSTATE: HY000
(ER_GENERATED_COLUMN_FUNCTION_IS_NOT_ALLOWED
)
Message: Expression of generated column '%s' contains a disallowed function.
Error: 3103
SQLSTATE: HY000
(ER_UNSUPPORTED_ALTER_INPLACE_ON_VIRTUAL_COLUMN
)
Message: INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actions
Error: 3104
SQLSTATE: HY000
(ER_WRONG_FK_OPTION_FOR_GENERATED_COLUMN
)
Message: Cannot define foreign key with %s clause on a generated column.
Error: 3105
SQLSTATE: HY000
(ER_NON_DEFAULT_VALUE_FOR_GENERATED_COLUMN
)
Message: The value specified for generated column '%s' in table '%s' is not allowed.
Error: 3106
SQLSTATE: HY000
(ER_UNSUPPORTED_ACTION_ON_GENERATED_COLUMN
)
Message: '%s' is not supported for generated columns.
Error: 3107
SQLSTATE: HY000
(ER_GENERATED_COLUMN_NON_PRIOR
)
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: 3108
SQLSTATE: HY000
(ER_DEPENDENT_BY_GENERATED_COLUMN
)
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: 3109
SQLSTATE: HY000
(ER_GENERATED_COLUMN_REF_AUTO_INC
)
Message: Generated column '%s' cannot refer to auto-increment column.
Error: 3110
SQLSTATE: HY000
(ER_FEATURE_NOT_AVAILABLE
)
Message: The '%s' feature is not available; you need to remove '%s' or use MySQL built with '%s'
Error: 3111
SQLSTATE: HY000
(ER_CANT_SET_GTID_MODE
)
Message: SET @@GLOBAL.GTID_MODE = %s is not allowed because %s.
Error: 3112
SQLSTATE: HY000
(ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF
)
Message: The replication receiver thread%s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.
Error: 3113
SQLSTATE: HY000
(ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION
)
Message: Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %s, position %lld.
Error: 3114
SQLSTATE: HY000
(ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON
)
Message: Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %s, position %lld.
Error: 3115
SQLSTATE: HY000
(ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF
)
Message: Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %s, position %lld.
Error: 3116
SQLSTATE: HY000
(ER_CANT_ENFORCE_GTID_CONSISTENCY_WITH_ONGOING_GTID_VIOLATING_TX
)
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: 3117
SQLSTATE: HY000
(ER_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TX
)
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: 3118
SQLSTATE: HY000
(ER_ACCOUNT_HAS_BEEN_LOCKED
)
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: 3119
SQLSTATE: 42000
(ER_WRONG_TABLESPACE_NAME
)
Message: Incorrect tablespace name `%s`
Error: 3120
SQLSTATE: HY000
(ER_TABLESPACE_IS_NOT_EMPTY
)
Message: Tablespace `%s` is not empty.
Error: 3121
SQLSTATE: HY000
(ER_WRONG_FILE_NAME
)
Message: Incorrect File Name '%s'.
Error: 3122
SQLSTATE: HY000
(ER_BOOST_GEOMETRY_INCONSISTENT_TURNS_EXCEPTION
)
Message: Inconsistent intersection points.
Error: 3123
SQLSTATE: HY000
(ER_WARN_OPTIMIZER_HINT_SYNTAX_ERROR
)
Message: Optimizer hint syntax error
Error: 3124
SQLSTATE: HY000
(ER_WARN_BAD_MAX_EXECUTION_TIME
)
Message: Unsupported MAX_EXECUTION_TIME
Error: 3125
SQLSTATE: HY000
(ER_WARN_UNSUPPORTED_MAX_EXECUTION_TIME
)
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: 3126
SQLSTATE: HY000
(ER_WARN_CONFLICTING_HINT
)
Message: Hint %s is ignored as conflicting/duplicated
Error: 3127
SQLSTATE: HY000
(ER_WARN_UNKNOWN_QB_NAME
)
Message: Query block name %s is not found for %s hint
Error: 3128
SQLSTATE: HY000
(ER_UNRESOLVED_HINT_NAME
)
Message: Unresolved name %s for %s hint
Error: 3129
SQLSTATE: HY000
(ER_WARN_ON_MODIFYING_GTID_EXECUTED_TABLE
)
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: 3130
SQLSTATE: HY000
(ER_PLUGGABLE_PROTOCOL_COMMAND_NOT_SUPPORTED
)
Message: Command not supported by pluggable protocols
Error: 3131
SQLSTATE: 42000
(ER_LOCKING_SERVICE_WRONG_NAME
)
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: 3132
SQLSTATE: HY000
(ER_LOCKING_SERVICE_DEADLOCK
)
Message: Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.
Error: 3133
SQLSTATE: HY000
(ER_LOCKING_SERVICE_TIMEOUT
)
Message: Service lock wait timeout exceeded.
Error: 3134
SQLSTATE: HY000
(ER_GIS_MAX_POINTS_IN_GEOMETRY_OVERFLOWED
)
Message: Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.
Error: 3135
SQLSTATE: HY000
(ER_SQL_MODE_MERGED
)
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: 3136
SQLSTATE: HY000
(ER_VTOKEN_PLUGIN_TOKEN_MISMATCH
)
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
Section 5.6.4, “Version Tokens”.
Error: 3137
SQLSTATE: HY000
(ER_VTOKEN_PLUGIN_TOKEN_NOT_FOUND
)
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 Section 5.6.4, “Version Tokens”.
Error: 3138
SQLSTATE: HY000
(ER_CANT_SET_VARIABLE_WHEN_OWNING_GTID
)
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: 3139
SQLSTATE: HY000
(ER_SLAVE_CHANNEL_OPERATION_NOT_ALLOWED
)
Message: %s cannot be performed on channel '%s'.
Error: 3140
SQLSTATE: 22032
(ER_INVALID_JSON_TEXT
)
Message: Invalid JSON text: "%s" at position %u in value for column '%s'.
Error: 3141
SQLSTATE: 22032
(ER_INVALID_JSON_TEXT_IN_PARAM
)
Message: Invalid JSON text in argument %u to function %s: "%s" at position %u.%s
Error: 3142
SQLSTATE: HY000
(ER_INVALID_JSON_BINARY_DATA
)
Message: The JSON binary value contains invalid data.
Error: 3143
SQLSTATE: 42000
(ER_INVALID_JSON_PATH
)
Message: Invalid JSON path expression. The error is around character position %u.%s
Error: 3144
SQLSTATE: 22032
(ER_INVALID_JSON_CHARSET
)
Message: Cannot create a JSON value from a string with CHARACTER SET '%s'.
Error: 3145
SQLSTATE: 22032
(ER_INVALID_JSON_CHARSET_IN_FUNCTION
)
Message: Invalid JSON character data provided to function %s: '%s'; utf8 is required.
Error: 3146
SQLSTATE: 22032
(ER_INVALID_TYPE_FOR_JSON
)
Message: Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.
Error: 3147
SQLSTATE: 22032
(ER_INVALID_CAST_TO_JSON
)
Message: Cannot CAST value to JSON.
Error: 3148
SQLSTATE: 42000
(ER_INVALID_JSON_PATH_CHARSET
)
Message: A path expression must be encoded in the utf8 character set. The path expression '%s' is encoded in character set '%s'.
Error: 3149
SQLSTATE: 42000
(ER_INVALID_JSON_PATH_WILDCARD
)
Message: In this situation, path expressions may not contain the * and ** tokens or an array range.
Error: 3150
SQLSTATE: 22032
(ER_JSON_VALUE_TOO_BIG
)
Message: The JSON value is too big to be stored in a JSON column.
Error: 3151
SQLSTATE: 22032
(ER_JSON_KEY_TOO_BIG
)
Message: The JSON object contains a key name that is too long.
Error: 3152
SQLSTATE: 42000
(ER_JSON_USED_AS_KEY
)
Message: JSON column '%s' supports indexing only via generated columns on a specified JSON path.
Error: 3153
SQLSTATE: 42000
(ER_JSON_VACUOUS_PATH
)
Message: The path expression '$' is not allowed in this context.
Error: 3154
SQLSTATE: 42000
(ER_JSON_BAD_ONE_OR_ALL_ARG
)
Message: The oneOrAll argument to %s may take these values: 'one' or 'all'.
Error: 3155
SQLSTATE: 22003
(ER_NUMERIC_JSON_VALUE_OUT_OF_RANGE
)
Message: Out of range JSON value for CAST to %s%s from column %s at row %ld
Error: 3156
SQLSTATE: 22018
(ER_INVALID_JSON_VALUE_FOR_CAST
)
Message: Invalid JSON value for CAST to %s%s from column %s at row %ld
Error: 3157
SQLSTATE: 22032
(ER_JSON_DOCUMENT_TOO_DEEP
)
Message: The JSON document exceeds the maximum depth.
Error: 3158
SQLSTATE: 22032
(ER_JSON_DOCUMENT_NULL_KEY
)
Message: JSON documents may not contain NULL member names.
Error: 3159
SQLSTATE: HY000
(ER_SECURE_TRANSPORT_REQUIRED
)
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: 3160
SQLSTATE: HY000
(ER_NO_SECURE_TRANSPORTS_CONFIGURED
)
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: 3161
SQLSTATE: HY000
(ER_DISABLED_STORAGE_ENGINE
)
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: 3162
SQLSTATE: HY000
(ER_USER_DOES_NOT_EXIST
)
Message: Authorization ID %s does not exist.
Error: 3163
SQLSTATE: HY000
(ER_USER_ALREADY_EXISTS
)
Message: Authorization ID %s already exists.
Error: 3164
SQLSTATE: HY000
(ER_AUDIT_API_ABORT
)
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: 3165
SQLSTATE: 42000
(ER_INVALID_JSON_PATH_ARRAY_CELL
)
Message: A path expression is not a path to a cell in an array.
Error: 3166
SQLSTATE: HY000
(ER_BUFPOOL_RESIZE_INPROGRESS
)
Message: Another buffer pool resize is already in progress.
Error: 3167
SQLSTATE: HY000
(ER_FEATURE_DISABLED_SEE_DOC
)
Message: The '%s' feature is disabled; see the documentation for '%s'
Error: 3168
SQLSTATE: HY000
(ER_SERVER_ISNT_AVAILABLE
)
Message: Server isn't available
Error: 3169
SQLSTATE: HY000
(ER_SESSION_WAS_KILLED
)
Message: Session was killed
Error: 3170
SQLSTATE: HY000
(ER_CAPACITY_EXCEEDED
)
Message: Memory capacity of %llu bytes for '%s' exceeded. %s
Error: 3171
SQLSTATE: HY000
(ER_CAPACITY_EXCEEDED_IN_RANGE_OPTIMIZER
)
Message: Range optimization was not done for this query.
Error: 3173
SQLSTATE: HY000
(ER_CANT_WAIT_FOR_EXECUTED_GTID_SET_WHILE_OWNING_A_GTID
)
Message: The client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.
Error: 3174
SQLSTATE: HY000
(ER_CANNOT_ADD_FOREIGN_BASE_COL_VIRTUAL
)
Message: Cannot add foreign key on the base column of indexed virtual column.
Error: 3175
SQLSTATE: HY000
(ER_CANNOT_CREATE_VIRTUAL_INDEX_CONSTRAINT
)
Message: Cannot create index on virtual column whose base column has foreign constraint.
Error: 3176
SQLSTATE: HY000
(ER_ERROR_ON_MODIFYING_GTID_EXECUTED_TABLE
)
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 neccessary you can modify it with a non-XA transaction.
Error: 3177
SQLSTATE: HY000
(ER_LOCK_REFUSED_BY_ENGINE
)
Message: Lock acquisition refused by storage engine.
Error: 3178
SQLSTATE: HY000
(ER_UNSUPPORTED_ALTER_ONLINE_ON_VIRTUAL_COLUMN
)
Message: ADD COLUMN col...VIRTUAL, ADD INDEX(col)
Error: 3179
SQLSTATE: HY000
(ER_MASTER_KEY_ROTATION_NOT_SUPPORTED_BY_SE
)
Message: Master key rotation is not supported by storage engine.
Error: 3181
SQLSTATE: HY000
(ER_MASTER_KEY_ROTATION_BINLOG_FAILED
)
Message: Write to binlog failed. However, master key rotation has been completed successfully.
Error: 3182
SQLSTATE: HY000
(ER_MASTER_KEY_ROTATION_SE_UNAVAILABLE
)
Message: Storage engine is not available.
Error: 3183
SQLSTATE: HY000
(ER_TABLESPACE_CANNOT_ENCRYPT
)
Message: This tablespace can't be encrypted.
Error: 3184
SQLSTATE: HY000
(ER_INVALID_ENCRYPTION_OPTION
)
Message: Invalid encryption option.
Error: 3185
SQLSTATE: HY000
(ER_CANNOT_FIND_KEY_IN_KEYRING
)
Message: Can't find master key from keyring, please check keyring plugin is loaded.
Error: 3186
SQLSTATE: HY000
(ER_CAPACITY_EXCEEDED_IN_PARSER
)
Message: Parser bailed out for this query.
Error: 3187
SQLSTATE: HY000
(ER_UNSUPPORTED_ALTER_ENCRYPTION_INPLACE
)
Message: Cannot alter encryption attribute by inplace algorithm.
Error: 3188
SQLSTATE: HY000
(ER_KEYRING_UDF_KEYRING_SERVICE_ERROR
)
Message: Function '%s' failed because underlying keyring service returned an error. Please check if a keyring plugin is installed and that provided arguments are valid for the keyring you are using.
Error: 3189
SQLSTATE: HY000
(ER_USER_COLUMN_OLD_LENGTH
)
Message: It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please run mysql_upgrade.
Error: 3190
SQLSTATE: HY000
(ER_CANT_RESET_MASTER
)
Message: RESET MASTER is not allowed because %s.
Error: 3191
SQLSTATE: HY000
(ER_GROUP_REPLICATION_MAX_GROUP_SIZE
)
Message: The START GROUP_REPLICATION command failed since the group already has 9 members.
Error: 3192
SQLSTATE: HY000
(ER_CANNOT_ADD_FOREIGN_BASE_COL_STORED
)
Message: Cannot add foreign key on the base column of stored column.
Error: 3193
SQLSTATE: HY000
(ER_TABLE_REFERENCED
)
Message: Cannot complete the operation because table is referenced by another connection.
Error: 3197
SQLSTATE: HY000
(ER_XA_RETRY
)
Message: The resource manager is not able to commit the transaction branch at this time. Please retry later.
ER_XA_RETRY
was added in 8.0.2.
Error: 3198
SQLSTATE: HY000
(ER_KEYRING_AWS_UDF_AWS_KMS_ERROR
)
Message: Function %s failed due to: %s.
ER_KEYRING_AWS_UDF_AWS_KMS_ERROR
was added in 8.0.2.
Error: 3199
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_XA
)
Message: Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on slaves when replicated using statements.
ER_BINLOG_UNSAFE_XA
was added in
8.0.2.
Error: 3500
SQLSTATE: HY000
(ER_UNSUPPORT_COMPRESSED_TEMPORARY_TABLE
)
Message: CREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.
Error: 3501
SQLSTATE: HY000
(ER_ACL_OPERATION_FAILED
)
Message: The ACL operation failed due to the following error from SE: errcode %d - %s
Error: 3502
SQLSTATE: HY000
(ER_UNSUPPORTED_INDEX_ALGORITHM
)
Message: This storage engine does not support the %s index algorithm, storage engine default was used instead.
Error: 3503
SQLSTATE: 42Y07
(ER_NO_SUCH_DB
)
Message: Database '%s' doesn't exist
Error: 3504
SQLSTATE: HY000
(ER_TOO_BIG_ENUM
)
Message: Too many enumeration values for column %s.
Error: 3505
SQLSTATE: HY000
(ER_TOO_LONG_SET_ENUM_VALUE
)
Message: Too long enumeration/set value for column %s.
Error: 3506
SQLSTATE: HY000
(ER_INVALID_DD_OBJECT
)
Message: %s dictionary object is invalid. (%s)
Error: 3507
SQLSTATE: HY000
(ER_UPDATING_DD_TABLE
)
Message: Failed to update %s dictionary object.
Error: 3508
SQLSTATE: HY000
(ER_INVALID_DD_OBJECT_ID
)
Message: Dictionary object id (%lu) does not exist.
Error: 3509
SQLSTATE: HY000
(ER_INVALID_DD_OBJECT_NAME
)
Message: Dictionary object name '%s' is invalid. (%s)
Error: 3510
SQLSTATE: HY000
(ER_TABLESPACE_MISSING_WITH_NAME
)
Message: Tablespace %s doesn't exist.
Error: 3511
SQLSTATE: HY000
(ER_TOO_LONG_ROUTINE_COMMENT
)
Message: Comment for routine '%s' is too long (max = %lu)
Error: 3512
SQLSTATE: HY000
(ER_SP_LOAD_FAILED
)
Message: Failed to load routine '%s'.
Error: 3513
SQLSTATE: HY000
(ER_INVALID_BITWISE_OPERANDS_SIZE
)
Message: Binary operands of bitwise operators must be of equal length
Error: 3514
SQLSTATE: HY000
(ER_INVALID_BITWISE_AGGREGATE_OPERANDS_SIZE
)
Message: Aggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() function
Error: 3515
SQLSTATE: HY000
(ER_WARN_UNSUPPORTED_HINT
)
Message: Hints aren't supported in %s
Error: 3516
SQLSTATE: 22S01
(ER_UNEXPECTED_GEOMETRY_TYPE
)
Message: %s value is a geometry of unexpected type %s in %s.
Error: 3517
SQLSTATE: SR002
(ER_SRS_PARSE_ERROR
)
Message: Can't parse the spatial reference system definition of SRID %u.
Error: 3518
SQLSTATE: SR003
(ER_SRS_PROJ_PARAMETER_MISSING
)
Message: The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.
Error: 3519
SQLSTATE: 01000
(ER_WARN_SRS_NOT_FOUND
)
Message: There's no spatial reference system with SRID %u. Calculations in function %s will be done in SRID 0.
Error: 3520
SQLSTATE: 22S00
(ER_SRS_NOT_CARTESIAN
)
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: 3521
SQLSTATE: SR001
(ER_SRS_NOT_CARTESIAN_UNDEFINED
)
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: 3522
SQLSTATE: HY000
(ER_PK_INDEX_CANT_BE_INVISIBLE
)
Message: A primary key index cannot be invisible
Error: 3523
SQLSTATE: HY000
(ER_UNKNOWN_AUTHID
)
Message: Unknown authorization ID `%s`@`%s`
Error: 3524
SQLSTATE: HY000
(ER_FAILED_ROLE_GRANT
)
Message: Failed to grant %s` to %s
Error: 3525
SQLSTATE: HY000
(ER_OPEN_ROLE_TABLES
)
Message: Failed to open the security system tables
Error: 3526
SQLSTATE: HY000
(ER_FAILED_DEFAULT_ROLES
)
Message: Failed to set default roles
Error: 3527
SQLSTATE: HY000
(ER_COMPONENTS_NO_SCHEME
)
Message: Cannot find schema in specified URN: '%s'.
Error: 3528
SQLSTATE: HY000
(ER_COMPONENTS_NO_SCHEME_SERVICE
)
Message: Cannot acquire scheme load service implementation for schema '%s' in specified URN: '%s'.
Error: 3529
SQLSTATE: HY000
(ER_COMPONENTS_CANT_LOAD
)
Message: Cannot load component from specified URN: '%s'.
Error: 3530
SQLSTATE: HY000
(ER_ROLE_NOT_GRANTED
)
Message: `%s`@`%s` is not granted to `%s`@`%s`
Error: 3531
SQLSTATE: HY000
(ER_FAILED_REVOKE_ROLE
)
Message: Could not revoke role from `%s`@`%s`
Error: 3532
SQLSTATE: HY000
(ER_RENAME_ROLE
)
Message: Renaming of a role identifier is forbidden
Error: 3533
SQLSTATE: HY000
(ER_COMPONENTS_CANT_ACQUIRE_SERVICE_IMPLEMENTATION
)
Message: Cannot acquire specified service implementation: '%s'.
Error: 3534
SQLSTATE: HY000
(ER_COMPONENTS_CANT_SATISFY_DEPENDENCY
)
Message: Cannot satisfy dependency for service '%s' required by component '%s'.
Error: 3535
SQLSTATE: HY000
(ER_COMPONENTS_LOAD_CANT_REGISTER_SERVICE_IMPLEMENTATION
)
Message: Cannot register service implementation '%s' provided by component '%s'.
Error: 3536
SQLSTATE: HY000
(ER_COMPONENTS_LOAD_CANT_INITIALIZE
)
Message: Initialization method provided by component '%s' failed.
Error: 3537
SQLSTATE: HY000
(ER_COMPONENTS_UNLOAD_NOT_LOADED
)
Message: Component specified by URN '%s' to unload has not been loaded before.
Error: 3538
SQLSTATE: HY000
(ER_COMPONENTS_UNLOAD_CANT_DEINITIALIZE
)
Message: De-initialization method provided by component '%s' failed.
Error: 3539
SQLSTATE: HY000
(ER_COMPONENTS_CANT_RELEASE_SERVICE
)
Message: Release of previously acquired service implementation failed.
Error: 3540
SQLSTATE: HY000
(ER_COMPONENTS_UNLOAD_CANT_UNREGISTER_SERVICE
)
Message: Unregistration of service implementation '%s' provided by component '%s' failed during unloading of the component.
Error: 3541
SQLSTATE: HY000
(ER_COMPONENTS_CANT_UNLOAD
)
Message: Cannot unload component from specified URN: '%s'.
Error: 3542
SQLSTATE: HY000
(ER_WARN_UNLOAD_THE_NOT_PERSISTED
)
Message: The Persistent Dynamic Loader was used to unload a component '%s', but it was not used to load that component before.
Error: 3543
SQLSTATE: HY000
(ER_COMPONENT_TABLE_INCORRECT
)
Message: The mysql.component table is missing or has an incorrect definition.
Error: 3544
SQLSTATE: HY000
(ER_COMPONENT_MANIPULATE_ROW_FAILED
)
Message: Failed to manipulate component '%s' persistence data. Error code %d from storage engine.
Error: 3545
SQLSTATE: HY000
(ER_COMPONENTS_UNLOAD_DUPLICATE_IN_GROUP
)
Message: The component with specified URN: '%s' was specified in group more than once.
Error: 3546
SQLSTATE: HY000
(ER_CANT_SET_GTID_PURGED_DUE_SETS_CONSTRAINTS
)
Message: @@GLOBAL.GTID_PURGED cannot be changed: %s
Error: 3547
SQLSTATE: HY000
(ER_CANNOT_LOCK_USER_MANAGEMENT_CACHES
)
Message: Can not lock user management caches for processing.
Error: 3548
SQLSTATE: SR001
(ER_SRS_NOT_FOUND
)
Message: There's no spatial reference system with SRID %u.
Error: 3549
SQLSTATE: HY000
(ER_VARIABLE_NOT_PERSISTED
)
Message: Variables cannot be persisted. Please retry.
Error: 3550
SQLSTATE: HY000
(ER_IS_QUERY_INVALID_CLAUSE
)
Message: Information schema queries do not support the '%s' clause.
Error: 3551
SQLSTATE: HY000
(ER_UNABLE_TO_STORE_STATISTICS
)
Message: Unable to store dynamic %s statistics into data dictionary.
Error: 3552
SQLSTATE: HY000
(ER_NO_SYSTEM_SCHEMA_ACCESS
)
Message: Access to system schema '%s' is rejected.
Error: 3553
SQLSTATE: HY000
(ER_NO_SYSTEM_TABLESPACE_ACCESS
)
Message: Access to system tablespace '%s' is rejected.
Error: 3554
SQLSTATE: HY000
(ER_NO_SYSTEM_TABLE_ACCESS
)
Message: Access to %s '%s.%s' is rejected.
Error: 3555
SQLSTATE: HY000
(ER_NO_SYSTEM_TABLE_ACCESS_FOR_DICTIONARY_TABLE
)
Message: data dictionary table
ER_NO_SYSTEM_TABLE_ACCESS_FOR_DICTIONARY_TABLE
was added in 8.0.1.
Error: 3556
SQLSTATE: HY000
(ER_NO_SYSTEM_TABLE_ACCESS_FOR_SYSTEM_TABLE
)
Message: system table
ER_NO_SYSTEM_TABLE_ACCESS_FOR_SYSTEM_TABLE
was added in 8.0.1.
Error: 3557
SQLSTATE: HY000
(ER_NO_SYSTEM_TABLE_ACCESS_FOR_TABLE
)
Message: table
ER_NO_SYSTEM_TABLE_ACCESS_FOR_TABLE
was added in 8.0.1.
Error: 3558
SQLSTATE: 22023
(ER_INVALID_OPTION_KEY
)
Message: Invalid option key '%s' in function %s.
ER_INVALID_OPTION_KEY
was added in
8.0.1.
Error: 3559
SQLSTATE: 22023
(ER_INVALID_OPTION_VALUE
)
Message: Invalid value '%s' for option '%s' in function '%s'.
ER_INVALID_OPTION_VALUE
was added
in 8.0.1.
Error: 3560
SQLSTATE: 22023
(ER_INVALID_OPTION_KEY_VALUE_PAIR
)
Message: The string '%s' is not a valid key %c value pair in function %s.
ER_INVALID_OPTION_KEY_VALUE_PAIR
was added in 8.0.1.
Error: 3561
SQLSTATE: 22023
(ER_INVALID_OPTION_START_CHARACTER
)
Message: The options argument in function %s starts with the invalid character '%c'.
ER_INVALID_OPTION_START_CHARACTER
was added in 8.0.1.
Error: 3562
SQLSTATE: 22023
(ER_INVALID_OPTION_END_CHARACTER
)
Message: The options argument in function %s ends with the invalid character '%c'.
ER_INVALID_OPTION_END_CHARACTER
was added in 8.0.1.
Error: 3563
SQLSTATE: 22023
(ER_INVALID_OPTION_CHARACTERS
)
Message: The options argument in function %s contains the invalid character sequence '%s'.
ER_INVALID_OPTION_CHARACTERS
was
added in 8.0.1.
Error: 3564
SQLSTATE: 22023
(ER_DUPLICATE_OPTION_KEY
)
Message: Duplicate option key '%s' in funtion '%s'.
ER_DUPLICATE_OPTION_KEY
was added
in 8.0.1.
Error: 3565
SQLSTATE: 01000
(ER_WARN_SRS_NOT_FOUND_AXIS_ORDER
)
Message: There's no spatial reference system with SRID %u. The axis order is unknown.
ER_WARN_SRS_NOT_FOUND_AXIS_ORDER
was added in 8.0.1.
Error: 3566
SQLSTATE: HY000
(ER_NO_ACCESS_TO_NATIVE_FCT
)
Message: Access to native function '%s' is rejected.
ER_NO_ACCESS_TO_NATIVE_FCT
was
added in 8.0.1.
Error: 3567
SQLSTATE: HY000
(ER_RESET_MASTER_TO_VALUE_OUT_OF_RANGE
)
Message: The requested value '%lu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.
ER_RESET_MASTER_TO_VALUE_OUT_OF_RANGE
was added in 8.0.1.
Error: 3568
SQLSTATE: HY000
(ER_UNRESOLVED_TABLE_LOCK
)
Message: Unresolved table name %s in locking clause.
ER_UNRESOLVED_TABLE_LOCK
was added
in 8.0.1.
Error: 3569
SQLSTATE: HY000
(ER_DUPLICATE_TABLE_LOCK
)
Message: Table %s appears in multiple locking clauses.
ER_DUPLICATE_TABLE_LOCK
was added
in 8.0.1.
Error: 3570
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_SKIP_LOCKED
)
Message: Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.
ER_BINLOG_UNSAFE_SKIP_LOCKED
was
added in 8.0.1.
Error: 3571
SQLSTATE: HY000
(ER_BINLOG_UNSAFE_NOWAIT
)
Message: Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.
ER_BINLOG_UNSAFE_NOWAIT
was added
in 8.0.1.
Error: 3572
SQLSTATE: HY000
(ER_LOCK_NOWAIT
)
Message: Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.
ER_LOCK_NOWAIT
was added in 8.0.1.
Error: 3573
SQLSTATE: HY000
(ER_CTE_RECURSIVE_REQUIRES_UNION
)
Message: Recursive Common Table Expression '%s' should contain a UNION
ER_CTE_RECURSIVE_REQUIRES_UNION
was added in 8.0.1.
Error: 3574
SQLSTATE: HY000
(ER_CTE_RECURSIVE_REQUIRES_NONRECURSIVE_FIRST
)
Message: Recursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive ones
ER_CTE_RECURSIVE_REQUIRES_NONRECURSIVE_FIRST
was added in 8.0.1.
Error: 3575
SQLSTATE: HY000
(ER_CTE_RECURSIVE_FORBIDS_AGGREGATION
)
Message: Recursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query block
ER_CTE_RECURSIVE_FORBIDS_AGGREGATION
was added in 8.0.1.
Error: 3576
SQLSTATE: HY000
(ER_CTE_RECURSIVE_FORBIDDEN_JOIN_ORDER
)
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
ER_CTE_RECURSIVE_FORBIDDEN_JOIN_ORDER
was added in 8.0.1.
Error: 3577
SQLSTATE: HY000
(ER_CTE_RECURSIVE_REQUIRES_SINGLE_REFERENCE
)
Message: In recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery
ER_CTE_RECURSIVE_REQUIRES_SINGLE_REFERENCE
was added in 8.0.1.
Error: 3578
SQLSTATE: HY000
(ER_SWITCH_TMP_ENGINE
)
Message: '%s' requires @@internal_tmp_disk_storage_engine=InnoDB
ER_SWITCH_TMP_ENGINE
was added in
8.0.1.
Error: 3579
SQLSTATE: HY000
(ER_WINDOW_NO_SUCH_WINDOW
)
Message: Window name '%s' is not defined.
ER_WINDOW_NO_SUCH_WINDOW
was added
in 8.0.2.
Error: 3580
SQLSTATE: HY000
(ER_WINDOW_CIRCULARITY_IN_WINDOW_GRAPH
)
Message: There is a circularity in the window dependency graph.
ER_WINDOW_CIRCULARITY_IN_WINDOW_GRAPH
was added in 8.0.2.
Error: 3581
SQLSTATE: HY000
(ER_WINDOW_NO_CHILD_PARTITIONING
)
Message: A window which depends on another cannot define partitioning.
ER_WINDOW_NO_CHILD_PARTITIONING
was added in 8.0.2.
Error: 3582
SQLSTATE: HY000
(ER_WINDOW_NO_INHERIT_FRAME
)
Message: Window '%s' has a frame definition, so cannot be referenced by another window.
ER_WINDOW_NO_INHERIT_FRAME
was
added in 8.0.2.
Error: 3583
SQLSTATE: HY000
(ER_WINDOW_NO_REDEFINE_ORDER_BY
)
Message: Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.
ER_WINDOW_NO_REDEFINE_ORDER_BY
was
added in 8.0.2.
Error: 3584
SQLSTATE: HY000
(ER_WINDOW_FRAME_START_ILLEGAL
)
Message: Window '%s': frame start cannot be UNBOUNDED FOLLOWING.
ER_WINDOW_FRAME_START_ILLEGAL
was
added in 8.0.2.
Error: 3585
SQLSTATE: HY000
(ER_WINDOW_FRAME_END_ILLEGAL
)
Message: Window '%s': frame end cannot be UNBOUNDED PRECEDING.
ER_WINDOW_FRAME_END_ILLEGAL
was
added in 8.0.2.
Error: 3586
SQLSTATE: HY000
(ER_WINDOW_FRAME_ILLEGAL
)
Message: Window '%s': frame start or end is negative, NULL or of non-integral type
ER_WINDOW_FRAME_ILLEGAL
was added
in 8.0.2.
Error: 3587
SQLSTATE: HY000
(ER_WINDOW_RANGE_FRAME_ORDER_TYPE
)
Message: Window '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal type
ER_WINDOW_RANGE_FRAME_ORDER_TYPE
was added in 8.0.2.
Error: 3588
SQLSTATE: HY000
(ER_WINDOW_RANGE_FRAME_TEMPORAL_TYPE
)
Message: Window '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.
ER_WINDOW_RANGE_FRAME_TEMPORAL_TYPE
was added in 8.0.2.
Error: 3589
SQLSTATE: HY000
(ER_WINDOW_RANGE_FRAME_NUMERIC_TYPE
)
Message: Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.
ER_WINDOW_RANGE_FRAME_NUMERIC_TYPE
was added in 8.0.2.
Error: 3590
SQLSTATE: HY000
(ER_WINDOW_RANGE_BOUND_NOT_CONSTANT
)
Message: Window '%s' has a non-constant frame bound.
ER_WINDOW_RANGE_BOUND_NOT_CONSTANT
was added in 8.0.2.
Error: 3591
SQLSTATE: HY000
(ER_WINDOW_DUPLICATE_NAME
)
Message: Window '%s' is defined twice.
ER_WINDOW_DUPLICATE_NAME
was added
in 8.0.2.
Error: 3592
SQLSTATE: HY000
(ER_WINDOW_ILLEGAL_ORDER_BY
)
Message: Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.
ER_WINDOW_ILLEGAL_ORDER_BY
was
added in 8.0.2.
Error: 3593
SQLSTATE: HY000
(ER_WINDOW_INVALID_WINDOW_FUNC_USE
)
Message: You cannot use the window function '%s' in this context.'
ER_WINDOW_INVALID_WINDOW_FUNC_USE
was added in 8.0.2.
Error: 3594
SQLSTATE: HY000
(ER_WINDOW_INVALID_WINDOW_FUNC_ALIAS_USE
)
Message: You cannot use the alias '%s' of an expression containing a window function in this context.'
ER_WINDOW_INVALID_WINDOW_FUNC_ALIAS_USE
was added in 8.0.2.
Error: 3595
SQLSTATE: HY000
(ER_WINDOW_NESTED_WINDOW_FUNC_USE_IN_WINDOW_SPEC
)
Message: You cannot nest a window function in the specification of window '%s'.
ER_WINDOW_NESTED_WINDOW_FUNC_USE_IN_WINDOW_SPEC
was added in 8.0.2.
Error: 3596
SQLSTATE: HY000
(ER_WINDOW_ROWS_INTERVAL_USE
)
Message: Window '%s': INTERVAL can only be used with RANGE frames.
ER_WINDOW_ROWS_INTERVAL_USE
was
added in 8.0.2.
Error: 3597
SQLSTATE: HY000
(ER_WINDOW_NO_GROUP_ORDER
)
Message: ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BY
ER_WINDOW_NO_GROUP_ORDER
was added
in 8.0.2.
Error: 3598
SQLSTATE: HY000
(ER_WINDOW_EXPLAIN_JSON
)
Message: To get information about window functions use EXPLAIN FORMAT=JSON
ER_WINDOW_EXPLAIN_JSON
was added
in 8.0.2.
Error: 3599
SQLSTATE: HY000
(ER_WINDOW_FUNCTION_IGNORES_FRAME
)
Message: Window function '%s' ignores the frame clause of window '%s' and aggregates over the whole partition
ER_WINDOW_FUNCTION_IGNORES_FRAME
was added in 8.0.2.
Error: 3600
SQLSTATE: HY000
(ER_WINDOW_SE_NOT_ACCEPTABLE
)
Message: Windowing requires @@internal_tmp_mem_storage_engine=TempTable.
ER_WINDOW_SE_NOT_ACCEPTABLE
was
added in 8.0.2.
Error: 3601
SQLSTATE: HY000
(ER_INVALID_NO_OF_ARGS
)
Message: Too many arguments for function %s: %lu; maximum allowed is %s.
ER_INVALID_NO_OF_ARGS
was added in
8.0.1.
Error: 3602
SQLSTATE: HY000
(ER_FIELD_IN_GROUPING_NOT_GROUP_BY
)
Message: Argument #%u of GROUPING function is not in GROUP BY
ER_FIELD_IN_GROUPING_NOT_GROUP_BY
was added in 8.0.1.
Error: 3603
SQLSTATE: HY000
(ER_TOO_LONG_TABLESPACE_COMMENT
)
Message: Comment for tablespace '%s' is too long (max = %lu)
ER_TOO_LONG_TABLESPACE_COMMENT
was
added in 8.0.1.
Error: 3604
SQLSTATE: HY000
(ER_ENGINE_CANT_DROP_TABLE
)
Message: Storage engine can't drop table '%s'
ER_ENGINE_CANT_DROP_TABLE
was
added in 8.0.1.
Error: 3605
SQLSTATE: HY000
(ER_ENGINE_CANT_DROP_MISSING_TABLE
)
Message: Storage engine can't drop table '%s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.
ER_ENGINE_CANT_DROP_MISSING_TABLE
was added in 8.0.1.
Error: 3606
SQLSTATE: HY000
(ER_TABLESPACE_DUP_FILENAME
)
Message: Duplicate file name for tablespace '%s'
ER_TABLESPACE_DUP_FILENAME
was
added in 8.0.1.
Error: 3607
SQLSTATE: HY000
(ER_DB_DROP_RMDIR2
)
Message: Problem while dropping database. Can't remove database directory (%s). Please remove it manually.
ER_DB_DROP_RMDIR2
was added in
8.0.1.
Error: 3608
SQLSTATE: HY000
(ER_IMP_NO_FILES_MATCHED
)
Message: No SDI files matched the pattern '%s'
ER_IMP_NO_FILES_MATCHED
was added
in 8.0.1.
Error: 3609
SQLSTATE: HY000
(ER_IMP_SCHEMA_DOES_NOT_EXIST
)
Message: Schema '%s', referenced in SDI, does not exist.
ER_IMP_SCHEMA_DOES_NOT_EXIST
was
added in 8.0.1.
Error: 3610
SQLSTATE: HY000
(ER_IMP_TABLE_ALREADY_EXISTS
)
Message: Table '%s.%s', referenced in SDI, already exists.
ER_IMP_TABLE_ALREADY_EXISTS
was
added in 8.0.1.
Error: 3611
SQLSTATE: HY000
(ER_IMP_INCOMPATIBLE_MYSQLD_VERSION
)
Message: Imported mysqld_version (%llu) is not compatible with current (%llu)
ER_IMP_INCOMPATIBLE_MYSQLD_VERSION
was added in 8.0.1.
Error: 3612
SQLSTATE: HY000
(ER_IMP_INCOMPATIBLE_DD_VERSION
)
Message: Imported dd version (%u) is not compatible with current (%u)
ER_IMP_INCOMPATIBLE_DD_VERSION
was
added in 8.0.1.
Error: 3613
SQLSTATE: HY000
(ER_IMP_INCOMPATIBLE_SDI_VERSION
)
Message: Imported sdi version (%llu) is not compatible with current (%llu)
ER_IMP_INCOMPATIBLE_SDI_VERSION
was added in 8.0.1.
Error: 3614
SQLSTATE: HY000
(ER_WARN_INVALID_HINT
)
Message: Invalid number of arguments for hint %s
ER_WARN_INVALID_HINT
was added in
8.0.1.
Error: 3615
SQLSTATE: HY000
(ER_VAR_DOES_NOT_EXIST
)
Message: Variable %s does not exist in persisted config file
ER_VAR_DOES_NOT_EXIST
was added in
8.0.1.
Error: 3616
SQLSTATE: 22S02
(ER_LONGITUDE_OUT_OF_RANGE
)
Message: Longitude %f is out of range in function %s. It must be within (%f, %f].
ER_LONGITUDE_OUT_OF_RANGE
was
added in 8.0.1.
Error: 3617
SQLSTATE: 22S03
(ER_LATITUDE_OUT_OF_RANGE
)
Message: Latitude %f is out of range in function %s. It must be within [%f, %f].
ER_LATITUDE_OUT_OF_RANGE
was added
in 8.0.1.
Error: 3618
SQLSTATE: 22S00
(ER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS
)
Message: %s(%s, %s) has not been implemented for geographic spatial reference systems.
ER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS
was added in 8.0.1.
Error: 3619
SQLSTATE: HY000
(ER_ILLEGAL_PRIVILEGE_LEVEL
)
Message: Illegal privilege level specified for %s
ER_ILLEGAL_PRIVILEGE_LEVEL
was
added in 8.0.1.
Error: 3620
SQLSTATE: HY000
(ER_NO_SYSTEM_VIEW_ACCESS
)
Message: Access to system view INFORMATION_SCHEMA.'%s' is rejected.
ER_NO_SYSTEM_VIEW_ACCESS
was added
in 8.0.2.
Error: 3621
SQLSTATE: XX999
(ER_PARSER_TRACE
)
Message: Parser saw: %s
ER_PARSER_TRACE
was added in
8.0.2.
Error: 3622
SQLSTATE: HY000
(ER_BOOTSTRAP_CANT_THREAD
)
Message: Can't create thread to handle bootstrap (errno: %d)
ER_BOOTSTRAP_CANT_THREAD
was added
in 8.0.2.
Error: 3623
SQLSTATE: HY000
(ER_COMPONENT_FILTER_FLABBERGASTED
)
Message: The log-filter component "%s" got confused at "%s" ...
ER_COMPONENT_FILTER_FLABBERGASTED
was added in 8.0.2.
Error: 3624
SQLSTATE: HY000
(ER_TRIGGER_INVALID_VALUE
)
Message: Trigger for table '%s'.'%s': invalid %s value (%s).
ER_TRIGGER_INVALID_VALUE
was added
in 8.0.2.
Error: 3625
SQLSTATE: HY000
(ER_OPT_WRONG_TREE
)
Message: Wrong tree: %s
ER_OPT_WRONG_TREE
was added in
8.0.2.
Error: 3626
SQLSTATE: HY000
(ER_DD_FAILSAFE
)
Message: Error: Invalid %s
ER_DD_FAILSAFE
was added in 8.0.2.
Error: 3627
SQLSTATE: HY000
(ER_DD_INIT_UPGRADE_FAILED
)
Message: Error in initializing dictionary, upgrade will do a cleanup and exit
ER_DD_INIT_UPGRADE_FAILED
was
added in 8.0.2.
Error: 3628
SQLSTATE: HY000
(ER_DD_NO_WRITES_NO_REPOPULATION
)
Message: Skip re-populating collations and character sets tables in %s%sread-only mode.
ER_DD_NO_WRITES_NO_REPOPULATION
was added in 8.0.2.
Error: 3629
SQLSTATE: HY000
(ER_DD_VERSION_FOUND
)
Message: Found data dictionary with version %d
ER_DD_VERSION_FOUND
was added in
8.0.2.
Error: 3630
SQLSTATE: HY000
(ER_DD_VERSION_INSTALLED
)
Message: Installed data dictionary with version %d
ER_DD_VERSION_INSTALLED
was added
in 8.0.2.
Error: 3631
SQLSTATE: HY000
(ER_DD_VERSION_UNSUPPORTED
)
Message: Data Dictionary version %d not supported
ER_DD_VERSION_UNSUPPORTED
was
added in 8.0.2.
Error: 3632
SQLSTATE: HY000
(ER_VIEW_UNKNOWN_CHARSET_OR_COLLATION
)
Message: View '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').
ER_VIEW_UNKNOWN_CHARSET_OR_COLLATION
was added in 8.0.2.
Error: 3633
SQLSTATE: HY000
(ER_DD_VIEW_CANT_ALLOC_CHARSET
)
Message: Error in allocating memory for character set name for view %s.%s.
ER_DD_VIEW_CANT_ALLOC_CHARSET
was
added in 8.0.2.
Error: 3634
SQLSTATE: HY000
(ER_DD_INIT_FAILED
)
Message: Data Dictionary initialization failed.
ER_DD_INIT_FAILED
was added in
8.0.2.
Error: 3635
SQLSTATE: HY000
(ER_DD_UPDATING_PLUGIN_MD_FAILED
)
Message: Failed to update plugin metadata in dictionary tables.
ER_DD_UPDATING_PLUGIN_MD_FAILED
was added in 8.0.2.
Error: 3636
SQLSTATE: HY000
(ER_DD_POPULATING_TABLES_FAILED
)
Message: Failed to Populate DD tables.
ER_DD_POPULATING_TABLES_FAILED
was
added in 8.0.2.
Error: 3637
SQLSTATE: HY000
(ER_DD_VIEW_CANT_CREATE
)
Message: Error in Creating View %s.%s
ER_DD_VIEW_CANT_CREATE
was added
in 8.0.2.
Error: 3638
SQLSTATE: HY000
(ER_DD_METADATA_NOT_FOUND
)
Message: Unable to start server. Cannot find the meta data for data dictionary table '%s'.
ER_DD_METADATA_NOT_FOUND
was added
in 8.0.2.
Error: 3639
SQLSTATE: HY000
(ER_DD_CACHE_NOT_EMPTY_AT_SHUTDOWN
)
Message: Dictionary cache not empty at shutdown.
ER_DD_CACHE_NOT_EMPTY_AT_SHUTDOWN
was added in 8.0.2.
Error: 3640
SQLSTATE: HY000
(ER_DD_OBJECT_REMAINS
)
Message: Dictionary objects used but not released.
ER_DD_OBJECT_REMAINS
was added in
8.0.2.
Error: 3641
SQLSTATE: HY000
(ER_DD_OBJECT_REMAINS_IN_RELEASER
)
Message: Dictionary objects left in default releaser.
ER_DD_OBJECT_REMAINS_IN_RELEASER
was added in 8.0.2.
Error: 3642
SQLSTATE: HY000
(ER_DD_OBJECT_RELEASER_REMAINS
)
Message: Dictionary object auto releaser not deleted
ER_DD_OBJECT_RELEASER_REMAINS
was
added in 8.0.2.
Error: 3643
SQLSTATE: HY000
(ER_DD_CANT_GET_OBJECT_KEY
)
Message: Error: Unable to create primary object key
ER_DD_CANT_GET_OBJECT_KEY
was
added in 8.0.2.
Error: 3644
SQLSTATE: HY000
(ER_DD_CANT_CREATE_OBJECT_KEY
)
Message: Error: Unable to create object key
ER_DD_CANT_CREATE_OBJECT_KEY
was
added in 8.0.2.
Error: 3645
SQLSTATE: HY000
(ER_LOG_SYSLOG_FACILITY_FAIL
)
Message: Failed to set syslog facility to "%s", setting to "%s" (%d) instead.
ER_LOG_SYSLOG_FACILITY_FAIL
was
added in 8.0.2.
Error: 3646
SQLSTATE: HY000
(ER_LOG_SYSLOG_CANNOT_OPEN
)
Message: Cannot open %s; check privileges, or start server with --log_syslog=0
ER_LOG_SYSLOG_CANNOT_OPEN
was
added in 8.0.2.
Error: 3647
SQLSTATE: HY000
(ER_LOG_FILE_CANNOT_OPEN
)
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.
ER_LOG_FILE_CANNOT_OPEN
was added
in 8.0.2.
Error: 3648
SQLSTATE: HY000
(ER_LOG_SLOW_CANNOT_OPEN
)
Message: either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or
ER_LOG_SLOW_CANNOT_OPEN
was added
in 8.0.2.
Error: 3649
SQLSTATE: HY000
(ER_LOG_GENERAL_CANNOT_OPEN
)
Message: either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" or
ER_LOG_GENERAL_CANNOT_OPEN
was
added in 8.0.2.
Error: 3650
SQLSTATE: HY000
(ER_LOG_CANNOT_WRITE
)
Message: Failed to write to %s: %s
ER_LOG_CANNOT_WRITE
was added in
8.0.2.
Error: 3651
SQLSTATE: HY000
(ER_RPL_ZOMBIE_ENCOUNTERED
)
Message: While initializing dump thread for slave with %s <%s>, found a zombie dump thread with the same %s. Master is killing the zombie dump thread(%u).
ER_RPL_ZOMBIE_ENCOUNTERED
was
added in 8.0.2.
Error: 3652
SQLSTATE: HY000
(ER_RPL_GTID_TABLE_CANNOT_OPEN
)
Message: Gtid table is not ready to be used. Table '%s.%s' cannot be opened.
ER_RPL_GTID_TABLE_CANNOT_OPEN
was
added in 8.0.2.
Error: 3653
SQLSTATE: HY000
(ER_SYSTEM_SCHEMA_NOT_FOUND
)
Message: System schema directory does not exist.
ER_SYSTEM_SCHEMA_NOT_FOUND
was
added in 8.0.2.
Error: 3654
SQLSTATE: HY000
(ER_CANT_CREATE_HANDLE_MGR_THREAD
)
Message: Can't create handle_manager thread (errno= %d)
ER_CANT_CREATE_HANDLE_MGR_THREAD
was added in 8.0.2.
Error: 3655
SQLSTATE: HY000
(ER_RPL_REPO_HAS_GAPS
)
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.
ER_RPL_REPO_HAS_GAPS
was added in
8.0.2.
Error: 3656
SQLSTATE: HY000
(ER_INVALID_VALUE_FOR_ENFORCE_GTID_CONSISTENCY
)
Message: option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.
ER_INVALID_VALUE_FOR_ENFORCE_GTID_CONSISTENCY
was added in 8.0.2.
Error: 3657
SQLSTATE: HY000
(ER_CHANGED_ENFORCE_GTID_CONSISTENCY
)
Message: Changed ENFORCE_GTID_CONSISTENCY from %s to %s.
ER_CHANGED_ENFORCE_GTID_CONSISTENCY
was added in 8.0.2.
Error: 3658
SQLSTATE: HY000
(ER_CHANGED_GTID_MODE
)
Message: Changed GTID_MODE from %s to %s.
ER_CHANGED_GTID_MODE
was added in
8.0.2.
Error: 3659
SQLSTATE: HY000
(ER_DISABLED_STORAGE_ENGINE_AS_DEFAULT
)
Message: %s is set to a disabled storage engine %s.
ER_DISABLED_STORAGE_ENGINE_AS_DEFAULT
was added in 8.0.2.
Error: 3660
SQLSTATE: HY000
(ER_DEBUG_SYNC_HIT
)
Message: Debug sync points hit: %s
ER_DEBUG_SYNC_HIT
was added in
8.0.2.
Error: 3661
SQLSTATE: HY000
(ER_DEBUG_SYNC_EXECUTED
)
Message: Debug sync points executed: %s
ER_DEBUG_SYNC_EXECUTED
was added
in 8.0.2.
Error: 3662
SQLSTATE: HY000
(ER_DEBUG_SYNC_THREAD_MAX
)
Message: Debug sync points max active per thread: %s
ER_DEBUG_SYNC_THREAD_MAX
was added
in 8.0.2.
Error: 3663
SQLSTATE: HY000
(ER_DEBUG_SYNC_OOM
)
Message: Debug Sync Facility disabled due to lack of memory.
ER_DEBUG_SYNC_OOM
was added in
8.0.2.
Error: 3664
SQLSTATE: HY000
(ER_CANT_INIT_TC_LOG
)
Message: Can't init tc log
ER_CANT_INIT_TC_LOG
was added in
8.0.2.
Error: 3665
SQLSTATE: HY000
(ER_EVENT_CANT_INIT_QUEUE
)
Message: Event Scheduler: Can't initialize the execution queue
ER_EVENT_CANT_INIT_QUEUE
was added
in 8.0.2.
Error: 3666
SQLSTATE: HY000
(ER_EVENT_PURGING_QUEUE
)
Message: Event Scheduler: Purging the queue. %u events
ER_EVENT_PURGING_QUEUE
was added
in 8.0.2.
Error: 3667
SQLSTATE: HY000
(ER_EVENT_LAST_EXECUTION
)
Message: Event Scheduler: Last execution of %s.%s. %s
ER_EVENT_LAST_EXECUTION
was added
in 8.0.2.
Error: 3668
SQLSTATE: HY000
(ER_EVENT_MESSAGE_STACK
)
Message: %*s
ER_EVENT_MESSAGE_STACK
was added
in 8.0.2.
Error: 3669
SQLSTATE: HY000
(ER_EVENT_EXECUTION_FAILED
)
Message: Event Scheduler: [%s].[%s.%s] event execution failed.
ER_EVENT_EXECUTION_FAILED
was
added in 8.0.2.
Error: 3670
SQLSTATE: HY000
(ER_CANT_INIT_SCHEDULER_THREAD
)
Message: Event Scheduler: Cannot initialize the scheduler thread
ER_CANT_INIT_SCHEDULER_THREAD
was
added in 8.0.2.
Error: 3671
SQLSTATE: HY000
(ER_CANT_CREATE_SCHEDULER_THREAD
)
Message: Event scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)
ER_CANT_CREATE_SCHEDULER_THREAD
was added in 8.0.2.
Error: 3672
SQLSTATE: HY000
(ER_SCHEDULER_STOPPED
)
Message: Event Scheduler: Stopped
ER_SCHEDULER_STOPPED
was added in
8.0.2.
Error: 3673
SQLSTATE: HY000
(ER_SCHEDULER_WAITING
)
Message: Event Scheduler: Waiting for the scheduler thread to reply
ER_SCHEDULER_WAITING
was added in
8.0.2.
Error: 3674
SQLSTATE: HY000
(ER_SCHEDULER_STARTED
)
Message: Event Scheduler: scheduler thread started with id %u
ER_SCHEDULER_STARTED
was added in
8.0.2.
Error: 3675
SQLSTATE: HY000
(ER_SCHEDULER_STOPPING_FAILED_TO_GET_EVENT
)
Message: Event Scheduler: Serious error during getting next event to execute. Stopping
ER_SCHEDULER_STOPPING_FAILED_TO_GET_EVENT
was added in 8.0.2.
Error: 3676
SQLSTATE: HY000
(ER_SCHEDULER_STOPPING_FAILED_TO_CREATE_WORKER
)
Message: Event_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event scheduler
ER_SCHEDULER_STOPPING_FAILED_TO_CREATE_WORKER
was added in 8.0.2.
Error: 3677
SQLSTATE: HY000
(ER_SCHEDULER_KILLING
)
Message: Event Scheduler: Killing the scheduler thread, thread id %u
ER_SCHEDULER_KILLING
was added in
8.0.2.
Error: 3678
SQLSTATE: HY000
(ER_UNABLE_TO_RESOLVE_IP
)
Message: IP address '%s' could not be resolved: %s
ER_UNABLE_TO_RESOLVE_IP
was added
in 8.0.2.
Error: 3679
SQLSTATE: HY000
(ER_UNABLE_TO_RESOLVE_HOSTNAME
)
Message: Host name '%s' could not be resolved: %s
ER_UNABLE_TO_RESOLVE_HOSTNAME
was
added in 8.0.2.
Error: 3680
SQLSTATE: HY000
(ER_HOSTNAME_RESEMBLES_IPV4
)
Message: IP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.
ER_HOSTNAME_RESEMBLES_IPV4
was
added in 8.0.2.
Error: 3681
SQLSTATE: HY000
(ER_HOSTNAME_DOESNT_RESOLVE_TO
)
Message: Hostname '%s' does not resolve to '%s'.
ER_HOSTNAME_DOESNT_RESOLVE_TO
was
added in 8.0.2.
Error: 3682
SQLSTATE: HY000
(ER_ADDRESSES_FOR_HOSTNAME_HEADER
)
Message: Hostname '%s' has the following IP addresses:
ER_ADDRESSES_FOR_HOSTNAME_HEADER
was added in 8.0.2.
Error: 3683
SQLSTATE: HY000
(ER_ADDRESSES_FOR_HOSTNAME_LIST_ITEM
)
Message: - %s
ER_ADDRESSES_FOR_HOSTNAME_LIST_ITEM
was added in 8.0.2.
Error: 3684
SQLSTATE: HY000
(ER_TRG_WITHOUT_DEFINER
)
Message: Definer clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.
ER_TRG_WITHOUT_DEFINER
was added
in 8.0.2.
Error: 3685
SQLSTATE: HY000
(ER_TRG_NO_CLIENT_CHARSET
)
Message: Client character set is missing for trigger of table %s. Using default character set.
ER_TRG_NO_CLIENT_CHARSET
was added
in 8.0.2.
Error: 3686
SQLSTATE: HY000
(ER_PARSING_VIEW
)
Message: Error in parsing view %s.%s
ER_PARSING_VIEW
was added in
8.0.2.
Error: 3687
SQLSTATE: HY000
(ER_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP
)
Message: Failed to bootstrap components infrastructure.
ER_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP
was added in 8.0.2.
Error: 3688
SQLSTATE: HY000
(ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN
)
Message: Failed to shutdown components infrastructure.
ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN
was added in 8.0.2.
Error: 3689
SQLSTATE: HY000
(ER_COMPONENTS_PERSIST_LOADER_BOOTSTRAP
)
Message: Failed to bootstrap persistent components loader.
ER_COMPONENTS_PERSIST_LOADER_BOOTSTRAP
was added in 8.0.2.
Error: 3690
SQLSTATE: HY000
(ER_DEPART_WITH_GRACE
)
Message: Giving %d client threads a chance to die gracefully
ER_DEPART_WITH_GRACE
was added in
8.0.2.
Error: 3691
SQLSTATE: HY000
(ER_CA_SELF_SIGNED
)
Message: CA certificate %s is self signed.
ER_CA_SELF_SIGNED
was added in
8.0.2.
Error: 3692
SQLSTATE: HY000
(ER_SSL_LIBRARY_ERROR
)
Message: Failed to set up SSL because of the following SSL library error: %s
ER_SSL_LIBRARY_ERROR
was added in
8.0.2.
Error: 3693
SQLSTATE: HY000
(ER_NO_THD_NO_UUID
)
Message: Failed to generate a server UUID because it is failed to allocate the THD.
ER_NO_THD_NO_UUID
was added in
8.0.2.
Error: 3694
SQLSTATE: HY000
(ER_UUID_SALT
)
Message: Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu,
ER_UUID_SALT
was added in 8.0.2.
Error: 3695
SQLSTATE: HY000
(ER_UUID_IS
)
Message: Generated uuid: '%s', server_start_time: %lu, bytes_sent: %llu
ER_UUID_IS
was added in 8.0.2.
Error: 3696
SQLSTATE: HY000
(ER_UUID_INVALID
)
Message: The server_uuid stored in auto.cnf file is not a valid UUID.
ER_UUID_INVALID
was added in
8.0.2.
Error: 3697
SQLSTATE: HY000
(ER_UUID_SCRUB
)
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.
ER_UUID_SCRUB
was added in 8.0.2.
Error: 3698
SQLSTATE: HY000
(ER_CREATING_NEW_UUID
)
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.
ER_CREATING_NEW_UUID
was added in
8.0.2.
Error: 3699
SQLSTATE: HY000
(ER_CANT_CREATE_UUID
)
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.
ER_CANT_CREATE_UUID
was added in
8.0.2.
Error: 3700
SQLSTATE: HY000
(ER_UNKNOWN_UNSUPPORTED_STORAGE_ENGINE
)
Message: Unknown/unsupported storage engine: %s
ER_UNKNOWN_UNSUPPORTED_STORAGE_ENGINE
was added in 8.0.2.
Error: 3701
SQLSTATE: HY000
(ER_SECURE_AUTH_VALUE_UNSUPPORTED
)
Message: Unsupported value 0 for secure-auth
ER_SECURE_AUTH_VALUE_UNSUPPORTED
was added in 8.0.2.
Error: 3702
SQLSTATE: HY000
(ER_INVALID_INSTRUMENT
)
Message: Invalid instrument name or value for performance_schema_instrument '%s'
ER_INVALID_INSTRUMENT
was added in
8.0.2.
Error: 3703
SQLSTATE: HY000
(ER_INNODB_MANDATORY
)
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.
ER_INNODB_MANDATORY
was added in
8.0.2.
Error: 3704
SQLSTATE: HY000
(ER_INNODB_CANNOT_BE_IGNORED
)
Message: ignore-builtin-innodb is ignored and will be removed in future releases.
ER_INNODB_CANNOT_BE_IGNORED
was
added in 8.0.2, removed after 8.0.2.
Error: 3705
SQLSTATE: HY000
(ER_OLD_PASSWORDS_NO_MIDDLE_GROUND
)
Message: Invalid old_passwords mode: 1. Valid values are 2 and 0
ER_OLD_PASSWORDS_NO_MIDDLE_GROUND
was added in 8.0.2.
Error: 3706
SQLSTATE: HY000
(ER_VERBOSE_REQUIRES_HELP
)
Message: --verbose is for use with --help; did you mean --log-error-verbosity?
ER_VERBOSE_REQUIRES_HELP
was added
in 8.0.2.
Error: 3707
SQLSTATE: HY000
(ER_POINTLESS_WITHOUT_SLOWLOG
)
Message: options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --slow-query-log is not set
ER_POINTLESS_WITHOUT_SLOWLOG
was
added in 8.0.2.
Error: 3708
SQLSTATE: HY000
(ER_WASTEFUL_NET_BUFFER_SIZE
)
Message: net_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.
ER_WASTEFUL_NET_BUFFER_SIZE
was
added in 8.0.2.
Error: 3709
SQLSTATE: HY000
(ER_DEPRECATED_TIMESTAMP_IMPLICIT_DEFAULTS
)
Message: TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
ER_DEPRECATED_TIMESTAMP_IMPLICIT_DEFAULTS
was added in 8.0.2.
Error: 3710
SQLSTATE: HY000
(ER_FT_BOOL_SYNTAX_INVALID
)
Message: Invalid ft-boolean-syntax string: %s
ER_FT_BOOL_SYNTAX_INVALID
was
added in 8.0.2.
Error: 3711
SQLSTATE: HY000
(ER_CREDENTIALLESS_AUTO_USER_BAD
)
Message: 'NO_AUTO_CREATE_USER' sql mode was not set.
ER_CREDENTIALLESS_AUTO_USER_BAD
was added in 8.0.2.
Error: 3712
SQLSTATE: HY000
(ER_CONNECTION_HANDLING_OOM
)
Message: Could not allocate memory for connection handling
ER_CONNECTION_HANDLING_OOM
was
added in 8.0.2.
Error: 3713
SQLSTATE: HY000
(ER_THREAD_HANDLING_OOM
)
Message: Could not allocate memory for thread handling
ER_THREAD_HANDLING_OOM
was added
in 8.0.2.
Error: 3714
SQLSTATE: HY000
(ER_CANT_CREATE_TEST_FILE
)
Message: Can't create test file %s
ER_CANT_CREATE_TEST_FILE
was added
in 8.0.2.
Error: 3715
SQLSTATE: HY000
(ER_CANT_CREATE_PID_FILE
)
Message: Can't start server: can't create PID file: %s
ER_CANT_CREATE_PID_FILE
was added
in 8.0.2.
Error: 3716
SQLSTATE: HY000
(ER_CANT_REMOVE_PID_FILE
)
Message: Unable to delete pid file: %s
ER_CANT_REMOVE_PID_FILE
was added
in 8.0.2.
Error: 3717
SQLSTATE: HY000
(ER_CANT_CREATE_SHUTDOWN_THREAD
)
Message: Can't create thread to handle shutdown requests (errno= %d)
ER_CANT_CREATE_SHUTDOWN_THREAD
was
added in 8.0.2.
Error: 3718
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_CANT_ACCESS_DIR
)
Message: Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %s
ER_SEC_FILE_PRIV_CANT_ACCESS_DIR
was added in 8.0.2.
Error: 3719
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_IGNORED
)
Message: Ignoring --secure-file-priv value as server is running with --initialize(-insecure).
ER_SEC_FILE_PRIV_IGNORED
was added
in 8.0.2.
Error: 3720
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_EMPTY
)
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.
ER_SEC_FILE_PRIV_EMPTY
was added
in 8.0.2.
Error: 3721
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_NULL
)
Message: --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
ER_SEC_FILE_PRIV_NULL
was added in
8.0.2.
Error: 3722
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_DIRECTORY_INSECURE
)
Message: Insecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.
ER_SEC_FILE_PRIV_DIRECTORY_INSECURE
was added in 8.0.2.
Error: 3723
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_CANT_STAT
)
Message: Failed to get stat for directory pointed out by --secure-file-priv
ER_SEC_FILE_PRIV_CANT_STAT
was
added in 8.0.2.
Error: 3724
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_DIRECTORY_PERMISSIONS
)
Message: Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
ER_SEC_FILE_PRIV_DIRECTORY_PERMISSIONS
was added in 8.0.2.
Error: 3725
SQLSTATE: HY000
(ER_SEC_FILE_PRIV_ARGUMENT_TOO_LONG
)
Message: Value for --secure-file-priv is longer than maximum limit of %d
ER_SEC_FILE_PRIV_ARGUMENT_TOO_LONG
was added in 8.0.2.
Error: 3726
SQLSTATE: HY000
(ER_CANT_CREATE_NAMED_PIPES_THREAD
)
Message: Can't create thread to handle named pipes (errno= %d)
ER_CANT_CREATE_NAMED_PIPES_THREAD
was added in 8.0.2.
Error: 3727
SQLSTATE: HY000
(ER_CANT_CREATE_TCPIP_THREAD
)
Message: Can't create thread to handle TCP/IP (errno= %d)
ER_CANT_CREATE_TCPIP_THREAD
was
added in 8.0.2.
Error: 3728
SQLSTATE: HY000
(ER_CANT_CREATE_SHM_THREAD
)
Message: Can't create thread to handle shared memory (errno= %d)
ER_CANT_CREATE_SHM_THREAD
was
added in 8.0.2.
Error: 3729
SQLSTATE: HY000
(ER_CANT_CREATE_INTERRUPT_THREAD
)
Message: Can't create interrupt-thread (error %d, errno: %d)
ER_CANT_CREATE_INTERRUPT_THREAD
was added in 8.0.2.
Error: 3730
SQLSTATE: HY000
(ER_WRITABLE_CONFIG_REMOVED
)
Message: World-writable config file '%s' has been removed.
ER_WRITABLE_CONFIG_REMOVED
was
added in 8.0.2.
Error: 3731
SQLSTATE: HY000
(ER_CORE_VALUES
)
Message: setrlimit could not change the size of core files to 'infinity'; We may not be able to generate a core file on signals
ER_CORE_VALUES
was added in 8.0.2.
Error: 3732
SQLSTATE: HY000
(ER_WRONG_DATETIME_SPEC
)
Message: Wrong date/time format specifier: %s
ER_WRONG_DATETIME_SPEC
was added
in 8.0.2.
Error: 3733
SQLSTATE: HY000
(ER_RPL_BINLOG_FILTERS_OOM
)
Message: Could not allocate replication and binlog filters: %s
ER_RPL_BINLOG_FILTERS_OOM
was
added in 8.0.2.
Error: 3734
SQLSTATE: HY000
(ER_KEYCACHE_OOM
)
Message: Cannot allocate the keycache
ER_KEYCACHE_OOM
was added in
8.0.2.
Error: 3735
SQLSTATE: HY000
(ER_CONFIRMING_THE_FUTURE
)
Message: Current time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.
ER_CONFIRMING_THE_FUTURE
was added
in 8.0.2.
Error: 3736
SQLSTATE: HY000
(ER_BACK_IN_TIME
)
Message: Iteration %d: Obtained valid current time from system
ER_BACK_IN_TIME
was added in
8.0.2.
Error: 3737
SQLSTATE: HY000
(ER_FUTURE_DATE
)
Message: Iteration %d: Current time obtained from system is greater than 2038
ER_FUTURE_DATE
was added in 8.0.2.
Error: 3738
SQLSTATE: HY000
(ER_UNSUPPORTED_DATE
)
Message: This MySQL server doesn't support dates later then 2038
ER_UNSUPPORTED_DATE
was added in
8.0.2.
Error: 3739
SQLSTATE: HY000
(ER_STARTING_AS
)
Message: %s (mysqld %s) starting as process %lu ...
ER_STARTING_AS
was added in 8.0.2.
Error: 3740
SQLSTATE: HY000
(ER_SHUTTING_DOWN_SLAVE_THREADS
)
Message: Shutting down slave threads
ER_SHUTTING_DOWN_SLAVE_THREADS
was
added in 8.0.2.
Error: 3741
SQLSTATE: HY000
(ER_DISCONNECTING_REMAINING_CLIENTS
)
Message: Forcefully disconnecting %d remaining clients
ER_DISCONNECTING_REMAINING_CLIENTS
was added in 8.0.2.
Error: 3742
SQLSTATE: HY000
(ER_ABORTING
)
Message: Aborting
ER_ABORTING
was added in 8.0.2.
Error: 3743
SQLSTATE: HY000
(ER_BINLOG_END
)
Message: Binlog end
ER_BINLOG_END
was added in 8.0.2.
Error: 3744
SQLSTATE: HY000
(ER_CALL_ME_LOCALHOST
)
Message: gethostname failed, using '%s' as hostname
ER_CALL_ME_LOCALHOST
was added in
8.0.2.
Error: 3745
SQLSTATE: HY000
(ER_USER_REQUIRES_ROOT
)
Message: One can only use the --user switch if running as root
ER_USER_REQUIRES_ROOT
was added in
8.0.2.
Error: 3746
SQLSTATE: HY000
(ER_REALLY_RUN_AS_ROOT
)
Message: Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
ER_REALLY_RUN_AS_ROOT
was added in
8.0.2.
Error: 3747
SQLSTATE: HY000
(ER_USER_WHAT_USER
)
Message: Fatal error: Can't change to run as user '%s' ; Please check that the user exists!
ER_USER_WHAT_USER
was added in
8.0.2.
Error: 3748
SQLSTATE: HY000
(ER_TRANSPORTS_WHAT_TRANSPORTS
)
Message: Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.
ER_TRANSPORTS_WHAT_TRANSPORTS
was
added in 8.0.2.
Error: 3749
SQLSTATE: HY000
(ER_FAIL_SETGID
)
Message: setgid: %s
ER_FAIL_SETGID
was added in 8.0.2.
Error: 3750
SQLSTATE: HY000
(ER_FAIL_SETUID
)
Message: setuid: %s
ER_FAIL_SETUID
was added in 8.0.2.
Error: 3751
SQLSTATE: HY000
(ER_FAIL_SETREGID
)
Message: setregid: %s
ER_FAIL_SETREGID
was added in
8.0.2.
Error: 3752
SQLSTATE: HY000
(ER_FAIL_SETREUID
)
Message: setreuid: %s
ER_FAIL_SETREUID
was added in
8.0.2.
Error: 3753
SQLSTATE: HY000
(ER_FAIL_CHROOT
)
Message: chroot: %s
ER_FAIL_CHROOT
was added in 8.0.2.
Error: 3754
SQLSTATE: HY000
(ER_WIN_LISTEN_BUT_HOW
)
Message: TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS
ER_WIN_LISTEN_BUT_HOW
was added in
8.0.2.
Error: 3755
SQLSTATE: HY000
(ER_NOT_RIGHT_NOW
)
Message: CTRL-C ignored during startup
ER_NOT_RIGHT_NOW
was added in
8.0.2.
Error: 3756
SQLSTATE: HY000
(ER_FIXING_CLIENT_CHARSET
)
Message: '%s' can not be used as client character set. '%s' will be used as default client character set.
ER_FIXING_CLIENT_CHARSET
was added
in 8.0.2.
Error: 3757
SQLSTATE: HY000
(ER_OOM
)
Message: Out of memory
ER_OOM
was added in 8.0.2.
Error: 3758
SQLSTATE: HY000
(ER_FAILED_TO_LOCK_MEM
)
Message: Failed to lock memory. Errno: %d
ER_FAILED_TO_LOCK_MEM
was added in
8.0.2.
Error: 3759
SQLSTATE: HY000
(ER_MYINIT_FAILED
)
Message: my_init() failed.
ER_MYINIT_FAILED
was added in
8.0.2.
Error: 3760
SQLSTATE: HY000
(ER_BEG_INITFILE
)
Message: Execution of init_file \'%s\' started.
ER_BEG_INITFILE
was added in
8.0.2.
Error: 3761
SQLSTATE: HY000
(ER_END_INITFILE
)
Message: Execution of init_file \'%s\' ended.
ER_END_INITFILE
was added in
8.0.2.
Error: 3762
SQLSTATE: HY000
(ER_CHANGED_MAX_OPEN_FILES
)
Message: Changed limits: max_open_files: %lu (requested %lu)
ER_CHANGED_MAX_OPEN_FILES
was
added in 8.0.2.
Error: 3763
SQLSTATE: HY000
(ER_CANT_INCREASE_MAX_OPEN_FILES
)
Message: Could not increase number of max_open_files to more than %lu (request: %lu)
ER_CANT_INCREASE_MAX_OPEN_FILES
was added in 8.0.2.
Error: 3764
SQLSTATE: HY000
(ER_CHANGED_MAX_CONNECTIONS
)
Message: Changed limits: max_connections: %lu (requested %lu)
ER_CHANGED_MAX_CONNECTIONS
was
added in 8.0.2.
Error: 3765
SQLSTATE: HY000
(ER_CHANGED_TABLE_OPEN_CACHE
)
Message: Changed limits: table_open_cache: %lu (requested %lu)
ER_CHANGED_TABLE_OPEN_CACHE
was
added in 8.0.2.
Error: 3766
SQLSTATE: HY000
(ER_THE_USER_ABIDES
)
Message: Ignoring user change to '%s' because the user was set to '%s' earlier on the command line
ER_THE_USER_ABIDES
was added in
8.0.2.
Error: 3767
SQLSTATE: HY000
(ER_RPL_CANT_ADD_DO_TABLE
)
Message: Could not add do table rule '%s'!
ER_RPL_CANT_ADD_DO_TABLE
was added
in 8.0.2.
Error: 3768
SQLSTATE: HY000
(ER_RPL_CANT_ADD_IGNORE_TABLE
)
Message: Could not add ignore table rule '%s'!
ER_RPL_CANT_ADD_IGNORE_TABLE
was
added in 8.0.2.
Error: 3769
SQLSTATE: HY000
(ER_TRACK_VARIABLES_BOGUS
)
Message: The variable session_track_system_variables either has duplicate values or invalid values.
ER_TRACK_VARIABLES_BOGUS
was added
in 8.0.2.
Error: 3770
SQLSTATE: HY000
(ER_EXCESS_ARGUMENTS
)
Message: Too many arguments (first extra is '%s').
ER_EXCESS_ARGUMENTS
was added in
8.0.2.
Error: 3771
SQLSTATE: HY000
(ER_VERBOSE_HINT
)
Message: Use --verbose --help to get a list of available options!
ER_VERBOSE_HINT
was added in
8.0.2.
Error: 3772
SQLSTATE: HY000
(ER_CANT_READ_ERRMSGS
)
Message: Unable to read errmsg.sys file
ER_CANT_READ_ERRMSGS
was added in
8.0.2.
Error: 3773
SQLSTATE: HY000
(ER_CANT_INIT_DBS
)
Message: Can't init databases
ER_CANT_INIT_DBS
was added in
8.0.2.
Error: 3774
SQLSTATE: HY000
(ER_LOG_OUTPUT_CONTRADICTORY
)
Message: There were other values specified to log-output besides NONE. Disabling slow and general logs anyway.
ER_LOG_OUTPUT_CONTRADICTORY
was
added in 8.0.2.
Error: 3775
SQLSTATE: HY000
(ER_NO_CSV_NO_LOG_TABLES
)
Message: CSV engine is not present, falling back to the log files
ER_NO_CSV_NO_LOG_TABLES
was added
in 8.0.2.
Error: 3776
SQLSTATE: HY000
(ER_RPL_REWRITEDB_MISSING_ARROW
)
Message: Bad syntax in replicate-rewrite-db - missing '->'!
ER_RPL_REWRITEDB_MISSING_ARROW
was
added in 8.0.2.
Error: 3777
SQLSTATE: HY000
(ER_RPL_REWRITEDB_EMPTY_FROM
)
Message: Bad syntax in replicate-rewrite-db - empty FROM db!
ER_RPL_REWRITEDB_EMPTY_FROM
was
added in 8.0.2.
Error: 3778
SQLSTATE: HY000
(ER_RPL_REWRITEDB_EMPTY_TO
)
Message: Bad syntax in replicate-rewrite-db - empty TO db!
ER_RPL_REWRITEDB_EMPTY_TO
was
added in 8.0.2.
Error: 3779
SQLSTATE: HY000
(ER_LOG_FILES_GIVEN_LOG_OUTPUT_IS_TABLE
)
Message: Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.
ER_LOG_FILES_GIVEN_LOG_OUTPUT_IS_TABLE
was added in 8.0.2.
Error: 3780
SQLSTATE: HY000
(ER_LOG_FILE_INVALID
)
Message: Invalid value for %s: %s
ER_LOG_FILE_INVALID
was added in
8.0.2.
Error: 3781
SQLSTATE: HY000
(ER_LOWER_CASE_TABLE_NAMES_CS_DD_ON_CI_FS_UNSUPPORTED
)
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.
ER_LOWER_CASE_TABLE_NAMES_CS_DD_ON_CI_FS_UNSUPPORTED
was added in 8.0.2.
Error: 3782
SQLSTATE: HY000
(ER_LOWER_CASE_TABLE_NAMES_USING_2
)
Message: Setting lower_case_table_names=2 because file system for %s is case insensitive
ER_LOWER_CASE_TABLE_NAMES_USING_2
was added in 8.0.2.
Error: 3783
SQLSTATE: HY000
(ER_LOWER_CASE_TABLE_NAMES_USING_0
)
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.
ER_LOWER_CASE_TABLE_NAMES_USING_0
was added in 8.0.2.
Error: 3784
SQLSTATE: HY000
(ER_NEED_LOG_BIN
)
Message: You need to use --log-bin to make %s work.
ER_NEED_LOG_BIN
was added in
8.0.2.
Error: 3785
SQLSTATE: HY000
(ER_NEED_FILE_INSTEAD_OF_DIR
)
Message: Path '%s' is a directory name, please specify a file name for %s option
ER_NEED_FILE_INSTEAD_OF_DIR
was
added in 8.0.2.
Error: 3786
SQLSTATE: HY000
(ER_LOG_BIN_BETTER_WITH_NAME
)
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 master and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.
ER_LOG_BIN_BETTER_WITH_NAME
was
added in 8.0.2.
Error: 3787
SQLSTATE: HY000
(ER_BINLOG_NEEDS_SERVERID
)
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
ER_BINLOG_NEEDS_SERVERID
was added
in 8.0.2.
Error: 3788
SQLSTATE: HY000
(ER_RPL_CANT_MAKE_PATHS
)
Message: Unable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).
ER_RPL_CANT_MAKE_PATHS
was added
in 8.0.2.
Error: 3789
SQLSTATE: HY000
(ER_CANT_INITIALIZE_GTID
)
Message: Failed to initialize GTID structures.
ER_CANT_INITIALIZE_GTID
was added
in 8.0.2.
Error: 3790
SQLSTATE: HY000
(ER_CANT_INITIALIZE_EARLY_PLUGINS
)
Message: Failed to initialize early plugins.
ER_CANT_INITIALIZE_EARLY_PLUGINS
was added in 8.0.2.
Error: 3791
SQLSTATE: HY000
(ER_CANT_INITIALIZE_BUILTIN_PLUGINS
)
Message: Failed to initialize builtin plugins.
ER_CANT_INITIALIZE_BUILTIN_PLUGINS
was added in 8.0.2.
Error: 3792
SQLSTATE: HY000
(ER_CANT_INITIALIZE_DYNAMIC_PLUGINS
)
Message: Failed to initialize dynamic plugins.
ER_CANT_INITIALIZE_DYNAMIC_PLUGINS
was added in 8.0.2.
Error: 3793
SQLSTATE: HY000
(ER_PERFSCHEMA_INIT_FAILED
)
Message: Performance schema disabled (reason: init failed).
ER_PERFSCHEMA_INIT_FAILED
was
added in 8.0.2.
Error: 3794
SQLSTATE: HY000
(ER_STACKSIZE_UNEXPECTED
)
Message: Asked for %lu thread stack, but got %ld
ER_STACKSIZE_UNEXPECTED
was added
in 8.0.2.
Error: 3795
SQLSTATE: HY000
(ER_CANT_SET_DATADIR
)
Message: failed to set datadir to %s
ER_CANT_SET_DATADIR
was added in
8.0.2.
Error: 3796
SQLSTATE: HY000
(ER_CANT_STAT_DATADIR
)
Message: Can't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/group
ER_CANT_STAT_DATADIR
was added in
8.0.2.
Error: 3797
SQLSTATE: HY000
(ER_CANT_CHOWN_DATADIR
)
Message: Can't change data directory owner to %s
ER_CANT_CHOWN_DATADIR
was added in
8.0.2.
Error: 3798
SQLSTATE: HY000
(ER_CANT_SET_UP_PERSISTED_VALUES
)
Message: Setting persistent options failed.
ER_CANT_SET_UP_PERSISTED_VALUES
was added in 8.0.2.
Error: 3799
SQLSTATE: HY000
(ER_CANT_SAVE_GTIDS
)
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.
ER_CANT_SAVE_GTIDS
was added in
8.0.2.
Error: 3800
SQLSTATE: HY000
(ER_AUTH_CANT_SET_DEFAULT_PLUGIN
)
Message: Can't start server: Invalid value for --default-authentication-plugin
ER_AUTH_CANT_SET_DEFAULT_PLUGIN
was added in 8.0.2.
Error: 3801
SQLSTATE: HY000
(ER_CANT_JOIN_SHUTDOWN_THREAD
)
Message: Could not join %sthread. error:%d
ER_CANT_JOIN_SHUTDOWN_THREAD
was
added in 8.0.2.
Error: 3802
SQLSTATE: HY000
(ER_CANT_HASH_DO_AND_IGNORE_RULES
)
Message: An error occurred while building do_table and ignore_table rules to hashes for global replication filter.
ER_CANT_HASH_DO_AND_IGNORE_RULES
was added in 8.0.2.
Error: 3803
SQLSTATE: HY000
(ER_CANT_OPEN_CA
)
Message: Error opening CA certificate file
ER_CANT_OPEN_CA
was added in
8.0.2.
Error: 3804
SQLSTATE: HY000
(ER_CANT_ACCESS_CAPATH
)
Message: Error accessing directory pointed by --ssl-capath
ER_CANT_ACCESS_CAPATH
was added in
8.0.2.
Error: 3805
SQLSTATE: HY000
(ER_SSL_TRYING_DATADIR_DEFAULTS
)
Message: Found %s, %s and %s in data directory. Trying to enable SSL support using them.
ER_SSL_TRYING_DATADIR_DEFAULTS
was
added in 8.0.2.
Error: 3806
SQLSTATE: HY000
(ER_AUTO_OPTIONS_FAILED
)
Message: Failed to create %s(file: '%s', errno %d)
ER_AUTO_OPTIONS_FAILED
was added
in 8.0.2.
Error: 3807
SQLSTATE: HY000
(ER_CANT_INIT_TIMER
)
Message: Failed to initialize timer component (errno %d).
ER_CANT_INIT_TIMER
was added in
8.0.2.
Error: 3808
SQLSTATE: HY000
(ER_SERVERID_TOO_LARGE
)
Message: server-id configured is too large to represent with server-id-bits configured.
ER_SERVERID_TOO_LARGE
was added in
8.0.2.
Error: 3809
SQLSTATE: HY000
(ER_DEFAULT_SE_UNAVAILABLE
)
Message: Default%s storage engine (%s) is not available
ER_DEFAULT_SE_UNAVAILABLE
was
added in 8.0.2.
Error: 3810
SQLSTATE: HY000
(ER_CANT_OPEN_ERROR_LOG
)
Message: Could not open %s file for error logging: %s.
ER_CANT_OPEN_ERROR_LOG
was added
in 8.0.2.
Error: 3811
SQLSTATE: HY000
(ER_INVALID_ERROR_LOG_NAME
)
Message: Invalid log file name after expanding symlinks: '%s'
ER_INVALID_ERROR_LOG_NAME
was
added in 8.0.2.
Error: 3812
SQLSTATE: HY000
(ER_RPL_INFINITY_DENIED
)
Message: using --replicate-same-server-id in conjunction with --log-slave-updates is impossible, it would lead to infinite loops in this server.
ER_RPL_INFINITY_DENIED
was added
in 8.0.2.
Error: 3813
SQLSTATE: HY000
(ER_RPL_INFINITY_IGNORED
)
Message: using --replicate-same-server-id in conjunction with --log-slave-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined.
ER_RPL_INFINITY_IGNORED
was added
in 8.0.2.
Error: 3814
SQLSTATE: HY000
(ER_NDB_TABLES_NOT_READY
)
Message: NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value
ER_NDB_TABLES_NOT_READY
was added
in 8.0.2.
Error: 3815
SQLSTATE: HY000
(ER_TABLE_CHECK_INTACT
)
Message: %s
ER_TABLE_CHECK_INTACT
was added in
8.0.2.
Error: 3816
SQLSTATE: HY000
(ER_DD_TABLESPACE_NOT_FOUND
)
Message: Unable to start server. The data dictionary tablespace '%s' does not exist.
ER_DD_TABLESPACE_NOT_FOUND
was
added in 8.0.2.
Error: 3817
SQLSTATE: HY000
(ER_DD_TRG_CONNECTION_COLLATION_MISSING
)
Message: Connection collation is missing for trigger of table %s. Using default connection collation.
ER_DD_TRG_CONNECTION_COLLATION_MISSING
was added in 8.0.2.
Error: 3818
SQLSTATE: HY000
(ER_DD_TRG_DB_COLLATION_MISSING
)
Message: Database collation is missing for trigger of table %s. Using Default character set.
ER_DD_TRG_DB_COLLATION_MISSING
was
added in 8.0.2.
Error: 3819
SQLSTATE: HY000
(ER_DD_TRG_DEFINER_OOM
)
Message: Error in Memory allocation for Definer %s for Trigger.
ER_DD_TRG_DEFINER_OOM
was added in
8.0.2.
Error: 3820
SQLSTATE: HY000
(ER_DD_TRG_FILE_UNREADABLE
)
Message: Error in reading %s.TRG file.
ER_DD_TRG_FILE_UNREADABLE
was
added in 8.0.2.
Error: 3821
SQLSTATE: HY000
(ER_TRG_CANT_PARSE
)
Message: Error in parsing Triggers from %s.TRG file.
ER_TRG_CANT_PARSE
was added in
8.0.2.
Error: 3822
SQLSTATE: HY000
(ER_DD_TRG_CANT_ADD
)
Message: Error in creating DD entry for Trigger %s.%s
ER_DD_TRG_CANT_ADD
was added in
8.0.2.
Error: 3823
SQLSTATE: HY000
(ER_DD_CANT_RESOLVE_VIEW
)
Message: Resolving dependency for the view '%s.%s' failed. View is no more valid to use
ER_DD_CANT_RESOLVE_VIEW
was added
in 8.0.2.
Error: 3824
SQLSTATE: HY000
(ER_DD_VIEW_WITHOUT_DEFINER
)
Message: %s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.
ER_DD_VIEW_WITHOUT_DEFINER
was
added in 8.0.2.
Error: 3825
SQLSTATE: HY000
(ER_PLUGIN_INIT_FAILED
)
Message: Plugin '%s' init function returned error.
ER_PLUGIN_INIT_FAILED
was added in
8.0.2.
Error: 3826
SQLSTATE: HY000
(ER_RPL_TRX_DELEGATES_INIT_FAILED
)
Message: Initialization of transaction delegates failed. Please report a bug.
ER_RPL_TRX_DELEGATES_INIT_FAILED
was added in 8.0.2.
Error: 3827
SQLSTATE: HY000
(ER_RPL_BINLOG_STORAGE_DELEGATES_INIT_FAILED
)
Message: Initialization binlog storage delegates failed. Please report a bug.
ER_RPL_BINLOG_STORAGE_DELEGATES_INIT_FAILED
was added in 8.0.2.
Error: 3828
SQLSTATE: HY000
(ER_RPL_BINLOG_TRANSMIT_DELEGATES_INIT_FAILED
)
Message: Initialization of binlog transmit delegates failed. Please report a bug.
ER_RPL_BINLOG_TRANSMIT_DELEGATES_INIT_FAILED
was added in 8.0.2.
Error: 3829
SQLSTATE: HY000
(ER_RPL_BINLOG_RELAY_DELEGATES_INIT_FAILED
)
Message: Initialization binlog relay IO delegates failed. Please report a bug.
ER_RPL_BINLOG_RELAY_DELEGATES_INIT_FAILED
was added in 8.0.2.
Error: 3830
SQLSTATE: HY000
(ER_RPL_PLUGIN_FUNCTION_FAILED
)
Message: Run function '...' in plugin '%s' failed
ER_RPL_PLUGIN_FUNCTION_FAILED
was
added in 8.0.2.
Error: 3831
SQLSTATE: HY000
(ER_SQL_HA_READ_FAILED
)
Message: mysql_ha_read: Got error %d when reading table '%s'
ER_SQL_HA_READ_FAILED
was added in
8.0.2.
Error: 3832
SQLSTATE: HY000
(ER_SR_BOGUS_VALUE
)
Message: Stored routine '%s'.'%s': invalid value in column %s.
ER_SR_BOGUS_VALUE
was added in
8.0.2.
Error: 3833
SQLSTATE: HY000
(ER_SR_INVALID_CONTEXT
)
Message: Invalid creation context '%s.%s'.
ER_SR_INVALID_CONTEXT
was added in
8.0.2.
Error: 3834
SQLSTATE: HY000
(ER_READING_TABLE_FAILED
)
Message: Got error %d when reading table '%s'
ER_READING_TABLE_FAILED
was added
in 8.0.2.
Error: 3835
SQLSTATE: HY000
(ER_DES_FILE_WRONG_KEY
)
Message: load_des_file: Found wrong key_number: %c
ER_DES_FILE_WRONG_KEY
was added in
8.0.2.
Error: 3836
SQLSTATE: HY000
(ER_CANT_SET_PERSISTED
)
Message: Failed to set persisted options.
ER_CANT_SET_PERSISTED
was added in
8.0.2.
Error: 3837
SQLSTATE: HY000
(ER_JSON_PARSE_ERROR
)
Message: JSON parsing error
ER_JSON_PARSE_ERROR
was added in
8.0.2.
Error: 3838
SQLSTATE: HY000
(ER_CONFIG_OPTION_WITHOUT_GROUP
)
Message: Found option without preceding group in config file
ER_CONFIG_OPTION_WITHOUT_GROUP
was
added in 8.0.2.
Error: 3839
SQLSTATE: HY000
(ER_VALGRIND_DO_QUICK_LEAK_CHECK
)
Message: VALGRIND_DO_QUICK_LEAK_CHECK
ER_VALGRIND_DO_QUICK_LEAK_CHECK
was added in 8.0.2.
Error: 3840
SQLSTATE: HY000
(ER_VALGRIND_COUNT_LEAKS
)
Message: VALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'
ER_VALGRIND_COUNT_LEAKS
was added
in 8.0.2.
Error: 3841
SQLSTATE: HY000
(ER_LOAD_DATA_INFILE_FAILED_IN_UNEXPECTED_WAY
)
Message: LOAD DATA INFILE in the slave SQL Thread can only read from --slave-load-tmpdir. Please, report a bug.
ER_LOAD_DATA_INFILE_FAILED_IN_UNEXPECTED_WAY
was added in 8.0.2.
Error: 3842
SQLSTATE: HY000
(ER_UNKNOWN_ERROR_NUMBER
)
Message: Got unknown error: %d
ER_UNKNOWN_ERROR_NUMBER
was added
in 8.0.2.
Error: 3843
SQLSTATE: HY000
(ER_UDF_CANT_ALLOC_FOR_STRUCTURES
)
Message: Can't allocate memory for udf structures
ER_UDF_CANT_ALLOC_FOR_STRUCTURES
was added in 8.0.2.
Error: 3844
SQLSTATE: HY000
(ER_UDF_CANT_ALLOC_FOR_FUNCTION
)
Message: Can't alloc memory for udf function: '%s'
ER_UDF_CANT_ALLOC_FOR_FUNCTION
was
added in 8.0.2.
Error: 3845
SQLSTATE: HY000
(ER_UDF_INVALID_ROW_IN_FUNCTION_TABLE
)
Message: Invalid row in mysql.func table for function '%s'
ER_UDF_INVALID_ROW_IN_FUNCTION_TABLE
was added in 8.0.2.
Error: 3846
SQLSTATE: HY000
(ER_UDF_CANT_OPEN_FUNCTION_TABLE
)
Message: Can't open the mysql.func table. Please run mysql_upgrade to create it.
ER_UDF_CANT_OPEN_FUNCTION_TABLE
was added in 8.0.2.
Error: 3847
SQLSTATE: HY000
(ER_XA_RECOVER_FOUND_TRX_IN_SE
)
Message: Found %d prepared transaction(s) in %s
ER_XA_RECOVER_FOUND_TRX_IN_SE
was
added in 8.0.2.
Error: 3848
SQLSTATE: HY000
(ER_XA_RECOVER_FOUND_XA_TRX
)
Message: Found %d prepared XA transactions
ER_XA_RECOVER_FOUND_XA_TRX
was
added in 8.0.2.
Error: 3849
SQLSTATE: HY000
(ER_XA_IGNORING_XID
)
Message: ignore xid %s
ER_XA_IGNORING_XID
was added in
8.0.2.
Error: 3850
SQLSTATE: HY000
(ER_XA_COMMITTING_XID
)
Message: commit xid %s
ER_XA_COMMITTING_XID
was added in
8.0.2.
Error: 3851
SQLSTATE: HY000
(ER_XA_ROLLING_BACK_XID
)
Message: rollback xid %s
ER_XA_ROLLING_BACK_XID
was added
in 8.0.2.
Error: 3852
SQLSTATE: HY000
(ER_XA_STARTING_RECOVERY
)
Message: Starting crash recovery...
ER_XA_STARTING_RECOVERY
was added
in 8.0.2.
Error: 3853
SQLSTATE: HY000
(ER_XA_NO_MULTI_2PC_HEURISTIC_RECOVER
)
Message: --tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.
ER_XA_NO_MULTI_2PC_HEURISTIC_RECOVER
was added in 8.0.2.
Error: 3854
SQLSTATE: HY000
(ER_XA_RECOVER_EXPLANATION
)
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.
ER_XA_RECOVER_EXPLANATION
was
added in 8.0.2.
Error: 3855
SQLSTATE: HY000
(ER_XA_RECOVERY_DONE
)
Message: Crash recovery finished.
ER_XA_RECOVERY_DONE
was added in
8.0.2.
Error: 3856
SQLSTATE: HY000
(ER_TRX_GTID_COLLECT_REJECT
)
Message: Failed to collect GTID to send in the response packet!
ER_TRX_GTID_COLLECT_REJECT
was
added in 8.0.2.
Error: 3857
SQLSTATE: HY000
(ER_SQL_AUTHOR_DEFAULT_ROLES_FAIL
)
Message: MYSQL.DEFAULT_ROLES couldn't be updated for authorizationidentifier %s
ER_SQL_AUTHOR_DEFAULT_ROLES_FAIL
was added in 8.0.2.
Error: 3858
SQLSTATE: HY000
(ER_SQL_USER_TABLE_CREATE_WARNING
)
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
ER_SQL_USER_TABLE_CREATE_WARNING
was added in 8.0.2.
Error: 3859
SQLSTATE: HY000
(ER_SQL_USER_TABLE_ALTER_WARNING
)
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
ER_SQL_USER_TABLE_ALTER_WARNING
was added in 8.0.2.
Error: 3860
SQLSTATE: HY000
(ER_ROW_IN_WRONG_PARTITION_PLEASE_REPAIR
)
Message: Table '%s' corrupted: row in wrong partition: %s -- Please REPAIR the table!
ER_ROW_IN_WRONG_PARTITION_PLEASE_REPAIR
was added in 8.0.2.
Error: 3861
SQLSTATE: HY000
(ER_MYISAM_CRASHED_ERROR_IN_THREAD
)
Message: Got an error from thread_id=%u, %s:%d
ER_MYISAM_CRASHED_ERROR_IN_THREAD
was added in 8.0.2.
Error: 3862
SQLSTATE: HY000
(ER_MYISAM_CRASHED_ERROR_IN
)
Message: Got an error from unknown thread, %s:%d
ER_MYISAM_CRASHED_ERROR_IN
was
added in 8.0.2.
Error: 3863
SQLSTATE: HY000
(ER_TOO_MANY_STORAGE_ENGINES
)
Message: Too many storage engines!
ER_TOO_MANY_STORAGE_ENGINES
was
added in 8.0.2.
Error: 3864
SQLSTATE: HY000
(ER_SE_TYPECODE_CONFLICT
)
Message: Storage engine '%s' has conflicting typecode. Assigning value %d.
ER_SE_TYPECODE_CONFLICT
was added
in 8.0.2.
Error: 3865
SQLSTATE: HY000
(ER_TRX_WRITE_SET_OOM
)
Message: Out of memory on transaction write set extraction
ER_TRX_WRITE_SET_OOM
was added in
8.0.2.
Error: 3866
SQLSTATE: HY000
(ER_HANDLERTON_OOM
)
Message: Unable to allocate memory for plugin '%s' handlerton.
ER_HANDLERTON_OOM
was added in
8.0.2.
Error: 3867
SQLSTATE: HY000
(ER_CONN_SHM_LISTENER
)
Message: Shared memory setting up listener
ER_CONN_SHM_LISTENER
was added in
8.0.2.
Error: 3868
SQLSTATE: HY000
(ER_CONN_SHM_CANT_CREATE_SERVICE
)
Message: Can't create shared memory service: %s. : %s
ER_CONN_SHM_CANT_CREATE_SERVICE
was added in 8.0.2.
Error: 3869
SQLSTATE: HY000
(ER_CONN_SHM_CANT_CREATE_CONNECTION
)
Message: Can't create shared memory connection: %s. : %s
ER_CONN_SHM_CANT_CREATE_CONNECTION
was added in 8.0.2.
Error: 3870
SQLSTATE: HY000
(ER_CONN_PIP_CANT_CREATE_EVENT
)
Message: Can't create event, last error=%u
ER_CONN_PIP_CANT_CREATE_EVENT
was
added in 8.0.2.
Error: 3871
SQLSTATE: HY000
(ER_CONN_PIP_CANT_CREATE_PIPE
)
Message: Can't create new named pipe!: %s
ER_CONN_PIP_CANT_CREATE_PIPE
was
added in 8.0.2.
Error: 3872
SQLSTATE: HY000
(ER_CONN_PER_THREAD_NO_THREAD
)
Message: Can't create thread to handle new connection(errno= %d)
ER_CONN_PER_THREAD_NO_THREAD
was
added in 8.0.2.
Error: 3873
SQLSTATE: HY000
(ER_CONN_TCP_NO_SOCKET
)
Message: Failed to create a socket for %s '%s': errno: %d.
ER_CONN_TCP_NO_SOCKET
was added in
8.0.2.
Error: 3874
SQLSTATE: HY000
(ER_CONN_TCP_CREATED
)
Message: Server socket created on IP: '%s'.
ER_CONN_TCP_CREATED
was added in
8.0.2.
Error: 3875
SQLSTATE: HY000
(ER_CONN_TCP_ADDRESS
)
Message: Server hostname (bind-address): '%s'; port: %d
ER_CONN_TCP_ADDRESS
was added in
8.0.2.
Error: 3876
SQLSTATE: HY000
(ER_CONN_TCP_IPV6_AVAILABLE
)
Message: IPv6 is available.
ER_CONN_TCP_IPV6_AVAILABLE
was
added in 8.0.2.
Error: 3877
SQLSTATE: HY000
(ER_CONN_TCP_IPV6_UNAVAILABLE
)
Message: IPv6 is not available.
ER_CONN_TCP_IPV6_UNAVAILABLE
was
added in 8.0.2.
Error: 3878
SQLSTATE: HY000
(ER_CONN_TCP_ERROR_WITH_STRERROR
)
Message: Can't create IP socket: %s
ER_CONN_TCP_ERROR_WITH_STRERROR
was added in 8.0.2.
Error: 3879
SQLSTATE: HY000
(ER_CONN_TCP_CANT_RESOLVE_HOSTNAME
)
Message: Can't start server: cannot resolve hostname!
ER_CONN_TCP_CANT_RESOLVE_HOSTNAME
was added in 8.0.2.
Error: 3880
SQLSTATE: HY000
(ER_CONN_TCP_IS_THERE_ANOTHER_USING_PORT
)
Message: Do you already have another mysqld server running on port: %d ?
ER_CONN_TCP_IS_THERE_ANOTHER_USING_PORT
was added in 8.0.2.
Error: 3881
SQLSTATE: HY000
(ER_CONN_UNIX_IS_THERE_ANOTHER_USING_SOCKET
)
Message: Do you already have another mysqld server running on socket: %s ?
ER_CONN_UNIX_IS_THERE_ANOTHER_USING_SOCKET
was added in 8.0.2.
Error: 3882
SQLSTATE: HY000
(ER_CONN_UNIX_PID_CLAIMED_SOCKET_FILE
)
Message: Another process with pid %d is using unix socket file.
ER_CONN_UNIX_PID_CLAIMED_SOCKET_FILE
was added in 8.0.2.
Error: 3883
SQLSTATE: HY000
(ER_CONN_TCP_CANT_RESET_V6ONLY
)
Message: Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.
ER_CONN_TCP_CANT_RESET_V6ONLY
was
added in 8.0.2.
Error: 3884
SQLSTATE: HY000
(ER_CONN_TCP_BIND_RETRY
)
Message: Retrying bind on TCP/IP port %u
ER_CONN_TCP_BIND_RETRY
was added
in 8.0.2.
Error: 3885
SQLSTATE: HY000
(ER_CONN_TPC_BIND_FAIL
)
Message: Can't start server: Bind on TCP/IP port: %s
ER_CONN_TPC_BIND_FAIL
was added in
8.0.2.
Error: 3886
SQLSTATE: HY000
(ER_CONN_TCP_IP_NOT_LOGGED
)
Message: Fails to print out IP-address.
ER_CONN_TCP_IP_NOT_LOGGED
was
added in 8.0.2.
Error: 3887
SQLSTATE: HY000
(ER_CONN_TCP_RESOLVE_INFO
)
Message: - '%s' resolves to '%s';
ER_CONN_TCP_RESOLVE_INFO
was added
in 8.0.2.
Error: 3888
SQLSTATE: HY000
(ER_CONN_TCP_START_FAIL
)
Message: Can't start server: listen() on TCP/IP port: %s
ER_CONN_TCP_START_FAIL
was added
in 8.0.2.
Error: 3889
SQLSTATE: HY000
(ER_CONN_TCP_LISTEN_FAIL
)
Message: listen() on TCP/IP failed with error %d
ER_CONN_TCP_LISTEN_FAIL
was added
in 8.0.2.
Error: 3890
SQLSTATE: HY000
(ER_CONN_UNIX_PATH_TOO_LONG
)
Message: The socket file path is too long (> %u): %s
ER_CONN_UNIX_PATH_TOO_LONG
was
added in 8.0.2.
Error: 3891
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_FAIL
)
Message: Unable to setup unix socket lock file.
ER_CONN_UNIX_LOCK_FILE_FAIL
was
added in 8.0.2.
Error: 3892
SQLSTATE: HY000
(ER_CONN_UNIX_NO_FD
)
Message: Can't start server: UNIX Socket : %s
ER_CONN_UNIX_NO_FD
was added in
8.0.2.
Error: 3893
SQLSTATE: HY000
(ER_CONN_UNIX_NO_BIND_NO_START
)
Message: Can't start server : Bind on unix socket: %s
ER_CONN_UNIX_NO_BIND_NO_START
was
added in 8.0.2.
Error: 3894
SQLSTATE: HY000
(ER_CONN_UNIX_LISTEN_FAILED
)
Message: listen() on Unix socket failed with error %d
ER_CONN_UNIX_LISTEN_FAILED
was
added in 8.0.2.
Error: 3895
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_GIVING_UP
)
Message: Unable to create unix socket lock file %s after retries.
ER_CONN_UNIX_LOCK_FILE_GIVING_UP
was added in 8.0.2.
Error: 3896
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_CANT_CREATE
)
Message: Could not create unix socket lock file %s.
ER_CONN_UNIX_LOCK_FILE_CANT_CREATE
was added in 8.0.2.
Error: 3897
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_CANT_OPEN
)
Message: Could not open unix socket lock file %s.
ER_CONN_UNIX_LOCK_FILE_CANT_OPEN
was added in 8.0.2.
Error: 3898
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_CANT_READ
)
Message: Could not read unix socket lock file %s.
ER_CONN_UNIX_LOCK_FILE_CANT_READ
was added in 8.0.2.
Error: 3899
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_EMPTY
)
Message: Unix socket lock file is empty %s.
ER_CONN_UNIX_LOCK_FILE_EMPTY
was
added in 8.0.2.
Error: 3900
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_PIDLESS
)
Message: Invalid pid in unix socket lock file %s.
ER_CONN_UNIX_LOCK_FILE_PIDLESS
was
added in 8.0.2.
Error: 3901
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_CANT_WRITE
)
Message: Could not write unix socket lock file %s errno %d.
ER_CONN_UNIX_LOCK_FILE_CANT_WRITE
was added in 8.0.2.
Error: 3902
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_CANT_DELETE
)
Message: Could not remove unix socket lock file %s errno %d.
ER_CONN_UNIX_LOCK_FILE_CANT_DELETE
was added in 8.0.2.
Error: 3903
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_CANT_SYNC
)
Message: Could not sync unix socket lock file %s errno %d.
ER_CONN_UNIX_LOCK_FILE_CANT_SYNC
was added in 8.0.2.
Error: 3904
SQLSTATE: HY000
(ER_CONN_UNIX_LOCK_FILE_CANT_CLOSE
)
Message: Could not close unix socket lock file %s errno %d.
ER_CONN_UNIX_LOCK_FILE_CANT_CLOSE
was added in 8.0.2.
Error: 3905
SQLSTATE: HY000
(ER_CONN_SOCKET_SELECT_FAILED
)
Message: mysqld: Got error %d from select
ER_CONN_SOCKET_SELECT_FAILED
was
added in 8.0.2.
Error: 3906
SQLSTATE: HY000
(ER_CONN_SOCKET_ACCEPT_FAILED
)
Message: Error in accept: %s
ER_CONN_SOCKET_ACCEPT_FAILED
was
added in 8.0.2.
Error: 3907
SQLSTATE: HY000
(ER_AUTH_RSA_CANT_FIND
)
Message: RSA %s key file not found: %s. Some authentication plugins will not work.
ER_AUTH_RSA_CANT_FIND
was added in
8.0.2.
Error: 3908
SQLSTATE: HY000
(ER_AUTH_RSA_CANT_PARSE
)
Message: Failure to parse RSA %s key (file exists): %s: %s
ER_AUTH_RSA_CANT_PARSE
was added
in 8.0.2.
Error: 3909
SQLSTATE: HY000
(ER_AUTH_RSA_CANT_READ
)
Message: Failure to read key file: %s
ER_AUTH_RSA_CANT_READ
was added in
8.0.2.
Error: 3910
SQLSTATE: HY000
(ER_AUTH_RSA_FILES_NOT_FOUND
)
Message: RSA key files not found. Some authentication plugins will not work.
ER_AUTH_RSA_FILES_NOT_FOUND
was
added in 8.0.2.
Error: 3911
SQLSTATE: HY000
(ER_CONN_ATTR_TRUNCATED
)
Message: Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %s
ER_CONN_ATTR_TRUNCATED
was added
in 8.0.2.
Error: 3912
SQLSTATE: HY000
(ER_X509_CIPHERS_MISMATCH
)
Message: X509 ciphers mismatch: should be '%s' but is '%s'
ER_X509_CIPHERS_MISMATCH
was added
in 8.0.2.
Error: 3913
SQLSTATE: HY000
(ER_X509_ISSUER_MISMATCH
)
Message: X509 issuer mismatch: should be '%s' but is '%s'
ER_X509_ISSUER_MISMATCH
was added
in 8.0.2.
Error: 3914
SQLSTATE: HY000
(ER_X509_SUBJECT_MISMATCH
)
Message: X509 subject mismatch: should be '%s' but is '%s'
ER_X509_SUBJECT_MISMATCH
was added
in 8.0.2.
Error: 3915
SQLSTATE: HY000
(ER_AUTH_CANT_ACTIVATE_ROLE
)
Message: Failed to activate default role %s for %s
ER_AUTH_CANT_ACTIVATE_ROLE
was
added in 8.0.2.
Error: 3916
SQLSTATE: HY000
(ER_X509_NEEDS_RSA_PRIVKEY
)
Message: Could not generate RSA private key required for X509 certificate.
ER_X509_NEEDS_RSA_PRIVKEY
was
added in 8.0.2.
Error: 3917
SQLSTATE: HY000
(ER_X509_CANT_WRITE_KEY
)
Message: Could not write key file: %s
ER_X509_CANT_WRITE_KEY
was added
in 8.0.2.
Error: 3918
SQLSTATE: HY000
(ER_X509_CANT_CHMOD_KEY
)
Message: Could not set file permission for %s
ER_X509_CANT_CHMOD_KEY
was added
in 8.0.2.
Error: 3919
SQLSTATE: HY000
(ER_X509_CANT_READ_CA_KEY
)
Message: Could not read CA key file: %s
ER_X509_CANT_READ_CA_KEY
was added
in 8.0.2.
Error: 3920
SQLSTATE: HY000
(ER_X509_CANT_READ_CA_CERT
)
Message: Could not read CA certificate file: %s
ER_X509_CANT_READ_CA_CERT
was
added in 8.0.2.
Error: 3921
SQLSTATE: HY000
(ER_X509_CANT_CREATE_CERT
)
Message: Could not generate X509 certificate.
ER_X509_CANT_CREATE_CERT
was added
in 8.0.2.
Error: 3922
SQLSTATE: HY000
(ER_X509_CANT_WRITE_CERT
)
Message: Could not write certificate file: %s
ER_X509_CANT_WRITE_CERT
was added
in 8.0.2.
Error: 3923
SQLSTATE: HY000
(ER_AUTH_CANT_CREATE_RSA_PAIR
)
Message: Could not generate RSA Private/Public key pair
ER_AUTH_CANT_CREATE_RSA_PAIR
was
added in 8.0.2.
Error: 3924
SQLSTATE: HY000
(ER_AUTH_CANT_WRITE_PRIVKEY
)
Message: Could not write private key file: %s
ER_AUTH_CANT_WRITE_PRIVKEY
was
added in 8.0.2.
Error: 3925
SQLSTATE: HY000
(ER_AUTH_CANT_WRITE_PUBKEY
)
Message: Could not write public key file: %s
ER_AUTH_CANT_WRITE_PUBKEY
was
added in 8.0.2.
Error: 3926
SQLSTATE: HY000
(ER_AUTH_SSL_CONF_PREVENTS_CERT_GENERATION
)
Message: Skipping generation of SSL certificates as options related to SSL are specified.
ER_AUTH_SSL_CONF_PREVENTS_CERT_GENERATION
was added in 8.0.2.
Error: 3927
SQLSTATE: HY000
(ER_AUTH_USING_EXISTING_CERTS
)
Message: Skipping generation of SSL certificates as certificate files are present in data directory.
ER_AUTH_USING_EXISTING_CERTS
was
added in 8.0.2.
Error: 3928
SQLSTATE: HY000
(ER_AUTH_CERTS_SAVED_TO_DATADIR
)
Message: Auto generated SSL certificates are placed in data directory.
ER_AUTH_CERTS_SAVED_TO_DATADIR
was
added in 8.0.2.
Error: 3929
SQLSTATE: HY000
(ER_AUTH_CERT_GENERATION_DISABLED
)
Message: Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.
ER_AUTH_CERT_GENERATION_DISABLED
was added in 8.0.2.
Error: 3930
SQLSTATE: HY000
(ER_AUTH_RSA_CONF_PREVENTS_KEY_GENERATION
)
Message: Skipping generation of RSA key pair as options related to RSA keys are specified.
ER_AUTH_RSA_CONF_PREVENTS_KEY_GENERATION
was added in 8.0.2.
Error: 3931
SQLSTATE: HY000
(ER_AUTH_KEY_GENERATION_SKIPPED_PAIR_PRESENT
)
Message: Skipping generation of RSA key pair as key files are present in data directory.
ER_AUTH_KEY_GENERATION_SKIPPED_PAIR_PRESENT
was added in 8.0.2.
Error: 3932
SQLSTATE: HY000
(ER_AUTH_KEYS_SAVED_TO_DATADIR
)
Message: Auto generated RSA key files are placed in data directory.
ER_AUTH_KEYS_SAVED_TO_DATADIR
was
added in 8.0.2.
Error: 3933
SQLSTATE: HY000
(ER_AUTH_KEY_GENERATION_DISABLED
)
Message: Skipping generation of RSA key pair as --sha256_password_auto_generate_rsa_keys is set to OFF.
ER_AUTH_KEY_GENERATION_DISABLED
was added in 8.0.2.
Error: 3934
SQLSTATE: HY000
(ER_AUTHCACHE_PROXIES_PRIV_SKIPPED_NEEDS_RESOLVE
)
Message: 'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.
ER_AUTHCACHE_PROXIES_PRIV_SKIPPED_NEEDS_RESOLVE
was added in 8.0.2.
Error: 3935
SQLSTATE: HY000
(ER_AUTHCACHE_PLUGIN_MISSING
)
Message: The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.
ER_AUTHCACHE_PLUGIN_MISSING
was
added in 8.0.2.
Error: 3936
SQLSTATE: HY000
(ER_AUTHCACHE_PLUGIN_CONFIG
)
Message: The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.
ER_AUTHCACHE_PLUGIN_CONFIG
was
added in 8.0.2.
Error: 3937
SQLSTATE: HY000
(ER_AUTHCACHE_ROLE_TABLES_DODGY
)
Message: Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless mysql_upgrade is executed.
ER_AUTHCACHE_ROLE_TABLES_DODGY
was
added in 8.0.2.
Error: 3938
SQLSTATE: HY000
(ER_AUTHCACHE_USER_SKIPPED_NEEDS_RESOLVE
)
Message: 'user' entry '%s@%s' ignored in --skip-name-resolve mode.
ER_AUTHCACHE_USER_SKIPPED_NEEDS_RESOLVE
was added in 8.0.2.
Error: 3939
SQLSTATE: HY000
(ER_AUTHCACHE_USER_TABLE_DODGY
)
Message: Fatal error: mysql.user table is damaged. Please run mysql_upgrade.
ER_AUTHCACHE_USER_TABLE_DODGY
was
added in 8.0.2.
Error: 3940
SQLSTATE: HY000
(ER_AUTHCACHE_USER_IGNORED_DEPRECATED_PASSWORD
)
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.
ER_AUTHCACHE_USER_IGNORED_DEPRECATED_PASSWORD
was added in 8.0.2.
Error: 3941
SQLSTATE: HY000
(ER_AUTHCACHE_USER_IGNORED_NEEDS_PLUGIN
)
Message: User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.
ER_AUTHCACHE_USER_IGNORED_NEEDS_PLUGIN
was added in 8.0.2.
Error: 3942
SQLSTATE: HY000
(ER_AUTHCACHE_USER_IGNORED_INVALID_PASSWORD
)
Message: Found invalid password for user: '%s@%s'; Ignoring user
ER_AUTHCACHE_USER_IGNORED_INVALID_PASSWORD
was added in 8.0.2.
Error: 3943
SQLSTATE: HY000
(ER_AUTHCACHE_EXPIRED_PASSWORD_UNSUPPORTED
)
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.
ER_AUTHCACHE_EXPIRED_PASSWORD_UNSUPPORTED
was added in 8.0.2.
Error: 3944
SQLSTATE: HY000
(ER_NO_SUPER_WITHOUT_USER_PLUGIN
)
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 we were not able to substitute for empty plugin column. Probably because of pre 4.1 password hash. If your account is disabled you will need to: 1. Stop the server and restart it with --skip-grant-tables. 2. Run mysql_upgrade. 3. Restart the server with the parameters you normally use. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual
ER_NO_SUPER_WITHOUT_USER_PLUGIN
was added in 8.0.2.
Error: 3945
SQLSTATE: HY000
(ER_AUTHCACHE_DB_IGNORED_EMPTY_NAME
)
Message: Found an entry in the 'db' table with empty database name; Skipped
ER_AUTHCACHE_DB_IGNORED_EMPTY_NAME
was added in 8.0.2.
Error: 3946
SQLSTATE: HY000
(ER_AUTHCACHE_DB_SKIPPED_NEEDS_RESOLVE
)
Message: 'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.
ER_AUTHCACHE_DB_SKIPPED_NEEDS_RESOLVE
was added in 8.0.2.
Error: 3947
SQLSTATE: HY000
(ER_AUTHCACHE_DB_ENTRY_LOWERCASED_REVOKE_WILL_FAIL
)
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.
ER_AUTHCACHE_DB_ENTRY_LOWERCASED_REVOKE_WILL_FAIL
was added in 8.0.2.
Error: 3948
SQLSTATE: HY000
(ER_AUTHCACHE_TABLE_PROXIES_PRIV_MISSING
)
Message: Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
ER_AUTHCACHE_TABLE_PROXIES_PRIV_MISSING
was added in 8.0.2.
Error: 3949
SQLSTATE: HY000
(ER_AUTHCACHE_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
)
Message: Fatal error: Can't open and lock privilege tables: %s
ER_AUTHCACHE_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
was added in 8.0.2.
Error: 3950
SQLSTATE: HY000
(ER_AUTHCACHE_CANT_INIT_GRANT_SUBSYSTEM
)
Message: Fatal: can't initialize grant subsystem - '%s'
ER_AUTHCACHE_CANT_INIT_GRANT_SUBSYSTEM
was added in 8.0.2.
Error: 3951
SQLSTATE: HY000
(ER_AUTHCACHE_PROCS_PRIV_SKIPPED_NEEDS_RESOLVE
)
Message: 'procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.
ER_AUTHCACHE_PROCS_PRIV_SKIPPED_NEEDS_RESOLVE
was added in 8.0.2.
Error: 3952
SQLSTATE: HY000
(ER_AUTHCACHE_PROCS_PRIV_ENTRY_IGNORED_BAD_ROUTINE_TYPE
)
Message: 'procs_priv' entry '%s' ignored, bad routine type
ER_AUTHCACHE_PROCS_PRIV_ENTRY_IGNORED_BAD_ROUTINE_TYPE
was added in 8.0.2.
Error: 3953
SQLSTATE: HY000
(ER_AUTHCACHE_TABLES_PRIV_SKIPPED_NEEDS_RESOLVE
)
Message: 'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.
ER_AUTHCACHE_TABLES_PRIV_SKIPPED_NEEDS_RESOLVE
was added in 8.0.2.
Error: 3954
SQLSTATE: HY000
(ER_USER_NOT_IN_EXTRA_USERS_BINLOG_POSSIBLY_INCOMPLETE
)
Message: Failed to add %s in extra_users. Binary log entry may miss some of the users.
ER_USER_NOT_IN_EXTRA_USERS_BINLOG_POSSIBLY_INCOMPLETE
was added in 8.0.2.
Error: 3955
SQLSTATE: HY000
(ER_DD_SCHEMA_NOT_FOUND
)
Message: Unable to start server. The data dictionary schema '%s' does not exist.
ER_DD_SCHEMA_NOT_FOUND
was added
in 8.0.2.
Error: 3956
SQLSTATE: HY000
(ER_DD_TABLE_NOT_FOUND
)
Message: Unable to start server. The data dictionary table '%s' does not exist.
ER_DD_TABLE_NOT_FOUND
was added in
8.0.2.
Error: 3957
SQLSTATE: HY000
(ER_DD_SE_INIT_FAILED
)
Message: Failed to initialize DD Storage Engine
ER_DD_SE_INIT_FAILED
was added in
8.0.2.
Error: 3958
SQLSTATE: HY000
(ER_DD_ABORTING_PARTIAL_UPGRADE
)
Message: Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.
ER_DD_ABORTING_PARTIAL_UPGRADE
was
added in 8.0.2.
Error: 3959
SQLSTATE: HY000
(ER_DD_FRM_EXISTS_FOR_TABLE
)
Message: Found .frm file with same name as one of the Dictionary Tables.
ER_DD_FRM_EXISTS_FOR_TABLE
was
added in 8.0.2.
Error: 3960
SQLSTATE: HY000
(ER_DD_CREATED_FOR_UPGRADE
)
Message: Created Data Dictionary for upgrade
ER_DD_CREATED_FOR_UPGRADE
was
added in 8.0.2.
Error: 3961
SQLSTATE: HY000
(ER_ERRMSG_CANT_FIND_FILE
)
Message: Can't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.
ER_ERRMSG_CANT_FIND_FILE
was added
in 8.0.2.
Error: 3962
SQLSTATE: HY000
(ER_ERRMSG_LOADING_55_STYLE
)
Message: Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.
ER_ERRMSG_LOADING_55_STYLE
was
added in 8.0.2.
Error: 3963
SQLSTATE: HY000
(ER_ERRMSG_MISSING_IN_FILE
)
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!
ER_ERRMSG_MISSING_IN_FILE
was
added in 8.0.2.
Error: 3964
SQLSTATE: HY000
(ER_ERRMSG_OOM
)
Message: Not enough memory for messagefile '%s'
ER_ERRMSG_OOM
was added in 8.0.2.
Error: 3965
SQLSTATE: HY000
(ER_ERRMSG_CANT_READ
)
Message: Can't read from messagefile '%s'
ER_ERRMSG_CANT_READ
was added in
8.0.2.
Error: 3966
SQLSTATE: HY000
(ER_TABLE_INCOMPATIBLE_DECIMAL_FIELD
)
Message: Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!
ER_TABLE_INCOMPATIBLE_DECIMAL_FIELD
was added in 8.0.2.
Error: 3967
SQLSTATE: HY000
(ER_TABLE_INCOMPATIBLE_YEAR_FIELD
)
Message: Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!
ER_TABLE_INCOMPATIBLE_YEAR_FIELD
was added in 8.0.2.
Error: 3968
SQLSTATE: HY000
(ER_INVALID_CHARSET_AND_DEFAULT_IS_MB
)
Message: '%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
ER_INVALID_CHARSET_AND_DEFAULT_IS_MB
was added in 8.0.2.
Error: 3969
SQLSTATE: HY000
(ER_TABLE_WRONG_KEY_DEFINITION
)
Message: Found wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!
ER_TABLE_WRONG_KEY_DEFINITION
was
added in 8.0.2.
Error: 3970
SQLSTATE: HY000
(ER_CANT_OPEN_FRM_FILE
)
Message: Unable to open file %s
ER_CANT_OPEN_FRM_FILE
was added in
8.0.2.
Error: 3971
SQLSTATE: HY000
(ER_CANT_READ_FRM_FILE
)
Message: Error in reading file %s
ER_CANT_READ_FRM_FILE
was added in
8.0.2.
Error: 3972
SQLSTATE: HY000
(ER_TABLE_CREATED_WITH_DIFFERENT_VERSION
)
Message: Table '%s' was created with a different version of MySQL and cannot be read
ER_TABLE_CREATED_WITH_DIFFERENT_VERSION
was added in 8.0.2.
Error: 3973
SQLSTATE: HY000
(ER_VIEW_UNPARSABLE
)
Message: Unable to read view %s
ER_VIEW_UNPARSABLE
was added in
8.0.2.
Error: 3974
SQLSTATE: HY000
(ER_FILE_TYPE_UNKNOWN
)
Message: File %s has unknown type in its header.
ER_FILE_TYPE_UNKNOWN
was added in
8.0.2.
Error: 3975
SQLSTATE: HY000
(ER_INVALID_INFO_IN_FRM
)
Message: Incorrect information in file %s
ER_INVALID_INFO_IN_FRM
was added
in 8.0.2.
Error: 3976
SQLSTATE: HY000
(ER_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
)
Message: Can't open and lock privilege tables: %s
ER_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
was added in 8.0.2.
Error: 3977
SQLSTATE: HY000
(ER_AUDIT_PLUGIN_DOES_NOT_SUPPORT_AUDIT_AUTH_EVENTS
)
Message: Plugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.
ER_AUDIT_PLUGIN_DOES_NOT_SUPPORT_AUDIT_AUTH_EVENTS
was added in 8.0.2.
Error: 3978
SQLSTATE: HY000
(ER_AUDIT_PLUGIN_HAS_INVALID_DATA
)
Message: Plugin '%s' has invalid data.
ER_AUDIT_PLUGIN_HAS_INVALID_DATA
was added in 8.0.2.
Error: 3979
SQLSTATE: HY000
(ER_TZ_OOM_INITIALIZING_TIME_ZONES
)
Message: Fatal error: OOM while initializing time zones
ER_TZ_OOM_INITIALIZING_TIME_ZONES
was added in 8.0.2.
Error: 3980
SQLSTATE: HY000
(ER_TZ_CANT_OPEN_AND_LOCK_TIME_ZONE_TABLE
)
Message: Can't open and lock time zone table: %s trying to live without them
ER_TZ_CANT_OPEN_AND_LOCK_TIME_ZONE_TABLE
was added in 8.0.2.
Error: 3981
SQLSTATE: HY000
(ER_TZ_OOM_LOADING_LEAP_SECOND_TABLE
)
Message: Fatal error: Out of memory while loading mysql.time_zone_leap_second table
ER_TZ_OOM_LOADING_LEAP_SECOND_TABLE
was added in 8.0.2.
Error: 3982
SQLSTATE: HY000
(ER_TZ_TOO_MANY_LEAPS_IN_LEAP_SECOND_TABLE
)
Message: Fatal error: While loading mysql.time_zone_leap_second table: too much leaps
ER_TZ_TOO_MANY_LEAPS_IN_LEAP_SECOND_TABLE
was added in 8.0.2.
Error: 3983
SQLSTATE: HY000
(ER_TZ_ERROR_LOADING_LEAP_SECOND_TABLE
)
Message: Fatal error: Error while loading mysql.time_zone_leap_second table
ER_TZ_ERROR_LOADING_LEAP_SECOND_TABLE
was added in 8.0.2.
Error: 3984
SQLSTATE: HY000
(ER_TZ_UNKNOWN_OR_ILLEGAL_DEFAULT_TIME_ZONE
)
Message: Fatal error: Illegal or unknown default time zone '%s'
ER_TZ_UNKNOWN_OR_ILLEGAL_DEFAULT_TIME_ZONE
was added in 8.0.2.
Error: 3985
SQLSTATE: HY000
(ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE
)
Message: Can't find description of time zone '%.*s'
ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE
was added in 8.0.2.
Error: 3986
SQLSTATE: HY000
(ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE_ID
)
Message: Can't find description of time zone '%u'
ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE_ID
was added in 8.0.2.
Error: 3987
SQLSTATE: HY000
(ER_TZ_TRANSITION_TYPE_TABLE_TYPE_TOO_LARGE
)
Message: Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type id
ER_TZ_TRANSITION_TYPE_TABLE_TYPE_TOO_LARGE
was added in 8.0.2.
Error: 3988
SQLSTATE: HY000
(ER_TZ_TRANSITION_TYPE_TABLE_ABBREVIATIONS_EXCEED_SPACE
)
Message: Error while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviations
ER_TZ_TRANSITION_TYPE_TABLE_ABBREVIATIONS_EXCEED_SPACE
was added in 8.0.2.
Error: 3989
SQLSTATE: HY000
(ER_TZ_TRANSITION_TYPE_TABLE_LOAD_ERROR
)
Message: Error while loading time zone description from mysql.time_zone_transition_type table
ER_TZ_TRANSITION_TYPE_TABLE_LOAD_ERROR
was added in 8.0.2.
Error: 3990
SQLSTATE: HY000
(ER_TZ_TRANSITION_TABLE_TOO_MANY_TRANSITIONS
)
Message: Error while loading time zone description from mysql.time_zone_transition table: too much transitions
ER_TZ_TRANSITION_TABLE_TOO_MANY_TRANSITIONS
was added in 8.0.2.
Error: 3991
SQLSTATE: HY000
(ER_TZ_TRANSITION_TABLE_BAD_TRANSITION_TYPE
)
Message: Error while loading time zone description from mysql.time_zone_transition table: bad transition type id
ER_TZ_TRANSITION_TABLE_BAD_TRANSITION_TYPE
was added in 8.0.2.
Error: 3992
SQLSTATE: HY000
(ER_TZ_TRANSITION_TABLE_LOAD_ERROR
)
Message: Error while loading time zone description from mysql.time_zone_transition table
ER_TZ_TRANSITION_TABLE_LOAD_ERROR
was added in 8.0.2.
Error: 3993
SQLSTATE: HY000
(ER_TZ_NO_TRANSITION_TYPES_IN_TIME_ZONE
)
Message: loading time zone without transition types
ER_TZ_NO_TRANSITION_TYPES_IN_TIME_ZONE
was added in 8.0.2.
Error: 3994
SQLSTATE: HY000
(ER_TZ_OOM_LOADING_TIME_ZONE_DESCRIPTION
)
Message: Out of memory while loading time zone description
ER_TZ_OOM_LOADING_TIME_ZONE_DESCRIPTION
was added in 8.0.2.
Error: 3995
SQLSTATE: HY000
(ER_TZ_CANT_BUILD_MKTIME_MAP
)
Message: Unable to build mktime map for time zone
ER_TZ_CANT_BUILD_MKTIME_MAP
was
added in 8.0.2.
Error: 3996
SQLSTATE: HY000
(ER_TZ_OOM_WHILE_LOADING_TIME_ZONE
)
Message: Out of memory while loading time zone
ER_TZ_OOM_WHILE_LOADING_TIME_ZONE
was added in 8.0.2.
Error: 3997
SQLSTATE: HY000
(ER_TZ_OOM_WHILE_SETTING_TIME_ZONE
)
Message: Fatal error: Out of memory while setting new time zone
ER_TZ_OOM_WHILE_SETTING_TIME_ZONE
was added in 8.0.2.
Error: 3998
SQLSTATE: HY000
(ER_SLAVE_SQL_THREAD_STOPPED_UNTIL_CONDITION_BAD
)
Message: Slave SQL thread is stopped because UNTIL condition is bad(%s:%llu).
ER_SLAVE_SQL_THREAD_STOPPED_UNTIL_CONDITION_BAD
was added in 8.0.2.
Error: 3999
SQLSTATE: HY000
(ER_SLAVE_SQL_THREAD_STOPPED_UNTIL_POSITION_REACHED
)
Message: Slave SQL thread stopped because it reached its UNTIL position %llu
ER_SLAVE_SQL_THREAD_STOPPED_UNTIL_POSITION_REACHED
was added in 8.0.2.
Error: 4000
SQLSTATE: HY000
(ER_SLAVE_SQL_THREAD_STOPPED_BEFORE_GTIDS_ALREADY_APPLIED
)
Message: Slave SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already applied
ER_SLAVE_SQL_THREAD_STOPPED_BEFORE_GTIDS_ALREADY_APPLIED
was added in 8.0.2.
Error: 4001
SQLSTATE: HY000
(ER_SLAVE_SQL_THREAD_STOPPED_BEFORE_GTIDS_REACHED
)
Message: Slave SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %s
ER_SLAVE_SQL_THREAD_STOPPED_BEFORE_GTIDS_REACHED
was added in 8.0.2.
Error: 4002
SQLSTATE: HY000
(ER_SLAVE_SQL_THREAD_STOPPED_AFTER_GTIDS_REACHED
)
Message: Slave SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %s
ER_SLAVE_SQL_THREAD_STOPPED_AFTER_GTIDS_REACHED
was added in 8.0.2.
Error: 4003
SQLSTATE: HY000
(ER_SLAVE_SQL_THREAD_STOPPED_GAP_TRX_PROCESSED
)
Message: Slave SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous slave session.
ER_SLAVE_SQL_THREAD_STOPPED_GAP_TRX_PROCESSED
was added in 8.0.2.
Error: 4004
SQLSTATE: HY000
(ER_GROUP_REPLICATION_PLUGIN_NOT_INSTALLED
)
Message: Group Replication plugin is not installed.
ER_GROUP_REPLICATION_PLUGIN_NOT_INSTALLED
was added in 8.0.2.
Error: 4005
SQLSTATE: HY000
(ER_GTID_ALREADY_ADDED_BY_USER
)
Message: The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.
ER_GTID_ALREADY_ADDED_BY_USER
was
added in 8.0.2.
Error: 4006
SQLSTATE: HY000
(ER_FAILED_TO_DELETE_FROM_GTID_EXECUTED_TABLE
)
Message: Failed to delete the row: '%s' from the gtid_executed table.
ER_FAILED_TO_DELETE_FROM_GTID_EXECUTED_TABLE
was added in 8.0.2.
Error: 4007
SQLSTATE: HY000
(ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE
)
Message: Failed to compress the gtid_executed table.
ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE
was added in 8.0.2.
Error: 4008
SQLSTATE: HY000
(ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE_OOM
)
Message: Failed to compress the gtid_executed table, because it is failed to allocate the THD.
ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE_OOM
was added in 8.0.2.
Error: 4009
SQLSTATE: HY000
(ER_FAILED_TO_INIT_THREAD_ATTR_FOR_GTID_TABLE_COMPRESSION
)
Message: Failed to initialize thread attribute when creating compression thread.
ER_FAILED_TO_INIT_THREAD_ATTR_FOR_GTID_TABLE_COMPRESSION
was added in 8.0.2.
Error: 4010
SQLSTATE: HY000
(ER_FAILED_TO_CREATE_GTID_TABLE_COMPRESSION_THREAD
)
Message: Can not create thread to compress gtid_executed table (errno= %d)
ER_FAILED_TO_CREATE_GTID_TABLE_COMPRESSION_THREAD
was added in 8.0.2.
Error: 4011
SQLSTATE: HY000
(ER_FAILED_TO_JOIN_GTID_TABLE_COMPRESSION_THREAD
)
Message: Could not join gtid_executed table compression thread. error:%d
ER_FAILED_TO_JOIN_GTID_TABLE_COMPRESSION_THREAD
was added in 8.0.2.
Error: 4012
SQLSTATE: HY000
(ER_NPIPE_FAILED_TO_INIT_SECURITY_DESCRIPTOR
)
Message: Can't start server : Initialize security descriptor: %s
ER_NPIPE_FAILED_TO_INIT_SECURITY_DESCRIPTOR
was added in 8.0.2.
Error: 4013
SQLSTATE: HY000
(ER_NPIPE_FAILED_TO_SET_SECURITY_DESCRIPTOR
)
Message: Can't start server : Set security descriptor: %s
ER_NPIPE_FAILED_TO_SET_SECURITY_DESCRIPTOR
was added in 8.0.2.
Error: 4014
SQLSTATE: HY000
(ER_NPIPE_PIPE_ALREADY_IN_USE
)
Message: Can't start server : Named Pipe "%s" already in use.
ER_NPIPE_PIPE_ALREADY_IN_USE
was
added in 8.0.2.
Error: 4015
SQLSTATE: HY000
(ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS_ON_START
)
Message: NDB Slave : At SQL thread start applying epoch %llu/%llu (%llu) from Master ServerId %u which is lower than previously applied epoch %llu/%llu (%llu). Group Master Log : %s Group Master Log Pos : %llu. Check slave positioning.
ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS_ON_START
was added in 8.0.2.
Error: 4016
SQLSTATE: HY000
(ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS
)
Message: NDB Slave : SQL thread stopped as applying epoch %llu/%llu (%llu) from Master ServerId %u which is lower than previously applied epoch %llu/%llu (%llu). Group Master Log : %s Group Master Log Pos : %llu
ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS
was added in 8.0.2.
Error: 4017
SQLSTATE: HY000
(ER_NDB_SLAVE_SAW_ALREADY_COMMITTED_EPOCH
)
Message: NDB Slave : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u. Group Master Log : %s Group Master Log Pos : %llu.
ER_NDB_SLAVE_SAW_ALREADY_COMMITTED_EPOCH
was added in 8.0.2.
Error: 4018
SQLSTATE: HY000
(ER_NDB_SLAVE_PREVIOUS_EPOCH_NOT_COMMITTED
)
Message: NDB Slave : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed. Master server id : %u. Group Master Log : %s Group Master Log Pos : %llu.
ER_NDB_SLAVE_PREVIOUS_EPOCH_NOT_COMMITTED
was added in 8.0.2.
Error: 4019
SQLSTATE: HY000
(ER_NDB_SLAVE_MISSING_DATA_FOR_TIMESTAMP_COLUMN
)
Message: NDB Slave: missing data for %s timestamp column %u.
ER_NDB_SLAVE_MISSING_DATA_FOR_TIMESTAMP_COLUMN
was added in 8.0.2.
Error: 4020
SQLSTATE: HY000
(ER_NDB_SLAVE_LOGGING_EXCEPTIONS_TO
)
Message: NDB Slave: Table %s.%s logging exceptions to %s.%s
ER_NDB_SLAVE_LOGGING_EXCEPTIONS_TO
was added in 8.0.2.
Error: 4021
SQLSTATE: HY000
(ER_NDB_SLAVE_LOW_EPOCH_RESOLUTION
)
Message: NDB Slave: Table %s.%s : %s, low epoch resolution
ER_NDB_SLAVE_LOW_EPOCH_RESOLUTION
was added in 8.0.2.
Error: 4022
SQLSTATE: HY000
(ER_NDB_INFO_FOUND_UNEXPECTED_FIELD_TYPE
)
Message: Found unexpected field type %u
ER_NDB_INFO_FOUND_UNEXPECTED_FIELD_TYPE
was added in 8.0.2.
Error: 4023
SQLSTATE: HY000
(ER_NDB_INFO_FAILED_TO_CREATE_NDBINFO
)
Message: Failed to create NdbInfo
ER_NDB_INFO_FAILED_TO_CREATE_NDBINFO
was added in 8.0.2.
Error: 4024
SQLSTATE: HY000
(ER_NDB_INFO_FAILED_TO_INIT_NDBINFO
)
Message: Failed to init NdbInfo
ER_NDB_INFO_FAILED_TO_INIT_NDBINFO
was added in 8.0.2.
Error: 4025
SQLSTATE: HY000
(ER_NDB_CLUSTER_WRONG_NUMBER_OF_FUNCTION_ARGUMENTS
)
Message: ndb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u
ER_NDB_CLUSTER_WRONG_NUMBER_OF_FUNCTION_ARGUMENTS
was added in 8.0.2.
Error: 4026
SQLSTATE: HY000
(ER_NDB_CLUSTER_SCHEMA_INFO
)
Message: %s - %s.%s
ER_NDB_CLUSTER_SCHEMA_INFO
was
added in 8.0.2.
Error: 4027
SQLSTATE: HY000
(ER_NDB_CLUSTER_GENERIC_MESSAGE
)
Message: %s
ER_NDB_CLUSTER_GENERIC_MESSAGE
was
added in 8.0.2.
Error: 4028
SQLSTATE: HY000
(ER_RPL_CANT_OPEN_INFO_TABLE
)
Message: Info table is not ready to be used. Table '%s.%s' cannot be opened.
ER_RPL_CANT_OPEN_INFO_TABLE
was
added in 8.0.2.
Error: 4029
SQLSTATE: HY000
(ER_RPL_CANT_SCAN_INFO_TABLE
)
Message: Info table is not ready to be used. Table '%s.%s' cannot be scanned.
ER_RPL_CANT_SCAN_INFO_TABLE
was
added in 8.0.2.
Error: 4030
SQLSTATE: HY000
(ER_RPL_CORRUPTED_INFO_TABLE
)
Message: Corrupted table %s.%s. Check out table definition.
ER_RPL_CORRUPTED_INFO_TABLE
was
added in 8.0.2.
Error: 4031
SQLSTATE: HY000
(ER_RPL_CORRUPTED_KEYS_IN_INFO_TABLE
)
Message: Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.
ER_RPL_CORRUPTED_KEYS_IN_INFO_TABLE
was added in 8.0.2.
Error: 4032
SQLSTATE: HY000
(ER_RPL_WORKER_ID_IS
)
Message: Choosing worker id %lu, the following is going to be %lu
ER_RPL_WORKER_ID_IS
was added in
8.0.2.
Error: 4033
SQLSTATE: HY000
(ER_RPL_INCONSISTENT_TIMESTAMPS_IN_TRX
)
Message: Transaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)
ER_RPL_INCONSISTENT_TIMESTAMPS_IN_TRX
was added in 8.0.2.
Error: 4034
SQLSTATE: HY000
(ER_RPL_INCONSISTENT_SEQUENCE_NO_IN_TRX
)
Message: Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)
ER_RPL_INCONSISTENT_SEQUENCE_NO_IN_TRX
was added in 8.0.2.
Error: 4035
SQLSTATE: HY000
(ER_RPL_CHANNELS_REQUIRE_TABLES_AS_INFO_REPOSITORIES
)
Message: For the creation of replication channels the master info and relay log info repositories must be set to TABLE
ER_RPL_CHANNELS_REQUIRE_TABLES_AS_INFO_REPOSITORIES
was added in 8.0.2.
Error: 4036
SQLSTATE: HY000
(ER_RPL_CHANNELS_REQUIRE_NON_ZERO_SERVER_ID
)
Message: For the creation of replication channels the server id must be different from 0
ER_RPL_CHANNELS_REQUIRE_NON_ZERO_SERVER_ID
was added in 8.0.2.
Error: 4037
SQLSTATE: HY000
(ER_RPL_REPO_SHOULD_BE_TABLE
)
Message: Slave: Wrong repository. Repository should be TABLE
ER_RPL_REPO_SHOULD_BE_TABLE
was
added in 8.0.2.
Error: 4038
SQLSTATE: HY000
(ER_RPL_ERROR_CREATING_MASTER_INFO
)
Message: Error creating master info: %s.
ER_RPL_ERROR_CREATING_MASTER_INFO
was added in 8.0.2.
Error: 4039
SQLSTATE: HY000
(ER_RPL_ERROR_CHANGING_MASTER_INFO_REPO_TYPE
)
Message: Error changing the type of master info's repository: %s.
ER_RPL_ERROR_CHANGING_MASTER_INFO_REPO_TYPE
was added in 8.0.2.
Error: 4040
SQLSTATE: HY000
(ER_RPL_CHANGING_RELAY_LOG_INFO_REPO_TYPE_FAILED_DUE_TO_GAPS
)
Message: It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.
ER_RPL_CHANGING_RELAY_LOG_INFO_REPO_TYPE_FAILED_DUE_TO_GAPS
was added in 8.0.2.
Error: 4041
SQLSTATE: HY000
(ER_RPL_ERROR_CREATING_RELAY_LOG_INFO
)
Message: Error creating relay log info: %s.
ER_RPL_ERROR_CREATING_RELAY_LOG_INFO
was added in 8.0.2.
Error: 4042
SQLSTATE: HY000
(ER_RPL_ERROR_CHANGING_RELAY_LOG_INFO_REPO_TYPE
)
Message: Error changing the type of relay log info's repository: %s.
ER_RPL_ERROR_CHANGING_RELAY_LOG_INFO_REPO_TYPE
was added in 8.0.2.
Error: 4043
SQLSTATE: HY000
(ER_RPL_FAILED_TO_DELETE_FROM_SLAVE_WORKERS_INFO_REPOSITORY
)
Message: Could not delete from Slave Workers info repository.
ER_RPL_FAILED_TO_DELETE_FROM_SLAVE_WORKERS_INFO_REPOSITORY
was added in 8.0.2.
Error: 4044
SQLSTATE: HY000
(ER_RPL_FAILED_TO_RESET_STATE_IN_SLAVE_INFO_REPOSITORY
)
Message: Could not store the reset Slave Worker state into the slave info repository.
ER_RPL_FAILED_TO_RESET_STATE_IN_SLAVE_INFO_REPOSITORY
was added in 8.0.2.
Error: 4045
SQLSTATE: HY000
(ER_RPL_ERROR_CHECKING_REPOSITORY
)
Message: Error in checking %s repository info type of %s.
ER_RPL_ERROR_CHECKING_REPOSITORY
was added in 8.0.2.
Error: 4046
SQLSTATE: HY000
(ER_RPL_SLAVE_GENERIC_MESSAGE
)
Message: Slave: %s
ER_RPL_SLAVE_GENERIC_MESSAGE
was
added in 8.0.2.
Error: 4047
SQLSTATE: HY000
(ER_RPL_SLAVE_COULD_NOT_CREATE_CHANNEL_LIST
)
Message: Slave: Could not create channel list
ER_RPL_SLAVE_COULD_NOT_CREATE_CHANNEL_LIST
was added in 8.0.2.
Error: 4048
SQLSTATE: HY000
(ER_RPL_MULTISOURCE_REQUIRES_TABLE_TYPE_REPOSITORIES
)
Message: Slave: This slave was a multisourced slave previously which is supported only by both TABLE based master info and relay log info repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.
ER_RPL_MULTISOURCE_REQUIRES_TABLE_TYPE_REPOSITORIES
was added in 8.0.2.
Error: 4049
SQLSTATE: HY000
(ER_RPL_SLAVE_FAILED_TO_INIT_A_MASTER_INFO_STRUCTURE
)
Message: Slave: Failed to initialize the master info structure for channel '%s'; its record may still be present in 'mysql.slave_master_info' table, consider deleting it.
ER_RPL_SLAVE_FAILED_TO_INIT_A_MASTER_INFO_STRUCTURE
was added in 8.0.2.
Error: 4050
SQLSTATE: HY000
(ER_RPL_SLAVE_FAILED_TO_INIT_MASTER_INFO_STRUCTURE
)
Message: Failed to initialize the master info structure%s
ER_RPL_SLAVE_FAILED_TO_INIT_MASTER_INFO_STRUCTURE
was added in 8.0.2.
Error: 4051
SQLSTATE: HY000
(ER_RPL_SLAVE_FAILED_TO_CREATE_CHANNEL_FROM_MASTER_INFO
)
Message: Slave: Failed to create a channel from master info table repository.
ER_RPL_SLAVE_FAILED_TO_CREATE_CHANNEL_FROM_MASTER_INFO
was added in 8.0.2.
Error: 4052
SQLSTATE: HY000
(ER_RPL_FAILED_TO_CREATE_NEW_INFO_FILE
)
Message: Failed to create a new info file (file '%s', errno %d)
ER_RPL_FAILED_TO_CREATE_NEW_INFO_FILE
was added in 8.0.2.
Error: 4053
SQLSTATE: HY000
(ER_RPL_FAILED_TO_CREATE_CACHE_FOR_INFO_FILE
)
Message: Failed to create a cache on info file (file '%s')
ER_RPL_FAILED_TO_CREATE_CACHE_FOR_INFO_FILE
was added in 8.0.2.
Error: 4054
SQLSTATE: HY000
(ER_RPL_FAILED_TO_OPEN_INFO_FILE
)
Message: Failed to open the existing info file (file '%s', errno %d)
ER_RPL_FAILED_TO_OPEN_INFO_FILE
was added in 8.0.2.
Error: 4055
SQLSTATE: HY000
(ER_RPL_GTID_MEMORY_FINALLY_AVAILABLE
)
Message: Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.
ER_RPL_GTID_MEMORY_FINALLY_AVAILABLE
was added in 8.0.2.
Error: 4056
SQLSTATE: HY000
(ER_SERVER_COST_UNKNOWN_COST_CONSTANT
)
Message: Unknown cost constant "%s" in mysql.server_cost table
ER_SERVER_COST_UNKNOWN_COST_CONSTANT
was added in 8.0.2.
Error: 4057
SQLSTATE: HY000
(ER_SERVER_COST_INVALID_COST_CONSTANT
)
Message: Invalid value for cost constant "%s" in mysql.server_cost table: %.1f
ER_SERVER_COST_INVALID_COST_CONSTANT
was added in 8.0.2.
Error: 4058
SQLSTATE: HY000
(ER_ENGINE_COST_UNKNOWN_COST_CONSTANT
)
Message: Unknown cost constant "%s" in mysql.engine_cost table
ER_ENGINE_COST_UNKNOWN_COST_CONSTANT
was added in 8.0.2.
Error: 4059
SQLSTATE: HY000
(ER_ENGINE_COST_UNKNOWN_STORAGE_ENGINE
)
Message: Unknown storage engine "%s" in mysql.engine_cost table
ER_ENGINE_COST_UNKNOWN_STORAGE_ENGINE
was added in 8.0.2.
Error: 4060
SQLSTATE: HY000
(ER_ENGINE_COST_INVALID_DEVICE_TYPE_FOR_SE
)
Message: Invalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost table
ER_ENGINE_COST_INVALID_DEVICE_TYPE_FOR_SE
was added in 8.0.2.
Error: 4061
SQLSTATE: HY000
(ER_ENGINE_COST_INVALID_CONST_CONSTANT_FOR_SE_AND_DEVICE
)
Message: Invalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1f
ER_ENGINE_COST_INVALID_CONST_CONSTANT_FOR_SE_AND_DEVICE
was added in 8.0.2.
Error: 4062
SQLSTATE: HY000
(ER_SERVER_COST_FAILED_TO_READ
)
Message: init_read_record returned error when reading from mysql.server_cost table.
ER_SERVER_COST_FAILED_TO_READ
was
added in 8.0.2.
Error: 4063
SQLSTATE: HY000
(ER_ENGINE_COST_FAILED_TO_READ
)
Message: init_read_record returned error when reading from mysql.engine_cost table.
ER_ENGINE_COST_FAILED_TO_READ
was
added in 8.0.2.
Error: 4064
SQLSTATE: HY000
(ER_FAILED_TO_OPEN_COST_CONSTANT_TABLES
)
Message: Failed to open optimizer cost constant tables
ER_FAILED_TO_OPEN_COST_CONSTANT_TABLES
was added in 8.0.2.
Error: 4065
SQLSTATE: HY000
(ER_RPL_UNSUPPORTED_UNIGNORABLE_EVENT_IN_STREAM
)
Message: Unsupported non-ignorable event fed into the event stream.
ER_RPL_UNSUPPORTED_UNIGNORABLE_EVENT_IN_STREAM
was added in 8.0.2.
Error: 4066
SQLSTATE: HY000
(ER_RPL_GTID_LOG_EVENT_IN_STREAM
)
Message: GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.
ER_RPL_GTID_LOG_EVENT_IN_STREAM
was added in 8.0.2.
Error: 4067
SQLSTATE: HY000
(ER_RPL_UNEXPECTED_BEGIN_IN_STREAM
)
Message: QUERY(BEGIN) is not expected in an event stream in the middle of a %s.
ER_RPL_UNEXPECTED_BEGIN_IN_STREAM
was added in 8.0.2.
Error: 4068
SQLSTATE: HY000
(ER_RPL_UNEXPECTED_COMMIT_ROLLBACK_OR_XID_LOG_EVENT_IN_STREAM
)
Message: QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.
ER_RPL_UNEXPECTED_COMMIT_ROLLBACK_OR_XID_LOG_EVENT_IN_STREAM
was added in 8.0.2.
Error: 4069
SQLSTATE: HY000
(ER_RPL_UNEXPECTED_XA_ROLLBACK_IN_STREAM
)
Message: QUERY(XA ROLLBACK) is not expected in an event stream %s.
ER_RPL_UNEXPECTED_XA_ROLLBACK_IN_STREAM
was added in 8.0.2.
Error: 4070
SQLSTATE: HY000
(ER_EVENT_EXECUTION_FAILED_CANT_AUTHENTICATE_USER
)
Message: Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.
ER_EVENT_EXECUTION_FAILED_CANT_AUTHENTICATE_USER
was added in 8.0.2.
Error: 4071
SQLSTATE: HY000
(ER_EVENT_EXECUTION_FAILED_USER_LOST_EVEN_PRIVILEGE
)
Message: Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.
ER_EVENT_EXECUTION_FAILED_USER_LOST_EVEN_PRIVILEGE
was added in 8.0.2.
Error: 4072
SQLSTATE: HY000
(ER_EVENT_ERROR_DURING_COMPILATION
)
Message: Event Scheduler: %serror during compilation of %s.%s
ER_EVENT_ERROR_DURING_COMPILATION
was added in 8.0.2.
Error: 4073
SQLSTATE: HY000
(ER_EVENT_DROPPING
)
Message: Event Scheduler: Dropping %s.%s
ER_EVENT_DROPPING
was added in
8.0.2.
Error: 4074
SQLSTATE: HY000
(ER_NDB_SCHEMA_GENERIC_MESSAGE
)
Message: Ndb schema[%s.%s]: %s
ER_NDB_SCHEMA_GENERIC_MESSAGE
was
added in 8.0.2.
Error: 4075
SQLSTATE: HY000
(ER_RPL_INCOMPATIBLE_DECIMAL_IN_RBR
)
Message: In RBR mode, Slave received incompatible DECIMAL field (old-style decimal field) from Master while creating conversion table. Please consider changing datatype on Master to new style decimal by executing ALTER command for column Name: %s.%s.%s.
ER_RPL_INCOMPATIBLE_DECIMAL_IN_RBR
was added in 8.0.2.
Error: 4076
SQLSTATE: HY000
(ER_INIT_ROOT_WITHOUT_PASSWORD
)
Message: root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
ER_INIT_ROOT_WITHOUT_PASSWORD
was
added in 8.0.2.
Error: 4077
SQLSTATE: HY000
(ER_INIT_GENERATING_TEMP_PASSWORD_FOR_ROOT
)
Message: A temporary password is generated for root@localhost: %s
ER_INIT_GENERATING_TEMP_PASSWORD_FOR_ROOT
was added in 8.0.2.
Error: 4078
SQLSTATE: HY000
(ER_INIT_CANT_OPEN_BOOTSTRAP_FILE
)
Message: Failed to open the bootstrap file %s
ER_INIT_CANT_OPEN_BOOTSTRAP_FILE
was added in 8.0.2.
Error: 4079
SQLSTATE: HY000
(ER_INIT_BOOTSTRAP_COMPLETE
)
Message: Bootstrapping complete
ER_INIT_BOOTSTRAP_COMPLETE
was
added in 8.0.2.
Error: 4080
SQLSTATE: HY000
(ER_INIT_DATADIR_NOT_EMPTY_WONT_INITIALIZE
)
Message: --initialize specified but the data directory has files in it. Aborting.
ER_INIT_DATADIR_NOT_EMPTY_WONT_INITIALIZE
was added in 8.0.2.
Error: 4081
SQLSTATE: HY000
(ER_INIT_DATADIR_EXISTS_WONT_INITIALIZE
)
Message: --initialize specified on an existing data directory.
ER_INIT_DATADIR_EXISTS_WONT_INITIALIZE
was added in 8.0.2.
Error: 4082
SQLSTATE: HY000
(ER_INIT_DATADIR_EXISTS_AND_PATH_TOO_LONG_WONT_INITIALIZE
)
Message: --initialize specified but the data directory exists and the path is too long. Aborting.
ER_INIT_DATADIR_EXISTS_AND_PATH_TOO_LONG_WONT_INITIALIZE
was added in 8.0.2.
Error: 4083
SQLSTATE: HY000
(ER_INIT_DATADIR_EXISTS_AND_NOT_WRITABLE_WONT_INITIALIZE
)
Message: --initialize specified but the data directory exists and is not writable. Aborting.
ER_INIT_DATADIR_EXISTS_AND_NOT_WRITABLE_WONT_INITIALIZE
was added in 8.0.2.
Error: 4084
SQLSTATE: HY000
(ER_INIT_CREATING_DD
)
Message: Creating the data directory %s
ER_INIT_CREATING_DD
was added in
8.0.2.
Error: 4085
SQLSTATE: HY000
(ER_RPL_BINLOG_STARTING_DUMP
)
Message: Start binlog_dump to master_thread_id(%u) slave_server(%u), pos(%s, %llu)
ER_RPL_BINLOG_STARTING_DUMP
was
added in 8.0.2.
Error: 4086
SQLSTATE: HY000
(ER_RPL_BINLOG_MASTER_SENDS_HEARTBEAT
)
Message: master sends heartbeat message
ER_RPL_BINLOG_MASTER_SENDS_HEARTBEAT
was added in 8.0.2.
Error: 4087
SQLSTATE: HY000
(ER_RPL_BINLOG_SKIPPING_REMAINING_HEARTBEAT_INFO
)
Message: the rest of heartbeat info skipped ...
ER_RPL_BINLOG_SKIPPING_REMAINING_HEARTBEAT_INFO
was added in 8.0.2.
Error: 4088
SQLSTATE: HY000
(ER_RPL_BINLOG_MASTER_USES_CHECKSUM_AND_SLAVE_CANT
)
Message: Master is configured to log replication events with checksum, but will not send such events to slaves that cannot process them
ER_RPL_BINLOG_MASTER_USES_CHECKSUM_AND_SLAVE_CANT
was added in 8.0.2.
Error: 4089
SQLSTATE: HY000
(ER_NDB_QUERY_FAILED
)
Message: NDB: Query '%s' failed, error: %d: %s
ER_NDB_QUERY_FAILED
was added in
8.0.2.
Error: 4090
SQLSTATE: HY000
(ER_KILLING_THREAD
)
Message: Killing thread %lu
ER_KILLING_THREAD
was added in
8.0.2.
Error: 4091
SQLSTATE: HY000
(ER_DETACHING_SESSION_LEFT_BY_PLUGIN
)
Message: Plugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.
ER_DETACHING_SESSION_LEFT_BY_PLUGIN
was added in 8.0.2.
Error: 4092
SQLSTATE: HY000
(ER_CANT_DETACH_SESSION_LEFT_BY_PLUGIN
)
Message: Failed to detach the session.
ER_CANT_DETACH_SESSION_LEFT_BY_PLUGIN
was added in 8.0.2.
Error: 4093
SQLSTATE: HY000
(ER_DETACHED_SESSIONS_LEFT_BY_PLUGIN
)
Message: Closed forcefully %u session%s left opened by plugin %s
ER_DETACHED_SESSIONS_LEFT_BY_PLUGIN
was added in 8.0.2.
Error: 4094
SQLSTATE: HY000
(ER_FAILED_TO_DECREMENT_NUMBER_OF_THREADS
)
Message: Failed to decrement the number of threads
ER_FAILED_TO_DECREMENT_NUMBER_OF_THREADS
was added in 8.0.2.
Error: 4095
SQLSTATE: HY000
(ER_PLUGIN_DID_NOT_DEINITIALIZE_THREADS
)
Message: Plugin %s did not deinitialize %u threads
ER_PLUGIN_DID_NOT_DEINITIALIZE_THREADS
was added in 8.0.2.
Error: 4096
SQLSTATE: HY000
(ER_KILLED_THREADS_OF_PLUGIN
)
Message: Killed %u threads of plugin %s
ER_KILLED_THREADS_OF_PLUGIN
was
added in 8.0.2.
Error: 4097
SQLSTATE: HY000
(ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_UNKNOWN
)
Message: NDB Slave : Could not determine maximum replicated epoch from %s.%s at Slave start, error %u %s
ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_UNKNOWN
was added in 8.0.2.
Error: 4098
SQLSTATE: HY000
(ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_SET_TO
)
Message: NDB Slave : MaxReplicatedEpoch set to %llu (%u/%u) at Slave start
ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_SET_TO
was added in 8.0.2.
Error: 4099
SQLSTATE: HY000
(ER_NDB_NODE_ID_AND_MANAGEMENT_SERVER_INFO
)
Message: NDB: NodeID is %lu, management server '%s:%lu'
ER_NDB_NODE_ID_AND_MANAGEMENT_SERVER_INFO
was added in 8.0.2.
Error: 4100
SQLSTATE: HY000
(ER_NDB_DISCONNECT_INFO
)
Message: tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%u
ER_NDB_DISCONNECT_INFO
was added
in 8.0.2.
Error: 4101
SQLSTATE: HY000
(ER_NDB_COLUMN_DEFAULTS_DIFFER
)
Message: NDB Internal error: Default values differ for column %u, ndb_default: %d
ER_NDB_COLUMN_DEFAULTS_DIFFER
was
added in 8.0.2.
Error: 4102
SQLSTATE: HY000
(ER_NDB_COLUMN_SHOULD_NOT_HAVE_NATIVE_DEFAULT
)
Message: NDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%u
ER_NDB_COLUMN_SHOULD_NOT_HAVE_NATIVE_DEFAULT
was added in 8.0.2.
Error: 4103
SQLSTATE: HY000
(ER_NDB_FIELD_INFO
)
Message: field[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]
ER_NDB_FIELD_INFO
was added in
8.0.2.
Error: 4104
SQLSTATE: HY000
(ER_NDB_COLUMN_INFO
)
Message: ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]
ER_NDB_COLUMN_INFO
was added in
8.0.2.
Error: 4105
SQLSTATE: HY000
(ER_NDB_OOM_IN_FIX_UNIQUE_INDEX_ATTR_ORDER
)
Message: fix_unique_index_attr_order: my_malloc(%u) failure
ER_NDB_OOM_IN_FIX_UNIQUE_INDEX_ATTR_ORDER
was added in 8.0.2.
Error: 4106
SQLSTATE: HY000
(ER_NDB_SLAVE_MALFORMED_EVENT_RECEIVED_ON_TABLE
)
Message: NDB Slave : Malformed event received on table %s cannot parse. Stopping Slave.
ER_NDB_SLAVE_MALFORMED_EVENT_RECEIVED_ON_TABLE
was added in 8.0.2.
Error: 4107
SQLSTATE: HY000
(ER_NDB_SLAVE_CONFLICT_FUNCTION_REQUIRES_ROLE
)
Message: NDB Slave : Conflict function %s defined on table %s requires ndb_slave_conflict_role variable to be set. Stopping slave.
ER_NDB_SLAVE_CONFLICT_FUNCTION_REQUIRES_ROLE
was added in 8.0.2.
Error: 4108
SQLSTATE: HY000
(ER_NDB_SLAVE_CONFLICT_DETECTION_REQUIRES_TRANSACTION_IDS
)
Message: NDB Slave : Transactional conflict detection defined on table %s, but events received without transaction ids. Check --ndb-log-transaction-id setting on upstream Cluster.
ER_NDB_SLAVE_CONFLICT_DETECTION_REQUIRES_TRANSACTION_IDS
was added in 8.0.2.
Error: 4109
SQLSTATE: HY000
(ER_NDB_SLAVE_BINLOG_MISSING_INFO_FOR_CONFLICT_DETECTION
)
Message: NDB Slave : Binlog event on table %s missing info necessary for conflict detection. Check binlog format options on upstream cluster.
ER_NDB_SLAVE_BINLOG_MISSING_INFO_FOR_CONFLICT_DETECTION
was added in 8.0.2.
Error: 4110
SQLSTATE: HY000
(ER_NDB_ERROR_IN_READAUTOINCREMENTVALUE
)
Message: Error %lu in readAutoIncrementValue(): %s
ER_NDB_ERROR_IN_READAUTOINCREMENTVALUE
was added in 8.0.2.
Error: 4111
SQLSTATE: HY000
(ER_NDB_FOUND_UNCOMMITTED_AUTOCOMMIT
)
Message: found uncommitted autocommit+rbwr transaction, commit status: %d
ER_NDB_FOUND_UNCOMMITTED_AUTOCOMMIT
was added in 8.0.2.
Error: 4112
SQLSTATE: HY000
(ER_NDB_SLAVE_TOO_MANY_RETRIES
)
Message: Ndb slave retried transaction %u time(s) in vain. Giving up.
ER_NDB_SLAVE_TOO_MANY_RETRIES
was
added in 8.0.2.
Error: 4113
SQLSTATE: HY000
(ER_NDB_SLAVE_ERROR_IN_UPDATE_CREATE_INFO
)
Message: Error %lu in ::update_create_info(): %s
ER_NDB_SLAVE_ERROR_IN_UPDATE_CREATE_INFO
was added in 8.0.2.
Error: 4114
SQLSTATE: HY000
(ER_NDB_SLAVE_CANT_ALLOCATE_TABLE_SHARE
)
Message: NDB: allocating table share for %s failed
ER_NDB_SLAVE_CANT_ALLOCATE_TABLE_SHARE
was added in 8.0.2.
Error: 4115
SQLSTATE: HY000
(ER_NDB_BINLOG_ERROR_INFO_FROM_DA
)
Message: NDB Binlog: (%d)%s
ER_NDB_BINLOG_ERROR_INFO_FROM_DA
was added in 8.0.2.
Error: 4116
SQLSTATE: HY000
(ER_NDB_BINLOG_CREATE_TABLE_EVENT
)
Message: NDB Binlog: CREATE TABLE Event: %s
ER_NDB_BINLOG_CREATE_TABLE_EVENT
was added in 8.0.2.
Error: 4117
SQLSTATE: HY000
(ER_NDB_BINLOG_FAILED_CREATE_TABLE_EVENT_OPERATIONS
)
Message: NDB Binlog: FAILED CREATE TABLE event operations. Event: %s
ER_NDB_BINLOG_FAILED_CREATE_TABLE_EVENT_OPERATIONS
was added in 8.0.2.
Error: 4118
SQLSTATE: HY000
(ER_NDB_BINLOG_RENAME_EVENT
)
Message: NDB Binlog: RENAME Event: %s
ER_NDB_BINLOG_RENAME_EVENT
was
added in 8.0.2.
Error: 4119
SQLSTATE: HY000
(ER_NDB_BINLOG_FAILED_CREATE_EVENT_OPERATIONS_DURING_RENAME
)
Message: NDB Binlog: FAILED create event operations during RENAME. Event %s
ER_NDB_BINLOG_FAILED_CREATE_EVENT_OPERATIONS_DURING_RENAME
was added in 8.0.2.
Error: 4120
SQLSTATE: HY000
(ER_NDB_UNEXPECTED_RENAME_TYPE
)
Message: Unexpected rename case detected, sql_command: %d
ER_NDB_UNEXPECTED_RENAME_TYPE
was
added in 8.0.2.
Error: 4121
SQLSTATE: HY000
(ER_NDB_ERROR_IN_GET_AUTO_INCREMENT
)
Message: Error %lu in ::get_auto_increment(): %s
ER_NDB_ERROR_IN_GET_AUTO_INCREMENT
was added in 8.0.2.
Error: 4122
SQLSTATE: HY000
(ER_NDB_CREATING_SHARE_IN_OPEN
)
Message: Calling ndbcluster_create_binlog_setup(%s) in ::open
ER_NDB_CREATING_SHARE_IN_OPEN
was
added in 8.0.2.
Error: 4123
SQLSTATE: HY000
(ER_NDB_TABLE_OPENED_READ_ONLY
)
Message: table '%s' opened read only
ER_NDB_TABLE_OPENED_READ_ONLY
was
added in 8.0.2.
Error: 4124
SQLSTATE: HY000
(ER_NDB_INITIALIZE_GIVEN_CLUSTER_PLUGIN_DISABLED
)
Message: NDB: '--initialize' -> ndbcluster plugin disabled
ER_NDB_INITIALIZE_GIVEN_CLUSTER_PLUGIN_DISABLED
was added in 8.0.2.
Error: 4125
SQLSTATE: HY000
(ER_NDB_BINLOG_FORMAT_CHANGED_FROM_STMT_TO_MIXED
)
Message: NDB: Changed global value of binlog_format from STATEMENT to MIXED
ER_NDB_BINLOG_FORMAT_CHANGED_FROM_STMT_TO_MIXED
was added in 8.0.2.
Error: 4126
SQLSTATE: HY000
(ER_NDB_TRAILING_SHARE_RELEASED_BY_CLOSE_CACHED_TABLES
)
Message: NDB_SHARE: trailing share %s, released by close_cached_tables
ER_NDB_TRAILING_SHARE_RELEASED_BY_CLOSE_CACHED_TABLES
was added in 8.0.2.
Error: 4127
SQLSTATE: HY000
(ER_NDB_SHARE_ALREADY_EXISTS
)
Message: NDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.
ER_NDB_SHARE_ALREADY_EXISTS
was
added in 8.0.2.
Error: 4128
SQLSTATE: HY000
(ER_NDB_HANDLE_TRAILING_SHARE_INFO
)
Message: handle_trailing_share: %s use_count: %u
ER_NDB_HANDLE_TRAILING_SHARE_INFO
was added in 8.0.2.
Error: 4129
SQLSTATE: HY000
(ER_NDB_CLUSTER_GET_SHARE_INFO
)
Message: ndbcluster_get_share: %s use_count: %u
ER_NDB_CLUSTER_GET_SHARE_INFO
was
added in 8.0.2.
Error: 4130
SQLSTATE: HY000
(ER_NDB_CLUSTER_REAL_FREE_SHARE_INFO
)
Message: ndbcluster_real_free_share: %s use_count: %u
ER_NDB_CLUSTER_REAL_FREE_SHARE_INFO
was added in 8.0.2.
Error: 4131
SQLSTATE: HY000
(ER_NDB_CLUSTER_REAL_FREE_SHARE_DROP_FAILED
)
Message: ndbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)
ER_NDB_CLUSTER_REAL_FREE_SHARE_DROP_FAILED
was added in 8.0.2.
Error: 4132
SQLSTATE: HY000
(ER_NDB_CLUSTER_FREE_SHARE_INFO
)
Message: ndbcluster_free_share: %s use_count: %u
ER_NDB_CLUSTER_FREE_SHARE_INFO
was
added in 8.0.2.
Error: 4133
SQLSTATE: HY000
(ER_NDB_CLUSTER_MARK_SHARE_DROPPED_INFO
)
Message: ndbcluster_mark_share_dropped: %s use_count: %u
ER_NDB_CLUSTER_MARK_SHARE_DROPPED_INFO
was added in 8.0.2.
Error: 4134
SQLSTATE: HY000
(ER_NDB_CLUSTER_MARK_SHARE_DROPPED_DESTROYING_SHARE
)
Message: ndbcluster_mark_share_dropped: destroys share %s
ER_NDB_CLUSTER_MARK_SHARE_DROPPED_DESTROYING_SHARE
was added in 8.0.2.
Error: 4135
SQLSTATE: HY000
(ER_NDB_CLUSTER_OOM_THD_NDB
)
Message: Could not allocate Thd_ndb object
ER_NDB_CLUSTER_OOM_THD_NDB
was
added in 8.0.2.
Error: 4136
SQLSTATE: HY000
(ER_NDB_BINLOG_NDB_TABLES_INITIALLY_READ_ONLY
)
Message: NDB Binlog: Ndb tables initially read only.
ER_NDB_BINLOG_NDB_TABLES_INITIALLY_READ_ONLY
was added in 8.0.2.
Error: 4137
SQLSTATE: HY000
(ER_NDB_UTIL_THREAD_OOM
)
Message: ndb util thread: malloc failure, query cache not maintained properly
ER_NDB_UTIL_THREAD_OOM
was added
in 8.0.2.
Error: 4138
SQLSTATE: HY000
(ER_NDB_ILLEGAL_VALUE_FOR_NDB_RECV_THREAD_CPU_MASK
)
Message: Trying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignored
ER_NDB_ILLEGAL_VALUE_FOR_NDB_RECV_THREAD_CPU_MASK
was added in 8.0.2.
Error: 4139
SQLSTATE: HY000
(ER_NDB_TOO_MANY_CPUS_IN_NDB_RECV_THREAD_CPU_MASK
)
Message: Trying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %s
ER_NDB_TOO_MANY_CPUS_IN_NDB_RECV_THREAD_CPU_MASK
was added in 8.0.2.
Error: 4140
SQLSTATE: HY000
(ER_DBUG_CHECK_SHARES_OPEN
)
Message: dbug_check_shares open:
ER_DBUG_CHECK_SHARES_OPEN
was
added in 8.0.2.
Error: 4141
SQLSTATE: HY000
(ER_DBUG_CHECK_SHARES_INFO
)
Message: %s.%s: state: %s(%u) use_count: %u
ER_DBUG_CHECK_SHARES_INFO
was
added in 8.0.2.
Error: 4142
SQLSTATE: HY000
(ER_DBUG_CHECK_SHARES_DROPPED
)
Message: dbug_check_shares dropped:
ER_DBUG_CHECK_SHARES_DROPPED
was
added in 8.0.2.
Error: 4143
SQLSTATE: HY000
(ER_INVALID_OR_OLD_TABLE_OR_DB_NAME
)
Message: Invalid (old?) table or database name '%s'
ER_INVALID_OR_OLD_TABLE_OR_DB_NAME
was added in 8.0.2.
Error: 4144
SQLSTATE: HY000
(ER_TC_RECOVERING_AFTER_CRASH_USING
)
Message: Recovering after a crash using %s
ER_TC_RECOVERING_AFTER_CRASH_USING
was added in 8.0.2.
Error: 4145
SQLSTATE: HY000
(ER_TC_CANT_AUTO_RECOVER_WITH_TC_HEURISTIC_RECOVER
)
Message: Cannot perform automatic crash recovery when --tc-heuristic-recover is used
ER_TC_CANT_AUTO_RECOVER_WITH_TC_HEURISTIC_RECOVER
was added in 8.0.2.
Error: 4146
SQLSTATE: HY000
(ER_TC_BAD_MAGIC_IN_TC_LOG
)
Message: Bad magic header in tc log
ER_TC_BAD_MAGIC_IN_TC_LOG
was
added in 8.0.2.
Error: 4147
SQLSTATE: HY000
(ER_TC_NEED_N_SE_SUPPORTING_2PC_FOR_RECOVERY
)
Message: Recovery failed! You must enable exactly %d storage engines that support two-phase commit protocol
ER_TC_NEED_N_SE_SUPPORTING_2PC_FOR_RECOVERY
was added in 8.0.2.
Error: 4148
SQLSTATE: HY000
(ER_TC_RECOVERY_FAILED_THESE_ARE_YOUR_OPTIONS
)
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}
ER_TC_RECOVERY_FAILED_THESE_ARE_YOUR_OPTIONS
was added in 8.0.2.
Error: 4149
SQLSTATE: HY000
(ER_TC_HEURISTIC_RECOVERY_MODE
)
Message: Heuristic crash recovery mode
ER_TC_HEURISTIC_RECOVERY_MODE
was
added in 8.0.2.
Error: 4150
SQLSTATE: HY000
(ER_TC_HEURISTIC_RECOVERY_FAILED
)
Message: Heuristic crash recovery failed
ER_TC_HEURISTIC_RECOVERY_FAILED
was added in 8.0.2.
Error: 4151
SQLSTATE: HY000
(ER_TC_RESTART_WITHOUT_TC_HEURISTIC_RECOVER
)
Message: Please restart mysqld without --tc-heuristic-recover
ER_TC_RESTART_WITHOUT_TC_HEURISTIC_RECOVER
was added in 8.0.2.
Error: 4152
SQLSTATE: HY000
(ER_RPL_SLAVE_FAILED_TO_CREATE_OR_RECOVER_INFO_REPOSITORIES
)
Message: Failed to create or recover replication info repositories.
ER_RPL_SLAVE_FAILED_TO_CREATE_OR_RECOVER_INFO_REPOSITORIES
was added in 8.0.2.
Error: 4153
SQLSTATE: HY000
(ER_RPL_SLAVE_AUTO_POSITION_IS_1_AND_GTID_MODE_IS_OFF
)
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 MASTER TO MASTER_AUTO_POSITION = 0 FOR CHANNEL '%s', or change GTID_MODE to some value other than OFF, before starting the slave receiver thread.
ER_RPL_SLAVE_AUTO_POSITION_IS_1_AND_GTID_MODE_IS_OFF
was added in 8.0.2.
Error: 4154
SQLSTATE: HY000
(ER_RPL_SLAVE_CANT_START_SLAVE_FOR_CHANNEL
)
Message: Slave: Could not start slave for channel '%s'. operation discontinued
ER_RPL_SLAVE_CANT_START_SLAVE_FOR_CHANNEL
was added in 8.0.2.
Error: 4155
SQLSTATE: HY000
(ER_RPL_SLAVE_CANT_STOP_SLAVE_FOR_CHANNEL
)
Message: Slave: Could not stop slave for channel '%s' operation discontinued
ER_RPL_SLAVE_CANT_STOP_SLAVE_FOR_CHANNEL
was added in 8.0.2.
Error: 4156
SQLSTATE: HY000
(ER_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_MASTER
)
Message: Error during --relay-log-recovery: Could not locate rotate event from the master.
ER_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_MASTER
was added in 8.0.2.
Error: 4157
SQLSTATE: HY000
(ER_RPL_RECOVERY_ERROR_READ_RELAY_LOG
)
Message: Error during --relay-log-recovery: Error reading events from relay log: %d
ER_RPL_RECOVERY_ERROR_READ_RELAY_LOG
was added in 8.0.2.
Error: 4158
SQLSTATE: HY000
(ER_RPL_RECOVERY_ERROR_FREEING_IO_CACHE
)
Message: Error during --relay-log-recovery: Error while freeing IO_CACHE object
ER_RPL_RECOVERY_ERROR_FREEING_IO_CACHE
was added in 8.0.2.
Error: 4159
SQLSTATE: HY000
(ER_RPL_RECOVERY_SKIPPED_GROUP_REPLICATION_CHANNEL
)
Message: Relay log recovery skipped for group replication channel.
ER_RPL_RECOVERY_SKIPPED_GROUP_REPLICATION_CHANNEL
was added in 8.0.2.
Error: 4160
SQLSTATE: HY000
(ER_RPL_RECOVERY_ERROR
)
Message: Error during --relay-log-recovery: %s
ER_RPL_RECOVERY_ERROR
was added in
8.0.2.
Error: 4161
SQLSTATE: HY000
(ER_RPL_RECOVERY_IO_ERROR_READING_RELAY_LOG_INDEX
)
Message: Error during --relay-log-recovery: Could not read relay log index file due to an IO error.
ER_RPL_RECOVERY_IO_ERROR_READING_RELAY_LOG_INDEX
was added in 8.0.2.
Error: 4162
SQLSTATE: HY000
(ER_RPL_RECOVERY_FILE_MASTER_POS_INFO
)
Message: Recovery from master pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.
ER_RPL_RECOVERY_FILE_MASTER_POS_INFO
was added in 8.0.2.
Error: 4163
SQLSTATE: HY000
(ER_RPL_RECOVERY_REPLICATE_SAME_SERVER_ID_REQUIRES_POSITION
)
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.
ER_RPL_RECOVERY_REPLICATE_SAME_SERVER_ID_REQUIRES_POSITION
was added in 8.0.2.
Error: 4164
SQLSTATE: HY000
(ER_RPL_MTS_RECOVERY_STARTING_COORDINATOR
)
Message: MTS recovery: starting coordinator thread to fill MTS gaps.
ER_RPL_MTS_RECOVERY_STARTING_COORDINATOR
was added in 8.0.2.
Error: 4165
SQLSTATE: HY000
(ER_RPL_MTS_RECOVERY_FAILED_TO_START_COORDINATOR
)
Message: MTS recovery: failed to start the coordinator thread. Check the error log for additional details.
ER_RPL_MTS_RECOVERY_FAILED_TO_START_COORDINATOR
was added in 8.0.2.
Error: 4166
SQLSTATE: HY000
(ER_RPL_MTS_AUTOMATIC_RECOVERY_FAILED
)
Message: MTS recovery: automatic recovery failed. Either the slave server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the slave side error and restart the slave server or consider using RESET SLAVE.
ER_RPL_MTS_AUTOMATIC_RECOVERY_FAILED
was added in 8.0.2.
Error: 4167
SQLSTATE: HY000
(ER_RPL_MTS_RECOVERY_CANT_OPEN_RELAY_LOG
)
Message: Failed to open the relay log '%s' (relay_log_pos %s).
ER_RPL_MTS_RECOVERY_CANT_OPEN_RELAY_LOG
was added in 8.0.2.
Error: 4168
SQLSTATE: HY000
(ER_RPL_MTS_RECOVERY_SUCCESSFUL
)
Message: MTS recovery: completed successfully.
ER_RPL_MTS_RECOVERY_SUCCESSFUL
was
added in 8.0.2.
Error: 4169
SQLSTATE: HY000
(ER_RPL_SERVER_ID_MISSING
)
Message: Server id not set, will not start slave%s
ER_RPL_SERVER_ID_MISSING
was added
in 8.0.2.
Error: 4170
SQLSTATE: HY000
(ER_RPL_CANT_CREATE_SLAVE_THREAD
)
Message: Can't create slave thread%s.
ER_RPL_CANT_CREATE_SLAVE_THREAD
was added in 8.0.2.
Error: 4171
SQLSTATE: HY000
(ER_RPL_SLAVE_IO_THREAD_WAS_KILLED
)
Message: The slave IO thread%s was killed while executing initialization query '%s'
ER_RPL_SLAVE_IO_THREAD_WAS_KILLED
was added in 8.0.2.
Error: 4172
SQLSTATE: HY000
(ER_RPL_SLAVE_MASTER_UUID_HAS_CHANGED
)
Message: The master's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.
ER_RPL_SLAVE_MASTER_UUID_HAS_CHANGED
was added in 8.0.2.
Error: 4173
SQLSTATE: HY000
(ER_RPL_SLAVE_USES_CHECKSUM_AND_MASTER_PRE_50
)
Message: Found a master with MySQL server version older than 5.0. With checksums enabled on the slave, replication might not work correctly. To ensure correct replication, restart the slave server with --slave_sql_verify_checksum=0.
ER_RPL_SLAVE_USES_CHECKSUM_AND_MASTER_PRE_50
was added in 8.0.2.
Error: 4174
SQLSTATE: HY000
(ER_RPL_SLAVE_SECONDS_BEHIND_MASTER_DUBIOUS
)
Message: "SELECT UNIX_TIMESTAMP()" failed on master, do not trust column Seconds_Behind_Master of SHOW SLAVE STATUS. Error: %s (%d)
ER_RPL_SLAVE_SECONDS_BEHIND_MASTER_DUBIOUS
was added in 8.0.2.
Error: 4175
SQLSTATE: HY000
(ER_RPL_SLAVE_CANT_FLUSH_MASTER_INFO_FILE
)
Message: Failed to flush master info file.
ER_RPL_SLAVE_CANT_FLUSH_MASTER_INFO_FILE
was added in 8.0.2.
Error: 4176
SQLSTATE: HY000
(ER_RPL_SLAVE_REPORT_HOST_TOO_LONG
)
Message: The length of report_host is %zu. It is larger than the max length(%d), so this slave cannot be registered to the master%s.
ER_RPL_SLAVE_REPORT_HOST_TOO_LONG
was added in 8.0.2.
Error: 4177
SQLSTATE: HY000
(ER_RPL_SLAVE_REPORT_USER_TOO_LONG
)
Message: The length of report_user is %zu. It is larger than the max length(%d), so this slave cannot be registered to the master%s.
ER_RPL_SLAVE_REPORT_USER_TOO_LONG
was added in 8.0.2.
Error: 4178
SQLSTATE: HY000
(ER_RPL_SLAVE_REPORT_PASSWORD_TOO_LONG
)
Message: The length of report_password is %zu. It is larger than the max length(%d), so this slave cannot be registered to the master%s.
ER_RPL_SLAVE_REPORT_PASSWORD_TOO_LONG
was added in 8.0.2.
Error: 4179
SQLSTATE: HY000
(ER_RPL_SLAVE_ERROR_RETRYING
)
Message: Error on %s: %d %s, will retry in %d secs
ER_RPL_SLAVE_ERROR_RETRYING
was
added in 8.0.2.
Error: 4180
SQLSTATE: HY000
(ER_RPL_SLAVE_ERROR_READING_FROM_SERVER
)
Message: Error reading packet from server%s: %s (server_errno=%d)
ER_RPL_SLAVE_ERROR_READING_FROM_SERVER
was added in 8.0.2.
Error: 4181
SQLSTATE: HY000
(ER_RPL_SLAVE_DUMP_THREAD_KILLED_BY_MASTER
)
Message: Slave%s: received end packet from server due to dump thread being killed on master. Dump threads are killed for example during master shutdown, explicitly by a user, or when the master receives a binlog send request from a duplicate server UUID <%s> : Error %s
ER_RPL_SLAVE_DUMP_THREAD_KILLED_BY_MASTER
was added in 8.0.2.
Error: 4182
SQLSTATE: HY000
(ER_RPL_MTS_STATISTICS
)
Message: Multi-threaded slave 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
ER_RPL_MTS_STATISTICS
was added in
8.0.2.
Error: 4183
SQLSTATE: HY000
(ER_RPL_MTS_RECOVERY_COMPLETE
)
Message: Slave%s: MTS Recovery has completed at relay log %s, position %llu master log %s, position %llu.
ER_RPL_MTS_RECOVERY_COMPLETE
was
added in 8.0.2.
Error: 4184
SQLSTATE: HY000
(ER_RPL_SLAVE_CANT_INIT_RELAY_LOG_POSITION
)
Message: Error initializing relay log position%s: %s
ER_RPL_SLAVE_CANT_INIT_RELAY_LOG_POSITION
was added in 8.0.2.
Error: 4185
SQLSTATE: HY000
(ER_RPL_SLAVE_CONNECTED_TO_MASTER_REPLICATION_STARTED
)
Message: Slave I/O thread%s: connected to master '%s@%s:%d',replication started in log '%s' at position %s
ER_RPL_SLAVE_CONNECTED_TO_MASTER_REPLICATION_STARTED
was added in 8.0.2.
Error: 4186
SQLSTATE: HY000
(ER_RPL_SLAVE_IO_THREAD_KILLED
)
Message: Slave I/O thread%s killed while connecting to master
ER_RPL_SLAVE_IO_THREAD_KILLED
was
added in 8.0.2.
Error: 4187
SQLSTATE: HY000
(ER_RPL_SLAVE_IO_THREAD_CANT_REGISTER_ON_MASTER
)
Message: Slave I/O thread couldn't register on master
ER_RPL_SLAVE_IO_THREAD_CANT_REGISTER_ON_MASTER
was added in 8.0.2.
Error: 4188
SQLSTATE: HY000
(ER_RPL_SLAVE_FORCING_TO_RECONNECT_IO_THREAD
)
Message: Forcing to reconnect slave I/O thread%s
ER_RPL_SLAVE_FORCING_TO_RECONNECT_IO_THREAD
was added in 8.0.2.
Error: 4189
SQLSTATE: HY000
(ER_RPL_SLAVE_ERROR_REQUESTING_BINLOG_DUMP
)
Message: Failed on request_dump()%s
ER_RPL_SLAVE_ERROR_REQUESTING_BINLOG_DUMP
was added in 8.0.2.
Error: 4190
SQLSTATE: HY000
(ER_RPL_LOG_ENTRY_EXCEEDS_SLAVE_MAX_ALLOWED_PACKET
)
Message: Log entry on master is longer than slave_max_allowed_packet (%lu) on slave. If the entry is correct, restart the server with a higher value of slave_max_allowed_packet
ER_RPL_LOG_ENTRY_EXCEEDS_SLAVE_MAX_ALLOWED_PACKET
was added in 8.0.2.
Error: 4191
SQLSTATE: HY000
(ER_RPL_SLAVE_STOPPING_AS_MASTER_OOM
)
Message: Stopping slave I/O thread due to out-of-memory error from master
ER_RPL_SLAVE_STOPPING_AS_MASTER_OOM
was added in 8.0.2.
Error: 4192
SQLSTATE: HY000
(ER_RPL_SLAVE_IO_THREAD_ABORTED_WAITING_FOR_RELAY_LOG_SPACE
)
Message: Slave I/O thread aborted while waiting for relay log space
ER_RPL_SLAVE_IO_THREAD_ABORTED_WAITING_FOR_RELAY_LOG_SPACE
was added in 8.0.2.
Error: 4193
SQLSTATE: HY000
(ER_RPL_SLAVE_IO_THREAD_EXITING
)
Message: Slave I/O thread exiting%s, read up to log '%s', position %s
ER_RPL_SLAVE_IO_THREAD_EXITING
was
added in 8.0.2.
Error: 4194
SQLSTATE: HY000
(ER_RPL_SLAVE_CANT_INITIALIZE_SLAVE_WORKER
)
Message: Failed during slave worker initialization%s
ER_RPL_SLAVE_CANT_INITIALIZE_SLAVE_WORKER
was added in 8.0.2.
Error: 4195
SQLSTATE: HY000
(ER_RPL_MTS_GROUP_RECOVERY_RELAY_LOG_INFO_FOR_WORKER
)
Message: Slave: MTS group recovery relay log info based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_master_log_name %s, group_master_log_pos %llu
ER_RPL_MTS_GROUP_RECOVERY_RELAY_LOG_INFO_FOR_WORKER
was added in 8.0.2.
Error: 4196
SQLSTATE: HY000
(ER_RPL_ERROR_LOOKING_FOR_LOG
)
Message: Error looking for %s.
ER_RPL_ERROR_LOOKING_FOR_LOG
was
added in 8.0.2.
Error: 4197
SQLSTATE: HY000
(ER_RPL_MTS_GROUP_RECOVERY_RELAY_LOG_INFO
)
Message: Slave: MTS group recovery relay log info group_master_log_name %s, event_master_log_pos %llu.
ER_RPL_MTS_GROUP_RECOVERY_RELAY_LOG_INFO
was added in 8.0.2.
Error: 4198
SQLSTATE: HY000
(ER_RPL_CANT_FIND_FOLLOWUP_FILE
)
Message: Error looking for file after %s.
ER_RPL_CANT_FIND_FOLLOWUP_FILE
was
added in 8.0.2.
Error: 4199
SQLSTATE: HY000
(ER_RPL_MTS_CHECKPOINT_PERIOD_DIFFERS_FROM_CNT
)
Message: This an error cnt != mts_checkpoint_period
ER_RPL_MTS_CHECKPOINT_PERIOD_DIFFERS_FROM_CNT
was added in 8.0.2.
Error: 4200
SQLSTATE: HY000
(ER_RPL_SLAVE_WORKER_THREAD_CREATION_FAILED
)
Message: Failed during slave worker thread creation%s
ER_RPL_SLAVE_WORKER_THREAD_CREATION_FAILED
was added in 8.0.2.
Error: 4201
SQLSTATE: HY000
(ER_RPL_SLAVE_WORKER_THREAD_CREATION_FAILED_WITH_ERRNO
)
Message: Failed during slave worker thread creation%s (errno= %d)
ER_RPL_SLAVE_WORKER_THREAD_CREATION_FAILED_WITH_ERRNO
was added in 8.0.2.
Error: 4202
SQLSTATE: HY000
(ER_RPL_SLAVE_FAILED_TO_INIT_PARTITIONS_HASH
)
Message: Failed to init partitions hash
ER_RPL_SLAVE_FAILED_TO_INIT_PARTITIONS_HASH
was added in 8.0.2.
Error: 4203
SQLSTATE: HY000
(ER_RPL_SLAVE_NDB_TABLES_NOT_AVAILABLE
)
Message: Slave SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value
ER_RPL_SLAVE_NDB_TABLES_NOT_AVAILABLE
was added in 8.0.2.
Error: 4204
SQLSTATE: HY000
(ER_RPL_SLAVE_SQL_THREAD_STARTING
)
Message: Slave SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s
ER_RPL_SLAVE_SQL_THREAD_STARTING
was added in 8.0.2.
Error: 4205
SQLSTATE: HY000
(ER_RPL_SLAVE_SKIP_COUNTER_EXECUTED
)
Message: 'SQL_SLAVE_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', master_log_name='%s', master_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', master_log_name='%s', master_log_pos='%ld'
ER_RPL_SLAVE_SKIP_COUNTER_EXECUTED
was added in 8.0.2.
Error: 4206
SQLSTATE: HY000
(ER_RPL_SLAVE_ADDITIONAL_ERROR_INFO_FROM_DA
)
Message: Slave (additional info): %s Error_code: %d
ER_RPL_SLAVE_ADDITIONAL_ERROR_INFO_FROM_DA
was added in 8.0.2.
Error: 4207
SQLSTATE: HY000
(ER_RPL_SLAVE_ERROR_INFO_FROM_DA
)
Message: Slave: %s Error_code: %d
ER_RPL_SLAVE_ERROR_INFO_FROM_DA
was added in 8.0.2.
Error: 4208
SQLSTATE: HY000
(ER_RPL_SLAVE_ERROR_LOADING_USER_DEFINED_LIBRARY
)
Message: Error loading user-defined library, slave SQL thread aborted. Install the missing library, and restart the slave SQL thread with "SLAVE START". We stopped at log '%s' position %s
ER_RPL_SLAVE_ERROR_LOADING_USER_DEFINED_LIBRARY
was added in 8.0.2.
Error: 4209
SQLSTATE: HY000
(ER_RPL_SLAVE_ERROR_RUNNING_QUERY
)
Message: Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log '%s' position %s
ER_RPL_SLAVE_ERROR_RUNNING_QUERY
was added in 8.0.2.
Error: 4210
SQLSTATE: HY000
(ER_RPL_SLAVE_SQL_THREAD_EXITING
)
Message: Slave SQL thread%s exiting, replication stopped in log '%s' at position %s
ER_RPL_SLAVE_SQL_THREAD_EXITING
was added in 8.0.2.
Error: 4211
SQLSTATE: HY000
(ER_RPL_SLAVE_READ_INVALID_EVENT_FROM_MASTER
)
Message: Read invalid event from master: '%s', master could be corrupt but a more likely cause of this is a bug
ER_RPL_SLAVE_READ_INVALID_EVENT_FROM_MASTER
was added in 8.0.2.
Error: 4212
SQLSTATE: HY000
(ER_RPL_SLAVE_QUEUE_EVENT_FAILED_INVALID_CONFIGURATION
)
Message: The queue event failed for channel '%s' as its configuration is invalid.
ER_RPL_SLAVE_QUEUE_EVENT_FAILED_INVALID_CONFIGURATION
was added in 8.0.2.
Error: 4213
SQLSTATE: HY000
(ER_RPL_SLAVE_IO_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE
)
Message: An unexpected event sequence was detected by the IO thread while queuing the event received from master '%s' binary log file, at position %llu.
ER_RPL_SLAVE_IO_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE
was added in 8.0.2.
Error: 4214
SQLSTATE: HY000
(ER_RPL_SLAVE_CANT_USE_CHARSET
)
Message: '%s' can not be used as client character set. '%s' will be used as default client character set while connecting to master.
ER_RPL_SLAVE_CANT_USE_CHARSET
was
added in 8.0.2.
Error: 4215
SQLSTATE: HY000
(ER_RPL_SLAVE_CONNECTED_TO_MASTER_REPLICATION_RESUMED
)
Message: Slave%s: connected to master '%s@%s:%d',replication resumed in log '%s' at position %s
ER_RPL_SLAVE_CONNECTED_TO_MASTER_REPLICATION_RESUMED
was added in 8.0.2.
Error: 4216
SQLSTATE: HY000
(ER_RPL_SLAVE_NEXT_LOG_IS_ACTIVE
)
Message: next log '%s' is active
ER_RPL_SLAVE_NEXT_LOG_IS_ACTIVE
was added in 8.0.2.
Error: 4217
SQLSTATE: HY000
(ER_RPL_SLAVE_NEXT_LOG_IS_INACTIVE
)
Message: next log '%s' is not active
ER_RPL_SLAVE_NEXT_LOG_IS_INACTIVE
was added in 8.0.2.
Error: 4218
SQLSTATE: HY000
(ER_RPL_SLAVE_SQL_THREAD_IO_ERROR_READING_EVENT
)
Message: Slave SQL thread%s: I/O error reading event (errno: %d cur_log->error: %d)
ER_RPL_SLAVE_SQL_THREAD_IO_ERROR_READING_EVENT
was added in 8.0.2.
Error: 4219
SQLSTATE: HY000
(ER_RPL_SLAVE_ERROR_READING_RELAY_LOG_EVENTS
)
Message: Error reading relay log event%s: %s
ER_RPL_SLAVE_ERROR_READING_RELAY_LOG_EVENTS
was added in 8.0.2.
Error: 4220
SQLSTATE: HY000
(ER_SLAVE_CHANGE_MASTER_TO_EXECUTED
)
Message: 'CHANGE MASTER TO%s executed'. Previous state master_host='%s', master_port= %u, master_log_file='%s', master_log_pos= %ld, master_bind='%s'. New state master_host='%s', master_port= %u, master_log_file='%s', master_log_pos= %ld, master_bind='%s'.
ER_SLAVE_CHANGE_MASTER_TO_EXECUTED
was added in 8.0.2.
Error: 4221
SQLSTATE: HY000
(ER_RPL_SLAVE_NEW_MASTER_INFO_NEEDS_REPOS_TYPE_OTHER_THAN_FILE
)
Message: Slave: Cannot create new master info structure when repositories are of type FILE. Convert slave repositories to TABLE to replicate from multiple sources.
ER_RPL_SLAVE_NEW_MASTER_INFO_NEEDS_REPOS_TYPE_OTHER_THAN_FILE
was added in 8.0.2.
Error: 4222
SQLSTATE: HY000
(ER_RPL_FAILED_TO_STAT_LOG_IN_INDEX
)
Message: log %s listed in the index, but failed to stat.
ER_RPL_FAILED_TO_STAT_LOG_IN_INDEX
was added in 8.0.2.
Error: 4223
SQLSTATE: HY000
(ER_RPL_LOG_NOT_FOUND_WHILE_COUNTING_RELAY_LOG_SPACE
)
Message: Could not find first log while counting relay log space.
ER_RPL_LOG_NOT_FOUND_WHILE_COUNTING_RELAY_LOG_SPACE
was added in 8.0.2.
Error: 4224
SQLSTATE: HY000
(ER_SLAVE_CANT_USE_TEMPDIR
)
Message: Unable to use slave's temporary directory '%s'.
ER_SLAVE_CANT_USE_TEMPDIR
was
added in 8.0.2.
Error: 4225
SQLSTATE: HY000
(ER_RPL_RELAY_LOG_NEEDS_FILE_NOT_DIRECTORY
)
Message: Path '%s' is a directory name, please specify a file name for --relay-log option.
ER_RPL_RELAY_LOG_NEEDS_FILE_NOT_DIRECTORY
was added in 8.0.2.
Error: 4226
SQLSTATE: HY000
(ER_RPL_RELAY_LOG_INDEX_NEEDS_FILE_NOT_DIRECTORY
)
Message: Path '%s' is a directory name, please specify a file name for --relay-log-index option.
ER_RPL_RELAY_LOG_INDEX_NEEDS_FILE_NOT_DIRECTORY
was added in 8.0.2.
Error: 4227
SQLSTATE: HY000
(ER_RPL_PLEASE_USE_OPTION_RELAY_LOG
)
Message: Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.
ER_RPL_PLEASE_USE_OPTION_RELAY_LOG
was added in 8.0.2.
Error: 4228
SQLSTATE: HY000
(ER_RPL_OPEN_INDEX_FILE_FAILED
)
Message: Failed in open_index_file() called from Relay_log_info::rli_init_info().
ER_RPL_OPEN_INDEX_FILE_FAILED
was
added in 8.0.2.
Error: 4229
SQLSTATE: HY000
(ER_RPL_CANT_INITIALIZE_GTID_SETS_IN_RLI_INIT_INFO
)
Message: Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().
ER_RPL_CANT_INITIALIZE_GTID_SETS_IN_RLI_INIT_INFO
was added in 8.0.2.
Error: 4230
SQLSTATE: HY000
(ER_RPL_CANT_OPEN_LOG_IN_RLI_INIT_INFO
)
Message: Failed in open_log() called from Relay_log_info::rli_init_info().
ER_RPL_CANT_OPEN_LOG_IN_RLI_INIT_INFO
was added in 8.0.2.
Error: 4231
SQLSTATE: HY000
(ER_RPL_ERROR_WRITING_RELAY_LOG_CONFIGURATION
)
Message: Error writing relay log configuration.
ER_RPL_ERROR_WRITING_RELAY_LOG_CONFIGURATION
was added in 8.0.2.
Error: 4232
SQLSTATE: HY000
(ER_NDB_OOM_GET_NDB_BLOBS_VALUE
)
Message: get_ndb_blobs_value: my_malloc(%u) failed
ER_NDB_OOM_GET_NDB_BLOBS_VALUE
was
added in 8.0.2.
Error: 4233
SQLSTATE: HY000
(ER_NDB_THREAD_TIMED_OUT
)
Message: NDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled. Progress : %u/%u -> %u/%u.
ER_NDB_THREAD_TIMED_OUT
was added
in 8.0.2.
Error: 4234
SQLSTATE: HY000
(ER_NDB_TABLE_IS_NOT_DISTRIBUTED
)
Message: NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributed
ER_NDB_TABLE_IS_NOT_DISTRIBUTED
was added in 8.0.2.
Error: 4235
SQLSTATE: HY000
(ER_NDB_CREATING_TABLE
)
Message: NDB: Creating %s.%s
ER_NDB_CREATING_TABLE
was added in
8.0.2.
Error: 4236
SQLSTATE: HY000
(ER_NDB_FLUSHING_TABLE_INFO
)
Message: NDB: Flushing %s.%s
ER_NDB_FLUSHING_TABLE_INFO
was
added in 8.0.2.
Error: 4237
SQLSTATE: HY000
(ER_NDB_CLEANING_STRAY_TABLES
)
Message: NDB: Cleaning stray tables from database '%s'
ER_NDB_CLEANING_STRAY_TABLES
was
added in 8.0.2.
Error: 4238
SQLSTATE: HY000
(ER_NDB_DISCOVERED_MISSING_DB
)
Message: NDB: Discovered missing database '%s'
ER_NDB_DISCOVERED_MISSING_DB
was
added in 8.0.2.
Error: 4239
SQLSTATE: HY000
(ER_NDB_DISCOVERED_REMAINING_DB
)
Message: NDB: Discovered remaining database '%s'
ER_NDB_DISCOVERED_REMAINING_DB
was
added in 8.0.2.
Error: 4240
SQLSTATE: HY000
(ER_NDB_CLUSTER_FIND_ALL_DBS_RETRY
)
Message: NDB: ndbcluster_find_all_databases retry: %u - %s
ER_NDB_CLUSTER_FIND_ALL_DBS_RETRY
was added in 8.0.2.
Error: 4241
SQLSTATE: HY000
(ER_NDB_CLUSTER_FIND_ALL_DBS_FAIL
)
Message: NDB: ndbcluster_find_all_databases fail: %u - %s
ER_NDB_CLUSTER_FIND_ALL_DBS_FAIL
was added in 8.0.2.
Error: 4242
SQLSTATE: HY000
(ER_NDB_SKIPPING_SETUP_TABLE
)
Message: NDB: skipping setup table %s.%s, in state %d
ER_NDB_SKIPPING_SETUP_TABLE
was
added in 8.0.2.
Error: 4243
SQLSTATE: HY000
(ER_NDB_FAILED_TO_SET_UP_TABLE
)
Message: NDB: failed to setup table %s.%s, error: %d, %s
ER_NDB_FAILED_TO_SET_UP_TABLE
was
added in 8.0.2.
Error: 4244
SQLSTATE: HY000
(ER_NDB_MISSING_FRM_DISCOVERING
)
Message: NDB: missing frm for %s.%s, discovering...
ER_NDB_MISSING_FRM_DISCOVERING
was
added in 8.0.2.
Error: 4245
SQLSTATE: HY000
(ER_NDB_MISMATCH_IN_FRM_DISCOVERING
)
Message: NDB: mismatch in frm for %s.%s, discovering...
ER_NDB_MISMATCH_IN_FRM_DISCOVERING
was added in 8.0.2.
Error: 4246
SQLSTATE: HY000
(ER_NDB_BINLOG_CLEANING_UP_SETUP_LEFTOVERS
)
Message: ndb_binlog_setup: Clean up leftovers
ER_NDB_BINLOG_CLEANING_UP_SETUP_LEFTOVERS
was added in 8.0.2.
Error: 4247
SQLSTATE: HY000
(ER_NDB_WAITING_INFO
)
Message: NDB %s: waiting max %u sec for %s %s. epochs: (%u/%u,%u/%u,%u/%u) injector proc_info: %s
ER_NDB_WAITING_INFO
was added in
8.0.2.
Error: 4248
SQLSTATE: HY000
(ER_NDB_WAITING_INFO_WITH_MAP
)
Message: NDB %s: waiting max %u sec for %s %s. epochs: (%u/%u,%u/%u,%u/%u) injector proc_info: %s map: %x%08x
ER_NDB_WAITING_INFO_WITH_MAP
was
added in 8.0.2.
Error: 4249
SQLSTATE: HY000
(ER_NDB_TIMEOUT_WHILE_DISTRIBUTING
)
Message: NDB %s: distributing %s timed out. Ignoring...
ER_NDB_TIMEOUT_WHILE_DISTRIBUTING
was added in 8.0.2.
Error: 4250
SQLSTATE: HY000
(ER_NDB_NOT_WAITING_FOR_DISTRIBUTING
)
Message: NDB %s: not waiting for distributing %s
ER_NDB_NOT_WAITING_FOR_DISTRIBUTING
was added in 8.0.2.
Error: 4251
SQLSTATE: HY000
(ER_NDB_DISTRIBUTED_INFO
)
Message: NDB: distributed %s.%s(%u/%u) type: %s(%u) query: \'%s\' to %x%08x
ER_NDB_DISTRIBUTED_INFO
was added
in 8.0.2.
Error: 4252
SQLSTATE: HY000
(ER_NDB_DISTRIBUTION_COMPLETE
)
Message: NDB: distribution of %s.%s(%u/%u) type: %s(%u) query: \'%s\' - complete!
ER_NDB_DISTRIBUTION_COMPLETE
was
added in 8.0.2.
Error: 4253
SQLSTATE: HY000
(ER_NDB_SCHEMA_DISTRIBUTION_FAILED
)
Message: NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08x
ER_NDB_SCHEMA_DISTRIBUTION_FAILED
was added in 8.0.2.
Error: 4254
SQLSTATE: HY000
(ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_SUBSCRIBE
)
Message: NDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08x
ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_SUBSCRIBE
was added in 8.0.2.
Error: 4255
SQLSTATE: HY000
(ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_UNSUBSCRIBE
)
Message: NDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08x
ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_UNSUBSCRIBE
was added in 8.0.2.
Error: 4256
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_DISCOVER_TABLE_FROM_SCHEMA_EVENT
)
Message: NDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %d
ER_NDB_BINLOG_CANT_DISCOVER_TABLE_FROM_SCHEMA_EVENT
was added in 8.0.2.
Error: 4257
SQLSTATE: HY000
(ER_NDB_BINLOG_SIGNALLING_UNKNOWN_VALUE
)
Message: NDB: unknown value for binlog signalling 0x%X, %s not logged
ER_NDB_BINLOG_SIGNALLING_UNKNOWN_VALUE
was added in 8.0.2.
Error: 4258
SQLSTATE: HY000
(ER_NDB_BINLOG_REPLY_TO
)
Message: NDB: reply to %s.%s(%u/%u) from %s to %x%08x
ER_NDB_BINLOG_REPLY_TO
was added
in 8.0.2.
Error: 4259
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_RELEASE_SLOCK
)
Message: NDB: Could not release slock on '%s.%s', Error code: %d Message: %s
ER_NDB_BINLOG_CANT_RELEASE_SLOCK
was added in 8.0.2.
Error: 4260
SQLSTATE: HY000
(ER_NDB_CANT_FIND_TABLE
)
Message: NDB schema: Could not find table '%s.%s' in NDB
ER_NDB_CANT_FIND_TABLE
was added
in 8.0.2.
Error: 4261
SQLSTATE: HY000
(ER_NDB_DISCARDING_EVENT_NO_OBJ
)
Message: NDB: Discarding event...no obj: %s (%u/%u)
ER_NDB_DISCARDING_EVENT_NO_OBJ
was
added in 8.0.2.
Error: 4262
SQLSTATE: HY000
(ER_NDB_DISCARDING_EVENT_ID_VERSION_MISMATCH
)
Message: NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]
ER_NDB_DISCARDING_EVENT_ID_VERSION_MISMATCH
was added in 8.0.2.
Error: 4263
SQLSTATE: HY000
(ER_NDB_CLEAR_SLOCK_INFO
)
Message: NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08x
ER_NDB_CLEAR_SLOCK_INFO
was added
in 8.0.2.
Error: 4264
SQLSTATE: HY000
(ER_NDB_BINLOG_SKIPPING_LOCAL_TABLE
)
Message: NDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.
ER_NDB_BINLOG_SKIPPING_LOCAL_TABLE
was added in 8.0.2.
Error: 4265
SQLSTATE: HY000
(ER_NDB_BINLOG_ONLINE_ALTER_RENAME
)
Message: NDB Binlog: handling online alter/rename
ER_NDB_BINLOG_ONLINE_ALTER_RENAME
was added in 8.0.2.
Error: 4266
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_REOPEN_SHADOW_TABLE
)
Message: NDB Binlog: Failed to re-open shadow table %s.%s
ER_NDB_BINLOG_CANT_REOPEN_SHADOW_TABLE
was added in 8.0.2.
Error: 4267
SQLSTATE: HY000
(ER_NDB_BINLOG_ONLINE_ALTER_RENAME_COMPLETE
)
Message: NDB Binlog: handling online alter/rename done
ER_NDB_BINLOG_ONLINE_ALTER_RENAME_COMPLETE
was added in 8.0.2.
Error: 4268
SQLSTATE: HY000
(ER_NDB_BINLOG_SKIPPING_DROP_OF_LOCAL_TABLE
)
Message: NDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d.
ER_NDB_BINLOG_SKIPPING_DROP_OF_LOCAL_TABLE
was added in 8.0.2.
Error: 4269
SQLSTATE: HY000
(ER_NDB_BINLOG_SKIPPING_RENAME_OF_LOCAL_TABLE
)
Message: NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d.
ER_NDB_BINLOG_SKIPPING_RENAME_OF_LOCAL_TABLE
was added in 8.0.2.
Error: 4270
SQLSTATE: HY000
(ER_NDB_BINLOG_SKIPPING_DROP_OF_DB_CONTAINING_LOCAL_TABLES
)
Message: NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d.
ER_NDB_BINLOG_SKIPPING_DROP_OF_DB_CONTAINING_LOCAL_TABLES
was added in 8.0.2.
Error: 4271
SQLSTATE: HY000
(ER_NDB_BINLOG_GOT_DIST_PRIV_EVENT_FLUSHING_PRIVILEGES
)
Message: Got dist_priv event: %s, flushing privileges
ER_NDB_BINLOG_GOT_DIST_PRIV_EVENT_FLUSHING_PRIVILEGES
was added in 8.0.2.
Error: 4272
SQLSTATE: HY000
(ER_NDB_BINLOG_GOT_SCHEMA_EVENT
)
Message: NDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08x
ER_NDB_BINLOG_GOT_SCHEMA_EVENT
was
added in 8.0.2.
Error: 4273
SQLSTATE: HY000
(ER_NDB_BINLOG_SKIPPING_OLD_SCHEMA_OPERATION
)
Message: NDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%s
ER_NDB_BINLOG_SKIPPING_OLD_SCHEMA_OPERATION
was added in 8.0.2.
Error: 4274
SQLSTATE: HY000
(ER_NDB_CLUSTER_FAILURE
)
Message: NDB Schema dist: cluster failure at epoch %u/%u.
ER_NDB_CLUSTER_FAILURE
was added
in 8.0.2.
Error: 4275
SQLSTATE: HY000
(ER_NDB_TABLES_INITIALLY_READ_ONLY_ON_RECONNECT
)
Message: NDB Binlog: ndb tables initially read only on reconnect.
ER_NDB_TABLES_INITIALLY_READ_ONLY_ON_RECONNECT
was added in 8.0.2.
Error: 4276
SQLSTATE: HY000
(ER_NDB_IGNORING_UNKNOWN_EVENT
)
Message: NDB Schema dist: unknown event %u, ignoring...
ER_NDB_IGNORING_UNKNOWN_EVENT
was
added in 8.0.2.
Error: 4277
SQLSTATE: HY000
(ER_NDB_BINLOG_OPENING_INDEX
)
Message: NDB Binlog: Opening ndb_binlog_index: %d, '%s'
ER_NDB_BINLOG_OPENING_INDEX
was
added in 8.0.2.
Error: 4278
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_LOCK_NDB_BINLOG_INDEX
)
Message: NDB Binlog: Unable to lock table ndb_binlog_index
ER_NDB_BINLOG_CANT_LOCK_NDB_BINLOG_INDEX
was added in 8.0.2.
Error: 4279
SQLSTATE: HY000
(ER_NDB_BINLOG_INJECTING_RANDOM_WRITE_FAILURE
)
Message: NDB Binlog: Injecting random write failure
ER_NDB_BINLOG_INJECTING_RANDOM_WRITE_FAILURE
was added in 8.0.2.
Error: 4280
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_WRITE_TO_NDB_BINLOG_INDEX
)
Message: NDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u orig_server_id %u orig_epoch %u/%u with error %d.
ER_NDB_BINLOG_CANT_WRITE_TO_NDB_BINLOG_INDEX
was added in 8.0.2.
Error: 4281
SQLSTATE: HY000
(ER_NDB_BINLOG_WRITING_TO_NDB_BINLOG_INDEX
)
Message: NDB Binlog: Writing row (%s) to ndb_binlog_index - %s
ER_NDB_BINLOG_WRITING_TO_NDB_BINLOG_INDEX
was added in 8.0.2.
Error: 4282
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_COMMIT_TO_NDB_BINLOG_INDEX
)
Message: NDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.
ER_NDB_BINLOG_CANT_COMMIT_TO_NDB_BINLOG_INDEX
was added in 8.0.2.
Error: 4283
SQLSTATE: HY000
(ER_NDB_BINLOG_WRITE_TO_NDB_BINLOG_INDEX_FAILED_AFTER_KILL
)
Message: NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdown
ER_NDB_BINLOG_WRITE_TO_NDB_BINLOG_INDEX_FAILED_AFTER_KILL
was added in 8.0.2.
Error: 4284
SQLSTATE: HY000
(ER_NDB_BINLOG_USING_SERVER_ID_0_SLAVES_WILL_NOT
)
Message: NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by slave mysqlds
ER_NDB_BINLOG_USING_SERVER_ID_0_SLAVES_WILL_NOT
was added in 8.0.2.
Error: 4285
SQLSTATE: HY000
(ER_NDB_SERVER_ID_RESERVED_OR_TOO_LARGE
)
Message: NDB: server id provided is too large to be represented in opt_server_id_bits or is reserved
ER_NDB_SERVER_ID_RESERVED_OR_TOO_LARGE
was added in 8.0.2.
Error: 4286
SQLSTATE: HY000
(ER_NDB_BINLOG_NDB_LOG_TRANSACTION_ID_REQUIRES_V2_ROW_EVENTS
)
Message: NDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.
ER_NDB_BINLOG_NDB_LOG_TRANSACTION_ID_REQUIRES_V2_ROW_EVENTS
was added in 8.0.2.
Error: 4287
SQLSTATE: HY000
(ER_NDB_BINLOG_NDB_LOG_APPLY_STATUS_FORCING_FULL_USE_WRITE
)
Message: NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITE
ER_NDB_BINLOG_NDB_LOG_APPLY_STATUS_FORCING_FULL_USE_WRITE
was added in 8.0.2.
Error: 4288
SQLSTATE: HY000
(ER_NDB_BINLOG_GENERIC_MESSAGE
)
Message: NDB Binlog: %s
ER_NDB_BINLOG_GENERIC_MESSAGE
was
added in 8.0.2.
Error: 4289
SQLSTATE: HY000
(ER_NDB_CONFLICT_GENERIC_MESSAGE
)
Message: %s
ER_NDB_CONFLICT_GENERIC_MESSAGE
was added in 8.0.2.
Error: 4290
SQLSTATE: HY000
(ER_NDB_TRANS_DEPENDENCY_TRACKER_ERROR
)
Message: %s
ER_NDB_TRANS_DEPENDENCY_TRACKER_ERROR
was added in 8.0.2.
Error: 4291
SQLSTATE: HY000
(ER_NDB_CONFLICT_FN_PARSE_ERROR
)
Message: NDB Slave: Table %s.%s : Parse error on conflict fn : %s
ER_NDB_CONFLICT_FN_PARSE_ERROR
was
added in 8.0.2.
Error: 4292
SQLSTATE: HY000
(ER_NDB_CONFLICT_FN_SETUP_ERROR
)
Message: NDB Slave: Table %s.%s : %s
ER_NDB_CONFLICT_FN_SETUP_ERROR
was
added in 8.0.2.
Error: 4293
SQLSTATE: HY000
(ER_NDB_BINLOG_FAILED_TO_GET_TABLE
)
Message: NDB Binlog: Failed to get table %s from ndb: %s, %d
ER_NDB_BINLOG_FAILED_TO_GET_TABLE
was added in 8.0.2.
Error: 4294
SQLSTATE: HY000
(ER_NDB_BINLOG_NOT_LOGGING
)
Message: NDB Binlog: NOT logging %s
ER_NDB_BINLOG_NOT_LOGGING
was
added in 8.0.2.
Error: 4295
SQLSTATE: HY000
(ER_NDB_BINLOG_CREATE_TABLE_EVENT_FAILED
)
Message: NDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %s
ER_NDB_BINLOG_CREATE_TABLE_EVENT_FAILED
was added in 8.0.2.
Error: 4296
SQLSTATE: HY000
(ER_NDB_BINLOG_CREATE_TABLE_EVENT_INFO
)
Message: NDB Binlog: CREATE (DISCOVER) TABLE Event: %s
ER_NDB_BINLOG_CREATE_TABLE_EVENT_INFO
was added in 8.0.2.
Error: 4297
SQLSTATE: HY000
(ER_NDB_BINLOG_DISCOVER_TABLE_EVENT_INFO
)
Message: NDB Binlog: DISCOVER TABLE Event: %s
ER_NDB_BINLOG_DISCOVER_TABLE_EVENT_INFO
was added in 8.0.2.
Error: 4298
SQLSTATE: HY000
(ER_NDB_BINLOG_BLOB_REQUIRES_PK
)
Message: NDB Binlog: logging of table %s with BLOB attribute and no PK is not supported
ER_NDB_BINLOG_BLOB_REQUIRES_PK
was
added in 8.0.2.
Error: 4299
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB
)
Message: NDB Binlog: Unable to create event in database. Event: %s Error Code: %d Message: %s
ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB
was added in 8.0.2.
Error: 4300
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_AND_CANT_DROP
)
Message: NDB Binlog: Unable to create event in database. Attempt to correct with drop failed. Event: %s Error Code: %d Message: %s
ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_AND_CANT_DROP
was added in 8.0.2.
Error: 4301
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_DROPPED
)
Message: NDB Binlog: Unable to create event in database. Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %s
ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_DROPPED
was added in 8.0.2.
Error: 4302
SQLSTATE: HY000
(ER_NDB_BINLOG_DISCOVER_REUSING_OLD_EVENT_OPS
)
Message: NDB Binlog: discover reusing old ev op
ER_NDB_BINLOG_DISCOVER_REUSING_OLD_EVENT_OPS
was added in 8.0.2.
Error: 4303
SQLSTATE: HY000
(ER_NDB_BINLOG_CREATING_NDBEVENTOPERATION_FAILED
)
Message: NDB Binlog: Creating NdbEventOperation failed for %s
ER_NDB_BINLOG_CREATING_NDBEVENTOPERATION_FAILED
was added in 8.0.2.
Error: 4304
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_CREATE_BLOB
)
Message: NDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %s
ER_NDB_BINLOG_CANT_CREATE_BLOB
was
added in 8.0.2.
Error: 4305
SQLSTATE: HY000
(ER_NDB_BINLOG_NDBEVENT_EXECUTE_FAILED
)
Message: NDB Binlog: ndbevent->execute failed for %s; %d %s
ER_NDB_BINLOG_NDBEVENT_EXECUTE_FAILED
was added in 8.0.2.
Error: 4306
SQLSTATE: HY000
(ER_NDB_CREATE_EVENT_OPS_LOGGING_INFO
)
Message: NDB Binlog: logging %s (%s,%s)
ER_NDB_CREATE_EVENT_OPS_LOGGING_INFO
was added in 8.0.2.
Error: 4307
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_DROP_EVENT_FROM_DB
)
Message: NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %s
ER_NDB_BINLOG_CANT_DROP_EVENT_FROM_DB
was added in 8.0.2.
Error: 4308
SQLSTATE: HY000
(ER_NDB_TIMED_OUT_IN_DROP_TABLE
)
Message: NDB %s: %s timed out. Ignoring...
ER_NDB_TIMED_OUT_IN_DROP_TABLE
was
added in 8.0.2.
Error: 4309
SQLSTATE: HY000
(ER_NDB_BINLOG_UNHANDLED_ERROR_FOR_TABLE
)
Message: NDB Binlog: unhandled error %d for table %s
ER_NDB_BINLOG_UNHANDLED_ERROR_FOR_TABLE
was added in 8.0.2.
Error: 4310
SQLSTATE: HY000
(ER_NDB_BINLOG_CLUSTER_FAILURE
)
Message: NDB Binlog: cluster failure for %s at epoch %u/%u.
ER_NDB_BINLOG_CLUSTER_FAILURE
was
added in 8.0.2.
Error: 4311
SQLSTATE: HY000
(ER_NDB_BINLOG_UNKNOWN_NON_DATA_EVENT
)
Message: NDB Binlog: unknown non data event %d for %s. Ignoring...
ER_NDB_BINLOG_UNKNOWN_NON_DATA_EVENT
was added in 8.0.2.
Error: 4312
SQLSTATE: HY000
(ER_NDB_BINLOG_INJECTOR_DISCARDING_ROW_EVENT_METADATA
)
Message: NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)
ER_NDB_BINLOG_INJECTOR_DISCARDING_ROW_EVENT_METADATA
was added in 8.0.2.
Error: 4313
SQLSTATE: HY000
(ER_NDB_REMAINING_OPEN_TABLES
)
Message: remove_all_event_operations: Remaining open tables:
ER_NDB_REMAINING_OPEN_TABLES
was
added in 8.0.2.
Error: 4314
SQLSTATE: HY000
(ER_NDB_REMAINING_OPEN_TABLE_INFO
)
Message: %s.%s, use_count: %u
ER_NDB_REMAINING_OPEN_TABLE_INFO
was added in 8.0.2.
Error: 4315
SQLSTATE: HY000
(ER_NDB_COULD_NOT_GET_APPLY_STATUS_SHARE
)
Message: NDB: Could not get apply status share
ER_NDB_COULD_NOT_GET_APPLY_STATUS_SHARE
was added in 8.0.2.
Error: 4316
SQLSTATE: HY000
(ER_NDB_BINLOG_SERVER_SHUTDOWN_DURING_NDB_CLUSTER_START
)
Message: NDB Binlog: Server shutdown detected while waiting for ndbcluster to start...
ER_NDB_BINLOG_SERVER_SHUTDOWN_DURING_NDB_CLUSTER_START
was added in 8.0.2.
Error: 4317
SQLSTATE: HY000
(ER_NDB_BINLOG_CLUSTER_RESTARTED_RESET_MASTER_SUGGESTED
)
Message: NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET MASTER should be issued. Resetting ndb_latest_handled_binlog_epoch.
ER_NDB_BINLOG_CLUSTER_RESTARTED_RESET_MASTER_SUGGESTED
was added in 8.0.2.
Error: 4318
SQLSTATE: HY000
(ER_NDB_BINLOG_CLUSTER_HAS_RECONNECTED
)
Message: NDB Binlog: cluster has reconnected. Changes to the database that occured while disconnected will not be in the binlog
ER_NDB_BINLOG_CLUSTER_HAS_RECONNECTED
was added in 8.0.2.
Error: 4319
SQLSTATE: HY000
(ER_NDB_BINLOG_STARTING_LOG_AT_EPOCH
)
Message: NDB Binlog: starting log at epoch %u/%u
ER_NDB_BINLOG_STARTING_LOG_AT_EPOCH
was added in 8.0.2.
Error: 4320
SQLSTATE: HY000
(ER_NDB_BINLOG_NDB_TABLES_WRITABLE
)
Message: NDB Binlog: ndb tables writable
ER_NDB_BINLOG_NDB_TABLES_WRITABLE
was added in 8.0.2.
Error: 4321
SQLSTATE: HY000
(ER_NDB_BINLOG_SHUTDOWN_DETECTED
)
Message: NDB Binlog: Server shutdown detected...
ER_NDB_BINLOG_SHUTDOWN_DETECTED
was added in 8.0.2.
Error: 4322
SQLSTATE: HY000
(ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_WAITING
)
Message: NDB Binlog: Just lost schema connection, hanging around
ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_WAITING
was added in 8.0.2.
Error: 4323
SQLSTATE: HY000
(ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_CONTINUING
)
Message: NDB Binlog: ...and on our way
ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_CONTINUING
was added in 8.0.2.
Error: 4324
SQLSTATE: HY000
(ER_NDB_BINLOG_ERROR_HANDLING_SCHEMA_EVENT
)
Message: NDB: error %lu (%s) on handling binlog schema event
ER_NDB_BINLOG_ERROR_HANDLING_SCHEMA_EVENT
was added in 8.0.2.
Error: 4325
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_INJECT_APPLY_STATUS_WRITE_ROW
)
Message: NDB Binlog: Failed to inject apply status write row
ER_NDB_BINLOG_CANT_INJECT_APPLY_STATUS_WRITE_ROW
was added in 8.0.2.
Error: 4326
SQLSTATE: HY000
(ER_NDB_BINLOG_ERROR_DURING_GCI_ROLLBACK
)
Message: NDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %d
ER_NDB_BINLOG_ERROR_DURING_GCI_ROLLBACK
was added in 8.0.2.
Error: 4327
SQLSTATE: HY000
(ER_NDB_BINLOG_ERROR_DURING_GCI_COMMIT
)
Message: NDB Binlog: Error during COMMIT of GCI. Error: %d
ER_NDB_BINLOG_ERROR_DURING_GCI_COMMIT
was added in 8.0.2.
Error: 4328
SQLSTATE: HY000
(ER_NDB_BINLOG_LATEST_TRX_IN_EPOCH_NOT_IN_BINLOG
)
Message: NDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%u
ER_NDB_BINLOG_LATEST_TRX_IN_EPOCH_NOT_IN_BINLOG
was added in 8.0.2.
Error: 4329
SQLSTATE: HY000
(ER_NDB_BINLOG_RELEASING_EXTRA_SHARE_REFERENCES
)
Message: NDB Binlog: Release extra share references
ER_NDB_BINLOG_RELEASING_EXTRA_SHARE_REFERENCES
was added in 8.0.2.
Error: 4330
SQLSTATE: HY000
(ER_NDB_BINLOG_REMAINING_OPEN_TABLES
)
Message: NDB Binlog: remaining open tables:
ER_NDB_BINLOG_REMAINING_OPEN_TABLES
was added in 8.0.2.
Error: 4331
SQLSTATE: HY000
(ER_NDB_BINLOG_REMAINING_OPEN_TABLE_INFO
)
Message: %s.%s state: %u use_count: %u
ER_NDB_BINLOG_REMAINING_OPEN_TABLE_INFO
was added in 8.0.2.
Error: 4332
SQLSTATE: HY000
(ER_TREE_CORRUPT_PARENT_SHOULD_POINT_AT_PARENT
)
Message: Wrong tree: Parent doesn't point at parent
ER_TREE_CORRUPT_PARENT_SHOULD_POINT_AT_PARENT
was added in 8.0.2.
Error: 4333
SQLSTATE: HY000
(ER_TREE_CORRUPT_ROOT_SHOULD_BE_BLACK
)
Message: Wrong tree: Root should be black
ER_TREE_CORRUPT_ROOT_SHOULD_BE_BLACK
was added in 8.0.2.
Error: 4334
SQLSTATE: HY000
(ER_TREE_CORRUPT_2_CONSECUTIVE_REDS
)
Message: Wrong tree: Found two red in a row
ER_TREE_CORRUPT_2_CONSECUTIVE_REDS
was added in 8.0.2.
Error: 4335
SQLSTATE: HY000
(ER_TREE_CORRUPT_RIGHT_IS_LEFT
)
Message: Wrong tree: Found right == left
ER_TREE_CORRUPT_RIGHT_IS_LEFT
was
added in 8.0.2.
Error: 4336
SQLSTATE: HY000
(ER_TREE_CORRUPT_INCORRECT_BLACK_COUNT
)
Message: Wrong tree: Incorrect black-count: %d - %d
ER_TREE_CORRUPT_INCORRECT_BLACK_COUNT
was added in 8.0.2.
Error: 4337
SQLSTATE: HY000
(ER_WRONG_COUNT_FOR_ORIGIN
)
Message: Use_count: Wrong count %lu for origin %p
ER_WRONG_COUNT_FOR_ORIGIN
was
added in 8.0.2.
Error: 4338
SQLSTATE: HY000
(ER_WRONG_COUNT_FOR_KEY
)
Message: Use_count: Wrong count for key at %p, %lu should be %lu
ER_WRONG_COUNT_FOR_KEY
was added
in 8.0.2.
Error: 4339
SQLSTATE: HY000
(ER_WRONG_COUNT_OF_ELEMENTS
)
Message: Wrong number of elements: %u (should be %u) for tree at %p
ER_WRONG_COUNT_OF_ELEMENTS
was
added in 8.0.2.
Error: 4340
SQLSTATE: HY000
(ER_RPL_ERROR_READING_SLAVE_WORKER_CONFIGURATION
)
Message: Error reading slave worker configuration
ER_RPL_ERROR_READING_SLAVE_WORKER_CONFIGURATION
was added in 8.0.2.
Error: 4341
SQLSTATE: HY000
(ER_RPL_ERROR_WRITING_SLAVE_WORKER_CONFIGURATION
)
Message: Error writing slave worker configuration
ER_RPL_ERROR_WRITING_SLAVE_WORKER_CONFIGURATION
was added in 8.0.2.
Error: 4342
SQLSTATE: HY000
(ER_RPL_FAILED_TO_OPEN_RELAY_LOG
)
Message: Failed to open relay log %s, error: %s
ER_RPL_FAILED_TO_OPEN_RELAY_LOG
was added in 8.0.2.
Error: 4343
SQLSTATE: HY000
(ER_RPL_WORKER_CANT_READ_RELAY_LOG
)
Message: Error when worker read relay log events,relay log name %s, position %llu
ER_RPL_WORKER_CANT_READ_RELAY_LOG
was added in 8.0.2.
Error: 4344
SQLSTATE: HY000
(ER_RPL_WORKER_CANT_FIND_NEXT_RELAY_LOG
)
Message: Failed to find next relay log when retrying the transaction, current relay log is %s
ER_RPL_WORKER_CANT_FIND_NEXT_RELAY_LOG
was added in 8.0.2.
Error: 4345
SQLSTATE: HY000
(ER_RPL_MTS_SLAVE_COORDINATOR_HAS_WAITED
)
Message: Multi-threaded slave: Coordinator has waited %lu times hitting slave_pending_jobs_size_max; current event size = %zu.
ER_RPL_MTS_SLAVE_COORDINATOR_HAS_WAITED
was added in 8.0.2.
Error: 4346
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_WRITE_DROP_FOR_TEMP_TABLES
)
Message: Failed to write the DROP statement for temporary tables to binary log
ER_BINLOG_FAILED_TO_WRITE_DROP_FOR_TEMP_TABLES
was added in 8.0.2.
Error: 4347
SQLSTATE: HY000
(ER_BINLOG_OOM_WRITING_DELETE_WHILE_OPENING_HEAP_TABLE
)
Message: When opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary log
ER_BINLOG_OOM_WRITING_DELETE_WHILE_OPENING_HEAP_TABLE
was added in 8.0.2.
Error: 4348
SQLSTATE: HY000
(ER_FAILED_TO_REPAIR_TABLE
)
Message: Couldn't repair table: %s.%s
ER_FAILED_TO_REPAIR_TABLE
was
added in 8.0.2.
Error: 4349
SQLSTATE: HY000
(ER_FAILED_TO_REMOVE_TEMP_TABLE
)
Message: Could not remove temporary table: '%s', error: %d
ER_FAILED_TO_REMOVE_TEMP_TABLE
was
added in 8.0.2.
Error: 4350
SQLSTATE: HY000
(ER_SYSTEM_TABLE_NOT_TRANSACTIONAL
)
Message: System table '%.*s' is expected to be transactional.
ER_SYSTEM_TABLE_NOT_TRANSACTIONAL
was added in 8.0.2.
Error: 4351
SQLSTATE: HY000
(ER_RPL_ERROR_WRITING_MASTER_CONFIGURATION
)
Message: Error writing master configuration.
ER_RPL_ERROR_WRITING_MASTER_CONFIGURATION
was added in 8.0.2.
Error: 4352
SQLSTATE: HY000
(ER_RPL_ERROR_READING_MASTER_CONFIGURATION
)
Message: Error reading master configuration.
ER_RPL_ERROR_READING_MASTER_CONFIGURATION
was added in 8.0.2.
Error: 4353
SQLSTATE: HY000
(ER_RPL_SSL_INFO_IN_MASTER_INFO_IGNORED
)
Message: SSL information in the master info file are ignored because this MySQL slave was compiled without SSL support.
ER_RPL_SSL_INFO_IN_MASTER_INFO_IGNORED
was added in 8.0.2.
Error: 4354
SQLSTATE: HY000
(ER_PLUGIN_FAILED_DEINITIALIZATION
)
Message: Plugin '%s' of type %s failed deinitialization
ER_PLUGIN_FAILED_DEINITIALIZATION
was added in 8.0.2.
Error: 4355
SQLSTATE: HY000
(ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_DEINITIALIZATION
)
Message: Plugin '%s' has ref_count=%d after deinitialization.
ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_DEINITIALIZATION
was added in 8.0.2.
Error: 4356
SQLSTATE: HY000
(ER_PLUGIN_SHUTTING_DOWN_PLUGIN
)
Message: Shutting down plugin '%s'
ER_PLUGIN_SHUTTING_DOWN_PLUGIN
was
added in 8.0.2.
Error: 4357
SQLSTATE: HY000
(ER_PLUGIN_REGISTRATION_FAILED
)
Message: Plugin '%s' registration as a %s failed.
ER_PLUGIN_REGISTRATION_FAILED
was
added in 8.0.2.
Error: 4358
SQLSTATE: HY000
(ER_PLUGIN_CANT_OPEN_PLUGIN_TABLE
)
Message: Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
ER_PLUGIN_CANT_OPEN_PLUGIN_TABLE
was added in 8.0.2.
Error: 4359
SQLSTATE: HY000
(ER_PLUGIN_CANT_LOAD
)
Message: Couldn't load plugin named '%s' with soname '%s'.
ER_PLUGIN_CANT_LOAD
was added in
8.0.2.
Error: 4360
SQLSTATE: HY000
(ER_PLUGIN_LOAD_PARAMETER_TOO_LONG
)
Message: plugin-load parameter too long
ER_PLUGIN_LOAD_PARAMETER_TOO_LONG
was added in 8.0.2.
Error: 4361
SQLSTATE: HY000
(ER_PLUGIN_FORCING_SHUTDOWN
)
Message: Plugin '%s' will be forced to shutdown
ER_PLUGIN_FORCING_SHUTDOWN
was
added in 8.0.2.
Error: 4362
SQLSTATE: HY000
(ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_SHUTDOWN
)
Message: Plugin '%s' has ref_count=%d after shutdown.
ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_SHUTDOWN
was added in 8.0.2.
Error: 4363
SQLSTATE: HY000
(ER_PLUGIN_UNKNOWN_VARIABLE_TYPE
)
Message: Unknown variable type code 0x%x in plugin '%s'.
ER_PLUGIN_UNKNOWN_VARIABLE_TYPE
was added in 8.0.2.
Error: 4364
SQLSTATE: HY000
(ER_PLUGIN_VARIABLE_SET_READ_ONLY
)
Message: Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag
ER_PLUGIN_VARIABLE_SET_READ_ONLY
was added in 8.0.2.
Error: 4365
SQLSTATE: HY000
(ER_PLUGIN_VARIABLE_MISSING_NAME
)
Message: Missing variable name in plugin '%s'.
ER_PLUGIN_VARIABLE_MISSING_NAME
was added in 8.0.2.
Error: 4366
SQLSTATE: HY000
(ER_PLUGIN_VARIABLE_NOT_ALLOCATED_THREAD_LOCAL
)
Message: Thread local variable '%s' not allocated in plugin '%s'.
ER_PLUGIN_VARIABLE_NOT_ALLOCATED_THREAD_LOCAL
was added in 8.0.2.
Error: 4367
SQLSTATE: HY000
(ER_PLUGIN_OOM
)
Message: Out of memory for plugin '%s'.
ER_PLUGIN_OOM
was added in 8.0.2.
Error: 4368
SQLSTATE: HY000
(ER_PLUGIN_BAD_OPTIONS
)
Message: Bad options for plugin '%s'.
ER_PLUGIN_BAD_OPTIONS
was added in
8.0.2.
Error: 4369
SQLSTATE: HY000
(ER_PLUGIN_PARSING_OPTIONS_FAILED
)
Message: Parsing options for plugin '%s' failed.
ER_PLUGIN_PARSING_OPTIONS_FAILED
was added in 8.0.2.
Error: 4370
SQLSTATE: HY000
(ER_PLUGIN_DISABLED
)
Message: Plugin '%s' is disabled.
ER_PLUGIN_DISABLED
was added in
8.0.2.
Error: 4371
SQLSTATE: HY000
(ER_PLUGIN_HAS_CONFLICTING_SYSTEM_VARIABLES
)
Message: Plugin '%s' has conflicting system variables
ER_PLUGIN_HAS_CONFLICTING_SYSTEM_VARIABLES
was added in 8.0.2.
Error: 4372
SQLSTATE: HY000
(ER_PLUGIN_CANT_SET_PERSISTENT_OPTIONS
)
Message: Setting persistent options for plugin '%s' failed.
ER_PLUGIN_CANT_SET_PERSISTENT_OPTIONS
was added in 8.0.2.
Error: 4373
SQLSTATE: HY000
(ER_MY_NET_WRITE_FAILED_FALLING_BACK_ON_STDERR
)
Message: Failed on my_net_write, writing to stderr instead: %s
ER_MY_NET_WRITE_FAILED_FALLING_BACK_ON_STDERR
was added in 8.0.2.
Error: 4374
SQLSTATE: HY000
(ER_RETRYING_REPAIR_WITHOUT_QUICK
)
Message: Retrying repair of: '%s' without quick
ER_RETRYING_REPAIR_WITHOUT_QUICK
was added in 8.0.2.
Error: 4375
SQLSTATE: HY000
(ER_RETRYING_REPAIR_WITH_KEYCACHE
)
Message: Retrying repair of: '%s' with keycache
ER_RETRYING_REPAIR_WITH_KEYCACHE
was added in 8.0.2.
Error: 4376
SQLSTATE: HY000
(ER_FOUND_ROWS_WHILE_REPAIRING
)
Message: Found %s of %s rows when repairing '%s'
ER_FOUND_ROWS_WHILE_REPAIRING
was
added in 8.0.2.
Error: 4377
SQLSTATE: HY000
(ER_ERROR_DURING_OPTIMIZE_TABLE
)
Message: Warning: Optimize table got errno %d on %s.%s, retrying
ER_ERROR_DURING_OPTIMIZE_TABLE
was
added in 8.0.2.
Error: 4378
SQLSTATE: HY000
(ER_ERROR_ENABLING_KEYS
)
Message: Warning: Enabling keys got errno %d on %s.%s, retrying
ER_ERROR_ENABLING_KEYS
was added
in 8.0.2.
Error: 4379
SQLSTATE: HY000
(ER_CHECKING_TABLE
)
Message: Checking table: '%s'
ER_CHECKING_TABLE
was added in
8.0.2.
Error: 4380
SQLSTATE: HY000
(ER_RECOVERING_TABLE
)
Message: Recovering table: '%s'
ER_RECOVERING_TABLE
was added in
8.0.2.
Error: 4381
SQLSTATE: HY000
(ER_CANT_CREATE_TABLE_SHARE_FROM_FRM
)
Message: Error in creating TABLE_SHARE from %s.frm file.
ER_CANT_CREATE_TABLE_SHARE_FROM_FRM
was added in 8.0.2.
Error: 4382
SQLSTATE: HY000
(ER_CANT_LOCK_TABLE
)
Message: Unable to acquire lock on %s.%s
ER_CANT_LOCK_TABLE
was added in
8.0.2.
Error: 4383
SQLSTATE: HY000
(ER_CANT_ALLOC_TABLE_OBJECT
)
Message: Error in allocation memory for TABLE object.
ER_CANT_ALLOC_TABLE_OBJECT
was
added in 8.0.2.
Error: 4384
SQLSTATE: HY000
(ER_CANT_CREATE_HANDLER_OBJECT_FOR_TABLE
)
Message: Error in creating handler object for table %s.%s
ER_CANT_CREATE_HANDLER_OBJECT_FOR_TABLE
was added in 8.0.2.
Error: 4385
SQLSTATE: HY000
(ER_CANT_SET_HANDLER_REFERENCE_FOR_TABLE
)
Message: Error in setting handler reference for table %s.%s
ER_CANT_SET_HANDLER_REFERENCE_FOR_TABLE
was added in 8.0.2.
Error: 4386
SQLSTATE: HY000
(ER_CANT_LOCK_TABLESPACE
)
Message: Unable to acquire lock on tablespace name %s
ER_CANT_LOCK_TABLESPACE
was added
in 8.0.2.
Error: 4387
SQLSTATE: HY000
(ER_CANT_UPGRADE_GENERATED_COLUMNS_TO_DD
)
Message: Error in processing generated columns
ER_CANT_UPGRADE_GENERATED_COLUMNS_TO_DD
was added in 8.0.2.
Error: 4388
SQLSTATE: HY000
(ER_DD_ERROR_CREATING_ENTRY
)
Message: Error in Creating DD entry for %s.%s
ER_DD_ERROR_CREATING_ENTRY
was
added in 8.0.2.
Error: 4389
SQLSTATE: HY000
(ER_DD_CANT_FETCH_TABLE_DATA
)
Message: Error in fetching %s.%s table data from dictionary
ER_DD_CANT_FETCH_TABLE_DATA
was
added in 8.0.2.
Error: 4390
SQLSTATE: HY000
(ER_DD_CANT_FIX_SE_DATA
)
Message: Error in fixing SE data for %s.%s
ER_DD_CANT_FIX_SE_DATA
was added
in 8.0.2.
Error: 4391
SQLSTATE: HY000
(ER_DD_CANT_CREATE_SP
)
Message: Error in creating stored program '%s.%s'
ER_DD_CANT_CREATE_SP
was added in
8.0.2.
Error: 4392
SQLSTATE: HY000
(ER_CANT_OPEN_DB_OPT_USING_DEFAULT_CHARSET
)
Message: Unable to open db.opt file %s. Using default Character set.
ER_CANT_OPEN_DB_OPT_USING_DEFAULT_CHARSET
was added in 8.0.2.
Error: 4393
SQLSTATE: HY000
(ER_CANT_CREATE_CACHE_FOR_DB_OPT
)
Message: Unable to intialize IO cache to open db.opt file %s.
ER_CANT_CREATE_CACHE_FOR_DB_OPT
was added in 8.0.2.
Error: 4394
SQLSTATE: HY000
(ER_CANT_IDENTIFY_CHARSET_USING_DEFAULT
)
Message: Unable to identify the charset in %s. Using default character set.
ER_CANT_IDENTIFY_CHARSET_USING_DEFAULT
was added in 8.0.2.
Error: 4395
SQLSTATE: HY000
(ER_DB_OPT_NOT_FOUND_USING_DEFAULT_CHARSET
)
Message: db.opt file not found for %s database. Using default Character set.
ER_DB_OPT_NOT_FOUND_USING_DEFAULT_CHARSET
was added in 8.0.2.
Error: 4396
SQLSTATE: HY000
(ER_EVENT_CANT_GET_TIMEZONE_FROM_FIELD
)
Message: Event '%s'.'%s': invalid value in column mysql.event.time_zone.
ER_EVENT_CANT_GET_TIMEZONE_FROM_FIELD
was added in 8.0.2.
Error: 4397
SQLSTATE: HY000
(ER_EVENT_CANT_FIND_TIMEZONE
)
Message: Event '%s'.'%s': has invalid time zone value
ER_EVENT_CANT_FIND_TIMEZONE
was
added in 8.0.2.
Error: 4398
SQLSTATE: HY000
(ER_EVENT_CANT_GET_CHARSET
)
Message: Event '%s'.'%s': invalid value in column mysql.event.character_set_client.
ER_EVENT_CANT_GET_CHARSET
was
added in 8.0.2.
Error: 4399
SQLSTATE: HY000
(ER_EVENT_CANT_GET_COLLATION
)
Message: Event '%s'.'%s': invalid value in column mysql.event.collation_connection.
ER_EVENT_CANT_GET_COLLATION
was
added in 8.0.2.
Error: 4400
SQLSTATE: HY000
(ER_EVENT_CANT_OPEN_TABLE_MYSQL_EVENT
)
Message: Failed to open mysql.event Table.
ER_EVENT_CANT_OPEN_TABLE_MYSQL_EVENT
was added in 8.0.2.
Error: 4401
SQLSTATE: HY000
(ER_CANT_PARSE_STORED_ROUTINE_BODY
)
Message: Parsing '%s.%s' routine body failed. Creating routine without parsing routine body
ER_CANT_PARSE_STORED_ROUTINE_BODY
was added in 8.0.2.
Error: 4402
SQLSTATE: HY000
(ER_CANT_OPEN_TABLE_MYSQL_PROC
)
Message: Failed to open mysql.proc Table.
ER_CANT_OPEN_TABLE_MYSQL_PROC
was
added in 8.0.2.
Error: 4403
SQLSTATE: HY000
(ER_CANT_READ_TABLE_MYSQL_PROC
)
Message: Failed to read mysql.proc table.
ER_CANT_READ_TABLE_MYSQL_PROC
was
added in 8.0.2.
Error: 4404
SQLSTATE: HY000
(ER_FILE_EXISTS_DURING_UPGRADE
)
Message: Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.
ER_FILE_EXISTS_DURING_UPGRADE
was
added in 8.0.2.
Error: 4405
SQLSTATE: HY000
(ER_CANT_OPEN_DATADIR_AFTER_UPGRADE_FAILURE
)
Message: Unable to open the data directory %s during clean up after upgrade failed
ER_CANT_OPEN_DATADIR_AFTER_UPGRADE_FAILURE
was added in 8.0.2.
Error: 4406
SQLSTATE: HY000
(ER_CANT_SET_PATH_FOR
)
Message: Failed to set path %s
ER_CANT_SET_PATH_FOR
was added in
8.0.2.
Error: 4407
SQLSTATE: HY000
(ER_CANT_OPEN_DIR
)
Message: Failed to open dir %s
ER_CANT_OPEN_DIR
was added in
8.0.2.
Error: 4408
SQLSTATE: HY000
(ER_NDB_EMPTY_NODEID_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
)
Message: NDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.
ER_NDB_EMPTY_NODEID_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
was added in 8.0.2.
Error: 4409
SQLSTATE: HY000
(ER_NDB_CANT_PARSE_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
)
Message: NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.
ER_NDB_CANT_PARSE_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
was added in 8.0.2.
Error: 4410
SQLSTATE: HY000
(ER_NDB_INVALID_NODEID_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
)
Message: NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.
ER_NDB_INVALID_NODEID_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
was added in 8.0.2.
Error: 4411
SQLSTATE: HY000
(ER_NDB_DUPLICATE_NODEID_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
)
Message: NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.
ER_NDB_DUPLICATE_NODEID_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
was added in 8.0.2.
Error: 4412
SQLSTATE: HY000
(ER_NDB_POOL_SIZE_MUST_MATCH_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
)
Message: NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.
ER_NDB_POOL_SIZE_MUST_MATCH_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
was added in 8.0.2.
Error: 4413
SQLSTATE: HY000
(ER_NDB_NODEID_NOT_FIRST_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
)
Message: NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.
ER_NDB_NODEID_NOT_FIRST_IN_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
was added in 8.0.2.
Error: 4414
SQLSTATE: HY000
(ER_NDB_USING_NODEID
)
Message: NDB: using nodeid %u
ER_NDB_USING_NODEID
was added in
8.0.2.
Error: 4415
SQLSTATE: HY000
(ER_NDB_CANT_ALLOC_GLOBAL_NDB_CLUSTER_CONNECTION
)
Message: NDB: failed to allocate global ndb cluster connection
ER_NDB_CANT_ALLOC_GLOBAL_NDB_CLUSTER_CONNECTION
was added in 8.0.2.
Error: 4416
SQLSTATE: HY000
(ER_NDB_CANT_ALLOC_GLOBAL_NDB_OBJECT
)
Message: NDB: failed to allocate global ndb object
ER_NDB_CANT_ALLOC_GLOBAL_NDB_OBJECT
was added in 8.0.2.
Error: 4417
SQLSTATE: HY000
(ER_NDB_USING_NODEID_LIST
)
Message: NDB[%u]: using nodeid %u
ER_NDB_USING_NODEID_LIST
was added
in 8.0.2.
Error: 4418
SQLSTATE: HY000
(ER_NDB_CANT_ALLOC_NDB_CLUSTER_CONNECTION
)
Message: NDB[%u]: failed to allocate cluster connect object
ER_NDB_CANT_ALLOC_NDB_CLUSTER_CONNECTION
was added in 8.0.2.
Error: 4419
SQLSTATE: HY000
(ER_NDB_STARTING_CONNECT_THREAD
)
Message: NDB[%u]: starting connect thread
ER_NDB_STARTING_CONNECT_THREAD
was
added in 8.0.2.
Error: 4420
SQLSTATE: HY000
(ER_NDB_NODE_INFO
)
Message: NDB[%u]: NodeID: %d, %s
ER_NDB_NODE_INFO
was added in
8.0.2.
Error: 4421
SQLSTATE: HY000
(ER_NDB_CANT_START_CONNECT_THREAD
)
Message: NDB[%u]: failed to start connect thread
ER_NDB_CANT_START_CONNECT_THREAD
was added in 8.0.2.
Error: 4422
SQLSTATE: HY000
(ER_NDB_GENERIC_ERROR
)
Message: NDB: error (%u) %s
ER_NDB_GENERIC_ERROR
was added in
8.0.2.
Error: 4423
SQLSTATE: HY000
(ER_NDB_CPU_MASK_TOO_SHORT
)
Message: Ignored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs provided
ER_NDB_CPU_MASK_TOO_SHORT
was
added in 8.0.2.
Error: 4424
SQLSTATE: HY000
(ER_EVENT_ERROR_CREATING_QUERY_TO_WRITE_TO_BINLOG
)
Message: Event Error: An error occurred while creating query string, before writing it into binary log.
ER_EVENT_ERROR_CREATING_QUERY_TO_WRITE_TO_BINLOG
was added in 8.0.2.
Error: 4425
SQLSTATE: HY000
(ER_EVENT_SCHEDULER_ERROR_LOADING_FROM_DB
)
Message: Event Scheduler: Error while loading from disk.
ER_EVENT_SCHEDULER_ERROR_LOADING_FROM_DB
was added in 8.0.2.
Error: 4426
SQLSTATE: HY000
(ER_EVENT_SCHEDULER_ERROR_GETTING_EVENT_OBJECT
)
Message: Event Scheduler: Error getting event object.
ER_EVENT_SCHEDULER_ERROR_GETTING_EVENT_OBJECT
was added in 8.0.2.
Error: 4427
SQLSTATE: HY000
(ER_EVENT_SCHEDULER_GOT_BAD_DATA_FROM_TABLE
)
Message: Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corrupted
ER_EVENT_SCHEDULER_GOT_BAD_DATA_FROM_TABLE
was added in 8.0.2.
Error: 4428
SQLSTATE: HY000
(ER_EVENT_CANT_GET_LOCK_FOR_DROPPING_EVENT
)
Message: Unable to obtain lock for dropping event %s from schema %s
ER_EVENT_CANT_GET_LOCK_FOR_DROPPING_EVENT
was added in 8.0.2.
Error: 4429
SQLSTATE: HY000
(ER_EVENT_UNABLE_TO_DROP_EVENT
)
Message: Unable to drop event %s from schema %s
ER_EVENT_UNABLE_TO_DROP_EVENT
was
added in 8.0.2.
Error: 4430
SQLSTATE: HY000
(ER_BINLOG_ATTACHING_THREAD_MEMORY_FINALLY_AVAILABLE
)
Message: Server overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.
ER_BINLOG_ATTACHING_THREAD_MEMORY_FINALLY_AVAILABLE
was added in 8.0.2.
Error: 4431
SQLSTATE: HY000
(ER_BINLOG_CANT_RESIZE_CACHE
)
Message: Unable to resize binlog IOCACHE auxiliary file
ER_BINLOG_CANT_RESIZE_CACHE
was
added in 8.0.2.
Error: 4432
SQLSTATE: HY000
(ER_BINLOG_FILE_BEING_READ_NOT_PURGED
)
Message: file %s was not purged because it was being read by thread number %u
ER_BINLOG_FILE_BEING_READ_NOT_PURGED
was added in 8.0.2.
Error: 4433
SQLSTATE: HY000
(ER_BINLOG_IO_ERROR_READING_HEADER
)
Message: I/O error reading the header from the binary log, errno=%d, io cache code=%d
ER_BINLOG_IO_ERROR_READING_HEADER
was added in 8.0.2.
Error: 4434
SQLSTATE: HY000
(ER_BINLOG_CANT_OPEN_LOG
)
Message: Failed to open log (file '%s', errno %d)
ER_BINLOG_CANT_OPEN_LOG
was added
in 8.0.2.
Error: 4435
SQLSTATE: HY000
(ER_BINLOG_CANT_CREATE_CACHE_FOR_LOG
)
Message: Failed to create a cache on log (file '%s')
ER_BINLOG_CANT_CREATE_CACHE_FOR_LOG
was added in 8.0.2.
Error: 4436
SQLSTATE: HY000
(ER_BINLOG_FILE_EXTENSION_NUMBER_EXHAUSTED
)
Message: Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.
ER_BINLOG_FILE_EXTENSION_NUMBER_EXHAUSTED
was added in 8.0.2.
Error: 4437
SQLSTATE: HY000
(ER_BINLOG_FILE_NAME_TOO_LONG
)
Message: Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.
ER_BINLOG_FILE_NAME_TOO_LONG
was
added in 8.0.2.
Error: 4438
SQLSTATE: HY000
(ER_BINLOG_FILE_EXTENSION_NUMBER_RUNNING_LOW
)
Message: Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.
ER_BINLOG_FILE_EXTENSION_NUMBER_RUNNING_LOW
was added in 8.0.2.
Error: 4439
SQLSTATE: HY000
(ER_BINLOG_CANT_OPEN_FOR_LOGGING
)
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.
ER_BINLOG_CANT_OPEN_FOR_LOGGING
was added in 8.0.2.
Error: 4440
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE
)
Message: MYSQL_BIN_LOG::open_index_file failed to sync the index file.
ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE
was added in 8.0.2.
Error: 4441
SQLSTATE: HY000
(ER_BINLOG_ERROR_READING_GTIDS_FROM_RELAY_LOG
)
Message: Error reading GTIDs from relaylog: %d
ER_BINLOG_ERROR_READING_GTIDS_FROM_RELAY_LOG
was added in 8.0.2.
Error: 4442
SQLSTATE: HY000
(ER_BINLOG_EVENTS_READ_FROM_RELAY_LOG_INFO
)
Message: %lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.
ER_BINLOG_EVENTS_READ_FROM_RELAY_LOG_INFO
was added in 8.0.2.
Error: 4443
SQLSTATE: HY000
(ER_BINLOG_ERROR_READING_GTIDS_FROM_BINARY_LOG
)
Message: Error reading GTIDs from binary log: %d
ER_BINLOG_ERROR_READING_GTIDS_FROM_BINARY_LOG
was added in 8.0.2.
Error: 4444
SQLSTATE: HY000
(ER_BINLOG_EVENTS_READ_FROM_BINLOG_INFO
)
Message: Read %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.
ER_BINLOG_EVENTS_READ_FROM_BINLOG_INFO
was added in 8.0.2.
Error: 4445
SQLSTATE: HY000
(ER_BINLOG_CANT_GENERATE_NEW_FILE_NAME
)
Message: MYSQL_BIN_LOG::open failed to generate new file name.
ER_BINLOG_CANT_GENERATE_NEW_FILE_NAME
was added in 8.0.2.
Error: 4446
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE_IN_OPEN
)
Message: MYSQL_BIN_LOG::open failed to sync the index file.
ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE_IN_OPEN
was added in 8.0.2.
Error: 4447
SQLSTATE: HY000
(ER_BINLOG_CANT_USE_FOR_LOGGING
)
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.
ER_BINLOG_CANT_USE_FOR_LOGGING
was
added in 8.0.2.
Error: 4448
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_CLOSE_INDEX_FILE_WHILE_REBUILDING
)
Message: While rebuilding index file %s: Failed to close the index file.
ER_BINLOG_FAILED_TO_CLOSE_INDEX_FILE_WHILE_REBUILDING
was added in 8.0.2.
Error: 4449
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_DELETE_INDEX_FILE_WHILE_REBUILDING
)
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.
ER_BINLOG_FAILED_TO_DELETE_INDEX_FILE_WHILE_REBUILDING
was added in 8.0.2.
Error: 4450
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_RENAME_INDEX_FILE_WHILE_REBUILDING
)
Message: While rebuilding index file %s: Failed to rename the new index file to the existing index file.
ER_BINLOG_FAILED_TO_RENAME_INDEX_FILE_WHILE_REBUILDING
was added in 8.0.2.
Error: 4451
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_OPEN_INDEX_FILE_AFTER_REBUILDING
)
Message: After rebuilding the index file %s: Failed to open the index file.
ER_BINLOG_FAILED_TO_OPEN_INDEX_FILE_AFTER_REBUILDING
was added in 8.0.2.
Error: 4452
SQLSTATE: HY000
(ER_BINLOG_CANT_APPEND_LOG_TO_TMP_INDEX
)
Message: MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.
ER_BINLOG_CANT_APPEND_LOG_TO_TMP_INDEX
was added in 8.0.2.
Error: 4453
SQLSTATE: HY000
(ER_BINLOG_CANT_LOCATE_OLD_BINLOG_OR_RELAY_LOG_FILES
)
Message: Failed to locate old binlog or relay log files
ER_BINLOG_CANT_LOCATE_OLD_BINLOG_OR_RELAY_LOG_FILES
was added in 8.0.2.
Error: 4454
SQLSTATE: HY000
(ER_BINLOG_CANT_DELETE_FILE
)
Message: Failed to delete file '%s'
ER_BINLOG_CANT_DELETE_FILE
was
added in 8.0.2.
Error: 4455
SQLSTATE: HY000
(ER_BINLOG_CANT_SET_TMP_INDEX_NAME
)
Message: MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.
ER_BINLOG_CANT_SET_TMP_INDEX_NAME
was added in 8.0.2.
Error: 4456
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_OPEN_TEMPORARY_INDEX_FILE
)
Message: MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.
ER_BINLOG_FAILED_TO_OPEN_TEMPORARY_INDEX_FILE
was added in 8.0.2.
Error: 4457
SQLSTATE: HY000
(ER_BINLOG_ERROR_GETTING_NEXT_LOG_FROM_INDEX
)
Message: next log error: %d offset: %s log: %s included: %d
ER_BINLOG_ERROR_GETTING_NEXT_LOG_FROM_INDEX
was added in 8.0.2.
Error: 4458
SQLSTATE: HY000
(ER_BINLOG_CANT_OPEN_TMP_INDEX
)
Message: %s failed to open the crash safe index file.
ER_BINLOG_CANT_OPEN_TMP_INDEX
was
added in 8.0.2.
Error: 4459
SQLSTATE: HY000
(ER_BINLOG_CANT_COPY_INDEX_TO_TMP
)
Message: %s failed to copy index file to crash safe index file.
ER_BINLOG_CANT_COPY_INDEX_TO_TMP
was added in 8.0.2.
Error: 4460
SQLSTATE: HY000
(ER_BINLOG_CANT_CLOSE_TMP_INDEX
)
Message: %s failed to close the crash safe index file.
ER_BINLOG_CANT_CLOSE_TMP_INDEX
was
added in 8.0.2.
Error: 4461
SQLSTATE: HY000
(ER_BINLOG_CANT_MOVE_TMP_TO_INDEX
)
Message: %s failed to move crash safe index file to index file.
ER_BINLOG_CANT_MOVE_TMP_TO_INDEX
was added in 8.0.2.
Error: 4462
SQLSTATE: HY000
(ER_BINLOG_PURGE_LOGS_CALLED_WITH_FILE_NOT_IN_INDEX
)
Message: MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.
ER_BINLOG_PURGE_LOGS_CALLED_WITH_FILE_NOT_IN_INDEX
was added in 8.0.2.
Error: 4463
SQLSTATE: HY000
(ER_BINLOG_PURGE_LOGS_CANT_SYNC_INDEX_FILE
)
Message: MYSQL_BIN_LOG::purge_logs failed to sync the index file.
ER_BINLOG_PURGE_LOGS_CANT_SYNC_INDEX_FILE
was added in 8.0.2.
Error: 4464
SQLSTATE: HY000
(ER_BINLOG_PURGE_LOGS_CANT_COPY_TO_REGISTER_FILE
)
Message: MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.
ER_BINLOG_PURGE_LOGS_CANT_COPY_TO_REGISTER_FILE
was added in 8.0.2.
Error: 4465
SQLSTATE: HY000
(ER_BINLOG_PURGE_LOGS_CANT_FLUSH_REGISTER_FILE
)
Message: MYSQL_BIN_LOG::purge_logs failed to flush register file.
ER_BINLOG_PURGE_LOGS_CANT_FLUSH_REGISTER_FILE
was added in 8.0.2.
Error: 4466
SQLSTATE: HY000
(ER_BINLOG_PURGE_LOGS_CANT_UPDATE_INDEX_FILE
)
Message: MYSQL_BIN_LOG::purge_logs failed to update the index file
ER_BINLOG_PURGE_LOGS_CANT_UPDATE_INDEX_FILE
was added in 8.0.2.
Error: 4467
SQLSTATE: HY000
(ER_BINLOG_PURGE_LOGS_FAILED_TO_PURGE_LOG
)
Message: MYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.
ER_BINLOG_PURGE_LOGS_FAILED_TO_PURGE_LOG
was added in 8.0.2.
Error: 4468
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_SET_PURGE_INDEX_FILE_NAME
)
Message: MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.
ER_BINLOG_FAILED_TO_SET_PURGE_INDEX_FILE_NAME
was added in 8.0.2.
Error: 4469
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_OPEN_REGISTER_FILE
)
Message: MYSQL_BIN_LOG::open_purge_index_file failed to open register file.
ER_BINLOG_FAILED_TO_OPEN_REGISTER_FILE
was added in 8.0.2.
Error: 4470
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_REINIT_REGISTER_FILE
)
Message: MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for read
ER_BINLOG_FAILED_TO_REINIT_REGISTER_FILE
was added in 8.0.2.
Error: 4471
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_READ_REGISTER_FILE
)
Message: MYSQL_BIN_LOG::purge_index_entry error %d reading from register file.
ER_BINLOG_FAILED_TO_READ_REGISTER_FILE
was added in 8.0.2.
Error: 4472
SQLSTATE: HY000
(ER_CANT_STAT_FILE
)
Message: Failed to execute mysql_file_stat on file '%s'
ER_CANT_STAT_FILE
was added in
8.0.2.
Error: 4473
SQLSTATE: HY000
(ER_BINLOG_CANT_DELETE_LOG_FILE_DOES_INDEX_MATCH_FILES
)
Message: Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog files
ER_BINLOG_CANT_DELETE_LOG_FILE_DOES_INDEX_MATCH_FILES
was added in 8.0.2.
Error: 4474
SQLSTATE: HY000
(ER_BINLOG_CANT_DELETE_FILE_AND_READ_BINLOG_INDEX
)
Message: Failed to delete file '%s' and read the binlog index file
ER_BINLOG_CANT_DELETE_FILE_AND_READ_BINLOG_INDEX
was added in 8.0.2.
Error: 4475
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_DELETE_LOG_FILE
)
Message: Failed to delete log file '%s'
ER_BINLOG_FAILED_TO_DELETE_LOG_FILE
was added in 8.0.2.
Error: 4476
SQLSTATE: HY000
(ER_BINLOG_LOGGING_INCIDENT_TO_STOP_SLAVES
)
Message: %s An incident event has been written to the binary log which will stop the slaves.
ER_BINLOG_LOGGING_INCIDENT_TO_STOP_SLAVES
was added in 8.0.2.
Error: 4477
SQLSTATE: HY000
(ER_BINLOG_CANT_FIND_LOG_IN_INDEX
)
Message: find_log_pos() failed (error: %d)
ER_BINLOG_CANT_FIND_LOG_IN_INDEX
was added in 8.0.2.
Error: 4478
SQLSTATE: HY000
(ER_BINLOG_RECOVERING_AFTER_CRASH_USING
)
Message: Recovering after a crash using %s
ER_BINLOG_RECOVERING_AFTER_CRASH_USING
was added in 8.0.2.
Error: 4479
SQLSTATE: HY000
(ER_BINLOG_CANT_OPEN_CRASHED_BINLOG
)
Message: Failed to open the crashed binlog file when master server is recovering it.
ER_BINLOG_CANT_OPEN_CRASHED_BINLOG
was added in 8.0.2.
Error: 4480
SQLSTATE: HY000
(ER_BINLOG_CANT_TRIM_CRASHED_BINLOG
)
Message: Failed to trim the crashed binlog file when master server is recovering it.
ER_BINLOG_CANT_TRIM_CRASHED_BINLOG
was added in 8.0.2.
Error: 4481
SQLSTATE: HY000
(ER_BINLOG_CRASHED_BINLOG_TRIMMED
)
Message: Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.
ER_BINLOG_CRASHED_BINLOG_TRIMMED
was added in 8.0.2.
Error: 4482
SQLSTATE: HY000
(ER_BINLOG_CANT_CLEAR_IN_USE_FLAG_FOR_CRASHED_BINLOG
)
Message: Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when master server is recovering it.
ER_BINLOG_CANT_CLEAR_IN_USE_FLAG_FOR_CRASHED_BINLOG
was added in 8.0.2.
Error: 4483
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_RUN_AFTER_SYNC_HOOK
)
Message: Failed to run 'after_sync' hooks
ER_BINLOG_FAILED_TO_RUN_AFTER_SYNC_HOOK
was added in 8.0.2.
Error: 4484
SQLSTATE: HY000
(ER_TURNING_LOGGING_OFF_FOR_THE_DURATION
)
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.
ER_TURNING_LOGGING_OFF_FOR_THE_DURATION
was added in 8.0.2.
Error: 4485
SQLSTATE: HY000
(ER_BINLOG_FAILED_TO_RUN_AFTER_FLUSH_HOOK
)
Message: Failed to run 'after_flush' hooks
ER_BINLOG_FAILED_TO_RUN_AFTER_FLUSH_HOOK
was added in 8.0.2.
Error: 4486
SQLSTATE: HY000
(ER_BINLOG_CRASH_RECOVERY_FAILED
)
Message: Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}
ER_BINLOG_CRASH_RECOVERY_FAILED
was added in 8.0.2.
Error: 4487
SQLSTATE: HY000
(ER_BINLOG_WARNING_SUPPRESSED
)
Message: The following warning was suppressed %d times during the last %d seconds in the error log
ER_BINLOG_WARNING_SUPPRESSED
was
added in 8.0.2.
Error: 4488
SQLSTATE: HY000
(ER_NDB_LOG_ENTRY
)
Message: NDB: %s
ER_NDB_LOG_ENTRY
was added in
8.0.2.
Error: 4489
SQLSTATE: HY000
(ER_NDB_LOG_ENTRY_WITH_PREFIX
)
Message: NDB %s: %s
ER_NDB_LOG_ENTRY_WITH_PREFIX
was
added in 8.0.2.
Error: 4490
SQLSTATE: HY000
(ER_NDB_BINLOG_CANT_CREATE_PURGE_THD
)
Message: NDB: Unable to purge %s.%s File=%s (failed to setup thd)
ER_NDB_BINLOG_CANT_CREATE_PURGE_THD
was added in 8.0.2.
Error: 4491
SQLSTATE: HY000
(ER_INNODB_UNKNOWN_COLLATION
)
Message: Unknown collation #%lu.
ER_INNODB_UNKNOWN_COLLATION
was
added in 8.0.2.
Error: 4492
SQLSTATE: HY000
(ER_INNODB_INVALID_LOG_GROUP_HOME_DIR
)
Message: syntax error in innodb_log_group_home_dir
ER_INNODB_INVALID_LOG_GROUP_HOME_DIR
was added in 8.0.2.
Error: 4493
SQLSTATE: HY000
(ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY
)
Message: syntax error in innodb_undo_directory
ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY
was added in 8.0.2.
Error: 4494
SQLSTATE: HY000
(ER_INNODB_ILLEGAL_COLON_IN_POOL
)
Message: InnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.
ER_INNODB_ILLEGAL_COLON_IN_POOL
was added in 8.0.2.
Error: 4495
SQLSTATE: HY000
(ER_INNODB_INVALID_PAGE_SIZE
)
Message: InnoDB: Invalid page size=%lu.
ER_INNODB_INVALID_PAGE_SIZE
was
added in 8.0.2.
Error: 4496
SQLSTATE: HY000
(ER_INNODB_DIRTY_WATER_MARK_NOT_LOW
)
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
ER_INNODB_DIRTY_WATER_MARK_NOT_LOW
was added in 8.0.2.
Error: 4497
SQLSTATE: HY000
(ER_INNODB_IO_CAPACITY_EXCEEDS_MAX
)
Message: InnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu
ER_INNODB_IO_CAPACITY_EXCEEDS_MAX
was added in 8.0.2.
Error: 4498
SQLSTATE: HY000
(ER_INNODB_FILES_SAME
)
Message: %s and %s file names seem to be the same.
ER_INNODB_FILES_SAME
was added in
8.0.2.
Error: 4499
SQLSTATE: HY000
(ER_INNODB_UNREGISTERED_TRX_ACTIVE
)
Message: Transaction not registered for MySQL 2PC, but transaction is active
ER_INNODB_UNREGISTERED_TRX_ACTIVE
was added in 8.0.2.
Error: 4500
SQLSTATE: HY000
(ER_INNODB_CLOSING_CONNECTION_ROLLS_BACK
)
Message: MySQL is closing a connection that has an active InnoDB transaction. %s row modifications will roll back.
ER_INNODB_CLOSING_CONNECTION_ROLLS_BACK
was added in 8.0.2.
Error: 4501
SQLSTATE: HY000
(ER_INNODB_TRX_XLATION_TABLE_OOM
)
Message: InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%lu
ER_INNODB_TRX_XLATION_TABLE_OOM
was added in 8.0.2.
Error: 4502
SQLSTATE: HY000
(ER_INNODB_CANT_FIND_INDEX_IN_INNODB_DD
)
Message: Cannot find index %s in InnoDB index dictionary.
ER_INNODB_CANT_FIND_INDEX_IN_INNODB_DD
was added in 8.0.2.
Error: 4503
SQLSTATE: HY000
(ER_INNODB_INDEX_COLUMN_INFO_UNLIKE_MYSQLS
)
Message: Found index %s whose column info does not match that of MySQL.
ER_INNODB_INDEX_COLUMN_INFO_UNLIKE_MYSQLS
was added in 8.0.2.
Error: 4504
SQLSTATE: HY000
(ER_INNODB_CANT_OPEN_TABLE
)
Message: Failed to open table %s.
ER_INNODB_CANT_OPEN_TABLE
was
added in 8.0.2.
Error: 4505
SQLSTATE: HY000
(ER_INNODB_CANT_BUILD_INDEX_XLATION_TABLE_FOR
)
Message: Build InnoDB index translation table for Table %s failed
ER_INNODB_CANT_BUILD_INDEX_XLATION_TABLE_FOR
was added in 8.0.2.
Error: 4506
SQLSTATE: HY000
(ER_INNODB_PK_NOT_IN_MYSQL
)
Message: Table %s has a primary key in InnoDB data dictionary, but not in MySQL!
ER_INNODB_PK_NOT_IN_MYSQL
was
added in 8.0.2.
Error: 4507
SQLSTATE: HY000
(ER_INNODB_PK_ONLY_IN_MYSQL
)
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.
ER_INNODB_PK_ONLY_IN_MYSQL
was
added in 8.0.2.
Error: 4508
SQLSTATE: HY000
(ER_INNODB_CLUSTERED_INDEX_PRIVATE
)
Message: Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.
ER_INNODB_CLUSTERED_INDEX_PRIVATE
was added in 8.0.2.
Error: 4509
SQLSTATE: HY000
(ER_INNODB_PARTITION_TABLE_LOWERCASED
)
Message: Partition table %s opened after converting to lower case. The table may have been moved from a case in-sensitive file system. Please recreate table in the current file system
ER_INNODB_PARTITION_TABLE_LOWERCASED
was added in 8.0.2.
Error: 4510
SQLSTATE: HY000
(ER_ERRMSG_REPLACEMENT_DODGY
)
Message: Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.
ER_ERRMSG_REPLACEMENT_DODGY
was
added in 8.0.2.
Error: 4511
SQLSTATE: HY000
(ER_ERRMSG_REPLACEMENTS_FAILED
)
Message: Table for error message replacements could not be found or read, or one or more replacements could not be applied.
ER_ERRMSG_REPLACEMENTS_FAILED
was
added in 8.0.2.
Error: 4512
SQLSTATE: HY000
(ER_NPIPE_CANT_CREATE
)
Message: %s: %s
ER_NPIPE_CANT_CREATE
was added in
8.0.2.
Error: 4513
SQLSTATE: HY000
(ER_PARTITION_MOVE_CREATED_DUPLICATE_ROW_PLEASE_FIX
)
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
ER_PARTITION_MOVE_CREATED_DUPLICATE_ROW_PLEASE_FIX
was added in 8.0.2.
Error: 4514
SQLSTATE: HY000
(ER_AUDIT_CANT_ABORT_COMMAND
)
Message: Command '%s' cannot be aborted. The trigger error was (%d) [%s]: %s
ER_AUDIT_CANT_ABORT_COMMAND
was
added in 8.0.2.
Error: 4515
SQLSTATE: HY000
(ER_AUDIT_CANT_ABORT_EVENT
)
Message: Event '%s' cannot be aborted. The trigger error was (%d) [%s]: %s
ER_AUDIT_CANT_ABORT_EVENT
was
added in 8.0.2.
Error: 4516
SQLSTATE: HY000
(ER_AUDIT_WARNING
)
Message: %s. The trigger error was (%d) [%s]: %s
ER_AUDIT_WARNING
was added in
8.0.2.
Error: 4517
SQLSTATE: HY000
(ER_NDB_NUMBER_OF_CHANNELS
)
Message: Slave SQL: Configuration with number of replication masters = %u' is not supported when applying to Ndb
ER_NDB_NUMBER_OF_CHANNELS
was
added in 8.0.2.
Error: 4518
SQLSTATE: HY000
(ER_NDB_SLAVE_PARALLEL_WORKERS
)
Message: Slave SQL: Configuration 'slave_parallel_workers = %lu' is not supported when applying to Ndb
ER_NDB_SLAVE_PARALLEL_WORKERS
was
added in 8.0.2.
Error: 4519
SQLSTATE: HY000
(ER_NDB_DISTRIBUTING_ERR
)
Message: NDB %s: distributing %s err: %u
ER_NDB_DISTRIBUTING_ERR
was added
in 8.0.2.
Error: 4520
SQLSTATE: HY000
(ER_PART_EXPR_TOO_LONG
)
Message: Partitioning expression is too long.
ER_PART_EXPR_TOO_LONG
was added in
8.0.2.
Error: 4521
SQLSTATE: HY000
(ER_UDF_DROP_DYNAMICALLY_REGISTERED
)
Message: DROP FUNCTION can't drop a dynamically registered user defined function
ER_UDF_DROP_DYNAMICALLY_REGISTERED
was added in 8.0.2.
Error: 4522
SQLSTATE: HY000
(ER_UNABLE_TO_STORE_COLUMN_STATISTICS
)
Message: Unable to store column statistics for column '%s' in table '%s'.'%s'
ER_UNABLE_TO_STORE_COLUMN_STATISTICS
was added in 8.0.2.
Error: 4523
SQLSTATE: HY000
(ER_UNABLE_TO_UPDATE_COLUMN_STATISTICS
)
Message: Unable to update column statistics for column '%s' in table '%s'.'%s'
ER_UNABLE_TO_UPDATE_COLUMN_STATISTICS
was added in 8.0.2.
Error: 4524
SQLSTATE: HY000
(ER_UNABLE_TO_DROP_COLUMN_STATISTICS
)
Message: Unable to remove column statistics for column '%s' in table '%s'.'%s'
ER_UNABLE_TO_DROP_COLUMN_STATISTICS
was added in 8.0.2.
Error: 4525
SQLSTATE: HY000
(ER_UNABLE_TO_BUILD_HISTOGRAM
)
Message: Unable to build histogram statistics for column '%s' in table '%s'.'%s'
ER_UNABLE_TO_BUILD_HISTOGRAM
was
added in 8.0.2.
Error: 4526
SQLSTATE: HY000
(ER_STOP_SLAVE_IO_THREAD_DISK_SPACE
)
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.
ER_STOP_SLAVE_IO_THREAD_DISK_SPACE
was added in 8.0.2.
Error: 4527
SQLSTATE: HY000
(ER_MANDATORY_ROLE
)
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.
ER_MANDATORY_ROLE
was added in
8.0.2.
Error: 4528
SQLSTATE: HY000
(ER_MISSING_TABLESPACE_FILE
)
Message: Tablespace '%s' does not have a file named '%s'
ER_MISSING_TABLESPACE_FILE
was
added in 8.0.3.
Error: 4529
SQLSTATE: 42000
(ER_PERSIST_ONLY_ACCESS_DENIED_ERROR
)
Message: Access denied; you need %s privileges for this operation
ER_PERSIST_ONLY_ACCESS_DENIED_ERROR
was added in 8.0.3.
Error: 4530
SQLSTATE: HY000
(ER_CMD_NEED_SUPER
)
Message: You need the SUPER privilege for command '%s'
ER_CMD_NEED_SUPER
was added in
8.0.3.
Error: 4531
SQLSTATE: HY000
(ER_PATH_IN_DATADIR
)
Message: Path is within the current data directory '%s'
ER_PATH_IN_DATADIR
was added in
8.0.3.
Error: 4532
SQLSTATE: HY000
(ER_DDL_IN_PROGRESS
)
Message: Concurrent DDL is performed during the operation. Please try again.
ER_DDL_IN_PROGRESS
was added in
8.0.3.
Error: 4533
SQLSTATE: HY000
(ER_TOO_MANY_CONCURRENT_CLONES
)
Message: Too many concurrent clone operations. Maximum allowed - %d.
ER_TOO_MANY_CONCURRENT_CLONES
was
added in 8.0.3.
Error: 4534
SQLSTATE: HY000
(ER_SDI_OPERATION_FAILED
)
Message: Failed to %s SDI '%s.%s' in tablespace '%s'.
ER_SDI_OPERATION_FAILED
was added
in 8.0.3.
Error: 4535
SQLSTATE: HY000
(ER_APPLIER_LOG_EVENT_VALIDATION_ERROR
)
Message: The table in transaction %s does not comply with the requirements by an external plugin.
ER_APPLIER_LOG_EVENT_VALIDATION_ERROR
was added in 8.0.3.
Error: 4536
SQLSTATE: HY000
(ER_CTE_MAX_RECURSION_DEPTH
)
Message: Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.
ER_CTE_MAX_RECURSION_DEPTH
was
added in 8.0.3.
Error: 4537
SQLSTATE: HY000
(ER_NOT_HINT_UPDATABLE_VARIABLE
)
Message: Variable %s cannot be set using SET_VAR hint.
ER_NOT_HINT_UPDATABLE_VARIABLE
was
added in 8.0.3.
Error: 4538
SQLSTATE: HY000
(ER_CREDENTIALS_CONTRADICT_TO_HISTORY
)
Message: Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policy
ER_CREDENTIALS_CONTRADICT_TO_HISTORY
was added in 8.0.3.
Error: 4539
SQLSTATE: HY000
(ER_WARNING_PASSWORD_HISTORY_CLAUSES_VOID
)
Message: Non-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password history
ER_WARNING_PASSWORD_HISTORY_CLAUSES_VOID
was added in 8.0.3.
Error: 4540
SQLSTATE: HY000
(ER_CLIENT_DOES_NOT_SUPPORT
)
Message: The client doesn't support %s
ER_CLIENT_DOES_NOT_SUPPORT
was
added in 8.0.3.
Error: 4541
SQLSTATE: HY000
(ER_I_S_SKIPPED_TABLESPACE
)
Message: Tablespace '%s' was skipped since its definition is being modified by concurrent DDL statement
ER_I_S_SKIPPED_TABLESPACE
was
added in 8.0.3.
Error: 4542
SQLSTATE: HY000
(ER_TABLESPACE_ENGINE_MISMATCH
)
Message: Engine '%s' does not match stored engine '%s' for tablespace '%s'
ER_TABLESPACE_ENGINE_MISMATCH
was
added in 8.0.3.
Error: 4543
SQLSTATE: HY000
(ER_RPL_CANT_HAVE_SAME_BASENAME
)
Message: Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s') and %s (default '%s') options to ensure they do not conflict
ER_RPL_CANT_HAVE_SAME_BASENAME
was
added in 8.0.4.
Error: 4544
SQLSTATE: HY000
(ER_WARN_NO_SERVERID_SPECIFIED
)
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.
ER_WARN_NO_SERVERID_SPECIFIED
was
added in 8.0.4.
Error: 4545
SQLSTATE: HY000
(ER_WRONG_SRID_FOR_COLUMN
)
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.
ER_WRONG_SRID_FOR_COLUMN
was added
in 8.0.4.
Error: 4546
SQLSTATE: HY000
(ER_CANNOT_ALTER_SRID_DUE_TO_INDEX
)
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.
ER_CANNOT_ALTER_SRID_DUE_TO_INDEX
was added in 8.0.4.
Error: 4547
SQLSTATE: HY000
(ER_WARN_BINLOG_PARTIAL_UPDATES_DISABLED
)
Message: When %s, the option binlog_row_value_options=%s will be ignored and updates will be written in full format to binary log.
ER_WARN_BINLOG_PARTIAL_UPDATES_DISABLED
was added in 8.0.4.
Error: 4548
SQLSTATE: HY000
(ER_WARN_BINLOG_V1_ROW_EVENTS_DISABLED
)
Message: When %s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.
ER_WARN_BINLOG_V1_ROW_EVENTS_DISABLED
was added in 8.0.4.
Error: 4549
SQLSTATE: HY000
(ER_WARN_BINLOG_PARTIAL_UPDATES_SUGGESTS_PARTIAL_IMAGES
)
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%%.
ER_WARN_BINLOG_PARTIAL_UPDATES_SUGGESTS_PARTIAL_IMAGES
was added in 8.0.4.
Error: 4550
SQLSTATE: HY000
(ER_COULD_NOT_APPLY_JSON_DIFF
)
Message: Could not apply JSON diff in table %.*s, column %s.
ER_COULD_NOT_APPLY_JSON_DIFF
was
added in 8.0.4.
Error: 4551
SQLSTATE: HY000
(ER_CORRUPTED_JSON_DIFF
)
Message: Corrupted JSON diff for table %.*s, column %s.
ER_CORRUPTED_JSON_DIFF
was added
in 8.0.4.
Error: 4552
SQLSTATE: HY000
(ER_RESOURCE_GROUP_EXISTS
)
Message: Resource Group '%s' exists
ER_RESOURCE_GROUP_EXISTS
was added
in 8.0.4.
Error: 4553
SQLSTATE: HY000
(ER_RESOURCE_GROUP_NOT_EXISTS
)
Message: Resource Group '%s' does not exist.
ER_RESOURCE_GROUP_NOT_EXISTS
was
added in 8.0.4.
Error: 4554
SQLSTATE: HY000
(ER_INVALID_VCPU_ID
)
Message: Invalid cpu id %u
ER_INVALID_VCPU_ID
was added in
8.0.4.
Error: 4555
SQLSTATE: HY000
(ER_INVALID_VCPU_RANGE
)
Message: Invalid VCPU range %u-%u
ER_INVALID_VCPU_RANGE
was added in
8.0.4.
Error: 4556
SQLSTATE: HY000
(ER_INVALID_THREAD_PRIORITY
)
Message: Invalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].
ER_INVALID_THREAD_PRIORITY
was
added in 8.0.4.
Error: 4557
SQLSTATE: HY000
(ER_DISALLOWED_OPERATION
)
Message: %s operation is disallowed on %s
ER_DISALLOWED_OPERATION
was added
in 8.0.4.
Error: 4558
SQLSTATE: HY000
(ER_RESOURCE_GROUP_BUSY
)
Message: Resource group %s is busy.
ER_RESOURCE_GROUP_BUSY
was added
in 8.0.4.
Error: 4559
SQLSTATE: HY000
(ER_RESOURCE_GROUP_DISABLED
)
Message: Resource group %s is disabled.
ER_RESOURCE_GROUP_DISABLED
was
added in 8.0.4.
Error: 4560
SQLSTATE: HY000
(ER_FEATURE_UNSUPPORTED
)
Message: Feature %s is unsupported (%s).
ER_FEATURE_UNSUPPORTED
was added
in 8.0.4.
Error: 4561
SQLSTATE: HY000
(ER_ATTRIBUTE_IGNORED
)
Message: Attribute %s is ignored (%s).
ER_ATTRIBUTE_IGNORED
was added in
8.0.4.
Error: 4562
SQLSTATE: HY000
(ER_INVALID_THREAD_ID
)
Message: Invalid thread id (%llu).
ER_INVALID_THREAD_ID
was added in
8.0.4.
Error: 4563
SQLSTATE: HY000
(ER_RESOURCE_GROUP_BIND_FAILED
)
Message: Unable to bind resource group %s with thread id (%llu).(%s).
ER_RESOURCE_GROUP_BIND_FAILED
was
added in 8.0.4.
Error: 4564
SQLSTATE: HY000
(ER_INVALID_USE_OF_FORCE_OPTION
)
Message: Option FORCE invalid as DISABLE option is not specified.
ER_INVALID_USE_OF_FORCE_OPTION
was
added in 8.0.4.
Error: 4565
SQLSTATE: HY000
(ER_GROUP_REPLICATION_COMMAND_FAILURE
)
Message: The %s command encountered a failure. %s
ER_GROUP_REPLICATION_COMMAND_FAILURE
was added in 8.0.4.
Client error information comes from the following source files:
The Error values and the symbols in parentheses correspond to
definitions in the include/errmsg.h
MySQL
source file.
The Message values correspond to the error messages that are
listed in the libmysql/errmsg.c
file.
%d
and %s
represent
numbers and strings, respectively, that are substituted into
the messages when they are displayed.
Because updates are frequent, it is possible that those files will contain additional error information not listed here.
Error: 2000
(CR_UNKNOWN_ERROR
)
Message: Unknown MySQL error
Error: 2001
(CR_SOCKET_CREATE_ERROR
)
Message: Can't create UNIX socket (%d)
Error: 2002
(CR_CONNECTION_ERROR
)
Message: Can't connect to local MySQL server through socket '%s' (%d)
Error: 2003
(CR_CONN_HOST_ERROR
)
Message: Can't connect to MySQL server on '%s' (%d)
Error: 2004
(CR_IPSOCK_ERROR
)
Message: Can't create TCP/IP socket (%d)
Error: 2005
(CR_UNKNOWN_HOST
)
Message: Unknown MySQL server host '%s' (%d)
Error: 2006
(CR_SERVER_GONE_ERROR
)
Message: MySQL server has gone away
Error: 2007
(CR_VERSION_ERROR
)
Message: Protocol mismatch; server version = %d, client version = %d
Error: 2008
(CR_OUT_OF_MEMORY
)
Message: MySQL client ran out of memory
Error: 2009
(CR_WRONG_HOST_INFO
)
Message: Wrong host info
Error: 2010
(CR_LOCALHOST_CONNECTION
)
Message: Localhost via UNIX socket
Error: 2011
(CR_TCP_CONNECTION
)
Message: %s via TCP/IP
Error: 2012
(CR_SERVER_HANDSHAKE_ERR
)
Message: Error in server handshake
Error: 2013
(CR_SERVER_LOST
)
Message: Lost connection to MySQL server during query
Error: 2014
(CR_COMMANDS_OUT_OF_SYNC
)
Message: Commands out of sync; you can't run this command now
Error: 2015
(CR_NAMEDPIPE_CONNECTION
)
Message: Named pipe: %s
Error: 2016
(CR_NAMEDPIPEWAIT_ERROR
)
Message: Can't wait for named pipe to host: %s pipe: %s (%lu)
Error: 2017
(CR_NAMEDPIPEOPEN_ERROR
)
Message: Can't open named pipe to host: %s pipe: %s (%lu)
Error: 2018
(CR_NAMEDPIPESETSTATE_ERROR
)
Message: Can't set state of named pipe to host: %s pipe: %s (%lu)
Error: 2019
(CR_CANT_READ_CHARSET
)
Message: Can't initialize character set %s (path: %s)
Error: 2020
(CR_NET_PACKET_TOO_LARGE
)
Message: Got packet bigger than 'max_allowed_packet' bytes
Error: 2021
(CR_EMBEDDED_CONNECTION
)
Message: Embedded server
Error: 2022
(CR_PROBE_SLAVE_STATUS
)
Message: Error on SHOW SLAVE STATUS:
Error: 2023
(CR_PROBE_SLAVE_HOSTS
)
Message: Error on SHOW SLAVE HOSTS:
Error: 2024
(CR_PROBE_SLAVE_CONNECT
)
Message: Error connecting to slave:
Error: 2025
(CR_PROBE_MASTER_CONNECT
)
Message: Error connecting to master:
Error: 2026
(CR_SSL_CONNECTION_ERROR
)
Message: SSL connection error: %s
Error: 2027
(CR_MALFORMED_PACKET
)
Message: Malformed packet
Error: 2028
(CR_WRONG_LICENSE
)
Message: This client library is licensed only for use with MySQL servers having '%s' license
Error: 2029
(CR_NULL_POINTER
)
Message: Invalid use of null pointer
Error: 2030
(CR_NO_PREPARE_STMT
)
Message: Statement not prepared
Error: 2031
(CR_PARAMS_NOT_BOUND
)
Message: No data supplied for parameters in prepared statement
Error: 2032
(CR_DATA_TRUNCATED
)
Message: Data truncated
Error: 2033
(CR_NO_PARAMETERS_EXISTS
)
Message: No parameters exist in the statement
Error: 2034
(CR_INVALID_PARAMETER_NO
)
Message: Invalid parameter number
The column number for
mysql_stmt_fetch_column()
was
invalid.
The parameter number for
mysql_stmt_send_long_data()
was
invalid.
A key name was empty or the amount of connection attribute data
for mysql_options4()
exceeds the
64KB limit.
Error: 2035
(CR_INVALID_BUFFER_USE
)
Message: Can't send long data for non-string/non-binary data types (parameter: %d)
Error: 2036
(CR_UNSUPPORTED_PARAM_TYPE
)
Message: Using unsupported buffer type: %d (parameter: %d)
Error: 2037
(CR_SHARED_MEMORY_CONNECTION
)
Message: Shared memory: %s
Error: 2038
(CR_SHARED_MEMORY_CONNECT_REQUEST_ERROR
)
Message: Can't open shared memory; client could not create request event (%lu)
Error: 2039
(CR_SHARED_MEMORY_CONNECT_ANSWER_ERROR
)
Message: Can't open shared memory; no answer event received from server (%lu)
Error: 2040
(CR_SHARED_MEMORY_CONNECT_FILE_MAP_ERROR
)
Message: Can't open shared memory; server could not allocate file mapping (%lu)
Error: 2041
(CR_SHARED_MEMORY_CONNECT_MAP_ERROR
)
Message: Can't open shared memory; server could not get pointer to file mapping (%lu)
Error: 2042
(CR_SHARED_MEMORY_FILE_MAP_ERROR
)
Message: Can't open shared memory; client could not allocate file mapping (%lu)
Error: 2043
(CR_SHARED_MEMORY_MAP_ERROR
)
Message: Can't open shared memory; client could not get pointer to file mapping (%lu)
Error: 2044
(CR_SHARED_MEMORY_EVENT_ERROR
)
Message: Can't open shared memory; client could not create %s event (%lu)
Error: 2045
(CR_SHARED_MEMORY_CONNECT_ABANDONED_ERROR
)
Message: Can't open shared memory; no answer from server (%lu)
Error: 2046
(CR_SHARED_MEMORY_CONNECT_SET_ERROR
)
Message: Can't open shared memory; cannot send request event to server (%lu)
Error: 2047
(CR_CONN_UNKNOW_PROTOCOL
)
Message: Wrong or unknown protocol
Error: 2048
(CR_INVALID_CONN_HANDLE
)
Message: Invalid connection handle
Error: 2049
(CR_UNUSED_1
)
Message: Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)
Error: 2050
(CR_FETCH_CANCELED
)
Message: Row retrieval was canceled by mysql_stmt_close() call
Error: 2051
(CR_NO_DATA
)
Message: Attempt to read column without prior row fetch
Error: 2052
(CR_NO_STMT_METADATA
)
Message: Prepared statement contains no metadata
Error: 2053
(CR_NO_RESULT_SET
)
Message: Attempt to read a row while there is no result set associated with the statement
Error: 2054
(CR_NOT_IMPLEMENTED
)
Message: This feature is not implemented yet
Error: 2055
(CR_SERVER_LOST_EXTENDED
)
Message: Lost connection to MySQL server at '%s', system error: %d
Error: 2056
(CR_STMT_CLOSED
)
Message: Statement closed indirectly because of a preceding %s() call
Error: 2057
(CR_NEW_STMT_METADATA
)
Message: The number of columns in the result set differs from the number of bound buffers. You must reset the statement, rebind the result set columns, and execute the statement again
Error: 2058
(CR_ALREADY_CONNECTED
)
Message: This handle is already connected. Use a separate handle for each connection.
Error: 2059
(CR_AUTH_PLUGIN_CANNOT_LOAD
)
Message: Authentication plugin '%s' cannot be loaded: %s
Error: 2060
(CR_DUPLICATE_CONNECTION_ATTR
)
Message: There is an attribute with the same name already
A duplicate connection attribute name was specified for
mysql_options4()
.
Error: 2061
(CR_AUTH_PLUGIN_ERR
)
Message: Authentication plugin '%s' reported error: %s
Error: 2062
(CR_INSECURE_API_ERR
)
Message: Insecure API function call: '%s' Use instead: '%s'
An insecure function call was detected. Modify the application to use the suggested alternative function instead.
Error: 2063
(CR_FILE_NAME_TOO_LONG
)
Message: File name is too long
CR_FILE_NAME_TOO_LONG
was added in
8.0.1.
This section lists some common problems and error messages that you may encounter. It describes how to determine the causes of the problems and what to do to solve them.
When you run into a problem, the first thing you should do is to find out which program or piece of equipment is causing it:
If you have one of the following symptoms, then it is probably a hardware problems (such as memory, motherboard, CPU, or hard disk) or kernel problem:
The keyboard does not work. This can normally be checked by pressing the Caps Lock key. If the Caps Lock light does not change, you have to replace your keyboard. (Before doing this, you should try to restart your computer and check all cables to the keyboard.)
The mouse pointer does not move.
The machine does not answer to a remote machine's pings.
Other programs that are not related to MySQL do not behave correctly.
Your system restarted unexpectedly. (A faulty user-level program should never be able to take down your system.)
In this case, you should start by checking all your cables
and run some diagnostic tool to check your hardware! You
should also check whether there are any patches, updates, or
service packs for your operating system that could likely
solve your problem. Check also that all your libraries (such
as glibc
) are up to date.
It is always good to use a machine with ECC memory to discover memory problems early.
If your keyboard is locked up, you may be able to recover by
logging in to your machine from another machine and
executing kbd_mode -a
.
Please examine your system log file
(/var/log/messages
or similar) for
reasons for your problem. If you think the problem is in
MySQL, you should also examine MySQL's log files. See
Section 5.4, “MySQL Server Logs”.
If you do not think you have hardware problems, you should try to find out which program is causing problems. Try using top, ps, Task Manager, or some similar program, to check which program is taking all CPU or is locking the machine.
Use top, df, or a similar program to check whether you are out of memory, disk space, file descriptors, or some other critical resource.
If the problem is some runaway process, you can always try to kill it. If it does not want to die, there is probably a bug in the operating system.
If after you have examined all other possibilities and you have concluded that the MySQL server or a MySQL client is causing the problem, it is time to create a bug report for our mailing list or our support team. In the bug report, try to give a very detailed description of how the system is behaving and what you think is happening. You should also state why you think that MySQL is causing the problem. Take into consideration all the situations in this chapter. State any problems exactly how they appear when you examine your system. Use the “copy and paste” method for any output and error messages from programs and log files.
Try to describe in detail which program is not working and all symptoms you see. We have in the past received many bug reports that state only “the system does not work.” This provides us with no information about what could be the problem.
If a program fails, it is always useful to know the following information:
Has the program in question made a segmentation fault (did it dump core)?
Is the program taking up all available CPU time? Check with top. Let the program run for a while, it may simply be evaluating something computationally intensive.
If the mysqld server is causing problems, can you get any response from it with mysqladmin -u root ping or mysqladmin -u root processlist?
What does a client program say when you try to connect to the MySQL server? (Try with mysql, for example.) Does the client jam? Do you get any output from the program?
When sending a bug report, you should follow the outline described in Section 1.7, “How to Report Bugs or Problems”.
This section lists some errors that users frequently encounter when running MySQL programs. Although the problems show up when you try to run client programs, the solutions to many of the problems involves changing the configuration of the MySQL server.
An Access denied
error can have many
causes. Often the problem is related to the MySQL accounts
that the server permits client programs to use when
connecting. See Section 6.2, “The MySQL Access Privilege System”, and
Section 6.2.9, “Troubleshooting Problems Connecting to MySQL”.
A MySQL client on Unix can connect to the
mysqld server in two different ways: By
using a Unix socket file to connect through a file in the file
system (default /tmp/mysql.sock
), or by
using TCP/IP, which connects through a port number. A Unix
socket file connection is faster than TCP/IP, but can be used
only when connecting to a server on the same computer. A Unix
socket file is used if you do not specify a host name or if
you specify the special host name
localhost
.
If the MySQL server is running on Windows, you can connect
using TCP/IP. If the server is started with the
--enable-named-pipe
option, you
can also connect with named pipes if you run the client on the
host where the server is running. The name of the named pipe
is MySQL
by default. If you do not give a
host name when connecting to mysqld, a
MySQL client first tries to connect to the named pipe. If that
does not work, it connects to the TCP/IP port. You can force
the use of named pipes on Windows by using
.
as the host name.
The error (2002) Can't connect to ...
normally means that there is no MySQL server running on the
system or that you are using an incorrect Unix socket file
name or TCP/IP port number when trying to connect to the
server. You should also check that the TCP/IP port you are
using has not been blocked by a firewall or port blocking
service.
The error (2003) Can't connect to MySQL server on
'
indicates that the network connection has been refused. You
should check that there is a MySQL server running, that it has
network connections enabled, and that the network port you
specified is the one configured on the server.
server
' (10061)
Start by checking whether there is a process named mysqld running on your server host. (Use ps xa | grep mysqld on Unix or the Task Manager on Windows.) If there is no such process, you should start the server. See Section 2.9.2, “Starting the Server”.
If a mysqld process is running, you can
check it by trying the following commands. The port number or
Unix socket file name might be different in your setup.
host_ip
represents the IP address of the
machine where the server is running.
shell>mysqladmin version
shell>mysqladmin variables
shell>mysqladmin -h `hostname` version variables
shell>mysqladmin -h `hostname` --port=3306 version
shell>mysqladmin -h host_ip version
shell>mysqladmin --protocol=SOCKET --socket=/tmp/mysql.sock version
Note the use of backticks rather than forward quotation marks
with the hostname command; these cause the
output of hostname (that is, the current
host name) to be substituted into the
mysqladmin command. If you have no
hostname command or are running on Windows,
you can manually type the host name of your machine (without
backticks) following the -h
option. You can
also try -h 127.0.0.1
to connect with
TCP/IP to the local host.
Make sure that the server has not been configured to ignore
network connections or (if you are attempting to connect
remotely) that it has not been configured to listen only
locally on its network interfaces. If the server was started
with --skip-networking
, it will
not accept TCP/IP connections at all. If the server was
started with
--bind-address=127.0.0.1
, it
will listen for TCP/IP connections only locally on the
loopback interface and will not accept remote connections.
Check to make sure that there is no firewall blocking access to MySQL. Your firewall may be configured on the basis of the application being executed, or the port number used by MySQL for communication (3306 by default). Under Linux or Unix, check your IP tables (or similar) configuration to ensure that the port has not been blocked. Under Windows, applications such as ZoneAlarm or Windows Firewall may need to be configured not to block the MySQL port.
Here are some reasons the Can't connect to local
MySQL server
error might occur:
mysqld is not running on the local host. Check your operating system's process list to ensure the mysqld process is present.
You're running a MySQL server on Windows with many TCP/IP connections to it. If you're experiencing that quite often your clients get that error, you can find a workaround here: Section B.5.2.2.1, “Connection to MySQL Server Failing on Windows”.
Someone has removed the Unix socket file that
mysqld uses
(/tmp/mysql.sock
by default). For
example, you might have a cron job that
removes old files from the /tmp
directory. You can always run mysqladmin
version to check whether the Unix socket file
that mysqladmin is trying to use really
exists. The fix in this case is to change the
cron job to not remove
mysql.sock
or to place the socket
file somewhere else. See
Section B.5.3.6, “How to Protect or Change the MySQL Unix Socket File”.
You have started the mysqld server with
the
--socket=/path/to/socket
option, but forgotten to tell client programs the new name
of the socket file. If you change the socket path name for
the server, you must also notify the MySQL clients. You
can do this by providing the same
--socket
option when you
run client programs. You also need to ensure that clients
have permission to access the
mysql.sock
file. To find out where
the socket file is, you can do:
shell> netstat -ln | grep mysql
See Section B.5.3.6, “How to Protect or Change the MySQL Unix Socket File”.
You are using Linux and one server thread has died (dumped core). In this case, you must kill the other mysqld threads (for example, with kill) before you can restart the MySQL server. See Section B.5.3.3, “What to Do If MySQL Keeps Crashing”.
The server or client program might not have the proper
access privileges for the directory that holds the Unix
socket file or the socket file itself. In this case, you
must either change the access privileges for the directory
or socket file so that the server and clients can access
them, or restart mysqld with a
--socket
option that
specifies a socket file name in a directory where the
server can create it and where client programs can access
it.
If you get the error message Can't connect to MySQL
server on some_host
, you can try the following
things to find out what the problem is:
Check whether the server is running on that host by
executing telnet some_host 3306
and
pressing the Enter key a couple of times. (3306 is the
default MySQL port number. Change the value if your server
is listening to a different port.) If there is a MySQL
server running and listening to the port, you should get a
response that includes the server's version number. If you
get an error such as telnet: Unable to connect to
remote host: Connection refused
, then there is
no server running on the given port.
If the server is running on the local host, try using
mysqladmin -h localhost variables to
connect using the Unix socket file. Verify the TCP/IP port
number that the server is configured to listen to (it is
the value of the port
variable.)
If you are running under Linux and Security-Enhanced Linux
(SELinux) is enabled, make sure you have disabled SELinux
protection for the mysqld
process.
When you're running a MySQL server on Windows with many
TCP/IP connections to it, and you're experiencing that quite
often your clients get a Can't connect to MySQL
server
error, the reason might be that Windows
does not allow for enough ephemeral (short-lived) ports to
serve those connections.
The purpose of TIME_WAIT
is to keep a
connection accepting packets even after the connection has
been closed. This is because Internet routing can cause a
packet to take a slow route to its destination and it may
arrive after both sides have agreed to close. If the port is
in use for a new connection, that packet from the old
connection could break the protocol or compromise personal
information from the original connection. The
TIME_WAIT
delay prevents this by ensuring
that the port cannot be reused until after some time has
been permitted for those delayed packets to arrive.
It is safe to reduce TIME_WAIT
greatly on
LAN connections because there is little chance of packets
arriving at very long delays, as they could through the
Internet with its comparatively large distances and
latencies.
Windows permits ephemeral (short-lived) TCP ports to the
user. After any port is closed it will remain in a
TIME_WAIT
status for 120 seconds. The
port will not be available again until this time expires.
The default range of port numbers depends on the version of
Windows, with a more limited number of ports in older
versions:
Windows through Server 2003: Ports in range 1025–5000
Windows Vista, Server 2008, and newer: Ports in range 49152–65535
With a small stack of available TCP ports (5000) and a high
number of TCP ports being open and closed over a short
period of time along with the TIME_WAIT
status you have a good chance for running out of ports.
There are two ways to address this problem:
Reduce the number of TCP ports consumed quickly by investigating connection pooling or persistent connections where possible
Tune some settings in the Windows registry (see below)
The following procedure involves modifying the Windows registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore it if a problem occurs. For information about how to back up, restore, and edit the registry, view the following article in the Microsoft Knowledge Base: http://support.microsoft.com/kb/256986/EN-US/.
Start Registry Editor
(Regedt32.exe
).
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit
menu, click Add
Value
, and then add the following registry
value:
Value Name: MaxUserPort Data Type: REG_DWORD Value: 65534
This sets the number of ephemeral ports available to any user. The valid range is between 5000 and 65534 (decimal). The default value is 0x1388 (5000 decimal).
On the Edit
menu, click Add
Value
, and then add the following registry
value:
Value Name: TcpTimedWaitDelay Data Type: REG_DWORD Value: 30
This sets the number of seconds to hold a TCP port
connection in TIME_WAIT
state before
closing. The valid range is between 30 and 300 decimal,
although you may wish to check with Microsoft for the
latest permitted values. The default value is 0x78 (120
decimal).
Quit Registry Editor.
Reboot the machine.
Note: Undoing the above should be as simple as deleting the registry entries you've created.
There are three likely causes for this error message.
Usually it indicates network connectivity trouble and you should check the condition of your network if this error occurs frequently. If the error message includes “during query,” this is probably the case you are experiencing.
Sometimes the “during query” form happens when
millions of rows are being sent as part of one or more
queries. If you know that this is happening, you should try
increasing net_read_timeout
from its default of 30 seconds to 60 seconds or longer,
sufficient for the data transfer to complete.
More rarely, it can happen when the client is attempting the
initial connection to the server. In this case, if your
connect_timeout
value is set
to only a few seconds, you may be able to resolve the problem
by increasing it to ten seconds, perhaps more if you have a
very long distance or slow connection. You can determine
whether you are experiencing this more uncommon cause by using
SHOW GLOBAL STATUS LIKE 'Aborted_connects'
.
It will increase by one for each initial connection attempt
that the server aborts. You may see “reading
authorization packet” as part of the error message; if
so, that also suggests that this is the solution that you
need.
If the cause is none of those just described, you may be
experiencing a problem with
BLOB
values that are larger
than max_allowed_packet
,
which can cause this error with some clients. Sometime you may
see an ER_NET_PACKET_TOO_LARGE
error, and that confirms that you need to increase
max_allowed_packet
.
MySQL client programs prompt for a password when invoked with
a --password
or
-p
option that has no following password
value:
shell> mysql -u user_name
-p
Enter password:
On some systems, you may find that your password works when
specified in an option file or on the command line, but not
when you enter it interactively at the Enter
password:
prompt. This occurs when the library
provided by the system to read passwords limits password
values to a small number of characters (typically eight). That
is a problem with the system library, not with MySQL. To work
around it, change your MySQL password to a value that is eight
or fewer characters long, or put your password in an option
file.
If the following error occurs, it means that mysqld has received many connection requests from the given host that were interrupted in the middle:
Host 'host_name
' is blocked because of many connection errors.
Unblock with 'mysqladmin flush-hosts'
The value of the
max_connect_errors
system
variable determines how many successive interrupted connection
requests are permitted. (See
Section 5.1.5, “Server System Variables”.) After
max_connect_errors
failed
requests without a successful connection,
mysqld assumes that something is wrong (for
example, that someone is trying to break in), and blocks the
host from further connections until you issue a
FLUSH HOSTS
statement or
execute a mysqladmin flush-hosts command.
By default, mysqld blocks a host after 100
connection errors. You can adjust the value by setting
max_connect_errors
at server
startup:
shell> mysqld_safe --max_connect_errors=10000 &
The value can also be set at runtime:
mysql> SET GLOBAL max_connect_errors=10000;
If you get the Host
'
error message for a given host, you should first verify that
there is nothing wrong with TCP/IP connections from that host.
If you are having network problems, it does you no good to
increase the value of the
host_name
' is blockedmax_connect_errors
variable.
If you get a Too many connections
error
when you try to connect to the mysqld
server, this means that all available connections are in use
by other clients.
The number of connections permitted is controlled by the
max_connections
system
variable. The default value is 151 to improve performance when
MySQL is used with the Apache Web server. (Previously, the
default was 100.) If you need to support more connections, you
should set a larger value for this variable.
mysqld actually permits
max_connections+1
clients to connect. The extra connection is reserved for use
by accounts that have the
CONNECTION_ADMIN
or
SUPER
privilege. By granting
the privilege to administrators and not to normal users (who
should not need it), an administrator who also has the
PROCESS
privilege can connect
to the server and use SHOW
PROCESSLIST
to diagnose problems even if the maximum
number of unprivileged clients are connected. See
Section 13.7.5.29, “SHOW PROCESSLIST Syntax”.
The maximum number of connections MySQL supports depends on the quality of the thread library on a given platform, the amount of RAM available, how much RAM is used for each connection, the workload from each connection, and the desired response time. Linux or Solaris should be able to support at least 500 to 1000 simultaneous connections routinely and as many as 10,000 connections if you have many gigabytes of RAM available and the workload from each is low or the response time target undemanding. Windows is limited to (open tables × 2 + open connections) < 2048 due to the Posix compatibility layer used on that platform.
Increasing open-files-limit
may
be necessary. Also see Section 2.5, “Installing MySQL on Linux”,
for how to raise the operating system limit on how many
handles can be used by MySQL.
If you issue a query using the mysql client program and receive an error like the following one, it means that mysql does not have enough memory to store the entire query result:
mysql: Out of memory at line 42, 'malloc.c' mysql: needed 8136 byte (8k), memory in use: 12481367 bytes (12189k) ERROR 2008: MySQL client ran out of memory
To remedy the problem, first check whether your query is
correct. Is it reasonable that it should return so many rows?
If not, correct the query and try again. Otherwise, you can
invoke mysql with the
--quick
option. This causes it
to use the mysql_use_result()
C API function to retrieve the result set, which places less
of a load on the client (but more on the server).
This section also covers the related Lost connection
to server during query
error.
The most common reason for the MySQL server has gone
away
error is that the server timed out and closed
the connection. In this case, you normally get one of the
following error codes (which one you get is operating
system-dependent).
Error Code | Description |
---|---|
CR_SERVER_GONE_ERROR | The client couldn't send a question to the server. |
CR_SERVER_LOST | The client didn't get an error when writing to the server, but it didn't get a full answer (or any answer) to the question. |
By default, the server closes the connection after eight hours
if nothing has happened. You can change the time limit by
setting the wait_timeout
variable when you start mysqld. See
Section 5.1.5, “Server System Variables”.
If you have a script, you just have to issue the query again
for the client to do an automatic reconnection. This assumes
that you have automatic reconnection in the client enabled
(which is the default for the mysql
command-line client).
Some other common reasons for the MySQL server has
gone away
error are:
You (or the db administrator) has killed the running
thread with a KILL
statement or a mysqladmin kill command.
You tried to run a query after closing the connection to the server. This indicates a logic error in the application that should be corrected.
A client application running on a different host does not have the necessary privileges to connect to the MySQL server from that host.
You got a timeout from the TCP/IP connection on the client
side. This may happen if you have been using the commands:
mysql_options(...,
MYSQL_OPT_READ_TIMEOUT,...)
or
mysql_options(...,
MYSQL_OPT_WRITE_TIMEOUT,...)
. In this case
increasing the timeout may help solve the problem.
You have encountered a timeout on the server side and the
automatic reconnection in the client is disabled (the
reconnect
flag in the
MYSQL
structure is equal to 0).
You are using a Windows client and the server had dropped
the connection (probably because
wait_timeout
expired)
before the command was issued.
The problem on Windows is that in some cases MySQL does not get an error from the OS when writing to the TCP/IP connection to the server, but instead gets the error when trying to read the answer from the connection.
The solution to this is to either do a
mysql_ping()
on the
connection if there has been a long time since the last
query (this is what Connector/ODBC does) or set
wait_timeout
on the
mysqld server so high that it in
practice never times out.
You can also get these errors if you send a query to the
server that is incorrect or too large. If
mysqld receives a packet that is too
large or out of order, it assumes that something has gone
wrong with the client and closes the connection. If you
need big queries (for example, if you are working with big
BLOB
columns), you can
increase the query limit by setting the server's
max_allowed_packet
variable, which has a default value of 64MB (4MB before
MySQL 8.0.3). You may also need to increase the maximum
packet size on the client end. More information on setting
the packet size is given in
Section B.5.2.9, “Packet Too Large”.
An INSERT
or
REPLACE
statement that
inserts a great many rows can also cause these sorts of
errors. Either one of these statements sends a single
request to the server irrespective of the number of rows
to be inserted; thus, you can often avoid the error by
reducing the number of rows sent per
INSERT
or
REPLACE
.
It is also possible to see this error if host name lookups fail (for example, if the DNS server on which your server or network relies goes down). This is because MySQL is dependent on the host system for name resolution, but has no way of knowing whether it is working—from MySQL's point of view the problem is indistinguishable from any other network timeout.
You may also see the MySQL server has gone
away
error if MySQL is started with the
--skip-networking
option.
Another networking issue that can cause this error occurs if the MySQL port (default 3306) is blocked by your firewall, thus preventing any connections at all to the MySQL server.
You can also encounter this error with applications that fork child processes, all of which try to use the same connection to the MySQL server. This can be avoided by using a separate connection for each child process.
You have encountered a bug where the server died while executing the query.
You can check whether the MySQL server died and restarted by executing mysqladmin version and examining the server's uptime. If the client connection was broken because mysqld crashed and restarted, you should concentrate on finding the reason for the crash. Start by checking whether issuing the query again kills the server again. See Section B.5.3.3, “What to Do If MySQL Keeps Crashing”.
You can get more information about the lost connections by
starting mysqld with the
log_error_verbosity
system
variable set to 3. This logs some of the disconnection
messages in the hostname.err
file. See
Section 5.4.2, “The Error Log”.
If you want to create a bug report regarding this problem, be sure that you include the following information:
Indicate whether the MySQL server died. You can find information about this in the server error log. See Section B.5.3.3, “What to Do If MySQL Keeps Crashing”.
If a specific query kills mysqld and
the tables involved were checked with
CHECK TABLE
before you ran
the query, can you provide a reproducible test case? See
Section 28.5, “Debugging and Porting MySQL”.
What is the value of the
wait_timeout
system
variable in the MySQL server? (mysqladmin
variables gives you the value of this variable.)
Have you tried to run mysqld with the general query log enabled to determine whether the problem query appears in the log? (See Section 5.4.3, “The General Query Log”.)
See also Section B.5.2.10, “Communication Errors and Aborted Connections”, and Section 1.7, “How to Report Bugs or Problems”.
A communication packet is a single SQL statement sent to the MySQL server, a single row that is sent to the client, or a binary log event sent from a master replication server to a slave.
The largest possible packet that can be transmitted to or from a MySQL 8.0 server or client is 1GB.
When a MySQL client or the mysqld server
receives a packet bigger than
max_allowed_packet
bytes, it
issues an
ER_NET_PACKET_TOO_LARGE
error
and closes the connection. With some clients, you may also get
a Lost connection to MySQL server during
query
error if the communication packet is too
large.
Both the client and the server have their own
max_allowed_packet
variable,
so if you want to handle big packets, you must increase this
variable both in the client and in the server.
If you are using the mysql client program,
its default
max_allowed_packet
variable
is 16MB. To set a larger value, start mysql
like this:
shell> mysql --max_allowed_packet=32M
That sets the packet size to 32MB.
The server's default
max_allowed_packet
value is
64MB (4MB before MySQL 8.0.3). You can increase this if the
server needs to handle big queries (for example, if you are
working with big BLOB
columns).
For example, to set the variable to 128MB, start the server
like this:
shell> mysqld --max_allowed_packet=128M
You can also use an option file to set
max_allowed_packet
. For
example, to set the size for the server to 128MB, add the
following lines in an option file:
[mysqld] max_allowed_packet=128M
It is safe to increase the value of this variable because the extra memory is allocated only when needed. For example, mysqld allocates more memory only when you issue a long query or when mysqld must return a large result row. The small default value of the variable is a precaution to catch incorrect packets between the client and server and also to ensure that you do not run out of memory by using large packets accidentally.
You can also get strange problems with large packets if you
are using large BLOB
values but
have not given mysqld access to enough
memory to handle the query. If you suspect this is the case,
try adding ulimit -d 256000 to the
beginning of the mysqld_safe script and
restarting mysqld.
If connection problems occur such as communication errors or aborted connections, use these sources of information to diagnose problems:
The error log. See Section 5.4.2, “The Error Log”.
The general query log. See Section 5.4.3, “The General Query Log”.
The
Aborted_
and
xxx
Connection_errors_
status variables. See
Section 5.1.7, “Server Status Variables”.
xxx
The host cache, which is accessible using the
host_cache
Performance Schema table.
See Section 8.12.4.2, “DNS Lookup Optimization and the Host Cache”, and
Section 25.11.16.1, “The host_cache Table”.
If you start the server with the
log_error_verbosity
system
variable set to 3, you might find messages like this in your
error log:
[Note] Aborted connection 854 to db: 'employees' user: 'josh'
If a client is unable even to connect, the server increments
the Aborted_connects
status
variable. Unsuccessful connection attempts can occur for the
following reasons:
A client attempts to access a database but has no privileges for it.
A client uses an incorrect password.
A connection packet does not contain the right information.
It takes more than
connect_timeout
seconds
to obtain a connect packet. See
Section 5.1.5, “Server System Variables”.
If these kinds of things happen, it might indicate that someone is trying to break into your server! If the general query log is enabled, messages for these types of problems are logged to it.
If a client successfully connects but later disconnects
improperly or is terminated, the server increments the
Aborted_clients
status
variable, and logs an Aborted
connection message to the error log. The cause can
be any of the following:
The client program did not call
mysql_close()
before
exiting.
The client had been sleeping more than
wait_timeout
or
interactive_timeout
seconds without issuing any requests to the server. See
Section 5.1.5, “Server System Variables”.
The client program ended abruptly in the middle of a data transfer.
Other reasons for problems with aborted connections or aborted clients:
The max_allowed_packet
variable value is too small or queries require more memory
than you have allocated for mysqld. See
Section B.5.2.9, “Packet Too Large”.
Use of Ethernet protocol with Linux, both half and full duplex. Some Linux Ethernet drivers have this bug. You should test for this bug by transferring a huge file using FTP between the client and server machines. If a transfer goes in burst-pause-burst-pause mode, you are experiencing a Linux duplex syndrome. Switch the duplex mode for both your network card and hub/switch to either full duplex or to half duplex and test the results to determine the best setting.
A problem with the thread library that causes interrupts on reads.
Badly configured TCP/IP.
Faulty Ethernets, hubs, switches, cables, and so forth. This can be diagnosed properly only by replacing hardware.
If a table-full error occurs, it may be that the disk is full or that the table has reached its maximum size. The effective maximum table size for MySQL databases is usually determined by operating system constraints on file sizes, not by MySQL internal limits. See Section C.10.3, “Limits on Table Size”.
If you get an error of the following type for some queries, it means that MySQL cannot create a temporary file for the result set in the temporary directory:
Can't create/write to file '\\sqla3fe_0.ism'.
The preceding error is a typical message for Windows; the Unix message is similar.
One fix is to start mysqld with the
--tmpdir
option or to add the
option to the [mysqld]
section of your
option file. For example, to specify a directory of
C:\temp
, use these lines:
[mysqld] tmpdir=C:/temp
The C:\temp
directory must exist and have
sufficient space for the MySQL server to write to. See
Section 4.2.6, “Using Option Files”.
Another cause of this error can be permissions issues. Make
sure that the MySQL server can write to the
tmpdir
directory.
Check also the error code that you get with perror. One reason the server cannot write to a table is that the file system is full:
shell> perror 28
OS error code 28: No space left on device
If you get an error of the following type during startup, it indicates that the file system or directory used for storing data files is write protected. Provided that the write error is to a test file, the error is not serious and can be safely ignored.
Can't create test file /usr/local/mysql/data/master.lower-test
If you get Commands out of sync; you can't run this
command now
in your client code, you are calling
client functions in the wrong order.
This can happen, for example, if you are using
mysql_use_result()
and try to
execute a new query before you have called
mysql_free_result()
. It can
also happen if you try to execute two queries that return data
without calling
mysql_use_result()
or
mysql_store_result()
in
between.
If you get the following error, it means that when
mysqld was started or when it reloaded the
grant tables, it found an account in the
user
table that had an invalid password.
Found wrong password for user
'
some_user
'@'some_host
';
ignoring user
As a result, the account is simply ignored by the permission system. To fix this problem, assign a new, valid password to the account.
If you get either of the following errors, it usually means that no table exists in the default database with the given name:
Table 'tbl_name
' doesn't exist Can't find file: 'tbl_name
' (errno: 2)
In some cases, it may be that the table does exist but that you are referring to it incorrectly:
Because MySQL uses directories and files to store databases and tables, database and table names are case sensitive if they are located on a file system that has case-sensitive file names.
Even for file systems that are not case sensitive, such as on Windows, all references to a given table within a query must use the same lettercase.
You can check which tables are in the default database with
SHOW TABLES
. See
Section 13.7.5, “SHOW Syntax”.
You might see an error like this if you have character set problems:
MySQL Connection Failed: Can't initialize character set charset_name
This error can have any of the following causes:
The character set is a multibyte character set and you
have no support for the character set in the client. In
this case, you need to recompile the client by running
CMake with the
-DDEFAULT_CHARSET=
option. See
Section 2.8.4, “MySQL Source-Configuration Options”.
charset_name
All standard MySQL binaries are compiled with support for all multibyte character sets.
The character set is a simple character set that is not compiled into mysqld, and the character set definition files are not in the place where the client expects to find them.
In this case, you need to use one of the following methods to solve the problem:
Recompile the client with support for the character set. See Section 2.8.4, “MySQL Source-Configuration Options”.
Specify to the client the directory where the
character set definition files are located. For many
clients, you can do this with the
--character-sets-dir
option.
Copy the character definition files to the path where the client expects them to be.
If you get ERROR
'
, file_name
' not found (errno:
23)Can't open file:
, or
any other error with file_name
(errno: 24)errno 23
or
errno 24
from MySQL, it means that you have
not allocated enough file descriptors for the MySQL server.
You can use the perror utility to get a
description of what the error number means:
shell>perror 23
OS error code 23: File table overflow shell>perror 24
OS error code 24: Too many open files shell>perror 11
OS error code 11: Resource temporarily unavailable
The problem here is that mysqld is trying to keep open too many files simultaneously. You can either tell mysqld not to open so many files at once or increase the number of file descriptors available to mysqld.
To tell mysqld to keep open fewer files at
a time, you can make the table cache smaller by reducing the
value of the table_open_cache
system variable (the default value is 64). This may not
entirely prevent running out of file descriptors because in
some circumstances the server may attempt to extend the cache
size temporarily, as described in
Section 8.4.3.1, “How MySQL Opens and Closes Tables”. Reducing the value of
max_connections
also reduces
the number of open files (the default value is 100).
To change the number of file descriptors available to
mysqld, you can use the
--open-files-limit
option
to mysqld_safe or set the
open_files_limit
system
variable. See Section 5.1.5, “Server System Variables”. The
easiest way to set these values is to add an option to your
option file. See Section 4.2.6, “Using Option Files”. If you have
an old version of mysqld that does not
support setting the open files limit, you can edit the
mysqld_safe script. There is a
commented-out line ulimit -n 256 in the
script. You can remove the #
character to
uncomment this line, and change the number
256
to set the number of file descriptors
to be made available to mysqld.
--open-files-limit
and
ulimit can increase the number of file
descriptors, but only up to the limit imposed by the operating
system. There is also a “hard” limit that can be
overridden only if you start mysqld_safe or
mysqld as root
(just
remember that you also need to start the server with the
--user
option in this case so
that it does not continue to run as root
after it starts up). If you need to increase the operating
system limit on the number of file descriptors available to
each process, consult the documentation for your system.
If you run the tcsh shell, ulimit does not work! tcsh also reports incorrect values when you ask for the current limits. In this case, you should start mysqld_safe using sh.
If you have started mysqld with
--myisam-recover-options
, MySQL
automatically checks and tries to repair
MyISAM
tables if they are marked as 'not
closed properly' or 'crashed'. If this happens, MySQL writes
an entry in the hostname.err
file
'Warning: Checking table ...'
which is
followed by Warning: Repairing table
if the
table needs to be repaired. If you get a lot of these errors,
without mysqld having died unexpectedly
just before, then something is wrong and needs to be
investigated further.
When the server detects MyISAM
table
corruption, it writes additional information to the error log,
such as the name and line number of the source file, and the
list of threads accessing the table. Example: Got an
error from thread_id=1, mi_dynrec.c:368
. This is
useful information to include in bug reports.
See also Section 5.1.4, “Server Command Options”, and Section 28.5.1.7, “Making a Test Case If You Experience Table Corruption”.
If you have problems with file permissions, the
UMASK
or UMASK_DIR
environment variable might be set incorrectly when
mysqld starts. For example, MySQL might
issue the following error message when you create a table:
ERROR: Can't find file: 'path/with/file_name
' (Errcode: 13)
The default UMASK
and
UMASK_DIR
values are
0640
and 0750
,
respectively. MySQL assumes that the value for
UMASK
or UMASK_DIR
is in
octal if it starts with a zero. For example, setting
UMASK=0600
is equivalent to
UMASK=384
because 0600 octal is 384
decimal.
To change the default UMASK
value, start
mysqld_safe as follows:
shell>UMASK=384 # = 600 in octal
shell>export UMASK
shell>mysqld_safe &
By default, MySQL creates database directories with an access
permission value of 0750
. To modify this
behavior, set the UMASK_DIR
variable. If
you set its value, new directories are created with the
combined UMASK
and
UMASK_DIR
values. For example, to give
group access to all new directories, start
mysqld_safe as follows:
shell>UMASK_DIR=504 # = 770 in octal
shell>export UMASK_DIR
shell>mysqld_safe &
For additional details, see Section 4.9, “MySQL Program Environment Variables”.
If you have never assigned a root
password
for MySQL, the server does not require a password at all for
connecting as root
. However, this is
insecure. For instructions on assigning a password, see
Section 2.9.4, “Securing the Initial MySQL Account”.
If you know the root
password and want to
change it, see Section 13.7.1.1, “ALTER USER Syntax”, and
Section 13.7.1.10, “SET PASSWORD Syntax”.
If you assigned a root
password previously
but have forgotten it, you can assign a new password. The
following sections provide instructions for Windows and Unix
and Unix-like systems, as well as generic instructions that
apply to any system.
On Windows, use the following procedure to reset the
password for the MySQL 'root'@'localhost'
account. To change the password for a
root
account with a different host name
part, modify the instructions to use that host name.
Log on to your system as Administrator.
Stop the MySQL server if it is running. For a server that is running as a Windows service, go to the Services manager: From the
menu, select , then , then . Find the MySQL service in the list and stop it.If your server is not running as a service, you may need to use the Task Manager to force it to stop.
Create a text file containing the password-assignment statement on a single line. Replace the password with the password that you want to use.
ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';
Save the file. This example assumes that you name the
file C:\mysql-init.txt
.
Open a console window to get to the command prompt: From the cmd as the command to be run.
menu, select , then enter
Start the MySQL server with the special
--init-file
option
(notice that the backslash in the option value is
doubled):
C:\>cd "C:\Program Files\MySQL\MySQL Server 8.0\bin"
C:\>mysqld --init-file=C:\\mysql-init.txt
If you installed MySQL to a different location, adjust the cd command accordingly.
The server executes the contents of the file named by
the --init-file
option at
startup, changing the
'root'@'localhost'
account password.
To have server output to appear in the console window
rather than in a log file, add the
--console
option to the
mysqld command.
If you installed MySQL using the MySQL Installation
Wizard, you may need to specify a
--defaults-file
option.
For example:
C:\>mysqld
--defaults-file="C:\\ProgramData\\MySQL\\MySQL Server 8.0\\my.ini"
--init-file=C:\\mysql-init.txt
The appropriate
--defaults-file
setting
can be found using the Services Manager: From the
menu, select
, then
, then
. Find the MySQL
service in the list, right-click it, and choose the
Properties
option. The Path
to executable
field contains the
--defaults-file
setting.
After the server has started successfully, delete
C:\mysql-init.txt
.
You should now be able to connect to the MySQL server as
root
using the new password. Stop the
MySQL server and restart it normally. If you run the server
as a service, start it from the Windows Services window. If
you start the server manually, use whatever command you
normally use.
On Unix, use the following procedure to reset the password
for the MySQL 'root'@'localhost'
account.
To change the password for a root
account
with a different host name part, modify the instructions to
use that host name.
The instructions assume that you will start the MySQL server
from the Unix login account that you normally use for
running it. For example, if you run the server using the
mysql
login account, you should log in as
mysql
before using the instructions.
Alternatively, you can log in as root
,
but in this case you must start
mysqld with the
--user=mysql
option. If you
start the server as root
without using
--user=mysql
, the server may
create root
-owned files in the data
directory, such as log files, and these may cause
permission-related problems for future server startups. If
that happens, you will need to either change the ownership
of the files to mysql
or remove them.
Log on to your system as the Unix user that the MySQL
server runs as (for example, mysql
).
Stop the MySQL server if it is running. Locate the
.pid
file that contains the
server's process ID. The exact location and name of this
file depend on your distribution, host name, and
configuration. Common locations are
/var/lib/mysql/
,
/var/run/mysqld/
, and
/usr/local/mysql/data/
. Generally,
the file name has an extension of
.pid
and begins with either
mysqld
or your system's host name.
Stop the MySQL server by sending a normal
kill
(not kill -9
)
to the mysqld process. Use the actual
path name of the .pid
file in the
following command:
shell> kill `cat /mysql-data-directory/host_name.pid`
Use backticks (not forward quotation marks) with the
cat
command. These cause the output
of cat
to be substituted into the
kill
command.
Create a text file containing the password-assignment statement on a single line. Replace the password with the password that you want to use.
ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';
Save the file. This example assumes that you name the
file /home/me/mysql-init
. The file
contains the password, so do not save it where it can be
read by other users. If you are not logged in as
mysql
(the user the server runs as),
make sure that the file has permissions that permit
mysql
to read it.
Start the MySQL server with the special
--init-file
option:
shell> mysqld --init-file=/home/me/mysql-init &
The server executes the contents of the file named by
the --init-file
option at
startup, changing the
'root'@'localhost'
account password.
Other options may be necessary as well, depending on how
you normally start your server. For example,
--defaults-file
may be
needed before
--init-file
.
After the server has started successfully, delete
/home/me/mysql-init
.
You should now be able to connect to the MySQL server as
root
using the new password. Stop the
server and restart it normally.
The preceding sections provide password-resetting instructions specifically for Windows and Unix and Unix-like systems. Alternatively, on any platform, you can reset the password using the mysql client (but this approach is less secure):
Stop the MySQL server if necessary, then restart it with
the --skip-grant-tables
option. This enables anyone to connect without a
password and with all privileges, and disables
account-management statements such as
ALTER USER
and
SET PASSWORD
. Because
this is insecure, you might want to use
--skip-grant-tables
in
conjunction with
--skip-networking
to
prevent remote clients from connecting. As of MySQL
8.0.3, if the server is started with the
--skip-grant-tables
option, the server enables
--skip-networking
automatically to prevent remote connections.
Connect to the MySQL server using the
mysql client; no password is
necessary because the server was started with
--skip-grant-tables
:
shell> mysql
In the mysql
client, tell the server
to reload the grant tables so that account-management
statements work:
mysql> FLUSH PRIVILEGES;
Then change the 'root'@'localhost'
account password. Replace the password with the password
that you want to use. To change the password for a
root
account with a different host
name part, modify the instructions to use that host
name.
mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';
You should now be able to connect to the MySQL server as
root
using the new password. Stop the
server and restart it normally (without the
--skip-grant-tables
and
--skip-networking
options).
Each MySQL version is tested on many platforms before it is released. This does not mean that there are no bugs in MySQL, but if there are bugs, they should be very few and can be hard to find. If you have a problem, it always helps if you try to find out exactly what crashes your system, because you have a much better chance of getting the problem fixed quickly.
First, you should try to find out whether the problem is that the mysqld server dies or whether your problem has to do with your client. You can check how long your mysqld server has been up by executing mysqladmin version. If mysqld has died and restarted, you may find the reason by looking in the server's error log. See Section 5.4.2, “The Error Log”.
On some systems, you can find in the error log a stack trace
of where mysqld died that you can resolve
with the resolve_stack_dump
program. See
Section 28.5, “Debugging and Porting MySQL”. Note that the variable values
written in the error log may not always be 100% correct.
Many server crashes are caused by corrupted data files or
index files. MySQL updates the files on disk with the
write()
system call after every SQL
statement and before the client is notified about the result.
(This is not true if you are running with
--delay-key-write
, in which
case data files are written but not index files.) This means
that data file contents are safe even if
mysqld crashes, because the operating
system ensures that the unflushed data is written to disk. You
can force MySQL to flush everything to disk after every SQL
statement by starting mysqld with the
--flush
option.
The preceding means that normally you should not get corrupted tables unless one of the following happens:
The MySQL server or the server host was killed in the middle of an update.
You have found a bug in mysqld that caused it to die in the middle of an update.
Some external program is manipulating data files or index files at the same time as mysqld without locking the table properly.
You are running many mysqld servers
using the same data directory on a system that does not
support good file system locks (normally handled by the
lockd
lock manager), or you are running
multiple servers with external locking disabled.
You have a crashed data file or index file that contains very corrupt data that confused mysqld.
You have found a bug in the data storage code. This isn't
likely, but it is at least possible. In this case, you can
try to change the storage engine to another engine by
using ALTER TABLE
on a
repaired copy of the table.
Because it is very difficult to know why something is crashing, first try to check whether things that work for others crash for you. Try the following things:
Stop the mysqld server with
mysqladmin shutdown, run
myisamchk --silent --force */*.MYI from
the data directory to check all MyISAM
tables, and restart mysqld. This
ensures that you are running from a clean state. See
Chapter 5, MySQL Server Administration.
Start mysqld with the general query log enabled (see Section 5.4.3, “The General Query Log”). Then try to determine from the information written to the log whether some specific query kills the server. About 95% of all bugs are related to a particular query. Normally, this is one of the last queries in the log file just before the server restarts. See Section 5.4.3, “The General Query Log”. If you can repeatedly kill MySQL with a specific query, even when you have checked all tables just before issuing it, then you have isolated the bug and should submit a bug report for it. See Section 1.7, “How to Report Bugs or Problems”.
Try to make a test case that we can use to repeat the problem. See Section 28.5, “Debugging and Porting MySQL”.
Try the fork_big.pl
script. (It is
located in the tests
directory of
source distributions.)
Configuring MySQL for debugging makes it much easier to
gather information about possible errors if something goes
wrong. Reconfigure MySQL with the
-DWITH_DEBUG=1
option to
CMake and then recompile. See
Section 28.5, “Debugging and Porting MySQL”.
Make sure that you have applied the latest patches for your operating system.
Use the
--skip-external-locking
option to mysqld. On some systems, the
lockd
lock manager does not work
properly; the
--skip-external-locking
option tells mysqld not to use external
locking. (This means that you cannot run two
mysqld servers on the same data
directory and that you must be careful if you use
myisamchk. Nevertheless, it may be
instructive to try the option as a test.)
If mysqld appears to be running but not responding, try mysqladmin -u root processlist. Sometimes mysqld is not hung even though it seems unresponsive. The problem may be that all connections are in use, or there may be some internal lock problem. mysqladmin -u root processlist usually is able to make a connection even in these cases, and can provide useful information about the current number of connections and their status.
Run the command mysqladmin -i 5 status or mysqladmin -i 5 -r status in a separate window to produce statistics while running other queries.
Try the following:
Start mysqld from gdb (or another debugger). See Section 28.5, “Debugging and Porting MySQL”.
Run your test scripts.
Print the backtrace and the local variables at the three lowest levels. In gdb, you can do this with the following commands when mysqld has crashed inside gdb:
backtrace info local up info local up info local
With gdb, you can also examine
which threads exist with info
threads
and switch to a specific thread with
thread
, where
N
N
is the thread ID.
Try to simulate your application with a Perl script to force MySQL to crash or misbehave.
Send a normal bug report. See Section 1.7, “How to Report Bugs or Problems”. Be even more detailed than usual. Because MySQL works for many people, the crash might result from something that exists only on your computer (for example, an error that is related to your particular system libraries).
If you have a problem with tables containing
dynamic-length rows and you are using only
VARCHAR
columns (not
BLOB
or
TEXT
columns), you can try
to change all VARCHAR
to
CHAR
with
ALTER TABLE
. This forces
MySQL to use fixed-size rows. Fixed-size rows take a
little extra space, but are much more tolerant to
corruption.
The current dynamic row code has been in use for several years with very few problems, but dynamic-length rows are by nature more prone to errors, so it may be a good idea to try this strategy to see whether it helps.
Consider the possibility of hardware faults when diagnosing problems. Defective hardware can be the cause of data corruption. Pay particular attention to your memory and disk subsystems when troubleshooting hardware.
This section describes how MySQL responds to disk-full errors (such as “no space left on device”), and to quota-exceeded errors (such as “write failed” or “user block limit reached”).
This section is relevant for writes to
MyISAM
tables. It also applies for writes
to binary log files and binary log index file, except that
references to “row” and “record”
should be understood to mean “event.”
When a disk-full condition occurs, MySQL does the following:
It checks once every minute to see whether there is enough space to write the current row. If there is enough space, it continues as if nothing had happened.
Every 10 minutes it writes an entry to the log file, warning about the disk-full condition.
To alleviate the problem, take the following actions:
To continue, you only have to free enough disk space to insert all records.
Alternatively, to abort the thread, use mysqladmin kill. The thread is aborted the next time it checks the disk (in one minute).
Other threads might be waiting for the table that caused the disk-full condition. If you have several “locked” threads, killing the one thread that is waiting on the disk-full condition enables the other threads to continue.
Exceptions to the preceding behavior are when you use
REPAIR TABLE
or
OPTIMIZE TABLE
or when the
indexes are created in a batch after
LOAD DATA
INFILE
or after an ALTER
TABLE
statement. All of these statements may create
large temporary files that, if left to themselves, would cause
big problems for the rest of the system. If the disk becomes
full while MySQL is doing any of these operations, it removes
the big temporary files and mark the table as crashed. The
exception is that for ALTER
TABLE
, the old table is left unchanged.
On Unix, MySQL uses the value of the TMPDIR
environment variable as the path name of the directory in
which to store temporary files. If TMPDIR
is not set, MySQL uses the system default, which is usually
/tmp
, /var/tmp
, or
/usr/tmp
.
On Windows, MySQL checks in order the values of the
TMPDIR
, TEMP
, and
TMP
environment variables. For the first
one found to be set, MySQL uses it and does not check those
remaining. If none of TMPDIR
,
TEMP
, or TMP
are set,
MySQL uses the Windows system default, which is usually
C:\windows\temp\
.
If the file system containing your temporary file directory is
too small, you can use the mysqld
--tmpdir
option to specify a
directory in a file system where you have enough space. On
replication slaves, you can use
--slave-load-tmpdir
to specify
a separate directory for holding temporary files when
replicating LOAD
DATA INFILE
statements.
The --tmpdir
option can be set
to a list of several paths that are used in round-robin
fashion. Paths should be separated by colon characters
(:
) on Unix and semicolon characters
(;
) on Windows.
To spread the load effectively, these paths should be located on different physical disks, not different partitions of the same disk.
If the MySQL server is acting as a replication slave, you
should be sure to set
--slave-load-tmpdir
not to
point to a directory that is on a memory-based file system or
to a directory that is cleared when the server host restarts.
A replication slave needs some of its temporary files to
survive a machine restart so that it can replicate temporary
tables or LOAD DATA
INFILE
operations. If files in the slave temporary
file directory are lost when the server restarts, replication
fails.
MySQL arranges that temporary files are removed if mysqld is terminated. On platforms that support it (such as Unix), this is done by unlinking the file after opening it. The disadvantage of this is that the name does not appear in directory listings and you do not see a big temporary file that fills up the file system in which the temporary file directory is located. (In such cases, lsof +L1 may be helpful in identifying large files associated with mysqld.)
When sorting (ORDER BY
or GROUP
BY
), MySQL normally uses one or two temporary files.
The maximum disk space required is determined by the following
expression:
(length of what is sorted + sizeof(row pointer)) * number of matched rows * 2
The row pointer size is usually four bytes, but may grow in the future for really big tables.
For some SELECT
queries, MySQL
also creates temporary SQL tables. These are not hidden and
have names of the form SQL_*
.
In most cases, ALTER TABLE
creates a temporary copy of the original table in the same
directory as the original table.
InnoDB
temporary tables are stored in a
temporary tablespace file named ibtmp1
,
which is located in the MySQL data
directory (datadir
) by
default. The
innodb_temp_data_file_path
option can be used at startup to specify a different file
name and location.
If an ALTER TABLE
operation
on an InnoDB
table uses the
ALGORITHM=COPY
technique,
InnoDB
creates a temporary copy of the
table in the same directory as the original table. Temporary
table file names begin with an #sql-
prefix and only appear briefly during the
ALTER TABLE
operation.
If an ALTER TABLE
operation
rebuilds an InnoDB
table using the
ALGORITHM=INPLACE
technique (online DDL),
InnoDB
creates an
intermediate copy of the table the same
directory as the original table. Intermediate table file
names begin with an #sql-ib
prefix and
only appear briefly during the ALTER
TABLE
operation.
ALTER TABLE
operations that
rebuild an InnoDB
table using the
ALGORITHM=INPLACE
technique (online DDL)
also create temporary sort files in the MySQL temporary
directory ($TMPDIR
on Unix,
%TEMP%
on Windows, or the directory
specified by the --tmpdir
configuration option). If the temporary directory is not
large enough to hold such files, you may need to reconfigure
tmpdir
. Alternatively, you
can define a separate temporary directory for
InnoDB
online ALTER
TABLE
operations using the
innodb_tmpdir
configuration
option. This option was introduced to help avoid temporary
directory overflows that could occur as a result of large
temporary sort files created during online
ALTER TABLE
operations.
innodb_tmpdir
can be
configured dynamically using a
SET
GLOBAL
or
SET
SESSION
statement.
The innodb_tmpdir
option is
not applicable to intermediate table files, which are always
created in the same directory as the original table.
In replication environments, only consider replicating an
innodb_tmpdir
setting if
all servers have the same operating system environment.
Otherwise, replicating an
innodb_tmpdir
setting could
result in a replication failure when running online
ALTER TABLE
operations. If
server operating environments differ, it is recommended that
you configure innodb_tmpdir
on each server individually.
For more information about online DDL, Section 15.12, “InnoDB and Online DDL”.
The default location for the Unix socket file that the server
uses for communication with local clients is
/tmp/mysql.sock
. (For some distribution
formats, the directory might be different, such as
/var/lib/mysql
for RPMs.)
On some versions of Unix, anyone can delete files in the
/tmp
directory or other similar
directories used for temporary files. If the socket file is
located in such a directory on your system, this might cause
problems.
On most versions of Unix, you can protect your
/tmp
directory so that files can be
deleted only by their owners or the superuser
(root
). To do this, set the
sticky
bit on the /tmp
directory by logging in as root
and using
the following command:
shell> chmod +t /tmp
You can check whether the sticky
bit is set
by executing ls -ld /tmp
. If the last
permission character is t
, the bit is set.
Another approach is to change the place where the server creates the Unix socket file. If you do this, you should also let client programs know the new location of the file. You can specify the file location in several ways:
Specify the path in a global or local option file. For
example, put the following lines in
/etc/my.cnf
:
[mysqld] socket=/path/to/socket [client] socket=/path/to/socket
Specify a --socket
option
on the command line to mysqld_safe and
when you run client programs.
Set the MYSQL_UNIX_PORT
environment
variable to the path of the Unix socket file.
Recompile MySQL from source to use a different default
Unix socket file location. Define the path to the file
with the MYSQL_UNIX_ADDR
option when you run CMake. See
Section 2.8.4, “MySQL Source-Configuration Options”.
You can test whether the new socket location works by attempting to connect to the server with this command:
shell> mysqladmin --socket=/path/to/socket version
If you have a problem with SELECT NOW()
returning values in UTC and not your local time, you have to
tell the server your current time zone. The same applies if
UNIX_TIMESTAMP()
returns the
wrong value. This should be done for the environment in which
the server runs; for example, in
mysqld_safe or
mysql.server. See
Section 4.9, “MySQL Program Environment Variables”.
You can set the time zone for the server with the
--timezone=
option to mysqld_safe. You can also set it
by setting the timezone_name
TZ
environment variable
before you start mysqld.
The permissible values for
--timezone
or
TZ
are system dependent. Consult your
operating system documentation to see what values are
acceptable.
For nonbinary strings (CHAR
,
VARCHAR
,
TEXT
), string searches use the
collation of the comparison operands. For binary strings
(BINARY
,
VARBINARY
,
BLOB
), comparisons use the
numeric values of the bytes in the operands; this means that
for alphabetic characters, comparisons will be case sensitive.
A comparison between a nonbinary string and binary string is treated as a comparison of binary strings.
Simple comparison operations (>=, >, =, <,
<=
, sorting, and grouping) are based on each
character's “sort value.” Characters with the
same sort value are treated as the same character. For
example, if e
and
é
have the same sort value in a
given collation, they compare as equal.
The default character set and collation are
utf8mb4
and
utf8mb4_0900_ai_ci
, so nonbinary string
comparisons are case insensitive by default. This means that
if you search with
, you get all column values that start with
col_name
LIKE
'a%'A
or a
. To make this
search case sensitive, make sure that one of the operands has
a case sensitive or binary collation. For example, if you are
comparing a column and a string that both have the
utf8mb4
character set, you can use the
COLLATE
operator to cause either operand to
have the utf8mb4_0900_as_cs
or
utf8mb4_bin
collation:
col_name
COLLATE utf8mb4_0900_as_cs LIKE 'a%'col_name
LIKE 'a%' COLLATE utf8mb4_0900_as_cscol_name
COLLATE utf8mb4_bin LIKE 'a%'col_name
LIKE 'a%' COLLATE utf8mb4_bin
If you want a column always to be treated in case-sensitive fashion, declare it with a case sensitive or binary collation. See Section 13.1.16, “CREATE TABLE Syntax”.
To cause a case-sensitive comparison of nonbinary strings to
be case insensitive, use COLLATE
to name a
case-insensitive collation. The strings in the following
example normally are case sensitive, but
COLLATE
changes the comparison to be case
insensitive:
mysql>SET NAMES 'utf8mb4';
mysql>SET @s1 = 'MySQL' COLLATE utf8mb4_bin,
@s2 = 'mysql' COLLATE utf8mb4_bin;
mysql>SELECT @s1 = @s2;
+-----------+ | @s1 = @s2 | +-----------+ | 0 | +-----------+ mysql>SELECT @s1 COLLATE utf8mb4_0900_ai_ci = @s2;
+--------------------------------------+ | @s1 COLLATE utf8mb4_0900_ai_ci = @s2 | +--------------------------------------+ | 1 | +--------------------------------------+
A binary string is case sensitive in comparisons. To compare
the string as case insensitive, convert it to a nonbinary
string and use COLLATE
to name a
case-insensitive collation:
mysql>SET @s = BINARY 'MySQL';
mysql>SELECT @s = 'mysql';
+--------------+ | @s = 'mysql' | +--------------+ | 0 | +--------------+ mysql>SELECT CONVERT(@s USING utf8mb4) COLLATE utf8mb4_0900_ai_ci = 'mysql';
+----------------------------------------------------------------+ | CONVERT(@s USING utf8mb4) COLLATE utf8mb4_0900_ai_ci = 'mysql' | +----------------------------------------------------------------+ | 1 | +----------------------------------------------------------------+
To determine whether a value will compare as a nonbinary or
binary string, use the
COLLATION()
function. This
example shows that VERSION()
returns a string that has a case-insensitive collation, so
comparisons are case insensitive:
mysql> SELECT COLLATION(VERSION());
+----------------------+
| COLLATION(VERSION()) |
+----------------------+
| utf8_general_ci |
+----------------------+
For binary strings, the collation value is
binary
, so comparisons will be case
sensitive. One context in which you will see
binary
is for compression and encryption
functions, which return binary strings as a general rule:
string:
mysql> SELECT COLLATION(ENCRYPT('x')), COLLATION(SHA1('x'));
+-------------------------+----------------------+
| COLLATION(ENCRYPT('x')) | COLLATION(SHA1('x')) |
+-------------------------+----------------------+
| binary | binary |
+-------------------------+----------------------+
To check the sort value of a string, the
WEIGHT_STRING()
may be helpful.
See Section 12.5, “String Functions”.
The format of a DATE
value is
'YYYY-MM-DD'
. According to standard SQL, no
other format is permitted. You should use this format in
UPDATE
expressions and in the
WHERE
clause of
SELECT
statements. For example:
SELECT * FROM t1 WHERE date >= '2003-05-05';
As a convenience, MySQL automatically converts a date to a
number if the date is used in a numeric context and vice
versa. MySQL also permits a “relaxed” string
format when updating and in a WHERE
clause
that compares a date to a DATE
,
DATETIME
, or
TIMESTAMP
column.
“Relaxed” format means that any punctuation
character may be used as the separator between parts. For
example, '2004-08-15'
and
'2004#08#15'
are equivalent. MySQL can also
convert a string containing no separators (such as
'20040815'
), provided it makes sense as a
date.
When you compare a DATE
,
TIME
,
DATETIME
, or
TIMESTAMP
to a constant string
with the <
, <=
,
=
, >=
,
>
, or BETWEEN
operators, MySQL normally converts the string to an internal
long integer for faster comparison (and also for a bit more
“relaxed” string checking). However, this
conversion is subject to the following exceptions:
For those exceptions, the comparison is done by converting the objects to strings and performing a string comparison.
To be on the safe side, assume that strings are compared as strings and use the appropriate string functions if you want to compare a temporal value to a string.
The special “zero” date
'0000-00-00'
can be stored and retrieved as
'0000-00-00'.
When a
'0000-00-00'
date is used through
Connector/ODBC, it is automatically converted to
NULL
because ODBC cannot handle that kind
of date.
Because MySQL performs the conversions just described, the
following statements work (assume that
idate
is a
DATE
column):
INSERT INTO t1 (idate) VALUES (19970505); INSERT INTO t1 (idate) VALUES ('19970505'); INSERT INTO t1 (idate) VALUES ('97-05-05'); INSERT INTO t1 (idate) VALUES ('1997.05.05'); INSERT INTO t1 (idate) VALUES ('1997 05 05'); INSERT INTO t1 (idate) VALUES ('0000-00-00'); SELECT idate FROM t1 WHERE idate >= '1997-05-05'; SELECT idate FROM t1 WHERE idate >= 19970505; SELECT MOD(idate,100) FROM t1 WHERE idate >= 19970505; SELECT idate FROM t1 WHERE idate >= '19970505';
However, the following statement does not work:
SELECT idate FROM t1 WHERE STRCMP(idate,'20030505')=0;
STRCMP()
is a string function,
so it converts idate
to a string in
'YYYY-MM-DD'
format and performs a string
comparison. It does not convert '20030505'
to the date '2003-05-05'
and perform a date
comparison.
If you enable the
ALLOW_INVALID_DATES
SQL
mode, MySQL permits you to store dates that are given only
limited checking: MySQL requires only that the day is in the
range from 1 to 31 and the month is in the range from 1 to 12.
This makes MySQL very convenient for Web applications where
you obtain year, month, and day in three different fields and
you want to store exactly what the user inserted (without date
validation).
MySQL permits you to store dates where the day or month and
day are zero. This is convenient if you want to store a
birthdate in a DATE
column and
you know only part of the date. To disallow zero month or day
parts in dates, enable the
NO_ZERO_IN_DATE
mode.
MySQL permits you to store a “zero” value of
'0000-00-00'
as a “dummy
date.” This is in some cases more convenient than using
NULL
values. If a date to be stored in a
DATE
column cannot be converted
to any reasonable value, MySQL stores
'0000-00-00'
. To disallow
'0000-00-00'
, enable the
NO_ZERO_DATE
mode.
To have MySQL check all dates and accept only legal dates
(unless overridden by IGNORE
), set the
sql_mode
system variable to
"NO_ZERO_IN_DATE,NO_ZERO_DATE"
.
The concept of the NULL
value is a common
source of confusion for newcomers to SQL, who often think that
NULL
is the same thing as an empty string
''
. This is not the case. For example, the
following statements are completely different:
mysql>INSERT INTO my_table (phone) VALUES (NULL);
mysql>INSERT INTO my_table (phone) VALUES ('');
Both statements insert a value into the
phone
column, but the first inserts a
NULL
value and the second inserts an empty
string. The meaning of the first can be regarded as
“phone number is not known” and the meaning of
the second can be regarded as “the person is known to
have no phone, and thus no phone number.”
To help with NULL
handling, you can use the
IS NULL
and IS
NOT NULL
operators and the
IFNULL()
function.
In SQL, the NULL
value is never true in
comparison to any other value, even NULL
.
An expression that contains NULL
always
produces a NULL
value unless otherwise
indicated in the documentation for the operators and functions
involved in the expression. All columns in the following
example return NULL
:
mysql> SELECT NULL, 1+NULL, CONCAT('Invisible',NULL);
To search for column values that are NULL
,
you cannot use an expr = NULL
test. The
following statement returns no rows, because expr =
NULL
is never true for any expression:
mysql> SELECT * FROM my_table WHERE phone = NULL;
To look for NULL
values, you must use the
IS NULL
test. The following
statements show how to find the NULL
phone
number and the empty phone number:
mysql>SELECT * FROM my_table WHERE phone IS NULL;
mysql>SELECT * FROM my_table WHERE phone = '';
See Section 3.3.4.6, “Working with NULL Values”, for additional information and examples.
You can add an index on a column that can have
NULL
values if you are using the
MyISAM
, InnoDB
, or
MEMORY
storage engine. Otherwise, you must
declare an indexed column NOT NULL
, and you
cannot insert NULL
into the column.
When reading data with
LOAD DATA
INFILE
, empty or missing columns are updated with
''
. To load a NULL
value
into a column, use \N
in the data file. The
literal word NULL
may also be used under
some circumstances. See Section 13.2.7, “LOAD DATA INFILE Syntax”.
When using DISTINCT
, GROUP
BY
, or ORDER BY
, all
NULL
values are regarded as equal.
When using ORDER BY
,
NULL
values are presented first, or last if
you specify DESC
to sort in descending
order.
Aggregate (summary) functions such as
COUNT()
,
MIN()
, and
SUM()
ignore
NULL
values. The exception to this is
COUNT(*)
, which counts rows and
not individual column values. For example, the following
statement produces two counts. The first is a count of the
number of rows in the table, and the second is a count of the
number of non-NULL
values in the
age
column:
mysql> SELECT COUNT(*), COUNT(age) FROM person;
For some data types, MySQL handles NULL
values specially. If you insert NULL
into a
TIMESTAMP
column, the current
date and time is inserted. If you insert
NULL
into an integer or floating-point
column that has the AUTO_INCREMENT
attribute, the next number in the sequence is inserted.
An alias can be used in a query select list to give a column a
different name. You can use the alias in GROUP
BY
, ORDER BY
, or
HAVING
clauses to refer to the column:
SELECT SQRT(a*b) AS root FROMtbl_name
GROUP BY root HAVING root > 0; SELECT id, COUNT(*) AS cnt FROMtbl_name
GROUP BY id HAVING cnt > 0; SELECT id AS 'Customer identity' FROMtbl_name
;
Standard SQL disallows references to column aliases in a
WHERE
clause. This restriction is imposed
because when the WHERE
clause is evaluated,
the column value may not yet have been determined. For
example, the following query is illegal:
SELECT id, COUNT(*) AS cnt FROM tbl_name
WHERE cnt > 0 GROUP BY id;
The WHERE
clause determines which rows
should be included in the GROUP BY
clause,
but it refers to the alias of a column value that is not known
until after the rows have been selected, and grouped by the
GROUP BY
.
In the select list of a query, a quoted column alias can be specified using identifier or string quoting characters:
SELECT 1 AS `one`, 2 AS 'two';
Elsewhere in the statement, quoted references to the alias
must use identifier quoting or the reference is treated as a
string literal. For example, this statement groups by the
values in column id
, referenced using the
alias `a`
:
SELECT id AS 'a', COUNT(*) AS cnt FROM tbl_name
GROUP BY `a`;
But this statement groups by the literal string
'a'
and will not work as expected:
SELECT id AS 'a', COUNT(*) AS cnt FROM tbl_name
GROUP BY 'a';
If you receive the following message when trying to perform a
ROLLBACK
, it
means that one or more of the tables you used in the
transaction do not support transactions:
Warning: Some non-transactional changed tables couldn't be rolled back
These nontransactional tables are not affected by the
ROLLBACK
statement.
If you were not deliberately mixing transactional and
nontransactional tables within the transaction, the most
likely cause for this message is that a table you thought was
transactional actually is not. This can happen if you try to
create a table using a transactional storage engine that is
not supported by your mysqld server (or
that was disabled with a startup option). If
mysqld does not support a storage engine,
it instead creates the table as a MyISAM
table, which is nontransactional.
You can check the storage engine for a table by using either of these statements:
SHOW TABLE STATUS LIKE 'tbl_name
'; SHOW CREATE TABLEtbl_name
;
See Section 13.7.5.36, “SHOW TABLE STATUS Syntax”, and Section 13.7.5.10, “SHOW CREATE TABLE Syntax”.
To check which storage engines your mysqld server supports, use this statement:
SHOW ENGINES;
See Section 13.7.5.16, “SHOW ENGINES Syntax” for full details.
If the total length of the
DELETE
statement for
related_table
is more than 1MB (the default
value of the
max_allowed_packet
system
variable), you should split it into smaller parts and execute
multiple DELETE
statements. You
probably get the fastest DELETE
by specifying only 100 to 1,000
related_column
values per statement if the
related_column
is indexed. If the
related_column
isn't indexed, the speed is
independent of the number of arguments in the
IN
clause.
If you have a complicated query that uses many tables but that returns no rows, you should use the following procedure to find out what is wrong:
Test the query with EXPLAIN
to check whether you can find something that is obviously
wrong. See Section 13.8.2, “EXPLAIN Syntax”.
Select only those columns that are used in the
WHERE
clause.
Remove one table at a time from the query until it returns
some rows. If the tables are large, it is a good idea to
use LIMIT 10
with the query.
Issue a SELECT
for the
column that should have matched a row against the table
that was last removed from the query.
If you are comparing FLOAT
or DOUBLE
columns with
numbers that have decimals, you cannot use equality
(=
) comparisons. This problem is common
in most computer languages because not all floating-point
values can be stored with exact precision. In some cases,
changing the FLOAT
to a
DOUBLE
fixes this. See
Section B.5.4.8, “Problems with Floating-Point Values”.
If you still cannot figure out what is wrong, create a
minimal test that can be run with mysql test <
query.sql
that shows your problems. You can
create a test file by dumping the tables with
mysqldump --quick db_name
tbl_name_1
...
tbl_name_n
>
query.sql. Open the file in an editor, remove
some insert lines (if there are more than needed to
demonstrate the problem), and add your
SELECT
statement at the end
of the file.
Verify that the test file demonstrates the problem by executing these commands:
shell>mysqladmin create test2
shell>mysql test2 < query.sql
Attach the test file to a bug report, which you can file using the instructions in Section 1.7, “How to Report Bugs or Problems”.
Floating-point numbers sometimes cause confusion because they
are approximate and not stored as exact values. A
floating-point value as written in an SQL statement may not be
the same as the value represented internally. Attempts to
treat floating-point values as exact in comparisons may lead
to problems. They are also subject to platform or
implementation dependencies. The
FLOAT
and
DOUBLE
data types are subject
to these issues. For DECIMAL
columns, MySQL performs operations with a precision of 65
decimal digits, which should solve most common inaccuracy
problems.
The following example uses
DOUBLE
to demonstrate how
calculations that are done using floating-point operations are
subject to floating-point error.
mysql>CREATE TABLE t1 (i INT, d1 DOUBLE, d2 DOUBLE);
mysql>INSERT INTO t1 VALUES (1, 101.40, 21.40), (1, -80.00, 0.00),
->(2, 0.00, 0.00), (2, -13.20, 0.00), (2, 59.60, 46.40),
->(2, 30.40, 30.40), (3, 37.00, 7.40), (3, -29.60, 0.00),
->(4, 60.00, 15.40), (4, -10.60, 0.00), (4, -34.00, 0.00),
->(5, 33.00, 0.00), (5, -25.80, 0.00), (5, 0.00, 7.20),
->(6, 0.00, 0.00), (6, -51.40, 0.00);
mysql>SELECT i, SUM(d1) AS a, SUM(d2) AS b
->FROM t1 GROUP BY i HAVING a <> b;
+------+-------+------+ | i | a | b | +------+-------+------+ | 1 | 21.4 | 21.4 | | 2 | 76.8 | 76.8 | | 3 | 7.4 | 7.4 | | 4 | 15.4 | 15.4 | | 5 | 7.2 | 7.2 | | 6 | -51.4 | 0 | +------+-------+------+
The result is correct. Although the first five records look
like they should not satisfy the comparison (the values of
a
and b
do not appear to
be different), they may do so because the difference between
the numbers shows up around the tenth decimal or so, depending
on factors such as computer architecture or the compiler
version or optimization level. For example, different CPUs may
evaluate floating-point numbers differently.
If columns d1
and d2
had
been defined as DECIMAL
rather
than DOUBLE
, the result of the
SELECT
query would have
contained only one row—the last one shown above.
The correct way to do floating-point number comparison is to first decide on an acceptable tolerance for differences between the numbers and then do the comparison against the tolerance value. For example, if we agree that floating-point numbers should be regarded the same if they are same within a precision of one in ten thousand (0.0001), the comparison should be written to find differences larger than the tolerance value:
mysql>SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1
->GROUP BY i HAVING ABS(a - b) > 0.0001;
+------+-------+------+ | i | a | b | +------+-------+------+ | 6 | -51.4 | 0 | +------+-------+------+ 1 row in set (0.00 sec)
Conversely, to get rows where the numbers are the same, the test should find differences within the tolerance value:
mysql>SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1
->GROUP BY i HAVING ABS(a - b) <= 0.0001;
+------+------+------+ | i | a | b | +------+------+------+ | 1 | 21.4 | 21.4 | | 2 | 76.8 | 76.8 | | 3 | 7.4 | 7.4 | | 4 | 15.4 | 15.4 | | 5 | 7.2 | 7.2 | +------+------+------+ 5 rows in set (0.03 sec)
Floating-point values are subject to platform or implementation dependencies. Suppose that you execute the following statements:
CREATE TABLE t1(c1 FLOAT(53,0), c2 FLOAT(53,0)); INSERT INTO t1 VALUES('1e+52','-1e+52'); SELECT * FROM t1;
On some platforms, the SELECT
statement
returns inf
and -inf
. On
others, it returns 0
and
-0
.
An implication of the preceding issues is that if you attempt to create a replication slave by dumping table contents with mysqldump on the master and reloading the dump file into the slave, tables containing floating-point columns might differ between the two hosts.
MySQL uses a cost-based optimizer to determine the best way to resolve a query. In many cases, MySQL can calculate the best possible query plan, but sometimes MySQL does not have enough information about the data at hand and has to make “educated” guesses about the data.
For the cases when MySQL does not do the "right" thing, tools that you have available to help MySQL are:
Use the EXPLAIN
statement to
get information about how MySQL processes a query. To use
it, just add the keyword
EXPLAIN
to the front of your
SELECT
statement:
mysql> EXPLAIN SELECT * FROM t1, t2 WHERE t1.i = t2.i;
EXPLAIN
is discussed in more
detail in Section 13.8.2, “EXPLAIN Syntax”.
Use ANALYZE TABLE
to update the
key distributions for the scanned table. See
Section 13.7.2.1, “ANALYZE TABLE Syntax”.
tbl_name
Use FORCE INDEX
for the scanned table to
tell MySQL that table scans are very expensive compared to
using the given index:
SELECT * FROM t1, t2 FORCE INDEX (index_for_column) WHERE t1.col_name=t2.col_name;
USE INDEX
and IGNORE
INDEX
may also be useful. See
Section 8.9.4, “Index Hints”.
Global and table-level STRAIGHT_JOIN
. See
Section 13.2.10, “SELECT Syntax”.
You can tune global or thread-specific system variables. For
example, start mysqld with the
--max-seeks-for-key=1000
option or use SET max_seeks_for_key=1000
to tell the optimizer to assume that no key scan causes more
than 1,000 key seeks. See
Section 5.1.5, “Server System Variables”.
If you get a duplicate-key error when using
ALTER TABLE
to change the
character set or collation of a character column, the cause is
either that the new column collation maps two keys to the same
value or that the table is corrupted. In the latter case, you
should run REPAIR TABLE
on the
table. REPAIR TABLE
works for
MyISAM
, ARCHIVE
, and
CSV
tables.
If you use ALTER TABLE
on a
transactional table or if you are using Windows,
ALTER TABLE
unlocks the table
if you had done a
LOCK
TABLE
on it. This is done because
InnoDB
and these operating systems cannot
drop a table that is in use.
Temporary tables created with
CREATE TEMPORARY
TABLE
have the following limitations:
TEMPORARY
tables are supported only by
the InnoDB
, MEMORY
,
MyISAM
, and MERGE
storage engines.
The SHOW TABLES
statement
does not list TEMPORARY
tables.
You cannot use RENAME TABLE
to rename a TEMPORARY
table. However,
you can use ALTER TABLE
instead:
ALTER TABLE old_name RENAME new_name;
You cannot refer to a TEMPORARY
table
more than once in the same query. For example, the
following does not work:
SELECT * FROM temp_table JOIN temp_table AS t2;
The statement produces this error:
ERROR 1137: Can't reopen table: 'temp_table'
You can work around this issue if your query permits use
of a common table expression (CTE) rather than a
TEMPORARY
table. For example, this
fails with the Can't reopen table
error:
CREATE TEMPORARY TABLE t SELECT 1 AS col_a, 2 AS col_b; SELECT * FROM t AS t1 JOIN t AS t2;
To avoid the error, use a
WITH
clause that defines a
CTE, rather than the TEMPORARY
table:
WITH cte AS (SELECT 1 AS col_a, 2 AS col_b) SELECT * FROM cte AS t1 JOIN cte AS t2;
The Can't reopen table error also occurs if you refer to a temporary table multiple times in a stored function under different aliases, even if the references occur in different statements within the function. It may occur for temporary tables created outside stored functions and referred to across multiple calling and callee functions.
There are known issues in using temporary tables with replication. See Section 18.4.1.24, “Replication and Temporary Tables”, for more information.
This section lists known issues in recent versions of MySQL.
For information about platform-specific issues, see the installation and porting instructions in Section 2.1, “General Installation Guidance”, and Section 28.5, “Debugging and Porting MySQL”.
The following problems are known:
Subquery optimization for IN
is not as
effective as for =
.
Even if you use lower_case_table_names=2
(which enables MySQL to remember the case used for databases
and table names), MySQL does not remember the case used for
database names for the function
DATABASE()
or within the
various logs (on case-insensitive systems).
Dropping a FOREIGN KEY
constraint does
not work in replication because the constraint may have
another name on the slave.
REPLACE
(and
LOAD DATA
with the
REPLACE
option) does not
trigger ON DELETE CASCADE
.
DISTINCT
with ORDER BY
does not work inside
GROUP_CONCAT()
if you do not
use all and only those columns that are in the
DISTINCT
list.
When inserting a big integer value (between 263 and 264−1) into a decimal or string column, it is inserted as a negative value because the number is evaluated in a signed integer context.
With statement-based binary logging, the master writes the executed queries to the binary log. This is a very fast, compact, and efficient logging method that works perfectly in most cases. However, it is possible for the data on the master and slave to become different if a query is designed in such a way that the data modification is nondeterministic (generally not a recommended practice, even outside of replication).
For example:
CREATE
TABLE ... SELECT
or
INSERT
... SELECT
statements that insert zero or
NULL
values into an
AUTO_INCREMENT
column.
DELETE
if you are
deleting rows from a table that has foreign keys with
ON DELETE CASCADE
properties.
REPLACE ...
SELECT
, INSERT IGNORE ...
SELECT
if you have duplicate key values in the
inserted data.
If and only if the preceding queries
have no ORDER BY
clause guaranteeing a
deterministic order.
For example, for
INSERT ...
SELECT
with no ORDER BY
, the
SELECT
may return rows in a
different order (which results in a row having different
ranks, hence getting a different number in the
AUTO_INCREMENT
column), depending on the
choices made by the optimizers on the master and slave.
A query is optimized differently on the master and slave only if:
The table is stored using a different storage engine on
the master than on the slave. (It is possible to use
different storage engines on the master and slave. For
example, you can use InnoDB
on the
master, but MyISAM
on the slave if
the slave has less available disk space.)
MySQL buffer sizes
(key_buffer_size
, and
so on) are different on the master and slave.
The master and slave run different MySQL versions, and the optimizer code differs between these versions.
This problem may also affect database restoration using mysqlbinlog|mysql.
The easiest way to avoid this problem is to add an
ORDER BY
clause to the aforementioned
nondeterministic queries to ensure that the rows are always
stored or modified in the same order. Using row-based or
mixed logging format also avoids the problem.
Log file names are based on the server host name if you do
not specify a file name with the startup option. To retain
the same log file names if you change your host name to
something else, you must explicitly use options such as
--log-bin=
.
See Section 5.1.4, “Server Command Options”. Alternatively, rename
the old files to reflect your host name change. If these are
binary logs, you must edit the binary log index file and fix
the binary log file names there as well. (The same is true
for the relay logs on a slave server.)
old_host_name
-bin
mysqlbinlog does not delete temporary
files left after a
LOAD DATA
INFILE
statement. See
Section 4.6.8, “mysqlbinlog — Utility for Processing Binary Log Files”.
RENAME
does not work with
TEMPORARY
tables or tables used in a
MERGE
table.
When using SET CHARACTER SET
, you cannot
use translated characters in database, table, and column
names.
You cannot use _
or %
with ESCAPE
in
LIKE ...
ESCAPE
.
The server uses only the first
max_sort_length
bytes when
comparing data values. This means that values cannot
reliably be used in GROUP BY
,
ORDER BY
, or DISTINCT
if they differ only after the first
max_sort_length
bytes. To
work around this, increase the variable value. The default
value of max_sort_length
is
1024 and can be changed at server startup time or at
runtime.
Numeric calculations are done with
BIGINT
or
DOUBLE
(both are normally 64
bits long). Which precision you get depends on the function.
The general rule is that bit functions are performed with
BIGINT
precision,
IF()
and
ELT()
with
BIGINT
or
DOUBLE
precision, and the
rest with DOUBLE
precision.
You should try to avoid using unsigned long long values if
they resolve to be larger than 63 bits (9223372036854775807)
for anything other than bit fields.
In MIN()
,
MAX()
, and other aggregate
functions, MySQL currently compares
ENUM
and
SET
columns by their string
value rather than by the string's relative position in the
set.
In an UPDATE
statement,
columns are updated from left to right. If you refer to an
updated column, you get the updated value instead of the
original value. For example, the following statement
increments KEY
by 2
,
not 1
:
mysql> UPDATE tbl_name
SET KEY=KEY+1,KEY=KEY+1;
You can refer to multiple temporary tables in the same query, but you cannot refer to any given temporary table more than once. For example, the following does not work:
mysql> SELECT * FROM temp_table, temp_table AS t2;
ERROR 1137: Can't reopen table: 'temp_table'
The optimizer may handle DISTINCT
differently when you are using “hidden” columns
in a join than when you are not. In a join, hidden columns
are counted as part of the result (even if they are not
shown), whereas in normal queries, hidden columns do not
participate in the DISTINCT
comparison.
An example of this is:
SELECT DISTINCT mp3id FROM band_downloads WHERE userid = 9 ORDER BY id DESC;
and
SELECT DISTINCT band_downloads.mp3id FROM band_downloads,band_mp3 WHERE band_downloads.userid = 9 AND band_mp3.id = band_downloads.mp3id ORDER BY band_downloads.id DESC;
In the second case, you may get two identical rows in the
result set (because the values in the hidden
id
column may differ).
Note that this happens only for queries that do not have the
ORDER BY
columns in the result.
If you execute a PROCEDURE
on a query
that returns an empty set, in some cases the
PROCEDURE
does not transform the columns.
Creation of a table of type MERGE
does
not check whether the underlying tables are compatible
types.
If you use ALTER TABLE
to add
a UNIQUE
index to a table used in a
MERGE
table and then add a normal index
on the MERGE
table, the key order is
different for the tables if there was an old,
non-UNIQUE
key in the table. This is
because ALTER TABLE
puts
UNIQUE
indexes before normal indexes to
be able to detect duplicate keys as early as possible.