Overview
Scenarios
Product Architecture
Instance Types
Compatibility Notes
Error Code | Error Description | Example |
1004 | Can't create the specified file due to an operating system error. | Can't create file '/var/lib/mysql/test/t1.frm' (errno: 13 - Permission denied) |
1005 | Can't create the specified table due to an operating system error. | Can't create table 'test.t1' (errno: 13 - Permission denied) |
1006 | Can't create the specified database due to an operating system error. | Can't create database 'new_db' (errno: 13 - Permission denied) |
1007 | Can't create the database because it already exists. | Can't create database 'existing_db'; database exists |
1008 | Can't drop the database because it doesn't exist. | Can't drop database 'non_existent_db'; database doesn't exist |
1009 | Error dropping the database because a file could not be deleted due to an operating system error. | Error dropping database (can't delete 'db.opt', errno: 13 - Permission denied) |
1010 | Error dropping the database because a directory could not be removed due to an operating system error. | Error dropping database (can't rmdir './old_db', errno: 17 - File exists) |
1011 | Error on delete of a file due to an operating system error. | Error on delete of 't1.MYI' (errno: 13 - Permission denied) |
1012 | Can't read record in system table | - |
1013 | Can't get the status of a file due to an operating system error. | Can't get status of './test/t1.frm' (errno: 2 - No such file or directory) |
1014 | Can't get the current working directory due to an operating system error. | Can't get working directory (errno: 13 - Permission denied) |
1015 | Can't lock a file due to an operating system error. | Can't lock file (errno: 11 - Resource temporarily unavailable) |
1016 | Can't open the specified file due to an operating system error. | Can't open file: './test/t1.frm' (errno: 2 - No such file or directory) |
1017 | Can't find the specified file due to an operating system error. | Can't find file: './test/t1.MYI' (errno: 2 - No such file or directory) |
1018 | Can't read the contents of a directory due to an operating system error. | Can't read dir of './test/' (errno: 13 - Permission denied) |
1019 | Can't change the current directory due to an operating system error. | Can't change dir to '/nonexistent_path/' (errno: 2 - No such file or directory) |
1020 | A record has changed in the specified table since it was last read. | Record has changed since last read in table 'products' |
1021 | The disk is full; waiting for space to be freed. | Disk full ('/tmp/#sql_1_0.MAI'); waiting for someone to free some space... (errno: 28 - No space left on device) |
1022 | Can't write to the table due to a duplicate key. | Can't write; duplicate key in table 'users' |
1023 | Error closing a file due to an operating system error. | Error on close of './test/t1.frm' (errno: 9 - Bad file descriptor) |
1024 | Error reading a file due to an operating system error. | Error reading file './test/t1.MYD' (errno: 5 - Input/output error) |
1025 | Error renaming a file or directory due to an operating system error. | Error on rename of './test/t1.frm' to './test/t2.frm' (errno: 13 - Permission denied) |
1026 | Error writing to a file due to an operating system error. | Error writing file '/var/lib/mysql/my_db/t1.MYD' (errno: 28 - No space left on device) |
1027 | The specified table is locked against change. | 'users' is locked against change |
1028 | Sort aborted | - |
1029 | The specified view does not exist for the given user or context. | View 'sales_summary' doesn't exist for 'web_user@localhost' |
1030 | An error was returned from the storage engine. | Got error 127 - 'Record not found' from storage engine |
1031 | The storage engine for the specified table does not support this option. | Table storage engine for 'archive_logs' doesn't have this option |
1032 | Can't find the specified record in the table. | Can't find record in 'products' |
1033 | The specified file contains incorrect information. | Incorrect information in file: 'users.frm' |
1034 | The key file for the specified table is incorrect; try to repair it. | Incorrect key file for table 'orders.MYI'; try to repair it |
1035 | The key file for the specified table is from an old version; repair it. | Old key file for table 'customers'; repair it! |
1036 | The specified table is read-only. | Table 'system_config' is read only |
1037 | Out of memory; restart the server and try again. The operation required a specific amount of memory. | Out of memory; restart server and try again (needed 262144 bytes) |
1038 | Out of sort memory, consider increasing server sort buffer size | - |
1039 | An unexpected end-of-file was found when reading a file. | Unexpected EOF found when reading file 'corrupt_table.MYI' (errno: 5 - Input/output error) |
1040 | Too many connections | - |
1041 | Out of memory; check if sqlengine or some other process uses all available memory; if not, you may have to use 'ulimit' to allow sqlengine to use more memory or you can add more swap space | - |
1042 | Can't get hostname for your address | - |
1043 | Bad handshake | - |
1044 | Access denied for the user to the specified database. | Access denied for user 'web_user'@'localhost' to database 'admin_db' |
1045 | Access denied for the user, indicating whether a password was used in the attempt. | Access denied for user 'root'@'192.168.1.10' (using password: YES) |
1046 | No database selected | - |
1047 | Unknown command | - |
1048 | The specified column cannot be null. | Column 'username' cannot be null |
1049 | Unknown database. | Unknown database 'non_existent_db' |
1050 | The specified table already exists. | Table 'users' already exists |
1051 | Unknown table. | Unknown table 'products_old' |
1052 | The specified column name is ambiguous in the given context. | Column 'id' in 'from clause' is ambiguous |
1053 | Server shutdown in progress | - |
1054 | An unknown column was referenced in a specific clause. | Unknown column 'user_email' in 'where clause' |
1055 | A column in the SELECT list is not in the GROUP BY clause and is not used in an aggregate function. | 'employees.name' isn't in GROUP BY |
1056 | Cannot perform a GROUP BY on the specified expression or column. | Can't group on 'user_data_blob' |
1057 | Statement has sum functions and columns in same statement | - |
1058 | Column count doesn't match value count | - |
1059 | The identifier name is too long. | Identifier name 'a_very_very_very_long_table_name_that_exceeds_the_limit' is too long |
1060 | Duplicate column name. | Duplicate column name 'id' |
1061 | Duplicate key name. | Duplicate key name 'idx_username' |
1062 | A duplicate entry was found for a unique or primary key. | Duplicate entry 'test@example.com' for key 2 |
1063 | The column specifier for the specified column is incorrect. | Incorrect column specifier for column 'creation_date' |
1064 | You have a syntax error near a specific part of your query at a given line. | You have an error in your SQL syntax; check the manual... near '' at line 1 |
1065 | Query was empty | - |
1066 | The specified table or alias name is not unique in the query. | Not unique table/alias: 't1' |
1067 | An invalid default value was specified for the column. | Invalid default value for 'status_code' |
1068 | Multiple primary key defined | - |
1069 | Too many keys were specified; a maximum number of keys are allowed. | Too many keys specified; max 64 keys allowed |
1070 | Too many key parts were specified; a maximum number of parts are allowed. | Too many key parts specified; max 16 parts allowed |
1071 | The specified key was too long; the maximum key length has been exceeded. | Specified key was too long; max key length is 3072 bytes |
1072 | The specified key column does not exist in the table. | Key column 'user_email' doesn't exist in table |
1073 | A BLOB column cannot be used in a key specification with the current table type. | BLOB column 'user_profile' can't be used in key specification with the used table type |
1074 | The specified column length is too large; use BLOB or TEXT instead. | Column length too big for column 'long_string' (max = 65535); use BLOB or TEXT instead |
1075 | Incorrect table definition; there can be only one auto column and it must be defined as a key | - |
1076 | Server is ready for connections on a specific socket and port. | mysqld: ready for connections. Version: '8.0.28' socket: '/tmp/mysql.sock' port: 3306 |
1077 | Server is performing a normal shutdown. | mysqld: Normal shutdown |
1078 | Server received a signal and is aborting. | mysqld: Got signal 15. Aborting! |
1079 | Server shutdown is complete. | mysqld: Shutdown complete |
1080 | Forcing the closure of a specific user's thread. | mysqld: Forcing close of thread 123 user: 'batch_user' |
1081 | Can't create IP socket | - |
1082 | The specified table has no index like the one used in CREATE INDEX; recreate the table. | Table 'corrupted_table' has no index like the one used in CREATE INDEX; recreate the table |
1083 | Field separator argument is not what is expected; check the manual | - |
1084 | You can't use fixed rowlength with BLOBs; please use 'fields terminated by' | - |
1085 | The specified file must be in the database directory or be readable by all. | The file '/tmp/data.csv' must be in the database directory or be readable by all |
1086 | The specified file already exists. | File '/var/lib/mysql/my_db/new_table.frm' already exists |
1087 | A summary of records processed, deleted, skipped, and warnings generated. | Records: 100 Deleted: 5 Skipped: 2 Warnings: 3 |
1088 | A summary of records processed and duplicates found. | Records: 1000 Duplicates: 15 |
1089 | 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 | - |
1090 | You can't delete all columns with ALTER TABLE; use DROP TABLE instead | - |
1091 | Cannot drop the specified column or key; check that it exists. | Can't DROP 'non_existent_column'; check that column/key exists |
1092 | A summary of records processed, duplicates found, and warnings generated. | Records: 500 Duplicates: 10 Warnings: 5 |
1093 | You cannot specify the target table for an UPDATE in the FROM clause. | You can't specify target table 'employees' for update in FROM clause |
1094 | Unknown thread id. | Unknown thread id: 99999 |
1095 | You are not the owner of the specified thread. | You are not owner of thread 123 |
1096 | No tables used | - |
1097 | Too many string values were provided for the specified SET column. | Too many strings for column 'options' and SET |
1098 | Cannot generate a unique log filename using the specified pattern. | Can't generate a unique log-filename /var/log/mysql/binlog.(1-999) |
1099 | The specified table was locked with a READ lock and cannot be updated. | Table 'products' was locked with a READ lock and can't be updated |
1100 | The specified table was not locked with LOCK TABLES. | Table 'sessions' was not locked with LOCK TABLES |
Error Code | Error Description | Example |
1101 | A BLOB, TEXT, GEOMETRY, or JSON column can't have a default value. | BLOB, TEXT, GEOMETRY or JSON column 'user_bio' can't have a default value |
1102 | Incorrect database name. | Incorrect database name 'my-db-with-invalid-chars!' |
1103 | Incorrect table name. | Incorrect table name '123_starts_with_number' |
1104 | 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 | - |
1105 | Unknown error | - |
1106 | Unknown procedure. | Unknown procedure 'calculate_yearly_bonus' |
1107 | Incorrect parameter count for the specified procedure. | Incorrect parameter count to procedure 'update_inventory' |
1108 | Incorrect parameters for the specified procedure. | Incorrect parameters to procedure 'register_user' |
1109 | Unknown table in a specific context. | Unknown table 'products' in 'foreign key constraint' |
1110 | A column was specified twice. | Column 'user_id' specified twice |
1111 | Invalid use of group function | - |
1112 | The table uses an extension that doesn't exist in this MySQL version. | Table 'legacy_data' uses an extension that doesn't exist in this MySQL version |
1113 | A table must have at least 1 column | - |
1114 | The table is full. | The table 'log_data' is full |
1115 | Unknown character set. | Unknown character set: 'utf8mb3' |
1116 | Too many tables were used in a join; MySQL has a limit. | Too many tables; MySQL can only use 61 tables in a join |
1117 | Too many columns | - |
1118 | Row size is too large. The maximum row size for the used table type has been exceeded. You may need to change some columns to TEXT or BLOBs. | Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead... |
1119 | Thread stack overrun. Use the 'thread_stack' setting to specify a bigger stack if needed. | Thread stack overrun: Used: 262144 of a 262144 stack. Use 'sqlengine --thread_stack=524288' to specify a bigger stack if needed. |
1120 | Cross dependency found in OUTER JOIN; examine your ON conditions | - |
1121 | The table handler doesn't support NULL in the given index. Please change the column to be NOT NULL or use another handler. | Table handler doesn't support NULL in given index. Please change column 'category_id' to be NOT NULL or use another handler. |
1122 | Can't load function. | Can't load function 'my_custom_udf' |
1123 | Can't initialize function due to a specific reason. | Can't initialize function 'udf_json_extract'; library is not thread-safe |
1124 | No paths allowed for shared library | - |
1125 | The function already exists. | Function 'calculate_distance' already exists |
1126 | Can't open shared library. | Can't open shared library 'udf_library.so' (errno: 2 No such file or directory) |
1127 | Can't find a symbol in the library. | Can't find symbol 'my_function_init' in library |
1128 | The function is not defined. | Function 'non_existent_func' is not defined |
1129 | The host is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'. | Host 'bad-client.example.com' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts' |
1130 | The host is not allowed to connect to this MySQL server. | Host 'unauthorized.example.com' is not allowed to connect to this MySQL server |
1131 | You are using MySQL as an anonymous user and anonymous users are not allowed to change passwords | - |
1132 | You must have privileges to update tables in the mysql database to be able to change passwords for others | - |
1133 | Can't find any matching row in the user table | - |
1134 | A summary of rows matched, changed, and warnings. | Rows matched: 1 Changed: 1 Warnings: 0 |
1135 | Can't create a new thread. If you are not out of available memory, consult the manual for a possible OS-dependent bug. | Can't create a new thread (errno 11); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug |
1136 | The column count doesn't match the value count at a specific row. | Column count doesn't match value count at row 521 |
1137 | Can't reopen table. | Can't reopen table: 'temp_results' |
1138 | Invalid use of NULL value | - |
1139 | An error was returned from the regular expression engine. | Got error 'empty range in char class' from regexp |
1140 | Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause | - |
1141 | There is no such grant defined for the user on the host. | There is no such grant defined for user 'temp_user' on host 'localhost' |
1142 | A specific command was denied to the user for the specified table. | UPDATE command denied to user 'web_user'@'10.0.1.5' for table 'config' |
1143 | A specific command was denied to the user for a column in a table. | SELECT command denied to user 'guest'@'%' for column 'salary' in table 'employees' |
1144 | Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used | - |
1145 | The host or user argument to GRANT is too long | - |
1146 | The specified table doesn't exist in the database. | Table 'production_db.non_existent_table' doesn't exist |
1147 | There is no such grant defined for the user on the host for the specified table. | There is no such grant defined for user 'readonly' on host '%' on table 'sensitive_data' |
1148 | The used command is not allowed with this MySQL version | - |
1149 | You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use | - |
1150 | The delayed insert thread couldn't get the requested lock for the table. | Delayed insert thread couldn't get requested lock for table 'event_log' |
1151 | Too many delayed threads in use | - |
1152 | A connection was aborted. | Aborted connection 123 to db: 'production_db' user: 'batch_user' (Got timeout reading communication packets) |
1153 | Got a packet bigger than 'max_allowed_packet' bytes | - |
1154 | Got a read error from the connection pipe | - |
1155 | Got an error from fcntl() | - |
1156 | Got packets out of order | - |
1157 | Couldn't uncompress communication packet | - |
1158 | Got an error reading communication packets | - |
1159 | Got timeout reading communication packets | - |
1160 | Got an error writing communication packets | - |
1161 | Got timeout writing communication packets | - |
1162 | Result string is longer than 'max_allowed_packet' bytes | - |
1163 | The used table type doesn't support BLOB/TEXT columns | - |
1164 | The used table type doesn't support AUTO_INCREMENT columns | - |
1165 | INSERT DELAYED can't be used with the table because it is locked with LOCK TABLES. | INSERT DELAYED can't be used with table 'job_queue' because it is locked with LOCK TABLES |
1166 | Incorrect column name. | Incorrect column name 'user-name' |
1167 | The used storage engine can't index the specified column. | The used storage engine can't index column 'full_address' |
1168 | Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist | - |
1169 | Can't write to the table because of a unique constraint. | Can't write, because of unique constraint, to table 'users' |
1170 | A BLOB/TEXT column was used in a key specification without a key length. | BLOB/TEXT column 'article_body' used in key specification without a key length |
1171 | All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead | - |
1172 | Result consisted of more than one row | - |
1173 | This table type requires a primary key | - |
1174 | This version of MySQL is not compiled with RAID support | - |
1175 | You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. | You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. To disable safe mode... |
1176 | The specified key doesn't exist in the table. | Key 'idx_user_email' doesn't exist in table 'accounts' |
1177 | Can't open table | - |
1178 | The storage engine for the table doesn't support a specific feature. | The storage engine for the table doesn't support 'partitioning' |
1179 | You are not allowed to execute this command in a transaction | - |
1180 | An error occurred during a COMMIT operation. | Got error 145 - 'Table is marked as crashed and should be repaired' during COMMIT |
1181 | An error occurred during a ROLLBACK operation. | Got error 1205 - 'Lock wait timeout exceeded' during ROLLBACK |
1182 | An error occurred during FLUSH_LOGS. | Got error 13 during FLUSH_LOGS |
1183 | An error occurred during CHECKPOINT. | Got error 145 during CHECKPOINT |
1184 | A connection was aborted. | Aborted connection 8 to db: 'analytics' user: 'etl_user' host: 'batch-worker-01.internal' (Got timeout reading communication packets) |
1185 | The storage engine for the table does not support binary table dump | - |
1186 | Binlog closed, cannot RESET MASTER | - |
1187 | Failed to rebuild the index of a dumped table. | Failed rebuilding the index of dumped table 'sales_archive' |
1188 | An error was received from the master server. | Error from master: 'Could not find first log file name in binary log index file' |
1189 | Net error reading from master | - |
1190 | Net error writing to master | - |
1191 | Can't find FULLTEXT index matching the column list | - |
1192 | Can't execute the given command because you have active locked tables or an active transaction | - |
1193 | Unknown system variable. | Unknown system variable 'max_join_sizee' |
1194 | The table is marked as crashed and should be repaired. | Table 'sessions' is marked as crashed and should be repaired |
1195 | The table is marked as crashed and the last repair attempt failed. | Table 'user_activity' is marked as crashed and last (automatic?) repair failed |
1196 | Some non-transactional changed tables couldn't be rolled back | - |
1197 | Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this sqlengine variable and try again | - |
1198 | This operation cannot be performed with a running slave; run STOP SLAVE first | - |
1199 | This operation requires a running slave; configure slave and do START SLAVE | - |
1200 | The server is not configured as slave; fix in config file or with CHANGE MASTER TO | - |
Error Code | Error Description | Example |
1201 | Could not initialize master info structure; more error messages can be found in the MySQL error log | - |
1202 | Could not create slave thread; check system resources | - |
1203 | A user already has more than 'max_user_connections' active connections. | User 'web_user' already has more than 'max_user_connections' active connections |
1204 | You may only use constant expressions with SET | - |
1205 | Lock wait timeout exceeded; try restarting transaction | - |
1206 | The total number of locks exceeds the lock table size | - |
1207 | Update locks cannot be acquired during a READ UNCOMMITTED transaction | - |
1208 | DROP DATABASE not allowed while thread is holding global read lock | - |
1209 | CREATE DATABASE not allowed while thread is holding global read lock | - |
1210 | Incorrect arguments for the specified function or operation. | Incorrect arguments to COUNT |
1211 | The specified user is not allowed to create new users. | 'app_user'@'localhost' is not allowed to create new users |
1212 | Incorrect table definition; all MERGE tables must be in the same database | - |
1213 | Deadlock found when trying to get lock; try restarting transaction | - |
1214 | The used table type doesn't support FULLTEXT indexes | - |
1215 | Cannot add foreign key constraint | - |
1216 | Cannot add or update a child row: a foreign key constraint fails | - |
1217 | Cannot delete or update a parent row: a foreign key constraint fails | - |
1218 | An error occurred while connecting to the master. | Error connecting to master: Lost connection to MySQL server at 'reading initial communication packet', system error: 111 |
1219 | An error occurred while running a query on the master. | Error running query on master: Query execution was interrupted |
1220 | An error occurred when executing a specific command. | Error when executing command COM_BINLOG_DUMP: Master has purged binary logs containing GTIDs that the slave requires. |
1221 | Incorrect usage of two specified keywords or clauses. | Incorrect usage of UNION and ORDER BY |
1222 | The used SELECT statements have a different number of columns | - |
1223 | Can't execute the query because you have a conflicting read lock | - |
1224 | Mixing of transactional and non-transactional tables is disabled | - |
1225 | An option was used twice in the statement. | Option 'ENCRYPTION' used twice in statement |
1226 | A user has exceeded a specific resource limit. | User 'batch_user' has exceeded the 'MAX_QUERIES_PER_HOUR' resource (current value: 1000) |
1227 | Access denied; you need at least one of the specified privileges for this operation. | Access denied; you need (at least one of) the SUPER privilege(s) for this operation |
1228 | The specified variable is a SESSION variable and cannot be used with SET GLOBAL. | Variable 'warning_count' is a SESSION variable and can't be used with SET GLOBAL |
1229 | The specified variable is a GLOBAL variable and should be set with SET GLOBAL. | Variable 'max_connections' is a GLOBAL variable and should be set with SET GLOBAL |
1230 | The specified variable does not have a default value. | Variable 'my_custom_var' doesn't have a default value |
1231 | A variable cannot be set to the specified value. | Variable 'sql_mode' can't be set to the value of 'INVALID_MODE' |
1232 | An incorrect argument type was provided for the specified variable. | Incorrect argument type to variable 'max_execution_time' |
1233 | The specified variable can only be set, not read. | Variable 'password' can only be set, not read |
1234 | Incorrect usage or placement of a specific keyword or clause. | Incorrect usage/placement of 'LIMIT' |
1235 | This version of the server does not yet support the specified feature. | This version of MySQL doesn't yet support 'CHECK Constraints' |
1236 | A fatal error was received from the master when reading data from the binary log. | Got fatal error 1236 from master when reading data from binary log: 'log event entry exceeded max_allowed_packet' |
1237 | Slave SQL thread ignored the query because of replicate-*-table rules | - |
1238 | The specified variable is of a certain type (e.g., read-only). | Variable 'version' is a read-only variable |
1239 | The foreign key definition for the specified table is incorrect for a given reason. | Incorrect foreign key definition for 'orders': Cannot find an index in the referenced table 'customers' that matches the columns |
1240 | Key reference and table reference don't match | - |
1241 | The operand should contain a specific number of columns. | Operand should contain 2 column(s) |
1242 | Subquery returns more than 1 row | - |
1243 | An unknown prepared statement handler was given to a command. | Unknown prepared statement handler (stmt1) given to EXECUTE |
1244 | Help database is corrupt or does not exist | - |
1245 | Cyclic reference on subqueries | - |
1246 | A column is being converted from one character set/collation to another. | Converting column 'name' from latin1 to utf8mb4 |
1247 | The specified reference is not supported for a given reason. | Reference 'outer_alias.column' not supported (forward reference) |
1248 | Every derived table must have its own alias | - |
1249 | A select statement was reduced during optimization. | Select 2 was reduced during optimization |
1250 | A table from a SELECT statement cannot be used in a specific clause. | Table 't1' from one of the SELECTs cannot be used in 'field list' |
1251 | Client does not support authentication protocol requested by server; consider upgrading MySQL client | - |
1252 | All parts of a SPATIAL index must be NOT NULL | - |
1253 | The specified collation is not valid for the given character set. | COLLATION 'latin1_swedish_ci' is not valid for CHARACTER SET 'utf8mb4' |
1254 | Slave is already running | - |
1255 | Slave already has been stopped | - |
1256 | Uncompressed data size is too large; there is a maximum size limit. | Uncompressed data size too large; the maximum size is 16777216 (probably, length of uncompressed data was corrupted) |
1257 | ZLIB: Not enough memory | - |
1258 | ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) | - |
1259 | ZLIB: Input data corrupted | - |
1260 | A row was cut by GROUP_CONCAT(). | Row 1 was cut by GROUP_CONCAT() |
1261 | A specific row does not contain data for all columns. | Row 5 doesn't contain data for all columns |
1262 | A specific row was truncated because it contained more data than there were input columns. | Row 10 was truncated; it contained more data than there were input columns |
1263 | A column was set to its default value because NULL was supplied to a NOT NULL column at a specific row. | Column set to default value; NULL supplied to NOT NULL column 'status' at row 3 |
1264 | An out-of-range value was provided for a specific column at a specific row. | Out of range value for column 'age' at row 1 |
1265 | Data was truncated for a specific column at a specific row. | Data truncated for column 'name' at row 2 |
1266 | A specific storage engine is being used for a table. | Using storage engine MyISAM for table 'legacy_table' |
1267 | An illegal mix of collations was found for a specific operation. | Illegal mix of collations (utf8mb4_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation 'like' |
1268 | Cannot drop one or more of the requested users | - |
1269 | Can't revoke all privileges for one or more of the requested users | - |
1270 | An illegal mix of collations was found for a specific operation. | Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT), (utf8mb4_general_ci,IMPLICIT), (latin1_swedish_ci,IMPLICIT) for operation 'union' |
1271 | An illegal mix of collations was found for a specific operation. | Illegal mix of collations for operation 'concat' |
1272 | The specified variable is not a variable component and cannot be used with dot notation. | Variable 'version' is not a variable component (can't be used as XXXX.variable_name) |
1273 | Unknown collation. | Unknown collation: 'utf8_turkish_ci' |
1274 | 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 | - |
1275 | The server is running in secure-auth mode, but a user has a password in the old format. The password should be changed to the new format. | Server is running in --secure-auth mode, but 'legacy_user'@'localhost' has a password in the old format; please change the password to the new format |
1276 | A field or reference from one SELECT statement was resolved in another SELECT statement. | Field or reference 'db1.t1.col1' of SELECT #2 was resolved in SELECT #1 |
1277 | Incorrect parameter or combination of parameters for START SLAVE UNTIL | - |
1278 | It is recommended to use --skip-replica-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's sqlengine restart | - |
1279 | SQL thread is not to be started so UNTIL options are ignored | - |
1280 | Incorrect index name. | Incorrect index name 'index-with-invalid-chars!' |
1281 | Incorrect catalog name. | Incorrect catalog name 'invalid_catalog' |
1282 | The query cache failed to set the requested size; the new size is reported. | Query cache failed to set size 16777216; new query cache size is 8388608 |
1283 | The specified column cannot be part of a FULLTEXT index. | Column 'id' cannot be part of FULLTEXT index |
1284 | Unknown key cache. | Unknown key cache 'hot_cache' |
1285 | MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work | - |
1286 | Unknown storage engine. | Unknown storage engine 'MyRocksDB' |
1287 | A feature is deprecated and will be removed in a future release. An alternative should be used instead. | 'PASSWORD()' is deprecated and will be removed in a future release. Please use 'CREATE USER' or 'ALTER USER' instead |
1288 | The target table of a specific operation is not updatable. | The target table 'v_sales' of the UPDATE is not updatable |
1289 | A feature is disabled; you need a version of the server built with a specific option to enable it. | The 'partitioning' feature is disabled; you need MySQL built with 'partitioning' to have it working |
1290 | The server is running with a specific option that prevents the execution of this statement. | The MySQL server is running with the --read-only option so it cannot execute this statement |
1291 | A column has a duplicated value in a specific context (e.g., an ENUM or SET definition). | Column 'status' has duplicated value 'active' in ENUM |
1292 | An incorrect value of a certain type was truncated. | Truncated incorrect DOUBLE value: 'abc' |
1293 | Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause | - |
1294 | The ON UPDATE clause for the specified column is invalid. | Invalid ON UPDATE clause for 'created_at' column |
1295 | This command is not supported in the prepared statement protocol yet | - |
1296 | An error was received from a specific component or engine. | Got error 145 'Table is marked as crashed' from NDB |
1297 | A temporary error was received from a specific component or engine. | Got temporary error 1205 'Lock wait timeout exceeded' from InnoDB |
1298 | Unknown or incorrect time zone. | Unknown or incorrect time zone: 'America/New_Yorkk' |
1299 | An invalid TIMESTAMP value was found in a specific column at a specific row. | Invalid TIMESTAMP value in column 'update_time' at row 5 |
1300 | An invalid character string was found for a specific character set. | Invalid utf8mb4 character string: '\\xF5' |
Error Code | Error Description | Example |
1301 | The result of a function was larger than the max_allowed_packet size and has been truncated. | Result of GROUP_CONCAT() was larger than max_allowed_packet (1048576) - truncated |
1302 | There are conflicting declarations for a stored routine parameter or variable. | Conflicting declarations: 'PARAMETER p_name' and 'VARIABLE p_name' |
1303 | Cannot create a specific object type from within another stored routine. | Can't create a TRIGGER from within another stored routine |
1304 | The specified stored routine or object already exists. | PROCEDURE calculate_salary already exists |
1305 | The specified stored routine or object does not exist. | FUNCTION get_user_name does not exist |
1306 | Failed to drop the specified stored routine or object. | Failed to DROP TRIGGER update_log |
1307 | Failed to create the specified stored routine or object. | Failed to CREATE FUNCTION new_func |
1308 | A control flow statement (like LEAVE or ITERATE) has no matching label. | LEAVE with no matching label: main_loop |
1309 | A label is being redefined within the same scope. | Redefining label my_loop |
1310 | An end-label was found without a matching begin-label. | End-label my_loop without match |
1311 | A reference was made to an uninitialized variable. | Referring to uninitialized variable user_count |
1312 | A procedure cannot return a result set in the current context. | PROCEDURE update_inventory can't return a result set in the given context |
1313 | RETURN is only allowed in a FUNCTION | - |
1314 | A specific statement or clause is not allowed in stored procedures. | LOAD DATA INFILE is not allowed in stored procedures |
1315 | The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored. | - |
1316 | The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN. | - |
1317 | Query execution was interrupted | - |
1318 | Incorrect number of arguments for a function or procedure; the expected and actual counts differ. | Incorrect number of arguments for PROCEDURE add_user; expected 3, got 2 |
1319 | An undefined condition was referenced. | Undefined CONDITION: not_found_error |
1320 | No RETURN statement was found in the function. | No RETURN found in FUNCTION calculate_tax |
1321 | A function's execution path ended without a RETURN statement. | FUNCTION get_status ended without RETURN |
1322 | Cursor statement must be a SELECT | - |
1323 | Cursor SELECT must not have INTO | - |
1324 | An undefined cursor was referenced. | Undefined CURSOR: user_cursor |
1325 | Cursor is already open | - |
1326 | Cursor is not open | - |
1327 | An undeclared variable was referenced. | Undeclared variable: total_count |
1328 | Incorrect number of FETCH variables | - |
1329 | No data - zero rows fetched, selected, or processed | - |
1330 | A duplicate parameter name was found in a stored routine definition. | Duplicate parameter: p_user_id |
1331 | A duplicate variable name was declared in a stored routine. | Duplicate variable: v_counter |
1332 | A duplicate condition name was declared in a stored routine. | Duplicate condition: sql_error_handler |
1333 | A duplicate cursor name was declared in a stored routine. | Duplicate cursor: product_cursor |
1334 | Failed to alter the specified stored routine or object. | Failed to ALTER PROCEDURE update_user_profile |
1335 | Subquery value not supported | - |
1336 | A specific statement is not allowed in a stored function or trigger. | COMMIT is not allowed in stored function or trigger |
1337 | Variable or condition declaration after cursor or handler declaration | - |
1338 | Cursor declaration after handler declaration | - |
1339 | Case not found for CASE statement | - |
1340 | The configuration file is too big. | Configuration file 'my.cnf' is too big |
1341 | The file has a malformed file type header. | Malformed file type header in file 'corrupted_table.frm' |
1342 | An unexpected end of file occurred while parsing a comment. | Unexpected end of file while parsing comment '/* unclosed comment' |
1343 | An error occurred while parsing a parameter on a specific line. | Error while parsing parameter 'max_connections' (line: 'max_connections=abc') |
1344 | An unexpected end of file occurred while skipping an unknown parameter. | Unexpected end of file while skipping unknown parameter 'unknown_param' |
1345 | EXPLAIN/SHOW can not be issued; lacking privileges for underlying table | - |
1346 | A file has an unknown type in its header. | File 'table.xyz' has unknown type 'XYZ' in its header |
1347 | The specified object is not of the expected type. | 'db1.my_obj' is not VIEW |
1348 | The specified column is not updatable. | Column 'total_sales' is not updatable |
1349 | View's SELECT contains a subquery in the FROM clause | - |
1350 | The view's SELECT statement contains a specific clause that is not allowed. | View's SELECT contains a 'INTO' clause |
1351 | View's SELECT contains a variable or parameter | - |
1352 | The view's SELECT statement refers to a temporary table. | View's SELECT refers to a temporary table 'temp_results' |
1353 | In definition of view, derived table or common table expression, SELECT list and column names list have different column counts | - |
1354 | View merge algorithm can't be used here for now (assumed undefined algorithm) | - |
1355 | View being updated does not have complete key of underlying table in it | - |
1356 | A view references invalid objects, or the definer/invoker lacks the necessary rights to use them. | View 'sales.monthly_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them |
1357 | Cannot drop or alter a specific object type from within another stored routine. | Can't drop or alter a TABLE from within another stored routine |
1358 | GOTO is not allowed in a stored procedure handler | - |
1359 | Trigger already exists | - |
1360 | Trigger does not exist | - |
1361 | The table associated with a trigger is a view or a temporary table. | Trigger's 'subject table' is view or temporary table |
1362 | Updating a specific row (NEW or OLD) is not allowed in the current trigger type. | Updating of OLD row is not allowed in INSERT trigger |
1363 | A specific row (NEW or OLD) is not available in the current trigger type. | There is no OLD row in INSERT trigger |
1364 | The specified field does not have a default value. | Field 'created_at' doesn't have a default value |
1365 | Division by 0 | - |
1366 | An incorrect value of a specific type was provided for a column at a given row. | Incorrect integer value: 'abc' for column 'quantity' at row 1 |
1367 | An illegal value for a specific type was found during parsing. | Illegal ENUM 'green' value found during parsing |
1368 | The CHECK OPTION was used on a non-updatable view. | CHECK OPTION on non-updatable view 'analytics.complex_summary' |
1369 | The CHECK OPTION failed for the specified view. | CHECK OPTION failed 'hr.v_current_employees' |
1370 | A command was denied to a user for a specific routine. | EXECUTE command denied to user 'app_user'@'localhost' for routine 'admin_proc' |
1371 | Failed to purge old relay logs for a specific reason. | Failed purging old relay logs: I/O error |
1372 | The password hash should be a hexadecimal number of a specific length. | Password hash should be a 41-digit hexadecimal number |
1373 | Target log not found in binlog index | - |
1374 | I/O error reading log index file | - |
1375 | Server configuration does not permit binlog purge | - |
1376 | Failed on fseek() | - |
1377 | Fatal error during log purge | - |
1378 | A purgeable log is in use, will not purge | - |
1379 | Unknown error during log purge | - |
1380 | Failed to initialize the relay log position for a specific reason. | Failed initializing relay log position: Could not find target log in relay log index |
1381 | You are not using binary logging | - |
1382 | The specified syntax is reserved for internal server purposes. | The 'GET_LOCK' syntax is reserved for purposes internal to the MySQL server |
1383 | WSAStartup Failed | - |
1384 | Can't handle procedures with different groups yet | - |
1385 | Select must have a group with this procedure | - |
1386 | Can't use ORDER clause with this procedure | - |
1387 | Binary logging and replication forbid changing a specific global server variable or setting. | Binary logging and replication forbid changing the global server SQL_MODE |
1388 | Cannot map the specified file into memory due to an operating system error. | Can't map file: /path/to/large_file.ibd, errno: 12 |
1389 | A file has an incorrect magic number, indicating corruption or wrong file type. | Wrong magic in table_name.frm |
1390 | Prepared statement contains too many placeholders | - |
1391 | The length of a key part cannot be zero. | Key part 'name' length cannot be 0 |
1392 | View text checksum failed | - |
1393 | Cannot modify more than one base table through the specified join view. | Can not modify more than one base table through a join view 'sales.order_details_view' |
1394 | Cannot insert into the specified join view without a fields list. | Can not insert into join view 'hr.employee_department' without fields list |
1395 | Cannot delete from the specified join view. | Can not delete from join view 'inventory.product_suppliers' |
1396 | A specific operation failed for a given object. | Operation 'DROP USER' failed for 'test_user'@'localhost' |
1397 | XAER_NOTA: Unknown XID | - |
1398 | XAER_INVAL: Invalid arguments (or unsupported command) | - |
1399 | The XA command cannot be executed when the global transaction is in a specific state. | XAER_RMFAIL: The command cannot be executed when global transaction is in the ACTIVE state |
1400 | XAER_OUTSIDE: Some work is done outside global transaction | - |
Error Code | Error Description | Example |
1401 | XAER_RMERR: A fatal error occurred in the transaction branch. You should check your data for consistency. | - |
1402 | XA_RBROLLBACK: The transaction branch was rolled back. | - |
1403 | The specified grant does not exist for the given user, host, and routine. | There is no such grant defined for user 'app_user' on host 'localhost' on routine 'get_report' |
1404 | Failed to grant EXECUTE and ALTER ROUTINE privileges | - |
1405 | Failed to revoke all privileges to dropped routine | - |
1406 | The data is too long for the specified column at a given row. | Data too long for column 'email' at row 1 |
1407 | An invalid SQLSTATE value was used. | Bad SQLSTATE: 'HY000X' |
1408 | Server is ready for connections, displaying version, socket, port, and other information. | mysqld: ready for connections. Version: '8.0.28' socket: '/var/run/mysqld/mysqld.sock' port: 3306 PID: 1234 |
1409 | Can't load value from file with fixed size rows to variable | - |
1410 | You are not allowed to create a user with GRANT | - |
1411 | An incorrect value of a specific type was provided for a function. | Incorrect datetime value: '2023-02-30' for function STR_TO_DATE |
1412 | The table definition has changed, and the transaction should be retried. | Table definition has changed, please retry transaction. |
1413 | A duplicate handler was declared in the same block of a stored routine. | - |
1414 | An OUT or INOUT argument for a routine is not a variable or a valid pseudo-variable. | OUT or INOUT argument 2 for routine update_counter is not a variable or NEW pseudo-variable in BEFORE trigger |
1415 | It is not allowed to return a result set from a specific context, such as a trigger or function. | Not allowed to return a result set from a trigger |
1416 | Cannot get geometry object from data you send to the GEOMETRY field | - |
1417 | A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes | - |
1418 | 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) | - |
1419 | 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) | - |
1420 | You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it. | - |
1421 | The specified prepared statement has no open cursor. | The statement (1) has no open cursor. |
1422 | Explicit or implicit commit is not allowed in stored function or trigger. | - |
1423 | A field of a view's underlying table does not have a default value, preventing an operation. | Field of view 'sales.v_orders' underlying table doesn't have a default value |
1424 | Recursive stored functions and triggers are not allowed. | - |
1425 | The specified scale for a column is too large; the maximum is noted. | Too big scale 35 specified for column 'price'. Maximum is 30. |
1426 | The specified precision for a column is too large; the maximum is noted. | Too-big precision 70 specified for 'measurement'. Maximum is 65. |
1427 | For numeric types like FLOAT(M,D), the precision (M) must be greater than or equal to the scale (D). | For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column 'discount_rate'). |
1428 | You can't combine write-locking of system tables with other tables or lock types | - |
1429 | Unable to connect to the specified foreign data source. | Unable to connect to foreign data source: remote_db_connection |
1430 | A problem occurred while processing a query on the foreign data source. | There was a problem processing the query on the foreign data source. Data source error: Query timeout expired |
1431 | The referenced foreign data source does not exist. | The foreign data source you are trying to reference does not exist. Data source error: Unknown connection 'old_server' |
1432 | The connection string for creating a federated table is not in the correct format. | Can't create federated table. The data source connection string 'user@host/db/table' is not in the correct format |
1433 | The data source connection string is not in the correct format. | The data source connection string 'invalid-connection-string' is not in the correct format |
1434 | Cannot create a federated table due to an error from the foreign data source. | Can't create federated table. Foreign data src error: Access denied for user |
1435 | Trigger in wrong schema | - |
1436 | The thread stack has been overrun. A larger stack may be needed. | Thread stack overrun: 262144 bytes used of a 262144 byte stack, and 8192 bytes needed. Use 'sqlengine --thread_stack=#' to specify a bigger stack. |
1437 | The body of the specified routine is too long. | Routine body for 'process_all_data' is too long |
1438 | Cannot drop default keycache | - |
1439 | The display width for the specified column is out of range. | Display width out of range for column 'id' (max = 255) |
1440 | XAER_DUPID: The XID already exists | - |
1441 | A field overflow occurred in a datetime function. | Datetime function: DATE_ADD field overflow |
1442 | Cannot update a table in a stored function/trigger because it is already being used by the statement that invoked the function/trigger. | Can't update table 'products' in stored function/trigger because it is already used by statement which invoked this stored function/trigger. |
1443 | The definition of one table prevents a specific operation on another table. | The definition of table 'orders' prevents DELETE on table 'customers'. |
1444 | 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 | - |
1445 | Not allowed to set autocommit from a stored function or trigger | - |
1446 | Definer is not fully qualified | - |
1447 | A view has no definer information (due to an old table format). The current user is used as the definer. The view should be recreated. | View 'db1'.'v_sales' has no definer information (old table format). Current user is used as definer. Please recreate the view! |
1448 | The SUPER privilege is required to create a view with a definer other than the current user. | You need the SUPER privilege for creation view with 'admin_user'@'localhost' definer |
1449 | The user specified as a definer does not exist. | The user specified as a definer ('deleted_user'@'localhost') does not exist |
1450 | Changing the schema from one to another is not allowed in this context. | Changing schema from 'db1' to 'db2' is not allowed. |
1451 | Cannot delete or update a parent row because a foreign key constraint fails. The constraint details are provided. | Cannot delete or update a parent row: a foreign key constraint fails ( db.orders, CONSTRAINT fk_customer FOREIGN KEY (customer_id) REFERENCES customers (id)) |
1452 | Cannot add or update a child row because a foreign key constraint fails. The constraint details are provided. | Cannot add or update a child row: a foreign key constraint fails ( db.orders, CONSTRAINT fk_customer FOREIGN KEY (customer_id) REFERENCES customers (id)) |
1453 | The specified variable name contains invalid characters and must be quoted with backticks or renamed. | Variable 'max-connections' must be quoted with ..., or renamed |
1454 | A trigger was created without a definer attribute, which is not allowed. | No definer attribute for trigger 'db1'.'update_log'. It's disallowed to create trigger without definer. |
1455 | An object has an old format and should be re-created. | 'my_proc' has an old format, you should re-create the 'PROCEDURE' object(s) |
1456 | The recursive limit, as set by the max_sp_recursion_depth variable, was exceeded for a routine. | Recursive limit 256 (as set by the max_sp_recursion_depth variable) was exceeded for routine recursive_fn |
1457 | Failed to load a routine because its definition in the data dictionary is missing, corrupt, or contains bad data. | Failed to load routine get_user. The data dictionary table missing, corrupt, or contains bad data (internal code 2) |
1458 | The specified routine name is incorrect. | Incorrect routine name 'my-proc()' |
1459 | The table requires an upgrade. You should run REPAIR TABLE or dump and reload the table. | Table upgrade required. Please do "REPAIR TABLE old_table" or dump/reload to fix it! |
1460 | AGGREGATE is not supported for stored functions | - |
1461 | Cannot create more statements than the max_prepared_stmt_count limit. | Can't create more than max_prepared_stmt_count statements (current value: 16382) |
1462 | The specified view contains a recursive reference to itself. | db1.v1 contains view recursion |
1463 | A non-grouping field is used in a clause where it is not allowed (e.g., HAVING). | Non-grouping field 'customer_name' is used in HAVING clause |
1464 | The used table type doesn't support SPATIAL indexes | - |
1465 | Triggers can not be created on system tables | - |
1466 | Leading spaces were removed from the specified name. | Leading spaces are removed from name ' my_table' |
1467 | Failed to read auto-increment value from storage engine | - |
1468 | This is not an error message, but likely a label for a user interface field. | user name |
1469 | This is not an error message, but likely a label for a user interface field. | host name |
1470 | The provided string is too long for the specified context (e.g., user name, host name). | String 'a_very_long_user_name_that_is_longer_than_the_allowed_limit' is too long for user name (should be no longer than 32) |
1471 | The target table of the operation is not insertable-into (e.g., it's a non-updatable view). | The target table v_report of the INSERT is not insertable-into |
1472 | For a MERGE table, a constituent table is differently defined, is not of the MyISAM type, or does not exist. | Table 'archive_2022' is differently defined or of non-MyISAM type or doesn't exist |
1473 | Too high level of nesting for select | - |
1474 | The specified name became an empty string after processing (e.g., after removing invalid characters). | Name '!!!' has become '' |
1475 | First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY | - |
1476 | The foreign server you are trying to create already exists. | The foreign server, remote_oracle_db, you are trying to create already exists. |
1477 | The foreign server name you are trying to reference does not exist. | The foreign server name you are trying to reference does not exist. Data source error: unknown_server |
1478 | The table storage engine does not support the specified create option. | Table storage engine 'InnoDB' does not support the create option 'INSERT_METHOD' |
1479 | A syntax error in a partitioning clause requires a specific definition for each partition. | Syntax error: RANGE PARTITIONING requires definition of VALUES LESS THAN for each partition |
1480 | A specific partitioning type is the only one that can use a certain clause. | Only RANGE PARTITIONING can use VALUES LESS THAN in partition definition |
1481 | MAXVALUE can only be used in last partition definition | - |
1482 | Subpartitions can only be hash partitions and by key | - |
1483 | Must define subpartitions on all partitions if on one partition | - |
1484 | Wrong number of partitions defined, mismatch with previous setting | - |
1485 | Wrong number of subpartitions defined, mismatch with previous setting | - |
1486 | Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed | - |
1487 | Expression in RANGE/LIST VALUES must be constant | - |
1488 | Field in list of fields for partition function not found in table | - |
1489 | List of fields is only allowed in KEY partitions | - |
1490 | The partition info in the frm file is not consistent with what can be written into the frm file | - |
1491 | The specified partitioning function returns the wrong data type. | The YEAR function returns the wrong type |
1492 | For a specific partitioning type, all partitions must be defined. | For LIST partitions each partition must be defined |
1493 | VALUES LESS THAN value must be strictly increasing for each partition | - |
1494 | VALUES value must be of same type as partition function | - |
1495 | Multiple definition of same constant in list partitioning | - |
1496 | Partitioning can not be used stand-alone in query | - |
1497 | The mix of handlers in the partitions is not allowed in this version of MySQL | - |
1498 | For the partitioned engine, it is necessary to define all partitions of a certain type. | For the partitioned engine it is necessary to define all partitions |
1499 | Too many partitions (including subpartitions) were defined | - |
1500 | It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning | - |
Error Code | Error Description | Example |
1501 | Failed to create a specific handler file (e.g., a partition file). | - |
1502 | A BLOB or TEXT field is not allowed in a partition function. | - |
1503 | A primary or unique key must include all columns from the table's partitioning function. | A UNIQUE KEY must include all columns in the table's partitioning function (prefixed columns are not considered). |
1504 | The number of a specific item (e.g., partitions) cannot be zero. | Number of PARTITIONS = 0 is not an allowed value |
1505 | Partition management on a not partitioned table is not possible | - |
1506 | Foreign keys are not yet supported in conjunction with partitioning | - |
1507 | There is an error in the list of partitions specified for an operation. | Error in list of partitions to REORGANIZE |
1508 | Cannot remove all partitions, use DROP TABLE instead | - |
1509 | COALESCE PARTITION can only be used on HASH/KEY partitions | - |
1510 | REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers | - |
1511 | REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs | - |
1512 | A specific partition operation can only be used on RANGE/LIST partitions. | ADD PARTITION can only be used on RANGE/LIST partitions |
1513 | Trying to Add partition(s) with wrong number of subpartitions | - |
1514 | At least one partition must be added | - |
1515 | At least one partition must be coalesced | - |
1516 | More partitions to reorganize than there are partitions | - |
1517 | A partition with the specified name already exists. | Duplicate partition name p_2023 |
1518 | It is not allowed to shut off binlog on this command | - |
1519 | When reorganizing a set of partitions they must be in consecutive order | - |
1520 | Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range | - |
1521 | Partition function not supported in this version for this handler | - |
1522 | Partition state cannot be defined from CREATE/ALTER TABLE | - |
1523 | The specified storage engine handler only supports 32-bit integers in VALUES clauses for partitioning. | The MyISAM handler only supports 32 bit integers in VALUES |
1524 | The specified plugin is not loaded. | Plugin 'keyring_file' is not loaded |
1525 | An incorrect value of a specific type was provided. | Incorrect TRUNCATE value: 'INVALID' |
1526 | A value being inserted or updated does not fit into any of the defined partitions. | Table has no partition for value 2025 |
1527 | It is not allowed to specify a clause more than once. | It is not allowed to specify DEFINER more than once |
1528 | Failed to create a specific object (e.g., a log file group). | Failed to create LOGFILE GROUP |
1529 | Failed to drop a specific object (e.g., a tablespace). | Failed to drop TABLESPACE |
1530 | The handler doesn't support autoextend of tablespaces | - |
1531 | A size parameter was incorrectly specified, either number or on the form 10M | - |
1532 | The size number was correct but we don't allow the digit part to be more than 2 billion | - |
1533 | Failed to alter a specific object. | Failed to alter: LOGFILE GROUP |
1534 | Writing one row to the row-based binary log failed | - |
1535 | The table definition on the master and replica does not match, causing a replication error. | Table definition on master and slave does not match: Column count doesn't match on table 'users' |
1536 | Slave running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log events | - |
1537 | An event with the specified name already exists. | Event 'daily_backup' already exists |
1538 | Failed to store an event due to an error from the storage engine. | Failed to store event new_event. Error code 145 from storage engine. |
1539 | The specified event does not exist. | Unknown event 'old_job' |
1540 | Failed to alter the specified event. | Failed to alter event 'cleanup_task' |
1541 | Failed to drop a specific object (e.g., an event). | Failed to drop EVENT |
1542 | The INTERVAL value is either not positive or too large. | - |
1543 | The ENDS time for an event is invalid or occurs before the STARTS time. | - |
1544 | Event execution time is in the past. Event has been disabled | - |
1545 | Failed to open the mysql.event table. | - |
1546 | No datetime expression provided for an event schedule. | - |
1547 | A system table has an incorrect number of columns, likely due to corruption or a failed upgrade. | Column count of mysql.event is wrong. Expected 21, found 20. The table is probably corrupted |
1548 | Cannot load from a system table, likely because it is corrupted. | Cannot load from mysql.proc. The table is probably corrupted |
1549 | Failed to delete the event from mysql.event | - |
1550 | An error occurred during the compilation of an event's body. | - |
1551 | Same old and new event name | - |
1552 | The data for the specified column is too long. | Data for column 'body_utf8' too long |
1553 | An index cannot be dropped because it is required by a foreign key constraint. | Cannot drop index 'idx_user_id': needed in a foreign key constraint |
1554 | The specified syntax is deprecated and will be removed in a future version. An alternative is suggested. | The syntax 'TIMESTAMP(N)' is deprecated and will be removed in MySQL 8.0. Please use DATETIME(N) instead |
1555 | You can't write-lock a log table. Only read access is possible | - |
1556 | You can't use locks with log tables. | - |
1557 | Upholding a foreign key constraint would lead to a duplicate entry in the referenced table. | Upholding foreign key constraints for table 'orders', entry '101', key 1 would lead to a duplicate entry |
1558 | A system table has an incorrect column count, indicating a version mismatch that requires an upgrade. | The column count of mysql.user is wrong. Expected 45, found 42. Created with MySQL 5.7, now running 8.0. Please perform the MySQL upgrade procedure. |
1559 | Cannot switch out of the row-based binary log format when the session has open temporary tables | - |
1560 | Cannot change the binary logging format inside a stored function or trigger | - |
1561 | The NDB cluster engine does not support changing the binlog format on the fly yet | - |
1562 | Cannot create temporary table with partitions | - |
1563 | A constant value used in a partition definition is out of the valid domain for the partitioning function. | - |
1564 | This partition function is not allowed | - |
1565 | Error in DDL log | - |
1566 | Not allowed to use NULL value in VALUES LESS THAN | - |
1567 | Incorrect partition name | - |
1568 | Transaction characteristics can't be changed while a transaction is in progress | - |
1569 | An ALTER TABLE statement caused the auto-increment sequence to reset, leading to a duplicate key error. | ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '1' for key 'PRIMARY' |
1570 | An internal scheduler error occurred with the specified code. | Internal scheduler error 101 |
1571 | An error occurred while starting or stopping the event scheduler. | Error during starting/stopping of the scheduler. Error code 1 |
1572 | The specified storage engine cannot be used in partitioned tables. | - |
1573 | Cannot activate the specified log (e.g., general log). | Cannot activate 'general' log |
1574 | The server was not built with row-based replication | - |
1575 | Decoding of base64 string failed | - |
1576 | Recursion of EVENT DDL statements is forbidden when body is present | - |
1577 | Cannot proceed because system tables used by Event Scheduler were found damaged at server start | - |
1578 | Only integers allowed as number here | - |
1579 | This storage engine cannot be used for log tables | - |
1580 | You cannot perform a specific operation on a log table if logging is enabled. | You cannot 'TRUNCATE' a log table if logging is enabled |
1581 | Cannot rename the specified log table directly. A special two-step process is required when logging is enabled. | Cannot rename 'general_log'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to 'general_log' |
1582 | The incorrect number of parameters was provided in the call to a native (built-in) function. | Incorrect parameter count in the call to native function 'LPAD' |
1583 | Incorrect parameters were provided in the call to a native (built-in) function. | Incorrect parameters in the call to native function 'STR_TO_DATE' |
1584 | Incorrect parameters were provided in the call to a stored function. | Incorrect parameters in the call to stored function get_user_email |
1585 | A user-defined function has the same name as a native (built-in) function. | This function 'TRIM' has the same name as a native function |
1586 | An attempt was made to insert a duplicate value into a column with a unique or primary key constraint. | Duplicate entry 'test-user' for key 'users.username_UNIQUE' |
1587 | Too many files opened, please execute the command again | - |
1588 | Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. | - |
1589 | 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. | - |
1590 | An incident occurred on the master, and the message is being relayed to the replica. | The incident DDL_LOG_ERROR occurred on the master. Message: Error in DDL log |
1591 | The table has no partition for some existing values. This can happen after a partition reorganization. | - |
1592 | A statement that is unsafe for statement-based replication was written to the binary log. | Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement used a LIMIT clause with a user-defined variable. |
1593 | A fatal error occurred, with the reason specified. | Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist |
1594 | A failure occurred while reading the relay log. | Relay log read failure: Could not find event in relay log |
1595 | A failure occurred while writing to the relay log. | Relay log write failure: IO error writing to file |
1596 | Failed to create a specific replication-related object. | Failed to create relay log |
1597 | A command sent to the master failed. | Master command COM_BINLOG_DUMP failed: Master has purged binary logs containing GTIDs that the slave requires |
1598 | Binary logging is not possible for the stated reason. | Binary logging not possible. Message: The storage engine for the table does not support binary logging. |
1599 | A view is missing its creation context information. | View db1.v1 has no creation context |
1600 | The creation context of a view is invalid. | Creation context of view db1.v1 is invalid |
Error Code | Error Description | Example |
1601 | The creation context of a stored routine is invalid. | Creation context of stored routine db1.my_proc is invalid |
1602 | The trigger definition file for a table is corrupted. | Corrupted TRG file for table sales.orders |
1603 | Triggers for a table have no creation context. | Triggers for table logs.audits have no creation context |
1604 | The trigger creation context of a table is invalid. | Trigger creation context of table inventory.products is invalid |
1605 | The creation context of an event is invalid. | Creation context of event db_maint.cleanup_job is invalid |
1606 | Cannot open the table for a specific trigger. | Cannot open table for trigger db1.my_trigger |
1607 | Cannot create a stored routine. Check warnings for details. | Cannot create stored routine calculate_totals. Check warnings |
1608 | There is an ambiguous or conflicting combination of replica modes. | Ambiguous slave modes combination. The slave is running with --log-slave-updates but the master does not have checksums enabled. |
1609 | A BINLOG statement was not preceded by a required format description BINLOG statement. | The BINLOG statement of type 'ROW_EVENT' was not preceded by a format description BINLOG statement. |
1610 | Corrupted replication event was detected | - |
1611 | An invalid column was referenced in a LOAD DATA statement. | Invalid column reference (non_existent_col) in LOAD DATA |
1612 | The log file being purged was not found. | Being purged log binlog.000123 was not found |
1613 | XA_RBTIMEOUT: Transaction branch was rolled back: took too long | - |
1614 | XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected | - |
1615 | Prepared statement needs to be re-prepared | - |
1616 | The DELAYED option is not supported for the specified table. | DELAYED option not supported for table 'my_innodb_table' |
1617 | The master info structure does not exist | - |
1618 | A specified server option was ignored. | <old_passwords> option ignored |
1619 | Built-in plugins cannot be deleted | - |
1620 | Plugin is busy and will be uninstalled on shutdown | - |
1621 | A specified variable is read-only. A different SET syntax may be required to assign the value. | GLOBAL variable 'version' is read-only. Use SET GLOBAL to assign the value |
1622 | The storage engine does not support rollback for this statement. The transaction was rolled back and must be restarted. | Storage engine MyISAM does not support rollback for this statement. Transaction rolled back and must be restarted |
1623 | The replica received unexpected heartbeat data from the master. | Unexpected master's heartbeat data: event size is incorrect |
1624 | The requested value for the heartbeat period is negative or exceeds the maximum allowed value. | The requested value for the heartbeat period is either negative or exceeds the maximum allowed (4294967 seconds). |
1625 | The schema for the mysql.ndb_replication table is incorrect. | Bad schema for mysql.ndb_replication table. Message: Missing column 'epoch' |
1626 | An error occurred while parsing the conflict function. | Error in parsing conflict function. Message: Syntax error near 'GREATEST' |
1627 | Writing to the exceptions table failed. | Write to exceptions table failed. Message: Table is full |
1628 | The comment for a table is too long. | Comment for table 'users' is too long (max = 2048) |
1629 | The comment for a field is too long. | Comment for field 'user_id' is too long (max = 1024) |
1630 | The specified function does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual. | FUNCTION my_db.get_name does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual |
1631 | Database | - |
1632 | Table | - |
1633 | Partition | - |
1634 | Subpartition | - |
1635 | Temporary | - |
1636 | Renamed | - |
1637 | Too many active concurrent transactions | - |
1638 | Non-ASCII separator arguments are not fully supported | - |
1639 | debug sync point wait timed out | - |
1640 | debug sync point hit limit reached | - |
1641 | A duplicate condition information item was specified. | Duplicate condition information item 'MESSAGE_TEXT' |
1642 | Unhandled user-defined warning condition | - |
1643 | Unhandled user-defined not found condition | - |
1644 | Unhandled user-defined exception condition | - |
1645 | RESIGNAL when handler not active | - |
1646 | SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE | - |
1647 | Data was truncated for a condition item. | Data truncated for condition item 'MYSQL_ERRNO' |
1648 | Data is too long for a condition item. | Data too long for condition item 'MESSAGE_TEXT' |
1649 | The specified locale is unknown. | Unknown locale: 'en_XX' |
1650 | The requested server ID clashes with the replica startup option --replicate-same-server-id. | The requested server id 1 clashes with the slave startup option --replicate-same-server-id |
1651 | Query cache is disabled; restart the server with query_cache_type=1 to enable it | - |
1652 | A duplicate partition field name was used. | Duplicate partition field name 'id' |
1653 | Inconsistency in usage of column lists for partitioning | - |
1654 | Partition column values of incorrect type | - |
1655 | Too many fields were specified in a partition definition. | Too many fields in 'partition p0 values in ((1,2,3))' |
1656 | Cannot use MAXVALUE as value in VALUES IN | - |
1657 | Cannot have more than one value for this type of partitioning. | Cannot have more than one value for this type of RANGE partitioning |
1658 | Row expressions in VALUES IN only allowed for multi-field column partitioning | - |
1659 | A field is of a type that is not allowed for this type of partitioning. | Field 'description' is of a not allowed type for this type of partitioning |
1660 | The total length of the partitioning fields is too large | - |
1661 | Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved. | - |
1662 | 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. | - |
1663 | Cannot execute statement: impossible to write to binary log since the statement is unsafe, the storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. | 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. The statement is unsafe because it uses a LIMIT clause. |
1664 | 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. | - |
1665 | 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. | 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. The statement is unsafe because it uses a UDF. |
1666 | Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT. | - |
1667 | Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging. | - |
1668 | The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. | - |
1669 | The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted. | - |
1670 | 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. | - |
1671 | 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. | - |
1672 | Statement is unsafe because it uses a UDF which may not return the same value on the slave. | - |
1673 | Statement is unsafe because it uses a system variable that may have a different value on the slave. | - |
1674 | Statement is unsafe because it uses a system function that may return a different value on the slave. | - |
1675 | Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction. | - |
1676 | Provides context for a statement that has replication safety issues. | Unsafe Statement: SELECT * FROM users LIMIT 10 |
1677 | A column of a table cannot be converted from one data type to another. | Column 3 of table 'db1.users' cannot be converted from type 'VARCHAR(50)' to type 'INT' |
1678 | A conversion table cannot be created for the specified table. | Can't create conversion table for table 'db1.old_data' |
1679 | Cannot modify @@session.binlog_format inside a transaction | - |
1680 | The specified path is too long. | The path specified for --log-bin is too long. |
1681 | A specified feature or variable is deprecated and will be removed in a future release. | 'storage_engine' is deprecated and will be removed in a future release. |
1682 | A native system table has the wrong structure. | Native table 'performance_schema'.'threads' has the wrong structure |
1683 | Invalid performance_schema usage. | - |
1684 | A table was skipped because its definition is being modified by a concurrent DDL statement. | Table 'db1'.'t1' was skipped since its definition is being modified by concurrent DDL statement |
1685 | Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction | - |
1686 | Cannot change the binlog direct flag inside a stored function or trigger | - |
1687 | A SPATIAL index may only contain a geometrical type column | - |
1688 | The comment for an index is too long. | Comment for index 'idx_location' is too long (max = 1024) |
1689 | Wait on a lock was aborted due to a pending exclusive lock | - |
1690 | A value is out of range in a given context. | BIGINT UNSIGNED value is out of range in '(9223372036854775807 * 2)' |
1691 | A variable of a non-integer based type in LIMIT clause | - |
1692 | Mixing self-logging and non-self-logging engines in a statement is unsafe. | - |
1693 | Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. | - |
1694 | Cannot modify @@session.sql_log_bin inside a transaction | - |
1695 | Cannot change the sql_log_bin inside a stored function or trigger | - |
1696 | Failed to read from the .par file | - |
1697 | The VALUES value for a partition must have type INT. | VALUES value for partition 'p0' must have type INT |
1698 | Access is denied for the specified user. | Access denied for user 'web_user'@'192.168.1.100' |
1699 | SET PASSWORD has no significance for users authenticating via plugins | - |
1700 | GRANT with IDENTIFIED WITH is illegal because the user already exists. | GRANT with IDENTIFIED WITH is illegal because the user 'testuser'@'localhost' already exists |
Error Code | Error Description | Example |
1701 | Cannot truncate a table referenced in a foreign key constraint. | Cannot truncate a table referenced in a foreign key constraint ( fk_order_customer) |
1702 | A plugin that is force_plus_permanent cannot be unloaded. | Plugin 'keyring_file' is force_plus_permanent and can not be unloaded |
1703 | 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. | - |
1704 | The requested value for the heartbeat period exceeds the value of 'replica_net_timeout' seconds. A sensible value for the period should be less than the timeout. | - |
1705 | Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this sqlengine variable and try again | - |
1706 | A primary key or partition key update is not allowed since the table is referenced with multiple aliases in the same statement. | Primary key/partition key update is not allowed since the table is updated both as 't1' and 't2'. |
1707 | A table rebuild is required. Please run ALTER TABLE ... FORCE or dump/reload to fix it. | Table rebuild required. Please do "ALTER TABLE corrupted_table FORCE" or dump/reload to fix it! |
1708 | The value of one variable should be no less than the value of another. | The value of 'max_binlog_cache_size' should be no less than the value of 'binlog_cache_size' |
1709 | The index column size is too large. | Index column size too large. The maximum column size is 767 bytes. |
1710 | A trigger has an error in its body. | Trigger 'update_summary' has an error in its body: 'Unknown column 'total' in 'field list'' |
1711 | An unknown trigger has an error in its body. | Unknown trigger has an error in its body: 'Table 'db1.summary' doesn't exist' |
1712 | An index is corrupted. | Index PRIMARY is corrupted |
1713 | Undo log record is too big. | - |
1714 | 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. | - |
1715 | 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. | - |
1716 | 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. | - |
1717 | 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. | - |
1718 | 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. | - |
1719 | 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. | - |
1720 | The specified plugin is marked as not dynamically uninstallable. You have to stop the server to uninstall it. | Plugin 'InnoDB' is marked as not dynamically uninstallable. You have to stop the server to uninstall it. |
1721 | The specified plugin is marked as not dynamically installable. You have to stop the server to install it. | Plugin 'some_plugin' is marked as not dynamically installable. You have to stop the server to install it. |
1722 | 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. | - |
1723 | 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. | - |
1724 | INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe | - |
1725 | Table is being used in foreign key check. | - |
1726 | The specified storage engine does not support system tables. | Storage engine 'MEMORY' does not support system tables. [mysql.user] |
1727 | INSERT into autoincrement field which is not the first part in the composed primary key is unsafe. | - |
1728 | Cannot load from the specified table. The table is probably corrupted. | Cannot load from db1.users. The table is probably corrupted |
1729 | The requested value for the master delay exceeds the maximum allowed value. | The requested value 90000000 for the master delay exceeds the maximum 4294967295 |
1730 | Only Format_description_log_event and row events are allowed in BINLOG statements. | Only Format_description_log_event and row events are allowed in BINLOG statements (but Query_log_event was provided) |
1731 | There is a non-matching attribute between a partition and its table. | Non matching attribute 'ROW_FORMAT' between partition and table |
1732 | The table to be exchanged with a partition is itself partitioned. | Table to exchange with partition is partitioned: 'staging_table' |
1733 | The table to be exchanged with a partition is a temporary table. | Table to exchange with partition is temporary: 'temp_data' |
1734 | Subpartitioned table, use subpartition instead of partition | - |
1735 | An unknown partition was specified for a table. | Unknown partition 'p_2025' in table 'sales_by_year' |
1736 | Tables have different definitions | - |
1737 | Found a row that does not match the partition | - |
1738 | The binlog_cache_size is greater than max_binlog_cache_size; it will be set to the maximum value. | Option binlog_cache_size (67108864) is greater than max_binlog_cache_size (33554432); setting binlog_cache_size equal to max_binlog_cache_size. |
1739 | Cannot use a specific access method on an index due to type or collation conversion on a field. | Cannot use key access on index 'idx_name' due to type or collation conversion on field 'last_name' |
1740 | The table to be exchanged with a partition has foreign key references. | Table to exchange with partition has foreign key references: 'staging_table' |
1741 | A key value was not found in the specified table. | Key value '12345' was not found in table 'db1.products' |
1742 | Data for a column is too long. | Data for column 'username' too long |
1743 | Replication event checksum verification failed while reading from network. | - |
1744 | Replication event checksum verification failed while reading from a log file. | - |
1745 | The binlog_stmt_cache_size is greater than max_binlog_stmt_cache_size; it will be set to the maximum value. | Option binlog_stmt_cache_size (65536) is greater than max_binlog_stmt_cache_size (32768); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size. |
1746 | Cannot update a table while another table is being created. | Can't update table 'users' while 'new_users' is being created. |
1747 | PARTITION () clause on non partitioned table | - |
1748 | Found a row not matching the given partition set | - |
1749 | The specified partition doesn't exist. | partition 'p_invalid' doesn't exist |
1750 | A failure occurred while changing the type of replication repository. | Failure while changing the type of replication repository: Could not create repository table. |
1751 | The creation of some temporary tables could not be rolled back. | - |
1752 | Some temporary tables were dropped, but these operations could not be rolled back. | - |
1753 | A specific feature is not supported in multi-threaded replica mode. | FLUSH TABLES is not supported in multi-threaded slave mode. It is not safe. |
1754 | The number of modified databases exceeds the maximum; the database names will not be included in the replication event metadata. | The number of modified databases exceeds the maximum 16; the database names will not be included in the replication event metadata. |
1755 | Cannot execute the current event group in parallel mode due to a specific event. | Cannot execute the current event group in the parallel mode. Encountered event Query, relay-log name relay-bin.000123, position 4567 which prevents execution of this event group in parallel mode. Reason: DDL statements are not parallelizable. |
1756 | A general error occurred, with details provided in the message. | The slave coordinator and worker threads are configured with different values for the event checksum. |
1757 | FULLTEXT index is not supported for partitioned tables. | - |
1758 | Invalid condition number | - |
1759 | Sending passwords in plain text without SSL/TLS is extremely insecure. | - |
1760 | 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. | - |
1761 | A foreign key constraint would lead to a duplicate entry in another table. | Foreign key constraint for table 'orders', record '101' would lead to a duplicate entry in table 'order_details', key 'PRIMARY' |
1762 | A foreign key constraint would lead to a duplicate entry in a child table. | Foreign key constraint for table 'products', record 'PROD-001' would lead to a duplicate entry in a child table |
1763 | Setting authentication options is not possible when only the Slave SQL Thread is being started. | - |
1764 | The table does not have FULLTEXT index to support this query | - |
1765 | A specific system variable cannot be set in stored functions or triggers. | The system variable gtid_next cannot be set in stored functions or triggers. |
1766 | A specific system variable cannot be set when there is an ongoing transaction. | The system variable binlog_format cannot be set when there is an ongoing transaction. |
1767 | The value of @@SESSION.GTID_NEXT is not listed in @@SESSION.GTID_NEXT_LIST. | The system variable @@SESSION.GTID_NEXT has the value 'uuid:10', which is not listed in @@SESSION.GTID_NEXT_LIST. |
1768 | The system variable @@SESSION.GTID_NEXT cannot change inside a transaction. | - |
1769 | A SET statement cannot invoke a stored function to assign a value. | The statement 'SET gtid_next = my_func()' cannot invoke a stored function. |
1770 | The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL. | - |
1771 | Skipping a transaction because it has already been executed and logged. | Skipping transaction 'a1b2c3d4-e5f6-11ee-8c90-0242ac120002:123' because it has already been executed and logged. |
1772 | The GTID set specification is malformed. | Malformed GTID set specification 'uuid:1-10,'. |
1773 | Malformed GTID set encoding. | - |
1774 | The GTID specification is malformed. | Malformed GTID specification 'uuid:abc'. |
1775 | Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid. | - |
1776 | Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active. | - |
1777 | CHANGE MASTER TO MASTER_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF. | - |
1778 | Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'. | - |
1779 | GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON. | - |
1780 | @@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates. | - |
1781 | @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF. | - |
1782 | @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON. | - |
1783 | @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF. | - |
1784 | Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF. | - |
1785 | 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. | - |
1786 | Statement violates GTID consistency: CREATE TABLE ... SELECT. | - |
1787 | 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. | - |
1788 | 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. | - |
1789 | Cannot replicate because the master purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the master's binary log expiration period. | ... The slave is trying to replay GTID 'uuid:1-100' which is not in the master's binlogs. |
1790 | @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. Ownership is released on COMMIT or ROLLBACK. | @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns 'uuid:123'. Ownership is released on COMMIT or ROLLBACK. |
1791 | An unknown EXPLAIN format name was used. | Unknown EXPLAIN format name: 'XML' |
1792 | Cannot execute statement in a READ ONLY transaction. | - |
1793 | The comment for a table partition is too long. | Comment for table partition 'p2023' is too long (max = 1024) |
1794 | Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a replica. Additional error messages can be found in the MySQL error log. | - |
1795 | InnoDB presently supports one FULLTEXT index creation at a time | - |
1796 | Cannot create FULLTEXT index on temporary InnoDB table | - |
1797 | A column is of the wrong type for an InnoDB FULLTEXT index. | Column 'location' is of wrong type for an InnoDB FULLTEXT index |
1798 | An index is of the wrong type for an InnoDB FULLTEXT index. | Index 'idx_location' is of wrong type for an InnoDB FULLTEXT index |
1799 | Creating an index required more than innodb_online_alter_log_max_size bytes of modification log. Please try again. | Creating index 'ft_idx_content' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again. |
1800 | An unknown algorithm was specified. | Unknown ALGORITHM 'INVALID_ALGO' |
Error Code | Error Description | Example |
1801 | An unknown LOCK type was specified. | Unknown LOCK type 'INVALID_LOCK' |
1802 | 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. | - |
1803 | Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log. | - |
1804 | Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log. | - |
1805 | The column count of a table is wrong. The expected count did not match the found count. The table is probably corrupted. | Column count of db1.users is wrong. Expected 5, found 4. The table is probably corrupted |
1806 | Slave must silently retry current transaction | - |
1807 | There is a foreign key check running on a table. The table cannot be discarded. | There is a foreign key check running on table 'orders'. Cannot discard the table. |
1808 | A schema mismatch was detected. | Schema mismatch (Table flags) |
1809 | A table is located in the system tablespace. | Table 'db1/t1' in system tablespace |
1810 | An I/O read error occurred. | IO Read error: (2, No such file or directory) Error reading file './db1/t1.ibd' |
1811 | An I/O write error occurred. | IO Write error: (28, No space left on device) Error writing file './db1/t1.ibd' |
1812 | The tablespace is missing for a table. | Tablespace is missing for table db1.t1. |
1813 | The specified tablespace already exists. | Tablespace 'ts1' exists. |
1814 | The tablespace has been discarded for a table. | Tablespace has been discarded for table 'db1/t1' |
1815 | An internal error occurred. | Internal error: Failed to find a suitable tablespace for the table |
1816 | An ALTER TABLE ... IMPORT TABLESPACE operation failed. | ALTER TABLE t1 IMPORT TABLESPACE failed with error 1812 : 'Tablespace is missing for table db1.t1.' |
1817 | An index is corrupt. | Index corrupt: Page is not of the expected type. |
1818 | Invalid display width. Use YEAR instead. | - |
1819 | Your password does not satisfy the current policy requirements | - |
1820 | You must reset your password using ALTER USER statement before executing this statement. | - |
1821 | Failed to add the foreign key constraint. A required index is missing in the foreign table. | Failed to add the foreign key constraint. Missing index for constraint 'fk_order_details' in the foreign table 'order_details' |
1822 | Failed to add the foreign key constraint. A required index is missing in the referenced table. | Failed to add the foreign key constraint. Missing index for constraint 'fk_order_customer' in the referenced table 'customers' |
1823 | Failed to add a foreign key constraint to system tables. | Failed to add the foreign key constraint 'fk_order_customer' to system tables |
1824 | Failed to open the referenced table. | Failed to open the referenced table 'customers' |
1825 | Failed to add a foreign key constraint on a table due to incorrect options. | Failed to add the foreign key constraint on table 'orders'. Incorrect options in FOREIGN KEY constraint 'fk_order_customer' |
1826 | A duplicate foreign key constraint name was used. | Duplicate foreign key constraint name 'fk_order_customer' |
1827 | The password hash doesn't have the expected format. | - |
1828 | Cannot drop a column because it is needed in a foreign key constraint. | Cannot drop column 'customer_id': needed in a foreign key constraint 'fk_order_customer' |
1829 | Cannot drop a column because it is needed in a foreign key constraint of another table. | Cannot drop column 'product_id': needed in a foreign key constraint 'fk_order_details_product' of table 'order_details' |
1830 | A column cannot be changed to NOT NULL because it is used in a foreign key constraint with a SET NULL action. | Column 'manager_id' cannot be NOT NULL: needed in a foreign key constraint 'fk_employee_manager' SET NULL |
1831 | A duplicate index was defined on a table. This is deprecated and will be disallowed in a future release. | Duplicate index 'idx_name' defined on the table 'db1.users'. This is deprecated and will be disallowed in a future release. |
1832 | Cannot change a column because it is used in a foreign key constraint. | Cannot change column 'customer_id': used in a foreign key constraint 'fk_order_customer' |
1833 | Cannot change a column because it is used in a foreign key constraint of another table. | Cannot change column 'product_id': used in a foreign key constraint 'fk_order_details_product' of table 'order_details' |
1834 | Cannot delete rows from a table that is a parent in a foreign key constraint. | Cannot delete rows from table which is parent in a foreign key constraint 'fk_order_customer' of table 'orders' |
1835 | Malformed communication packet. | - |
1836 | Running in read-only mode | - |
1837 | When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. | ... Current @@SESSION.GTID_NEXT is 'a1b2c3d4-e5f6-11ee-8c90-0242ac120002:123'. |
1838 | A specific system variable cannot be set in stored procedures. | The system variable gtid_next cannot be set in stored procedures. |
1839 | @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON. | - |
1840 | @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty. | - |
1841 | @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients). | - |
1842 | @@GLOBAL.GTID_PURGED was changed. | @@GLOBAL.GTID_PURGED was changed from '' to 'a1b2c3d4-e5f6-11ee-8c90-0242ac120002:1-10'. |
1843 | @@GLOBAL.GTID_EXECUTED was changed. | @@GLOBAL.GTID_EXECUTED was changed from 'uuid:1-5' to 'uuid:1-10'. |
1844 | Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to. | - |
1845 | A specific feature is not supported for this operation. An alternative is suggested. | ALGORITHM=INPLACE is not supported for this operation. Try ALGORITHM=COPY. |
1846 | A specific feature is not supported for a given reason. An alternative is suggested. | ALGORITHM=INSTANT is not supported. Reason: Adding a column with a default value. Try ALGORITHM=INPLACE. |
1847 | COPY algorithm requires a lock | - |
1848 | Partition specific operations do not yet support LOCK/ALGORITHM | - |
1849 | Columns participating in a foreign key are renamed | - |
1850 | Cannot change column type INPLACE | - |
1851 | Adding foreign keys needs foreign_key_checks=OFF | - |
1852 | Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows | - |
1853 | Dropping a primary key is not allowed without also adding a new primary key | - |
1854 | Adding an auto-increment column requires a lock | - |
1855 | Cannot replace hidden FTS_DOC_ID with a user-visible one | - |
1856 | Cannot drop or rename FTS_DOC_ID | - |
1857 | Fulltext index creation requires a lock | - |
1858 | sql_replica_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 | - |
1859 | A duplicate entry was found for a key. | Duplicate entry for key 'PRIMARY' |
1860 | A long database name and object identifier resulted in a path length exceeding the system limit. | Long database name and identifier for object resulted in path length exceeding 255 characters. Path: '/var/lib/mysql/.../long_name.ibd'. |
1861 | cannot silently convert NULL values, as required in this SQL_MODE | - |
1862 | Your password has expired. To log in you must change it using a client that supports expired passwords. | - |
1863 | A row was found in the wrong partition. | Found a row in wrong partition p1 |
1864 | Cannot schedule a replication event to a worker thread because its size exceeds replica_pending_jobs_size_max. | Cannot schedule event Query, relay-log name relay-bin.000123, position 4567 to Worker thread because its size 1000000 exceeds 500000 of replica_pending_jobs_size_max. |
1865 | Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table | - |
1866 | A binary log file is logically corrupted. | The binary log file 'binlog.000123' is logically corrupted: The event's master-side-size is 123, but the event's content size is 120 |
1867 | A file was not purged because it was being read by one or more threads. | file binlog.000123 was not purged because it was being read by 1 thread(s), purged only 5 out of 6 files. |
1868 | A file was not purged because it is the active log file. | file binlog.000125 was not purged because it is the active log file. |
1869 | Auto-increment value in UPDATE conflicts with internally generated values | - |
1870 | Row events are not logged for certain statements that modify BLACKHOLE tables in row format. | Row events are not logged for DML statements that modify BLACKHOLE tables in row format. Table(s): 't1' |
1871 | Slave failed to initialize master info structure from the repository | - |
1872 | Slave failed to initialize relay log info structure from the repository | - |
1873 | Access denied when trying to change to a user. The connection will be disconnected. | Access denied trying to change to user 'new_user'@'localhost' (using password: YES). Disconnecting. |
1874 | InnoDB is in read only mode. | - |
1875 | 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. | - |
1876 | 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. | - |
1877 | Operation cannot be performed. A required table is missing, corrupt, or contains bad data. | Operation cannot be performed. The table 'db1.users' is missing, corrupt or contains bad data. |
1878 | Temporary file write failure. | - |
1879 | Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index. | - |
1880 | TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format. | - |
1881 | Operation not allowed when innodb_force_recovery > 0. | - |
1882 | The initialization vector supplied to a function is too short. | The initialization vector supplied to AES_ENCRYPT is too short. Must be at least 16 bytes long |
1883 | A plugin cannot be uninstalled at this time for a specific reason. | Plugin 'audit_log' cannot be uninstalled now. It is in use by active sessions. |
1884 | 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'. | - |
1885 | 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. | - |
1886 | A table does not have the necessary key(s) defined on it. Please check the table definition and create the required index(es). | The table 'db1.order_details' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly. |
1887 | Setting named_pipe_full_access_group to a specific value is insecure. Consider using a Windows group with fewer members. | Setting named_pipe_full_access_group='Everyone' is insecure. Consider using a Windows group with fewer members. |
Error Code | Error Description | Example |
3000 | A file is corrupted. | File /var/lib/mysql/db1/my_table.ibd is corrupted |
3001 | A query was partially completed on the master and then aborted due to an error. The master may be inconsistent. If the master is okay, the query should be run manually on the replica, and the replica should be advanced past this event. | Query partially completed on the master (error on master: 1062) and was aborted... Query:'INSERT INTO t1 VALUES (1)' |
3002 | A query caused different errors on the master and the replica. | Error on master: message='Duplicate entry '1' for key 'PRIMARY'' error code=1062; Error on slave: message='Table 'db1.t1' doesn't exist', error code=1146. Default database:'db1'. Query:'INSERT INTO t1 VALUES (1)' |
3003 | The storage engine for a table is not loaded. | Storage engine for table 'db1'.'archive_table' is not loaded. |
3004 | GET STACKED DIAGNOSTICS when handler not active | - |
3005 | A specified feature is no longer supported and the statement was converted to a new form. | PASSWORD() is no longer supported. The statement was converted to SET PASSWORD = '...'. |
3006 | Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the slave. | - |
3007 | Cannot DISCARD/IMPORT tablespace associated with temporary table | - |
3008 | A foreign key cascade delete or update operation has exceeded the maximum depth. | Foreign key cascade delete/update exceeds max depth of 15. |
3009 | The column count of a table is wrong, likely due to a version mismatch. An upgrade procedure is required. | The column count of db1.users is wrong. Expected 5, found 4. Created with MySQL 50700, now running 80015. Please perform the MySQL upgrade procedure. |
3010 | A trigger does not have the CREATED attribute. | Trigger db1.users.before_insert_trigger does not have CREATED attribute. |
3011 | The referenced trigger for a given action time and event type does not exist. | Referenced trigger 'non_existent_trigger' for the given action time and event type does not exist. |
3012 | EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE | - |
3013 | An invalid size was specified for a column. | Invalid size for column 'my_column'. |
3014 | The table's storage engine found a required create option was missing. | Table storage engine 'InnoDB' found required create option missing |
3015 | The storage engine ran out of memory. | Out of memory in storage engine 'InnoDB'. |
3016 | The password for anonymous user cannot be expired. | - |
3017 | This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD first | - |
3018 | Cannot create FULLTEXT index on materialized subquery | - |
3019 | An error occurred in the Undo Log. | Undo Log error: page is corrupt |
3020 | Invalid argument for logarithm | - |
3021 | This operation cannot be performed with a running replica I/O thread; run STOP SLAVE IO_THREAD for the specified channel first. | This operation cannot be performed with a running slave io thread; run STOP SLAVE IO_THREAD FOR CHANNEL 'channel_1' first. |
3022 | This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. It is suggested to wait until replica_open_temp_tables = 0. | - |
3023 | Using 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. | - |
3024 | Query execution was interrupted, maximum statement execution time exceeded | - |
3025 | Select is not a read only statement, disabling timer | - |
3026 | A duplicate entry was found. | Duplicate entry 'user@example.com'. |
3027 | A specified SQL mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead. | 'NO_AUTO_CREATE_USER' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead. |
3028 | An expression in the ORDER BY clause contains an aggregate function and applies to a UNION. | Expression #1 of ORDER BY contains aggregate function and applies to a UNION |
3029 | An expression in the ORDER BY clause contains an aggregate function and applies to the result of a non-aggregated query. | Expression #2 of ORDER BY contains aggregate function and applies to the result of a non-aggregated query |
3030 | A replica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well. | - |
3031 | The replica_preserve_commit_order option is not supported in this context. | replica_preserve_commit_order is not supported when using row-based replication with non-transactional tables. |
3032 | The server is currently in offline mode | - |
3033 | A binary geometry function was given two geometries of different SRIDs, which should have been identical. | Binary geometry function ST_Intersects given two geometries of different srids: 4326 and 3857, which should have been identical. |
3034 | A geometry function was called with unsupported types of arguments. | Calling geometry function ST_Distance with unsupported types of arguments. |
3035 | An unknown GIS error occurred in a function. | Unknown GIS error occurred in function ST_Buffer. |
3036 | An unknown exception was caught in a GIS function. | Unknown exception caught in GIS function ST_Union. |
3037 | Invalid GIS data was provided to a function. | Invalid GIS data provided to function ST_GeomFromText. |
3038 | The geometry has no data in a function. | The geometry has no data in function ST_Centroid. |
3039 | Unable to calculate the centroid because the geometry is empty in a function. | Unable to calculate centroid because geometry is empty in function ST_Centroid. |
3040 | A geometry overlay calculation error occurred because the geometry data is invalid in a function. | Geometry overlay calculation error: geometry data is invalid in function ST_Intersection. |
3041 | A geometry turn info calculation error occurred because the geometry data is invalid in a function. | Geometry turn info calculation error: geometry data is invalid in function ST_Intersection. |
3042 | Analysis procedures of intersection points were interrupted unexpectedly in a function. | Analysis procedures of intersection points interrupted unexpectedly in function ST_Intersection. |
3043 | An unknown exception was thrown in a function. | Unknown exception thrown in function ST_Simplify. |
3044 | A memory allocation error occurred in a function. | Memory allocation error: failed to allocate 16384 bytes in function ST_Buffer. |
3045 | A domain error occurred in a function. | Domain error: input value is out of range in function ST_Transform. |
3046 | A length error occurred in a function. | Length error: string is too long in function ST_AsText. |
3047 | An invalid argument error occurred in a function. | Invalid argument error: buffer distance must be non-negative in function ST_Buffer. |
3048 | An out of range error occurred in a function. | Out of range error: coordinate value exceeds limits in function ST_Point. |
3049 | An overflow error occurred in a function. | Overflow error: calculation resulted in a value too large to be represented in function ST_Area. |
3050 | A range error occurred in a function. | Range error: SRID value is not within the valid range in function ST_SRID. |
3051 | An underflow error occurred in a function. | Underflow error: calculation resulted in a value too small to be represented in function ST_Length. |
3052 | A logic error occurred in a function. | Logic error: inconsistent internal state in function ST_IsValid. |
3053 | A runtime error occurred in a function. | Runtime error: external library failed in function ST_Transform. |
3054 | An unknown exception occurred in a function. | Unknown exception: An unexpected error occurred during geometry processing in function ST_Union. |
3055 | Geometry byte string must be little endian. | - |
3056 | The password provided for the replication user exceeds the maximum length of 32 characters | - |
3057 | An incorrect user-level lock name was used. | Incorrect user-level lock name 'my_lock_name_is_way_too_long_for_the_system_to_handle'. |
3058 | Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition. | - |
3059 | REPLACE cannot be executed as it requires deleting rows that are not in the view | - |
3060 | Do not support online operation on table with GIS index | - |
3061 | An illegal user variable name was used. | User variable name '@1illegal' is illegal |
3062 | A specific operation cannot be performed when GTID_MODE = OFF. | Cannot enable MASTER_AUTO_POSITION when GTID_MODE = OFF. |
3063 | A specific operation cannot be performed from a replication replica thread. | Cannot SET GTID_NEXT from a replication slave thread. |
3064 | An incorrect type was used for an argument in a function. | Incorrect type for argument 1 in function LENGTH. |
3065 | An expression in the ORDER BY clause is not in the SELECT list and references a column that is also not in the SELECT list; this is incompatible with the current SQL mode. | Expression #1 of ORDER BY clause is not in SELECT list, references column 't2.name' which is not in SELECT list; this is incompatible with sql_mode=only_full_group_by |
3066 | An expression in the ORDER BY clause is not in the SELECT list and contains an aggregate function; this is incompatible with the current SQL mode. | Expression #1 of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with sql_mode=only_full_group_by |
3067 | Supplied filter list contains a value which is not in the required format 'db_pattern.table_pattern' | - |
3068 | OK packet too large | - |
3069 | Invalid JSON data was provided to a function. | Invalid JSON data provided to function JSON_EXTRACT: The document is not a valid JSON text. |
3070 | Invalid GeoJSON data was provided to a function: a required member is missing. | Invalid GeoJSON data provided to function ST_GeomFromGeoJSON: Missing required member 'type' |
3071 | Invalid GeoJSON data was provided to a function: a member has the wrong type. | Invalid GeoJSON data provided to function ST_GeomFromGeoJSON: Member 'coordinates' must be of type 'array' |
3072 | Invalid GeoJSON data was provided to a function. | Invalid GeoJSON data provided to function ST_GeomFromGeoJSON |
3073 | An unsupported number of coordinate dimensions was found in a function. | Unsupported number of coordinate dimensions in function ST_GeomFromGeoJSON: Found 4, expected 2 |
3074 | A replica channel does not exist. | Slave channel 'channel_2' does not exist. |
3075 | A replica channel with the same name already exists for the given host and port combination. | A slave channel 'channel_1' already exists for the given host and port combination. |
3076 | Couldn't create channel: Channel name is either invalid or too long. | - |
3077 | To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE. | - |
3078 | Cannot delete replica info objects for a channel. | Cannot delete slave info objects for channel 'channel_1'. |
3079 | Multiple channels exist on the replica. Please provide channel name as an argument. | - |
3080 | Maximum number of replication channels allowed exceeded. | - |
3081 | This operation cannot be performed with running replication threads; run STOP SLAVE for the specified channel first. | This operation cannot be performed with running replication threads; run STOP SLAVE FOR CHANNEL 'channel_1' first |
3082 | This operation requires running replication threads; configure the replica and run START SLAVE for the specified channel. | This operation requires running replication threads; configure slave and run START SLAVE FOR CHANNEL 'channel_1' |
3083 | Replication thread(s) for a channel are already running. | Replication thread(s) for channel 'channel_1' are already runnning. |
3084 | Replication thread(s) for a channel are already stopped. | Replication thread(s) for channel 'channel_1' are already stopped. |
3085 | This operation cannot be performed with a running replica SQL thread; run STOP SLAVE SQL_THREAD for the specified channel first. | This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL 'channel_1' first. |
3086 | When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START SLAVE [SQL_THREAD]'. The value of sql_replica_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_replica_skip_counter. | - |
3087 | An expression is not in the GROUP BY clause and contains a non-aggregated column which is not functionally dependent on columns in the GROUP BY clause; this is incompatible with sql_mode=only_full_group_by. | Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'db1.t1.name' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by |
3088 | In an aggregated query without a GROUP BY, an expression contains a non-aggregated column; this is incompatible with sql_mode=only_full_group_by. | In aggregated query without GROUP BY, expression #1 of SELECT list contains nonaggregated column 'db1.t1.name'; this is incompatible with sql_mode=only_full_group_by |
3089 | Updating a specific variable is deprecated and it will be made read-only in a future release. | Updating 'log_warnings' is deprecated. It will be made read-only in a future release. |
3090 | Changing a specific SQL mode is deprecated and will be removed in a future release. | Changing sql mode 'NO_AUTO_CREATE_USER' is deprecated. It will be removed in a future release. |
3091 | 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. Manual steps are required to fix this. | ...database directory /var/lib/mysql/db_to_drop; ...SET GTID_NEXT='a1b2c3d4-e5f6-11ee-8c90-0242ac120002:123'; ...DROP DATABASE db_to_drop. |
3092 | The server is not configured properly to be an active member of the group. Please see more details on error log. | - |
3093 | The START GROUP_REPLICATION command failed since the group is already running. | - |
3094 | The START GROUP_REPLICATION command failed as the applier module failed to start. | - |
3095 | 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. | - |
3096 | The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer. | - |
3097 | The START GROUP_REPLICATION command failed as there was an error when joining the communication group. | - |
3098 | The table does not comply with the requirements by an external plugin. | - |
3099 | Cannot change the value of a specific variable without the binary log format being set to ROW. | Cannot change the value of variable replica_parallel_type without binary log format as ROW. |
3100 | An error occurred on an observer member while running a replication hook. | Error on observer while running replication hook 'before_commit'. |
Error Code | Error Description | Example |
3101 | Plugin instructed the server to rollback the current transaction. | - |
3102 | The expression of a generated column contains a disallowed function (e.g., non-deterministic functions like UUID()). | Expression of generated column 'unique_id' contains a disallowed function. |
3103 | INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actions | - |
3104 | Cannot define a foreign key with a specific clause (e.g., ON UPDATE) on a generated column. | Cannot define foreign key with ON UPDATE CASCADE clause on a generated column. |
3105 | The value specified for a generated column in a table is not allowed. | The value specified for generated column 'full_name' in table 'users' is not allowed. |
3106 | A specific clause or option is not supported for generated columns. | 'DEFAULT' is not supported for generated columns. |
3107 | Generated column can refer only to generated columns defined prior to it. | - |
3108 | A column cannot be modified or dropped because it has a generated column dependency. | Column 'first_name' has a generated column dependency. |
3109 | A generated column cannot refer to an auto-increment column. | Generated column 'new_id' cannot refer to auto-increment column. |
3110 | A required feature is not available in the current MySQL build. | The 'WITH_SSL' feature is not available; you need to remove 'REQUIRE SSL' or use MySQL built with 'WITH_SSL' |
3111 | Setting the global GTID_MODE is not allowed for a specific reason. | SET @@GLOBAL.GTID_MODE = ON is not allowed because GTID_EXECUTED is not empty. |
3112 | The replication receiver thread for a channel cannot start in AUTO_POSITION mode because the server's GTID_MODE is OFF. | The replication receiver thread for channel 'ch1' cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF. |
3113 | Cannot replicate an anonymous transaction when AUTO_POSITION = 1. | Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file binlog.000123, position 4567. |
3114 | Cannot replicate an anonymous transaction when @@GLOBAL.GTID_MODE = ON. | Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file binlog.000123, position 4567. |
3115 | Cannot replicate a GTID-transaction when @@GLOBAL.GTID_MODE = OFF. | Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file binlog.000123, position 4567. |
3116 | Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency. | - |
3117 | There are ongoing transactions that violate GTID consistency. | - |
3118 | Access was denied for a user because their account is locked. | Access denied for user 'jdoe'@'localhost'. Account is locked. |
3119 | An incorrect tablespace name was provided. | Incorrect tablespace name invalid/name |
3120 | A tablespace cannot be dropped because it is not empty. | Tablespace ts_data is not empty. |
3121 | An incorrect file name was provided. | Incorrect File Name '../etc/passwd'. |
3122 | Inconsistent intersection points. | - |
3123 | Optimizer hint syntax error | - |
3124 | Unsupported MAX_EXECUTION_TIME | - |
3125 | MAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements only | - |
3126 | An optimizer hint is ignored because it is conflicting or duplicated. | Hint BNL is ignored as conflicting/duplicated |
3127 | A query block name specified in an optimizer hint was not found. | Query block name qb2 is not found for INDEX hint |
3128 | A name (e.g., table or index) specified in an optimizer hint could not be resolved. | Unresolved name t3 for JOIN_ORDER hint |
3129 | Do not modify the specified internal system table. Modifying it can lead to an inconsistent GTID state. | Please do not modify the mysql.gtid_executed table. ... |
3130 | Command not supported by pluggable protocols | - |
3131 | An incorrect locking service lock name was used. | Incorrect locking service lock name 'invalid/lock'. |
3132 | A deadlock was found when trying to get a locking service lock; try releasing locks and restarting the lock acquisition. | - |
3133 | Service lock wait timeout exceeded. | - |
3134 | A parameter exceeds the maximum number of points allowed in a geometry for a given function. | Parameter polygon exceeds the maximum number of points in a geometry (1000000) in function ST_GeomFromText. |
3135 | '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. | - |
3136 | A version token mismatch occurred. | Version token mismatch for my_token. Correct value 1.2.3 |
3137 | A specified version token was not found. | Version token my_token not found. |
3138 | A variable cannot be changed by a client that owns a GTID. Ownership is released on COMMIT or ROLLBACK. | Variable binlog_format cannot be changed by a client that owns a GTID. The client owns a1b2c3d4-...:123. Ownership is released on COMMIT or ROLLBACK. |
3139 | A specific operation cannot be performed on the specified channel. | START SLAVE cannot be performed on channel 'inactive_channel'. |
3140 | Invalid JSON text was found in a value for a specific column. | Invalid JSON text: "{'key': 'value'}" at position 1 in value for column 'json_data'. |
3141 | Invalid JSON text was found in an argument to a function. | Invalid JSON text in argument 1 to function JSON_EXTRACT: "[1, 2," at position 6. |
3142 | The JSON binary value contains invalid data. | - |
3143 | An invalid JSON path expression was used. | Invalid JSON path expression. The error is around character position 5. |
3144 | Cannot create a JSON value from a string with a non-UTF8 character set. | Cannot create a JSON value from a string with CHARACTER SET 'latin1'. |
3145 | Invalid JSON character data was provided to a function; UTF-8 is required. | Invalid JSON character data provided to function JSON_OBJECT: 'key\\xFF'; utf8 is required. |
3146 | An invalid data type was provided for a JSON argument to a function; a JSON string or JSON type is required. | Invalid data type for JSON data in argument 1 to function JSON_KEYS; a JSON string or JSON type is required. |
3147 | Cannot CAST value to JSON. | - |
3148 | A path expression must be encoded in the utf8 character set. | A path expression must be encoded in the utf8 character set. The path expression '$.ключ' is encoded in character set 'cp1251'. |
3149 | In this situation, path expressions may not contain the * and ** tokens or an array range. | - |
3150 | The JSON value is too big to be stored in a JSON column. | - |
3151 | The JSON object contains a key name that is too long. | - |
3152 | A JSON column supports indexing only via generated columns on a specified JSON path. | JSON column 'doc' supports indexing only via generated columns on a specified JSON path. |
3153 | The path expression '$' is not allowed in this context. | - |
3154 | The oneOrAll argument to a function may only take the values 'one' or 'all'. | The oneOrAll argument to JSON_REMOVE may take these values: 'one' or 'all'. |
3155 | An out-of-range JSON value was encountered during a CAST operation. | Out of range JSON value for CAST to SIGNED from column data at row 1 |
3156 | An invalid JSON value was encountered during a CAST operation. | Invalid JSON value for CAST to DATETIME from column data at row 1 |
3157 | The JSON document exceeds the maximum depth. | - |
3158 | JSON documents may not contain NULL member names. | - |
3159 | Connections using insecure transport are prohibited while --require_secure_transport=ON. | - |
3160 | No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON. | - |
3161 | The specified storage engine is disabled, and table creation is disallowed. | Storage engine MyISAM is disabled (Table creation is disallowed). |
3162 | The specified authorization ID (user or role) does not exist. | Authorization ID 'role_admin'@'%' does not exist. |
3163 | The specified authorization ID (user or role) already exists. | Authorization ID 'role_admin'@'%' already exists. |
3164 | The operation was aborted by the Audit API. | Aborted by Audit API ('my_audit_plugin';123). |
3165 | A path expression is not a path to a cell in an array. | - |
3166 | Another buffer pool resize is already in progress. | - |
3167 | A specific feature is disabled. | The 'partitioning' feature is disabled; see the documentation for 'have_partitioning' |
3168 | Server isn't available | - |
3169 | Session was killed | - |
3170 | The memory capacity for a specific buffer or operation was exceeded. | Memory capacity of 1073741824 bytes for 'sort_buffer' exceeded. Consider increasing sort_buffer_size. |
3171 | Range optimization was not done for this query. | - |
3172 | A partitioning upgrade is required for the table. | Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE sales.sales_data UPGRADE PARTITIONING |
3173 | WAIT_FOR_EXECUTED_GTID_SET cannot wait for a GTID that is owned by the current client. | The client holds ownership of the GTID a1b2c3d4-...:123. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID. |
3174 | Cannot add foreign key on the base column of indexed virtual column. | - |
3175 | Cannot create index on virtual column whose base column has foreign constraint. | - |
3176 | Do not modify the specified internal system table with an XA transaction. A non-XA transaction can be used if necessary. | Please do not modify the mysql.gtid_executed table with an XA transaction. ... |
3177 | Lock acquisition refused by storage engine. | - |
3178 | A syntax hint indicating an invalid combination of ALTER TABLE clauses. | ADD COLUMN col...VIRTUAL, ADD INDEX(col) |
3179 | Master key rotation is not supported by storage engine. | - |
3180 | An encryption key rotation error was reported by the storage engine. | Encryption key rotation error reported by SE: Key not found |
3181 | Write to binlog failed. However, master key rotation has been completed successfully. | - |
3182 | Storage engine is not available. | - |
3183 | This tablespace can't be encrypted. | - |
3184 | Invalid encryption option. | - |
3185 | Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully. | - |
3186 | Parser bailed out for this query. | - |
3187 | Cannot alter encryption attribute by inplace algorithm. | - |
3188 | A function failed because the underlying keyring service returned an error. | Function 'keyring_key_generate' failed because underlying keyring service returned an error. ... |
3189 | The database schema is old. A specific column has an incorrect length and requires a MySQL upgrade. | It seems that your db schema is old. The user column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure. |
3190 | RESET MASTER is not allowed for a specific reason. | RESET MASTER is not allowed because there are active replicas. |
3191 | The START GROUP_REPLICATION command failed since the group already has 9 members. | - |
3192 | Cannot add foreign key on the base column of stored column. | - |
3193 | Cannot complete the operation because table is referenced by another connection. | - |
3194 | The partition engine used by a table is deprecated and will be removed in a future release. Use native partitioning instead. | The partition engine, used by table 'old_db.old_table', is deprecated and will be removed in a future release. ... |
3195 | A specific SRID function is deprecated and will be replaced in a future version. An alternative is suggested. | srid(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use srid(st_aswkb(geometry), 0) instead. |
3196 | A specific SRID function is deprecated and will be replaced in a future version. An alternative is suggested. | setsrid(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use setsrid(st_aswkb(geometry), srid) instead. |
3197 | The resource manager is not able to commit the transaction branch at this time. Please retry later. | - |
3198 | A function failed for a specified reason. | Function MY_UDF failed due to: Out of memory. |
3199 | Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on slaves when replicated using statements. | - |
3200 | A User-Defined Function (UDF) failed for a specified reason. | my_udf UDF failed; invalid input |
Error Code | Error Description | Example |
3201 | Keyring migration cannot be performed due to a specific reason. | Can not perform keyring migration : Source keyring not found. |
3202 | Access is denied because the user lacks the required privileges for the operation. | Access denied; you need (at least one of) the SUPER privileges for this operation |
3203 | Reports the status of a keyring migration. | Keyring migration failed. |
3204 | The server failed to open the filter tables for a specific component (e.g., audit log). | Failed to open the audit log filter tables. |
3205 | The server failed to open a specific system table. | Failed to open 'mysql.audit_log_user' filter table. |
3206 | No keyring plugin installed. | - |
3207 | A notice that the audit log encryption password was not set and will be auto-generated. It provides instructions on how to retrieve or set it. | Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one. |
3208 | Could not create AES key. OpenSSL's EVP_BytesToKey function failed. | - |
3209 | The audit log encryption password could not be retrieved from the keyring. The existing password will continue to be used for encryption. | - |
3210 | Audit Log filtering has not been installed. | - |
3211 | A request was ignored because the user lacks the SUPER privilege or the AUDIT_ADMIN role. | Request ignored for 'user'@'localhost'. SUPER privilege or AUDIT_ADMIN role needed to perform operation |
3212 | The specified user requires the SUPER privilege or the AUDIT_ADMIN role for an operation. | SUPER privilege or AUDIT_ADMIN role required for 'user'@'localhost' user. |
3213 | Could not reinitialize audit log filters. | - |
3214 | Invalid argument type | - |
3215 | Invalid argument count | - |
3216 | audit_log plugin has not been installed using INSTALL PLUGIN syntax. | - |
3217 | Invalid "max_array_length" argument type. | - |
3218 | Invalid "max_array_length" argument value. | - |
3219 | A generic error message where the entire text is provided by a component, such as the Audit Log. | Audit Log: Filter definition is invalid. |
3220 | Filter name cannot be empty. | - |
3221 | User cannot be empty. | - |
3222 | Specified filter has not been found. | - |
3223 | First character of the user name must be alphanumeric. | - |
3224 | Invalid character in the user name. | - |
3225 | Invalid character in the host name. | - |
3226 | A warning that with the deprecated MAXDB SQL mode, TIMESTAMP is treated as DATETIME. It advises disabling this mode and using DATETIME instead. | With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead. |
3227 | A warning that using replication filters with XA transactions is unsupported and can lead to an undefined state on the replica. | The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replication slave. |
3228 | The server could not open the specified file for error logging. | Could not open file '/var/log/mysql/error.log' for error logging (Errcode: 13 - Permission denied) |
3229 | A warning that grouping by a temporal column can produce non-deterministic results in timezones with Daylight Saving Time (DST). It suggests switching to UTC. | Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query. |
3230 | The server cannot start because the specified Windows Named Pipe is already in use by another process. | Can't start server : Named Pipe "MySQL" already in use. |
3231 | The transaction's writeset size exceeds a configured limit, often related to Group Replication's group_replication_transaction_size_limit. | The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'. |
Error Code | Error Description | Example |
3500 | CREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE. | - |
3501 | An Access Control List (ACL) operation failed due to an error from the storage engine. | The ACL operation failed due to the following error from SE: errcode 1 - Operation not permitted |
3502 | The specified index algorithm is not supported by the storage engine; the default was used instead. | This storage engine does not support the HASH index algorithm, storage engine default was used instead. |
3503 | The specified database does not exist. | Database 'non_existent_db' doesn't exist |
3504 | Too many enumeration values were specified for a column. | Too many enumeration values for column status. |
3505 | An enumeration or set value is too long for the specified column. | Too long enumeration/set value for column options. |
3506 | A data dictionary object is invalid for a given reason. | Table dictionary object is invalid. (Column count mismatch) |
3507 | Failed to update a data dictionary object. | Failed to update Table dictionary object. |
3508 | The specified dictionary object ID does not exist. | Dictionary object id (12345) does not exist. |
3509 | The name provided for a data dictionary object is invalid. | Dictionary object name 'my-table' is invalid. (Contains invalid character '-') |
3510 | The specified tablespace does not exist. | Tablespace ts_project_data doesn't exist. |
3511 | The comment for a routine (procedure or function) is too long. | Comment for routine 'calculate_totals' is too long (max = 65535) |
3512 | Failed to load a specified routine. | Failed to load routine 'get_user_data'. |
3513 | Binary operands of bitwise operators must be of equal length | - |
3514 | Aggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() function | - |
3515 | Optimizer hints are not supported in the current context (e.g., within a view or subquery). | Hints aren't supported in subqueries |
3516 | A value is a geometry of an unexpected type in a given context. | point_data value is a geometry of unexpected type Polygon in ST_X. |
3517 | The server cannot parse the spatial reference system definition of the specified SRID. | Can't parse the spatial reference system definition of SRID 4326. |
3518 | The spatial reference system definition for an SRID is missing a mandatory projection parameter. | The spatial reference system definition for SRID 3857 does not specify the mandatory PROJ_PARAM_LATITUDE_OF_ORIGIN (EPSG 8801) projection parameter. |
3519 | There is no spatial reference system with the specified SRID. | There's no spatial reference system with SRID 99999. |
3520 | A function is only defined for Cartesian spatial reference systems, but an argument uses a non-Cartesian SRID. | Function ST_Distance is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID 4326, which is not Cartesian. |
3521 | A function is only defined for Cartesian spatial reference systems, but an argument uses an undefined SRID. | Function ST_Distance is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID 99999, which has not been defined. |
3522 | A primary key index cannot be invisible | - |
3523 | The specified authorization ID (user or role) does not exist. | Unknown authorization ID no_such_user@localhost |
3524 | Failed to grant a role to a user or another role. | Failed to grant 'app_reader'@'%' to 'app_user'@'localhost' |
3525 | Failed to open the security system tables (e.g., mysql.user, mysql.roles_mapping). | - |
3526 | Failed to set default roles for a user. | - |
3527 | Cannot find a schema in the specified Uniform Resource Name (URN). | Cannot find schema in specified URN: 'urn:mysql:component:my_comp/my_schema'. |
3528 | Cannot acquire a service implementation for a schema specified in a URN. | Cannot acquire scheme load service implementation for schema 'my_schema' in specified URN: 'urn:mysql:component:my_comp/my_schema'. |
3529 | Cannot load a component from the specified URN. | Cannot load component from specified URN: 'file://component_validate_password'. |
3530 | An attempt was made to revoke a role that was not granted to the specified user or role. | 'db_reader'@'%' is not granted to 'app_user'@'localhost' |
3531 | Could not revoke a role from a user or another role. | Could not revoke role from 'app_user'@'localhost' |
3532 | Renaming of a role identifier is forbidden | - |
3533 | The server cannot acquire the specified service implementation. | Cannot acquire specified service implementation: 'mysql_component_infrastructure_v1'. |
3534 | A required dependency for a component could not be satisfied. | Cannot satisfy dependency for service 'mysql_string_service' required by component 'my_custom_component'. |
3535 | Cannot register a service implementation provided by a component. | Cannot register service implementation 'my_service_v1' provided by component 'my_custom_component'. |
3536 | The initialization method provided by a component failed. | Initialization method provided by component 'file://component_validate_password' failed. |
3537 | An attempt was made to unload a component that was not loaded. | Component specified by URN 'file://non_loaded_component' to unload has not been loaded before. |
3538 | The de-initialization method provided by a component failed during unload. | De-initialization method provided by component 'file://component_validate_password' failed. |
3539 | Release of a previously acquired service implementation failed. | - |
3540 | Unregistration of a service implementation failed during component unload. | Unregistration of service implementation 'my_service_v1' provided by component 'my_custom_component' failed during unloading of the component. |
3541 | Cannot unload a component from the specified URN. | Cannot unload component from specified URN: 'file://component_that_is_in_use'. |
3542 | The Persistent Dynamic Loader was used to unload a component that it did not load. | The Persistent Dynamic Loader was used to unload a component 'my_component', but it was not used to load that component before. |
3543 | The mysql.component table is missing or has an incorrect definition. | - |
3544 | Failed to manipulate a component's persistence data in the mysql.component table. | Failed to manipulate component 'my_component' persistence data. Error code 1 from storage engine. |
3545 | A component was specified more than once in a group (e.g., in an INSTALL COMPONENT statement). | The component with specified URN: 'file://component_a' was specified in group more than once. |
3546 | The global GTID_PURGED variable cannot be changed for a specific reason. | @@GLOBAL.GTID_PURGED cannot be changed: GTID_EXECUTED is not empty. |
3547 | Can not lock user management caches for processing. | - |
3548 | There is no spatial reference system with the specified SRID. (Duplicate of 3519) | There's no spatial reference system with SRID 99999. |
3549 | Variables cannot be persisted. Please retry. | - |
3550 | A specific clause (e.g., FOR UPDATE) is not supported in Information Schema queries. | Information schema queries do not support the 'FOR UPDATE' clause. |
3551 | Unable to store dynamic statistics (e.g., histogram) into the data dictionary. | Unable to store dynamic histogram statistics into data dictionary. |
3552 | Access to a protected system schema is rejected. | Access to system schema 'mysql' is rejected. |
3553 | Access to a system tablespace is rejected. | Access to system tablespace 'innodb_system' is rejected. |
3554 | Access to a specific system object (e.g., table) is rejected. | Access to system table 'mysql.user' is rejected. |
3555 | data dictionary table (Used as a descriptive string in other errors, e.g., 3554) | - |
3556 | system table (Used as a descriptive string in other errors, e.g., 3554) | - |
3557 | table (Used as a descriptive string in other errors, e.g., 3554) | - |
3558 | An invalid option key was used in a function's options argument. | Invalid option key 'colour' in function 'my_func'. |
3559 | An invalid value was provided for an option in a function's options argument. | Invalid value 'blue' for option 'color' in function 'my_func'. |
3560 | A string is not a valid key-value pair in a function's options argument. | The string 'color=blue;size' is not a valid key = value pair in function my_func. |
3561 | The options argument in a function starts with an invalid character. | The options argument in function my_func starts with the invalid character ';'. |
3562 | The options argument in a function ends with an invalid character. | The options argument in function my_func ends with the invalid character ';'. |
3563 | The options argument in a function contains an invalid character sequence. | The options argument in function my_func contains the invalid character sequence '=='. |
3564 | A duplicate option key was found in a function's options argument. | Duplicate option key 'color' in funtion 'my_func'. |
3565 | There is no spatial reference system with the specified SRID, so the axis order is unknown. | There's no spatial reference system with SRID 99999. The axis order is unknown. |
3566 | Access to a native (built-in) function is rejected. | Access to native function 'inet6_aton' is rejected. |
3567 | The requested value for the next binary log index is out of range. | The requested value '0' for the next binary log index is out of range. Please use a value between '1' and '4294967295'. |
3568 | A table name in a locking clause ( LOCK IN SHARE MODE, FOR UPDATE) could not be resolved. | Unresolved table name t2 in locking clause. |
3569 | A table appears in multiple locking clauses in the same statement. | Table t1 appears in multiple locking clauses. |
3570 | Statement is unsafe for replication because it uses SKIP LOCKED, making the set of inserted values non-deterministic. | - |
3571 | Statement is unsafe for replication because it uses NOWAIT, making its success or failure non-deterministic. | - |
3572 | Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set. | - |
3573 | A recursive Common Table Expression (CTE) is missing a UNION or UNION ALL. | Recursive Common Table Expression 'cte_name' should contain a UNION |
3574 | A recursive CTE must have one or more non-recursive query blocks followed by one or more recursive ones. | Recursive Common Table Expression 'cte_name' should have one or more non-recursive query blocks followed by one or more recursive ones |
3575 | The recursive query block of a recursive CTE cannot contain aggregation or window functions. | Recursive Common Table Expression 'cte_name' can contain neither aggregation nor window functions in recursive query block |
3576 | In a recursive CTE, the recursive table cannot be on the right side of a LEFT JOIN or have its join order forced. | In recursive query block of Recursive Common Table Expression 'cte_name', the recursive table must neither be in the right argument of a LEFT JOIN... |
3577 | In a recursive CTE, the recursive table must be referenced only once and not in any subquery. | In recursive query block of Recursive Common Table Expression 'cte_name', the recursive table must be referenced only once, and not in any subquery |
3578 | A specific feature requires the internal temporary disk storage engine to be InnoDB. | 'Recursive CTE' requires @@internal_tmp_disk_storage_engine=InnoDB |
3579 | A window name used in an OVER clause is not defined in the WINDOW clause. | Window name 'w2' is not defined. |
3580 | There is a circularity in the window dependency graph (e.g., w1 inherits from w2, and w2 inherits from w1). | - |
3581 | A window which depends on (inherits from) another cannot define its own partitioning ( PARTITION BY) clause. | - |
3582 | A window that has a frame definition ( ROWS or RANGE) cannot be referenced by another window. | Window 'w1' has a frame definition, so cannot be referenced by another window. |
3583 | A window cannot inherit from another window if both contain an ORDER BY clause. | Window 'w2' cannot inherit 'w1' since both contain an ORDER BY clause. |
3584 | A window frame start cannot be UNBOUNDED FOLLOWING. | Window 'w1': frame start cannot be UNBOUNDED FOLLOWING. |
3585 | A window frame end cannot be UNBOUNDED PRECEDING. | Window 'w1': frame end cannot be UNBOUNDED PRECEDING. |
3586 | A window frame start or end value is negative, NULL, or not an integer. | Window 'w1': frame start or end is negative, NULL or of non-integral type |
3587 | A RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression of a numeric or temporal type. | Window 'w1' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal type |
3588 | A RANGE frame with a datetime ORDER BY expression requires an INTERVAL value for its bounds. | Window 'w1' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed. |
3589 | A RANGE frame with a numeric ORDER BY expression cannot use an INTERVAL value for its bounds. | Window 'w1' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed. |
3590 | A window has a non-constant frame bound (e.g., based on a column value). | Window 'w1' has a non-constant frame bound. |
3591 | A window name is defined more than once in the WINDOW clause. | Window 'w1' is defined twice. |
3592 | A window's ORDER BY or PARTITION BY clause uses a legacy column position (e.g., ORDER BY 1), which is not supported. | Window 'w1': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression. |
3593 | A window function was used in a context where it is not permitted (e.g., WHERE or GROUP BY clause). | You cannot use the window function 'ROW_NUMBER' in this context.' |
3594 | An alias of an expression containing a window function cannot be used in certain contexts (e.g., WHERE clause). | You cannot use the alias 'rn' of an expression containing a window function in this context.' |
3595 | You cannot nest a window function within the specification of another window. | You cannot nest a window function in the specification of window 'w1'. |
3596 | INTERVAL can only be used with RANGE frames, not ROWS frames. | Window 'w1': INTERVAL can only be used with RANGE frames. |
3597 | ASC or DESC with GROUP BY is not allowed when window functions are present; sorting should be specified in the ORDER BY clause. | - |
3598 | To get information about window functions use EXPLAIN FORMAT=JSON | - |
3599 | A specific window function ignores the frame clause and always aggregates over the entire partition. | Window function 'NTILE' ignores the frame clause of window 'w1' and aggregates over the whole partition |
3600 | Windowing requires the internal temporary memory storage engine to be TempTable. | Windowing requires @@internal_tmp_mem_storage_engine=TempTable. |
Error Code | Error Description | Example |
3601 | A function was called with too many arguments. | Too many arguments for function LPAD: 4; maximum allowed is 3. |
3602 | The GROUPING() function was used with an argument (column) that is not part of the GROUP BY clause. | Argument #1 of GROUPING function is not in GROUP BY |
3603 | The comment provided for a tablespace exceeds the maximum allowed length. | Comment for tablespace 'ts_archive' is too long (max = 2048) |
3604 | The storage engine cannot drop the specified table. | Storage engine can't drop table 'db1.t1' |
3605 | The storage engine cannot drop a table because it is missing. It suggests using DROP TABLE IF EXISTS. | Storage engine can't drop table 'db1.t1' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary. |
3606 | A duplicate file name was specified for a tablespace. | Duplicate file name for tablespace 'ts_data' |
3607 | The database was dropped, but its directory could not be removed from the filesystem. This requires manual intervention. | Problem while dropping database. Can't remove database directory (/var/lib/mysql/old_db). Please remove it manually. |
3608 | No Serialized Dictionary Information (SDI) files matched the specified pattern during an import operation. | No SDI files matched the pattern '*.sdi' |
3609 | During an import from SDI, a referenced schema (database) does not exist. | Schema 'legacy_db', referenced in SDI, does not exist. |
3610 | During an import from SDI, a referenced table already exists in the target schema. | Table 'prod_db.customers', referenced in SDI, already exists. |
3611 | The SQL engine version in the imported SDI file is not compatible with the current server's version. | Imported sqlengine_version (80015) is not compatible with current (80025) |
3612 | The data dictionary version in the imported SDI file is not compatible with the current server's version. | Imported dd version (1) is not compatible with current (2) |
3613 | The SDI version in the imported file is not compatible with the current server's version. | Imported sdi version (1) is not compatible with current (2) |
3614 | An invalid number of arguments was provided for an optimizer hint. | Invalid number of arguments for hint NO_INDEX |
3615 | A variable does not exist in the TDMetaCluster. | Variable some_var does not exist in TDMetaCluster |
3616 | A longitude value provided to a geospatial function is outside the valid range of (-180, 180]. | Longitude 185.000000 is out of range in function ST_GeomFromText. It must be within (-180.000000, 180.000000]. |
3617 | A latitude value provided to a geospatial function is outside the valid range of [-90, 90]. | Latitude -95.000000 is out of range in function ST_GeomFromText. It must be within [-90.000000, 90.000000]. |
3618 | A specific function has not been implemented for geographic spatial reference systems. | ST_IsSimple(geometry) has not been implemented for geographic spatial reference systems. |
3619 | An illegal privilege level was specified for an operation. | Illegal privilege level specified for GRANT |
3620 | Access to a system view in the INFORMATION_SCHEMA is rejected. | Access to system view INFORMATION_SCHEMA.'PROCESSLIST' is rejected. |
3621 | A log-filter component encountered a parsing error. | The log-filter component "my_filter" got confused at "some invalid rule" ... |
3622 | The expression used for table partitioning is too long. | - |
3623 | DROP FUNCTION cannot be used to drop a dynamically registered User-Defined Function (UDF). | - |
3624 | The server was unable to store new column statistics (e.g., a histogram) in the data dictionary. | Unable to store column statistics for column 'user_id' in table 'my_db'.'orders' |
3625 | The server was unable to update existing column statistics in the data dictionary. | Unable to update column statistics for column 'user_id' in table 'my_db'.'orders' |
3626 | The server was unable to remove column statistics from the data dictionary. | Unable to remove column statistics for column 'user_id' in table 'my_db'.'orders' |
3627 | The server was unable to build a histogram for the specified column. | Unable to build histogram statistics for column 'user_id' in table 'my_db'.'orders' |
3628 | An attempt was made to revoke or drop a mandatory role. | The role mysql.session_admin is a mandatory role and can't be revoked or dropped. ... |
3629 | A tablespace does not have a file with the specified name. | Tablespace 'ts_data' does not have a file named 'data02.ibd' |
3630 | Access is denied because the user lacks the required privileges for the operation. (More specific than 3202) | Access denied; you need (at least one of) the CLONE_ADMIN privileges for this operation |
3631 | The specified command requires the SUPER privilege. | You need the SUPER privilege for command 'CLONE' |
3632 | A specified path is invalid because it is within the current data directory. | Path is within the current data directory '/var/lib/mysql/' |
3633 | A CLONE operation failed because a concurrent DDL statement was running. The operation should be retried. | - |
3634 | Too many concurrent clone operations are running. | Too many concurrent clone operations. Maximum allowed - 1. |
3635 | A table involved in a transaction does not comply with requirements set by an external plugin (e.g., Group Replication). | The table in transaction t1 does not comply with the requirements by an external plugin. |
3636 | A recursive CTE aborted after exceeding the maximum number of iterations defined by cte_max_recursion_depth. | Recursive query aborted after 1001 iterations. Try increasing @@cte_max_recursion_depth to a larger value. |
3637 | The SET_VAR hint cannot be used to set the specified variable. | Variable autocommit cannot be set using SET_VAR hint. |
3638 | A password change was rejected because the new password violates the password history policy (e.g., it has been used recently). | Cannot use these credentials for 'user'@'host' because they contradict the password history policy |
3639 | Password history clauses were ignored for a user because their authentication plugin does not support this feature. | Non-zero password history clauses ignored for user 'legacy_user'@'localhost' as its authentication plugin mysql_native_password does not support password history |
3640 | The client does not support a feature required by the server (e.g., a specific authentication method). | The client doesn't support caching_sha2_password |
3641 | A tablespace was skipped during an operation (like CLONE) because a concurrent DDL statement was modifying its definition. | Tablespace 'ts_temp' was skipped since its definition is being modified by concurrent DDL statement |
3642 | The storage engine specified in an operation does not match the stored engine for the tablespace. | Engine 'MyISAM' does not match stored engine 'InnoDB' for tablespace 'ts_data' |
3643 | The SRID of a geometry being inserted/updated does not match the SRID defined for the column. | The SRID of the geometry does not match the SRID of the column 'location'. The SRID of the geometry is 4326, but the SRID of the column is 3857. ... |
3644 | The SRID of a column cannot be changed because a spatial index exists on it. | The SRID specification on the column 'location' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification. |
3645 | A warning that binlog_row_value_options will be ignored when partial JSON updates are enabled. | When binlog_row_update=PARTIAL_JSON, the option binlog_row_value_options=PARTIAL_JSON will be ignored and updates will be written in full format to binary log. |
3646 | A warning that log_bin_use_v1_row_events will be ignored when partial JSON updates are enabled. | When binlog_row_update=PARTIAL_JSON, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log. |
3647 | A warning about the limited effectiveness of binlog_row_value_options when partial JSON updates are enabled. | When binlog_row_update=PARTIAL_JSON, the option binlog_row_value_options=PARTIAL_JSON will be used only for the after-image. ... |
3648 | An error occurred while applying a JSON diff during replication. | Could not apply JSON diff in table mydb.docs, column json_col. |
3649 | A corrupted JSON diff was encountered during replication. | Corrupted JSON diff for table mydb.docs, column json_col. |
3650 | The specified Resource Group already exists. | Resource Group 'BatchJobs' exists |
3651 | The specified Resource Group does not exist. | Resource Group 'WebUsers' does not exist. |
3652 | An invalid CPU ID was specified for a resource group. | Invalid cpu id 99 |
3653 | An invalid VCPU range was specified for a resource group. | Invalid VCPU range 8-4 |
3654 | An invalid thread priority value was provided for a resource group. | Invalid thread priority value 20 for BatchJobs resource group ALTER. Allowed range is [-20, 19]. |
3655 | A specific operation is not allowed on a resource group. | DROP operation is disallowed on SYS_default |
3656 | The resource group is busy and cannot be modified or dropped. | Resource group UserThreads is busy. |
3657 | The operation failed because the resource group is disabled. | Resource group BatchJobs is disabled. |
3658 | A feature is unsupported for a given reason. | Feature VCPU is unsupported (not available on this platform). |
3659 | An attribute was ignored for a given reason. | Attribute THREAD_PRIORITY is ignored (not available on this platform). |
3660 | An invalid thread ID was provided. | Invalid thread id (99999). |
3661 | Unable to bind a thread to a resource group. | Unable to bind resource group WebUsers with thread id (123). (Thread not found). |
3662 | The FORCE option is invalid because the DISABLE option was not specified. | - |
3663 | A command (e.g., ALTER INSTANCE) encountered a failure. | The ALTER INSTANCE command encountered a failure. RELOAD TLS failed. |
3664 | Failed to perform an operation (create/update/drop) on an SDI in a tablespace. | Failed to create SDI 'db1.t1' in tablespace 'ts1'. |
3665 | A column in a JSON_TABLE requires a value, but none was found in the JSON document for a given row. | Missing value for JSON_TABLE column 'product_name' |
3666 | An attempt was made to store a JSON array or object in a scalar column defined by JSON_TABLE. | Can't store an array or an object in the scalar JSON_TABLE column 'price' |
3667 | Every table function must have an alias | - |
3668 | LATERAL references made by a table function must use INNER JOIN or LEFT JOIN. | INNER or LEFT JOIN must be used for LATERAL references made by 'JSON_TABLE' |
3669 | A value is out of range for a column defined by JSON_TABLE. | Value is out of range for JSON_TABLE's column 'quantity' |
3670 | More than the supported number of NESTED PATH clauses were used in a JSON_TABLE. | More than supported 64 NESTED PATHs were found in JSON_TABLE 't1' |
3671 | The selected authentication method does not support password expiration. | The selected authentication method auth_socket does not support password expiration |
3672 | Invalid GeoJSON data was provided; the 'crs' member must be in the top-level object. | Invalid GeoJSON data provided to function ST_GeomFromGeoJSON: Member 'crs' must be specified in the top level object. |
3673 | A column cannot be null. (Often seen with JSON_TABLE where a path does not exist and no default is provided). | Column 'id' cannot be null |
3674 | A warning that a spatial index will not be used because the column lacks an SRID attribute. | The spatial index on column 'coords' will not be used by the query optimizer since the column does not have an SRID attribute. ... |
3675 | A CREATE TABLE or CREATE TABLESPACE operation failed because the disk is full. | Create table/tablespace 'new_db.new_table' failed, as disk is full |
3676 | Could not parse the argument to a digest function (e.g., STATEMENT_DIGEST). | Could not parse argument to digest function: "SELECT * FROM t1 WHERE". |
3677 | Could not parse the argument to a digest function. (Generic version of 3676). | - |
3678 | A schema directory already exists, preventing creation of a new schema with the same name. This requires manual resolution. | Schema directory 'my_db' already exists. This must be resolved manually (e.g. by moving the schema directory to another location). |
3679 | The schema directory does not exist. | Schema directory 'my_db' does not exist |
3680 | Failed to create a schema directory due to a filesystem error. | Failed to create schema directory 'new_db' (errno: 13 - Permission denied) |
3681 | A schema does not exist in the data dictionary, but its directory was found on disk. This inconsistency must be resolved manually. | Schema 'my_db' does not exist, but schema directory 'my_db' was found. This must be resolved manually... |
3682 | A geospatial function is only defined for specific SRIDs (typically 0 for Cartesian and 4326 for geographic). | Function ST_Distance_Sphere is only defined for SRID 0 and SRID 4326. |
3683 | A warning that the deprecated expire_logs_days and current binlog_expire_logs_seconds variables cannot be used together. | The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds... |
3684 | The result string is larger than the result buffer. | - |
3685 | An illegal argument was passed to a regular expression function. | - |
3686 | An index was out of bounds in a regular expression search. | - |
3687 | An internal error occurred in the regular expression library. | - |
3688 | A syntax error was found in a regular expression pattern. | Syntax error in regular expression on line 1, character 5. |
3689 | An unrecognized escape sequence was used in a regular expression. | - |
3690 | A regular expression contains a feature not implemented in the current library version. | - |
3691 | A regular expression contains mismatched parentheses. | - |
3692 | A regular expression contains an incorrect quantifier interval like {min,max}. | - |
3693 | A regular expression contains a {min,max} interval where the maximum is less than the minimum. | - |
3694 | An invalid back-reference was used in a regular expression. | - |
3695 | A look-behind assertion in a regular expression exceeds the implementation's limit. | - |
3696 | A regular expression contains an unclosed bracket expression (e.g., [a-z). | - |
3697 | A regular expression contains a character range where the start character comes after the end character (e.g., [z-a]). | - |
3698 | The regular expression engine's backtrack stack overflowed, often due to a very complex pattern on a long string. | - |
3699 | A regular expression match exceeded its timeout limit ( regexp_time_limit). | - |
3700 | A regular expression pattern exceeds internal limits on size or complexity. | - |
Error Code | Error Description | Example |
3701 | A configuration value (e.g., for log_error_services) has a syntax error or references a component that is not installed or listed correctly. | Value for log_error_services got confusing at or around "log_filter_dragon". Syntax may be wrong... |
3702 | A warning that setting a logging pipeline (like log_error_services) to an empty value will disable that type of logging. | Setting an empty log_error_services pipeline disables error logging! |
3703 | A generic error message from a log filter component, indicating a problem with a specific filter. | filter my_custom_filter: Rule is invalid |
3704 | A specific geospatial function is not implemented for Cartesian (flat-earth) spatial reference systems. | ST_Distance_Sphere(point) has not been implemented for Cartesian spatial reference systems. |
3705 | A specific geospatial function is not implemented for projected spatial reference systems. | ST_SomeFunction(polygon) has not been implemented for projected spatial reference systems. |
3706 | A function that takes a radius argument was given a non-positive value. | Invalid radius provided to function ST_Buffer: Radius must be greater than zero. |
3707 | The RESTART command failed for a specific reason. | Restart server failed (Permission denied). |
3708 | When creating or altering a Spatial Reference System (SRS), a required attribute is missing. | Missing mandatory attribute NAME. |
3709 | When creating or altering an SRS, an attribute was defined more than once. | Multiple definitions of attribute AUTHORITY. |
3710 | The spatial reference system name can't be an empty string or start or end with whitespace. | - |
3711 | The organization name for an SRS can't be an empty string or start or end with whitespace. | - |
3712 | An attempt was made to create an SRS with an SRID that is already in use. | There is already a spatial reference system with SRID 4326. |
3713 | An attempt was made to create an SRS with an SRID that is already in use. (Duplicate of 3712) | There is already a spatial reference system with SRID 3857. |
3714 | SRID 0 is a special system value and cannot be altered. | - |
3715 | A warning or error when trying to use an SRID from a range reserved for MySQL internal use. | The SRID range [4294967295, 4294967295] has been reserved for system use... |
3716 | An attempt to modify or drop an SRS failed because it is currently being used by one or more table columns. | Can't modify SRID 3857. There is at least one column depending on it. |
3717 | An attribute for an SRS definition contains an invalid character. | Invalid character in attribute NAME. |
3718 | The value for an SRS attribute exceeds its maximum allowed length. | Attribute NAME is too long. The maximum length is 64 characters. |
3719 | A warning that the utf8 alias will point to utf8mb4 in a future release, and utf8mb4 should be used for clarity. | 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release... |
3720 | A warning that national character types imply utf8mb3, which will change to utf8mb4 in the future. | NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release... |
3721 | An invalid default collation was specified where a specific utf8mb4 collation was expected. | Invalid default collation latin1_swedish_ci: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected |
3722 | The server failed to collect statistics or metadata for a column for a specific reason. | Unable to collect information for column 'data': Column is of a type that is not analyzable. |
3723 | An attempt was made to create a table in a tablespace reserved for system use (e.g., the mysql tablespace). | The table 'my_table' may not be created in the reserved tablespace 'mysql'. |
3724 | A system variable or option cannot be set in the current context (e.g., at runtime). | This option cannot be set at runtime. |
3725 | A warning about a potential replication divergence because an atomic DDL statement failed differently on the source and replica. | - |
3726 | A function requires a geographic SRS (like 4326), but was given data with a non-geographic SRID. | Function ST_Distance_Sphere is only defined for geographic spatial reference systems, but one of its arguments is in SRID 0, which is not geographic. |
3727 | A geospatial function failed because a polygon argument was too large (e.g., it covered more than a hemisphere). | Function ST_Area encountered a polygon that was too large. Polygons must cover less than half the planet. |
3728 | Spatial indexes can't be primary or unique indexes. | - |
3729 | An unsupported index type (like HASH) was specified for a spatial index. | The index type HASH is not supported for spatial indexes. |
3730 | An attempt to drop a table failed because it is the referenced (parent) table in a foreign key constraint. | Cannot drop table 'countries' referenced by a foreign key constraint 'fk_city_country' on table 'cities'. |
3731 | A geometry value passed to a function has a longitude outside the valid range of (-180, 180]. | A parameter of function ST_GeomFromText contains a geometry with longitude 190.000000, which is out of range... |
3732 | A geometry value passed to a function has a latitude outside the valid range of [-90, 90]. | A parameter of function ST_GeomFromText contains a geometry with latitude -91.000000, which is out of range... |
3733 | A foreign key constraint cannot be defined on a virtual (generated) column. | Foreign key 'fk_order_user' uses virtual column 'user_id_hash' which is not supported. |
3734 | A foreign key constraint could not be created because the referenced column does not exist in the parent table. | Failed to add the foreign key constraint. Missing column 'id' for constraint 'fk_orders_customer' in the referenced table 'customers' |
3735 | An error log suppression rule could not be added, either because the rule set is full or the error code is invalid. | log_filter_internal: Could not add suppression rule for code "MY1001". Rule-set may be full... |
3736 | The axes defined for a geographic SRS are invalid. One must be latitudinal (N/S) and the other longitudinal (E/W). | The spatial reference system definition for SRID 4326 specifies invalid geographic axes 'NORTH' and 'NORTH'... |
3737 | When defining an ellipsoid for an SRS, the semi-major axis must be a positive number. | - |
3738 | An invalid inverse flattening value was provided for an SRS ellipsoid definition. | - |
3739 | When defining an SRS, the conversion factor for the angular unit must be a positive number. | - |
3740 | An invalid prime meridian value was provided for an SRS definition. | - |
3741 | Coordinate transformation from the specified source SRID is not supported. | Transformation from SRID 99999 is not supported. |
3742 | Coordinate transformation to the specified target SRID is not supported. | Transformation to SRID 99999 is not supported. |
3743 | Transformation is not possible because the source SRS lacks a TOWGS84 clause defining its relationship to the WGS84 datum. | Transformation from SRID 32632 is not supported. The spatial reference system has no TOWGS84 clause. |
3744 | Transformation is not possible because the target SRS lacks a TOWGS84 clause. | Transformation to SRID 32632 is not supported. The spatial reference system has no TOWGS84 clause. |
3745 | Cannot change the session's binary log format while temporary tables exist in that session. | - |
3746 | Cannot change the global binary log format while a replica has open temporary tables. | - |
3747 | Cannot change the global binary log format while a replica's SQL thread is running. | - |
3748 | With GTIDs enabled and statement-based logging, temporary table operations are not allowed inside transactions. | Statement violates GTID consistency: CREATE TEMPORARY TABLE ... are not allowed inside a transaction ... when @@session.binlog_format=STATEMENT. |
3749 | An internal error related to XA transactions where a metadata lock backup failed when a client disconnected. | - |
3750 | The operation is blocked because sql_require_primary_key is enabled and the table lacks a primary key. | Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. |
3751 | During an insert or update, the result of a functional index expression was truncated. | Data truncated for functional index 'idx_name_upper' at row 1 |
3752 | The result of a functional index expression was out of range for the index's data type. | Value is out of range for functional index 'idx_calc_value' at row 1 |
3753 | Functional indexes are not supported on expressions that return JSON or GEOMETRY types. | - |
3754 | A functional index expression cannot include an AUTO_INCREMENT column. | Functional index 'idx_id_plus_one' cannot refer to an auto-increment column. |
3755 | A column cannot be dropped because it is part of an expression in a functional index. | Cannot drop column 'first_name' because it is used by a functional index... |
3756 | A PRIMARY KEY cannot be defined on an expression (i.e., be a functional index). | - |
3757 | Functional indexes are not supported on expressions that return BLOB or TEXT types. | - |
3758 | The expression for a functional index uses a function that is not deterministic or is otherwise disallowed. | Expression of functional index 'idx_rand' contains a disallowed function. |
3759 | A FULLTEXT index cannot be created on an expression. | - |
3760 | A SPATIAL index cannot be created on an expression. | - |
3761 | The table's storage engine does not support functional indexes on the given expression. | The used storage engine cannot index the expression 'UPPER(name)'. |
3762 | The expression for a functional index is just a bare column, so a regular index should be used instead. | - |
3763 | A generated column's expression uses a disallowed function (e.g., non-deterministic). | Expression of generated column 'rand_val' contains a disallowed function: RAND. |
3764 | A generated column's expression cannot refer to a whole row value. | - |
3765 | A generated column's expression cannot use user or system variables. | - |
3766 | A column cannot be dropped or renamed because another column's DEFAULT expression depends on it. | Column 'created_at' of table 'logs' has a default value expression dependency and cannot be dropped or renamed. |
3767 | A forward reference in a DEFAULT expression is disallowed if the referenced column is generated or has a default expression itself. | - |
3768 | A DEFAULT expression cannot reference an AUTO_INCREMENT column. | - |
3769 | A DEFAULT expression uses a non-deterministic or otherwise disallowed function. | Default value expression of column 'c1' contains a disallowed function. |
3770 | A DEFAULT expression uses a specific disallowed function. | Default value expression of column 'c1' contains a disallowed function: UUID. |
3771 | A DEFAULT expression cannot refer to a whole row value. | - |
3772 | A DEFAULT expression cannot use user or system variables. | - |
3773 | The DEFAULT() function cannot be used within another column's DEFAULT expression. | - |
3774 | A specific construct (like a subquery) is not allowed in a DEFAULT expression. | 'Subquery' is not supported for default value expressions. |
3775 | Adding a column with a default expression is unsafe for GTID-based replication. | - |
3776 | ALTER TABLE ... ENGINE= failed because the table has or is referenced by a foreign key. | - |
3777 | A warning that using := to set variables inside a query is deprecated. | - |
3778 | A warning about using a collation belonging to the deprecated utf8mb3 character set. | 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4... |
3779 | A warning that using nested comment syntax (e.g., /* ... /* ... */ ... */) is deprecated. | - |
3780 | The data types or character sets/collations of the columns in a foreign key relationship are not compatible. | Referencing column 'user_id' and referenced column 'id' in foreign key constraint 'fk_posts_users' are incompatible. |
3781 | A client statement was held during a Group Replication primary changeover and timed out while the new primary was catching up. | - |
3782 | A client statement held during a Group Replication primary changeover was aborted because the plugin was shut down or the thread was killed. | - |
3783 | A client statement held during a Group Replication primary changeover was aborted because the member entered an error state. | - |
3784 | A keyring operation failed because a key could not be fetched. Suggests checking if the keyring plugin is loaded. | - |
3785 | A specific key could not be found in the keyring. | - |
3786 | A key was retrieved from the keyring, but it was corrupted or had an invalid format. | - |
3787 | An error occurred while trying to read the encryption header of a binary log or relay log. | Error reading a replication log encryption header: Corrupted header. |
3788 | After changing binlog_encryption, the automatic log rotation failed and requires manual intervention. | - |
3789 | An attempt to create a keyring key failed because a key with that ID already exists unexpectedly. | Key mysql.binlog.12345 exists unexpected. |
3790 | Key generation for a feature like binlog encryption failed, likely because the keyring plugin is not loaded. | - |
3791 | Storing a newly generated key in the keyring failed. | - |
3792 | Removing a key from the keyring failed. | - |
3793 | Setting binlog_encryption failed for a specific reason. | Failed to change binlog_encryption value. Failed to generate new binlog master key. |
3794 | On startup, the server could not retrieve the binlog encryption key from the keyring. | - |
3795 | A warning that changing the slow log format has no effect if logging is configured to a table instead of a file. | - |
3796 | SET group_replication_consistency was attempted when the Group Replication member was not in a valid state (e.g., not ONLINE). | - |
3797 | A transaction with BEFORE consistency level failed while waiting for preceding transactions to be certified by the group. | - |
3798 | An error occurred during the COMMIT phase for a transaction with AFTER consistency level. | - |
3799 | A new transaction was attempted while the Group Replication plugin was in the process of shutting down. | - |
3800 | A functional index expression cannot refer to a whole row value. | - |
Error Code | Error Description | Example |
3801 | Encryption of binary log content failed for a specific reason. | Failed to encrypt content to write into binlog file: Keyring service is not available. |
3802 | An operation that requires Page Tracking was attempted before it was started. | - |
3803 | The specified LSN (Log Sequence Number) range was not being tracked. | - |
3804 | A data purge operation cannot be performed while a CLONE operation is in progress. | - |
3805 | The binary log master key cannot be rotated if binary log encryption is disabled. | - |
3806 | The server failed to recover the binlog master key due to an inconsistent sequence of key numbers. | Unable to recover binary log master key, the combination of new_master_key_seqno=3, master_key_seqno=2 and old_master_key_seqno=2 are wrong. |
3807 | A keyring operation for the binlog master key failed, leaving the old key in use and preventing rotation. | Failed to operate binary log master key on keyring, please check if keyring is loaded... |
3808 | Log rotation failed for some files, but a new master key was generated and will be used for future logs. | Failed to rotate one or more binary or relay log files. A new binary log master key was generated... |
3809 | An error occurred during key rotation, but a new key was generated and will be used for future logs. | Keyring operation failed. A new binary log master key was generated and will be used to encrypt new binary and relay log files... |
3810 | Cleanup of old, unused binlog encryption keys from the keyring failed and will be retried later. | Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded... |
3811 | Cleanup of an auxiliary key used during key rotation failed and will be retried later. | Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded... |
3812 | A CHECK constraint expression must evaluate to a boolean (TRUE, FALSE, or UNKNOWN) value, not a number or string. | An expression of non-boolean type specified to a check constraint 'chk_price'. |
3813 | A CHECK constraint defined at the column level cannot reference other columns in the table. | Column check constraint 'chk_dates' references other column. |
3814 | A CHECK constraint expression uses a specific function that is not allowed (e.g., non-deterministic functions). | An expression of a check constraint 'chk_id' contains disallowed function: UUID. |
3815 | A CHECK constraint expression uses a function that is not allowed. | An expression of a check constraint 'chk_rand' contains disallowed function. |
3816 | A CHECK constraint expression cannot refer to user or system variables. | - |
3817 | A CHECK constraint expression cannot refer to a whole row value. | - |
3818 | A CHECK constraint expression cannot refer to an AUTO_INCREMENT column. | - |
3819 | An INSERT or UPDATE operation was rejected because the new data would violate a CHECK constraint. | Check constraint 'chk_age' is violated. |
3820 | A CHECK constraint refers to a column that does not exist in the table. | Check constraint 'chk_col' refers to non-existing column 'non_existent_col'. |
3821 | An ALTER TABLE ... DROP CHECK statement specified a constraint name that does not exist. | Check constraint 'chk_old' is not found in the table. |
3822 | An attempt was made to create a CHECK constraint with a name that is already in use by another constraint in the same table. | Duplicate check constraint name 'chk_data'. |
3823 | A column cannot be used in a CHECK constraint if it is also part of a foreign key's referential action (e.g., ON UPDATE SET NULL). | Column 'status' cannot be used in a check constraint 'chk_status': needed in a foreign key constraint 'fk_ref' referential action. |
3824 | A warning issued when creating an unencrypted table in a database that has default encryption enabled. | - |
3825 | There is a mismatch between the table's encryption status and its tablespace's encryption status. | Request to create encrypted table while using an unencrypted tablespace. |
3826 | A user tried to create a table with an encryption setting different from the database default without the necessary privileges. | Table encryption differ from its database default encryption, and user doesn't have enough privilege. |
3827 | A user tried to set a database's default encryption to a value different from the server default without the necessary privileges. | Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege. |
3828 | A user tried to create a tablespace with an encryption setting different from the server default without the necessary privileges. | Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege. |
3829 | A tablespace cannot be encrypted because it contains a table from a schema with default encryption turned off, and the user lacks privileges. | - |
3830 | A tablespace cannot be decrypted because it contains a table from a schema with default encryption turned on, and the user lacks privileges. | - |
3831 | The server could not determine the type (e.g., general, undo, temporary) of the specified tablespace. | Cannot determine the type of the tablespace named 'unknown_ts'. |
3832 | An operation like ALTER TABLE ... TABLESPACE failed because the source tablespace is encrypted but the target is not. | - |
3833 | The ENCRYPTION clause cannot be used with a specific type of tablespace (e.g., temporary). | ENCRYPTION clause is not valid for temporary tablespace. |
3834 | A statement contains multiple instances of the same clause (e.g., ENCRYPTION). | Multiple ENCRYPTION clauses |
3835 | The GRANT ... AS user syntax is only supported for global-level privileges (ON *.*). | - |
3836 | A GRANT ... AS statement failed because a specified user does not exist or the current user lacks proxy privileges. | - |
3837 | A column cannot be dropped or renamed because it is used in a functional index. | Column 'name' has a functional index dependency and cannot be dropped or renamed. |
3838 | A warning that a specific plugin should not be loaded with the --early-plugin-load option. | Plugin 'keyring_file' is not to be used as an "early" plugin... |
3839 | The innodb_redo_log_archive_start() function was called with a path, which is not allowed. | - |
3840 | Starting redo log archiving timed out. | - |
3841 | Redo log archiving cannot start because the innodb_redo_log_archive_dirs variable is not set. | - |
3842 | The label provided to innodb_redo_log_archive_start() was not found in innodb_redo_log_archive_dirs. | Label 'backup1' not found in server variable 'innodb_redo_log_archive_dirs' |
3843 | The innodb_redo_log_archive_dirs variable has a malformed entry (a label without a directory). | Directory is empty after label 'backup1' in server variable 'innodb_redo_log_archive_dirs' |
3844 | The directory specified for redo log archiving does not exist or is not a directory. | Redo log archive directory '/mnt/archive/redo' does not exist or is not a directory |
3845 | The redo log archive directory cannot be inside, under, or contain the server's data, log, or binary log directories. | Redo log archive directory '/var/lib/mysql/archive' is in, under, or over server directory '/var/lib/mysql' - 'datadir' |
3846 | The redo log archive directory has insecure permissions (world-writable). | Redo log archive directory '/mnt/archive' is accessible to all OS users |
3847 | The server failed to create a redo log archive file due to an OS error. | Cannot create redo log archive file '.../archive-log.0' (OS errno: 13 - Permission denied) |
3848 | An attempt was made to start redo log archiving when it is already active. | Redo log archiving has been started on '.../archive-log.0' - Call innodb_redo_log_archive_stop() first |
3849 | An attempt was made to stop redo log archiving when it is not active. | - |
3850 | Redo log archiving failed for a specific reason. | Redo log archiving failed: Disk full |
3851 | A session tried to stop redo log archiving that was started by a different session. | - |
3852 | A regular expression function encountered a syntax error or other problem in the pattern. | Regex error: Unmatched parenthesis in function REGEXP_LIKE. |
3853 | An argument to a JSON function has an incorrect JSON type (e.g., passing an array where an object is required). | Invalid JSON type in argument 1 to function JSON_KEYS; an object is required. |
3854 | A string could not be converted between two character sets. | Cannot convert string '...' from utf8mb4 to gbk |
3855 | A column cannot be dropped or renamed because it is used in the table's partitioning function. | Column 'order_date' has a partitioning function dependency and cannot be dropped or renamed. |
3856 | A warning that using AUTO_INCREMENT on FLOAT or DOUBLE columns is deprecated. | AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated... Consider removing AUTO_INCREMENT from column 'my_col'. |
3857 | STOP SLAVE cannot be executed while the instance is locked for backup (LOCK INSTANCE FOR BACKUP). | - |
3858 | A warning that specifying precision and scale for floating-point types (e.g., FLOAT(10,2)) is deprecated. | - |
3859 | A warning that the UNSIGNED attribute for DECIMAL, FLOAT, and DOUBLE types is deprecated. | - |
3860 | A warning that specifying a display width for integer types (e.g., INT(11)) is deprecated. | - |
3861 | A warning that the ZEROFILL attribute is deprecated. | - |
3862 | A clone operation failed due to a specific error on the donor (source) instance. | Clone Donor Error: Failed to read data file. |
3863 | The clone recipient received an unexpected or malformed response from the donor. | Clone received unexpected response from Donor : Invalid packet header. |
3864 | Clone failed because the donor and recipient MySQL versions are different. | Clone Donor MySQL version: 8.0.25 is different from Recipient MySQL version 8.0.26. |
3865 | Clone failed because the donor and recipient operating systems are different. | Clone Donor OS: Linux is different from Recipient OS: Windows. |
3866 | Clone failed because the donor and recipient CPU architectures are different. | Clone Donor platform: x86_64 is different from Recipient platform: aarch64. |
3867 | Clone failed because a collation used on the donor is not available on the recipient. | Clone Donor collation: utf8mb4_de_pb_0900_ai_ci is unavailable in Recipient. |
3868 | Clone failed because a critical server variable has a different value on the donor and recipient. | Clone Configuration innodb_page_size: Donor value: 16384 is different from Recipient value: 32768. |
3869 | An informational message showing a system configuration detail during a clone operation. | Clone system configuration: innodb_data_file_path = ibdata1:12M:autoextend |
3870 | Clone failed because a plugin active on the donor is not active on the recipient. | Clone Donor plugin keyring_file is not active in Recipient. |
3871 | Clone cannot use a loopback connection (to the same host) when cloning into the existing data directory. | - |
3872 | Clone requires an SSL connection because the donor has encrypted tables. | - |
3873 | Clone failed because the available disk space on the recipient is less than the estimated size of the donor's data. | Clone estimated database size is 100.00 GB. Available space 50.00 GB is not enough. |
3874 | An operation (like another clone) failed because a clone is already in progress. | - |
3875 | The clone operation cannot be executed when another blocking operation (like a backup) is active. | The clone operation cannot be executed when instance is locked. |
3876 | Roles cannot be granted to an anonymous user (a user with an empty username). | - |
3877 | A generic wrapper for another error message. | Invalid value for parameter. |
3878 | When using dual passwords, the second password cannot be an empty password that is being retained from a previous state. | Empty password can not be retained as second password for user 'user'@'host'. |
3879 | A specific user ( AuthId) was denied access to a specific database. | Access denied for AuthId user@host to database 'admin_db'. |
3880 | A user cannot be added to mandatory_roles because they hold a privilege (like SYSTEM_USER) that conflicts with this feature. | Cannot set mandatory_roles: AuthId admin@localhost has 'SYSTEM_USER' privilege. |
3881 | A replication-related operation failed because the GTID persistence table ( mysql.gtid_executed) could not be opened. | Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened. |
3882 | A geospatial function cannot perform a unit conversion because the input geometry is in SRID 0, which is unitless. | The geometry passed to function ST_Buffer is in SRID 0, which doesn't specify a length unit. Can't convert to 'metre'. |
3883 | Plugin installation failed for a specific reason. | Error installing plugin 'my_plugin': Plugin is not compatible with this server version |
3884 | The storage engine failed to allocate a temporary tablespace for the current session, possibly due to resource limits. | - |
3885 | A generic wrapper for an unknown error code from an underlying system or library. | Got unknown error: 10060 |
3886 | An ALTER TABLE operation failed because the resulting index would be larger than the storage engine's maximum key length. | Could not change column 'c1' of table 't1'. The resulting size of index 'idx1' would exceed the max key length of 3072 bytes. |
3887 | A capture group in a regular expression has an invalid name. | - |
3888 | The server failed to initialize SSL/TLS due to an error from the underlying SSL library (e.g., OpenSSL). | Failed to set up SSL because of the following SSL library error: No certificate specified |
3889 | An operation on a secondary engine (like HeatWave) failed. | Secondary engine operation failed. Query was interrupted. |
3890 | DDL statements (like ALTER TABLE) are not allowed on a table that is loaded into a secondary engine. | - |
3891 | ALTER USER ... REPLACE 'current_pass' failed because the provided current password was incorrect. | - |
3892 | ALTER USER for the current user requires the REPLACE clause to change the password. | - |
3893 | The REPLACE clause (specifying a current password) cannot be used when a privileged user is changing another user's password. | - |
3894 | The current password cannot be retained as a secondary password because the user's authentication plugin is being changed. | - |
3895 | The current password cannot be retained as a secondary password if the new primary password is set to be empty. | - |
3896 | A REVOKE on a database failed because partial revokes are not enabled (partial_revokes=OFF). | - |
3897 | A privilege cannot be granted to a user who is listed in mandatory_roles, as it would create a conflict. | AuthId app_role@% is set as mandatory_roles. Cannot grant the 'SYSTEM_USER' privilege. |
3898 | A warning that using replication filters (like replicate-do-db) with XA transactions is unsupported and may cause issues. | - |
3899 | The specified sql_mode value is not supported. | sql_mode=0x00000001 is not supported. |
3900 | An invalid flag was used for the match mode in a regular expression function. | - |
Error Code | Error Description | Example |
3901 | A data dictionary inconsistency where a privilege for a database exists as both a partial revoke and a full grant simultaneously. | 'SELECT' privilege for database 'testdb' exists both as partial revoke and mysql.db simultaneously... |
3902 | An invalid unit of measure name was used in a function (e.g., CONVERT). | There's no unit of measure named 'FURLONG'. |
3903 | A value could not be cast to the target type for a functional index due to an invalid JSON value. | Invalid JSON value for CAST for functional index 'idx_json_val'. |
3904 | A value could not be cast to the target type for a functional index because the JSON value was out of range. | Out of range JSON value for CAST for functional index 'idx_json_val'. |
3905 | A record exceeded the maximum number of values allowed for a multi-valued index. | Exceeded max number of values per record for multi-valued index 'idx_tags' by 3 value(s). |
3906 | A record exceeded the maximum total byte length of all values for a multi-valued index. | Exceeded max total length of values per record for multi-valued index 'idx_tags' by 512 bytes. |
3907 | The result of a functional index expression is too long for the index key part. | Data too long for functional index 'idx_name_upper'. |
3908 | An attempt was made to store a JSON array or object in an index key part that is defined as a scalar value. | Cannot store an array or an object in a scalar key part of the index 'idx_json_data'. |
3909 | A functional index could not be used for a query, likely due to an implicit type or collation conversion being required. | Cannot use functional index 'idx_name' due to type or collation conversion. |
3910 | A generic error indicating that a function failed for a specific reason. | The function 'my_udf' failed. Invalid input data. |
3911 | SET GTID_PURGED cannot be executed while the Group Replication plugin is running. | - |
3912 | A warning that grouping by a temporal column can produce non-deterministic results in time zones with Daylight Saving Time (DST). | - |
3913 | The combination of a long database name and object identifier resulted in a file path that is too long for the operating system. | Long database name and identifier for object resulted in a path length too long for table 't1'. Please check the path limit for your OS. |
3914 | A request was ignored because the user lacks the specific role required for the operation. | Request ignored for 'dev_user'@'localhost'. Role needed to perform operation: 'BACKUP_ADMIN' |
3915 | An informational message indicating that a password from the audit_log user has been migrated to another user's password history. | 'audit_log' password has been copied into 'user'@'host' and will be removed with first purged password. |
3916 | An informational message from Group Replication indicating it has started an attempt to automatically rejoin the group. | Started auto-rejoin procedure attempt 1 of 5 |
3917 | A query was affected because a plugin was loaded or unloaded, which changed the structure of a system variable table. | - |
3918 | A query was affected because a plugin was loaded or unloaded, which changed a global status variable. | - |
3919 | The START GROUP_REPLICATION command failed because its internal communication service could not be started. | - |
3920 | An invalid value was provided for the MASTER_COMPRESSION_ALGORITHMS option in CHANGE MASTER TO. | Invalid MASTER_COMPRESSION_ALGORITHMS 'lz5' for channel ''. |
3921 | An invalid value was provided for the MASTER_ZSTD_COMPRESSION_LEVEL option in CHANGE MASTER TO. | Invalid MASTER_ZSTD_COMPRESSION_LEVEL 23 for channel ''. |
3922 | An invalid compression algorithm name was specified. | Invalid compression algorithm 'lz5'. |
3923 | An invalid zstd compression level was specified for the 'zstd' algorithm. | Invalid zstd compression level for algorithm 'zstd'. |
3924 | The list of compression algorithms for a replication channel exceeds the maximum allowed count. | Specified compression algorithm list 'zlib,zstd,lz4,uncompressed' exceeds total count of 3 for channel ''. |
3925 | The PRIVILEGE_CHECKS_USER for a replication channel cannot be an anonymous user. | PRIVILEGE_CHECKS_USER for replication channel '' was set to ``@ localhost, but anonymous users are disallowed... |
3926 | The PRIVILEGE_CHECKS_USER specified for a replication channel does not exist. | PRIVILEGE_CHECKS_USER for replication channel '' was set to nonexistent@localhost, but this is not an existing user. |
3927 | The PRIVILEGE_CHECKS_USER setting stored in the replication repository is corrupted. | - |
3928 | The PRIVILEGE_CHECKS_USER for a replication channel lacks the required REPLICATION_APPLIER privilege. | PRIVILEGE_CHECKS_USER for replication channel '' was set to app_user@localhost, but this user does not have REPLICATION_APPLIER privilege. |
3929 | An operation referenced a dynamic privilege that has not been registered with the server. | Dynamic privilege 'MY_CUSTOM_PRIV' is not registered with the server. |
3930 | A keyring function failed because the specified key is invalid. | Function 'keyring_key_fetch' failed because key is invalid. |
3931 | A keyring function failed because the specified key type is invalid. | Function 'keyring_key_generate' failed because key type is invalid. |
3932 | A keyring function failed because the specified key length is too long. | Function 'keyring_key_generate' failed because key length is too long. |
3933 | A keyring function failed because the specified key type name is too long. | Function 'keyring_key_generate' failed because key type is too long. |
3934 | A generic placeholder for another error message. | An internal error occurred. |
3935 | An invalid character set or collation name was specified. | Invalid character set 'utf8mb3' was specified. It must be either character set name or collation name as supported by server. |
3936 | An invalid character set name was specified. | Invalid character set 'utf8mb4_general_ci' was specified. It must be a character set name as supported by server. |
3937 | An invalid collation name was specified. | Invalid collation 'utf8mb4' was specified. It must be a collation name as supported by server. |
3938 | An invalid argument type was specified for a UDF extension. | Invalid extension argument type 'INTEGER_ARRAY' was specified. Refer the MySQL manual for the valid UDF extension arguments type. |
3939 | An ALTER TABLE statement is ambiguous because multiple constraints have the same name. | Table has multiple constraints with the name 'chk1'. Please use constraint specific 'DROP CHECK' clause. |
3940 | The specified constraint name does not exist on the table. | Constraint 'chk_nonexistent' does not exist. |
3941 | An attempt was made to alter the enforcement of a constraint type that does not support it (e.g., PRIMARY KEY). | Altering constraint enforcement is not supported for the constraint 'fk_1'. ... |
3942 | A row in a VALUES clause must contain at least one column, unless it's part of an INSERT statement. | - |
3943 | The DEFAULT keyword cannot be used in a VALUES clause unless it is the source for an INSERT statement. | - |
3944 | The query violates restrictions set by the require_row_format variable. | - |
3945 | An invalid value was set for the require_row_format variable. | The requested value 2 is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1. |
3946 | An internal locking error occurred in the user management service while checking for mandatory roles. | Failed to acquire lock on user management service, unable to determine if role my_role@% is mandatory |
3947 | An internal locking error occurred in the user management service while fetching the list of mandatory roles. | Failed to acquire lock on user management service, unable to fetch mandatory role list |
3948 | LOAD DATA LOCAL INFILE failed because it is disabled on either the client or server side. | - |
3949 | A component or plugin import failed due to an incompatible configuration file version. | Failed to import component because the CFG file version (1) is not compatible with the current version (2) |
3950 | The server ran out of memory while executing an operation. | - |
3951 | In a UDF definition, a character set can only be specified for arguments of type STRING. | - |
3952 | In a UDF definition, a character set can only be specified for a return type of STRING. | - |
3953 | A query block contains more than one INTO clause. | - |
3954 | An INTO clause is misplaced (e.g., inside a subquery or not at the end of a UNION). | - |
3955 | A login attempt was denied because the account is temporarily blocked due to too many consecutive failed logins. | Access denied for user 'user'@'host'. Account is blocked for 1 day(s) (1 day(s) remaining) due to 5 consecutive failed logins. |
3956 | A warning that using the UNSIGNED attribute for the YEAR data type is deprecated. | - |
3957 | A CLONE operation requires a larger max_allowed_packet size than is currently configured. | Clone needs max_allowed_packet value to be 67108864 or more. Current value is 16777216 |
3958 | A data dictionary operation on an SDI record failed because the record was missing. | Failed to update sdi for table.t1 in tablespace.ts1 due to missing record. |
3959 | A column cannot be dropped or renamed because it is used in a CHECK constraint. | Check constraint 'chk_price' uses column 'price', hence column cannot be dropped or renamed. |
3960 | An operation failed because it cannot be performed while Group Replication is running. | This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION first |
3961 | A warning that the order of ON EMPTY and ON ERROR clauses in JSON_TABLE is deprecated and should be reversed. | - |
3962 | A warning that using INTO within the individual query blocks of a UNION is deprecated. | - |
3963 | A warning that the VALUES() function in ON DUPLICATE KEY UPDATE clauses is deprecated. | - |
3964 | A warning that the SQL_CALC_FOUND_ROWS query modifier is deprecated. | - |
3965 | A warning that the FOUND_ROWS() function is deprecated. | - |
3966 | A function like JSON_VALUE did not find any value at the specified JSON path. | No value was found by 'JSON_VALUE' on the specified path. |
3967 | A function like JSON_VALUE found more than one value at the specified JSON path, where only a scalar is expected. | More than one value was found by 'JSON_VALUE' on the specified path. |
3968 | A hostname exceeds the maximum allowed length. | Hostname cannot be longer than 255 characters. |
3969 | A warning that using a prefixed column in a PARTITION BY KEY clause is deprecated. | Column 'db1.t1.c1' having prefix key part 'c1(10)' is ignored by the partitioning function... |
3970 | START GROUP_REPLICATION failed because the username for the recovery channel was empty. | - |
3971 | START GROUP_REPLICATION failed because a password was provided for the recovery channel without a username. | - |
3972 | START GROUP_REPLICATION failed because the password for the recovery channel was too long. | - |
3973 | A query could not be executed because it requires a subquery transformation that conflicts with the subquery_to_derived optimizer switch. | - |
3974 | The list of recovery endpoints for Group Replication has an invalid format. | Invalid input value for recovery socket endpoints '127.0.0.1:33061;127.0.0.1:33062'. Please, provide a valid, comma separated, list... |
3975 | A specified Group Replication recovery endpoint is not an address the server is currently listening on. | The server is not listening on endpoint '127.0.0.1:9999'. Only endpoints that the server is listening on are valid recovery endpoints. |
3976 | Setting a variable failed because the value is invalid for a specific reason. | Variable 'max_connections' cannot be set to the value of '0'. The value should be in the range 1 to 100000. |
3977 | An invalid statement was executed after CREATE TABLE ... START TRANSACTION. | - |
3978 | Foreign keys cannot be created in a CREATE TABLE ... AS SELECT statement that also uses START TRANSACTION. | - |
3979 | The START TRANSACTION clause was used in an unsupported statement (e.g., CREATE TABLESPACE). | START TRANSACTION clause cannot be used with CREATE TABLESPACE |
3980 | A JSON attribute string has a syntax error. | Invalid json attribute, error: "Missing a comma or '}'" at pos 15: '{"a":1 "b":2}' |
3981 | The ENGINE_ATTRIBUTE clause was used with a storage engine that does not support it. | Storage engine 'MyISAM' does not support ENGINE_ATTRIBUTE. |
3982 | The value provided for the USER_ATTRIBUTES option must be a valid JSON object. | - |
3983 | An operation failed because InnoDB redo logging is disabled. | Cannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCE |
3984 | An operation failed because InnoDB is currently archiving its redo log. | Cannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive... |
3985 | A lock request could not be completed due to insufficient resources. | - |
3986 | A warning that evaluating a JSON value in a boolean context performs an implicit comparison to the JSON integer 0. | - |
3987 | A function does not support the specified character set. | The function REGEXP_LIKE does not support the character set 'binary'. |
3988 | A conversion between two collations is impossible for a given operation. | Conversion from collation utf8mb4_general_ci into utf16_general_ci impossible for operation '=' |
3989 | An operation failed because the target schema is in read-only mode. | Schema 'reporting_db' is in read only mode. |
3990 | Asynchronous Replication Connection Failover cannot be enabled because GTID mode is not ON. | Failed to enable Asynchronous Replication Connection Failover feature... can only be set when @@GLOBAL.GTID_MODE = ON. |
3991 | Asynchronous Replication Connection Failover cannot be enabled because MASTER_AUTO_POSITION is not enabled. | Failed to enable Asynchronous Replication Connection Failover feature... can only be set when MASTER_AUTO_POSITION... is enabled. |
3992 | GTID mode cannot be changed while Asynchronous Replication Connection Failover is enabled. | The @@GLOBAL.GTID_MODE = OFF cannot be executed because Asynchronous Replication Connection Failover is enabled... |
3993 | MASTER_AUTO_POSITION cannot be disabled while Asynchronous Replication Connection Failover is enabled. | CHANGE MASTER TO MASTER_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled... |
3994 | A function was called with an invalid combination or use of parameters. | Invalid use of parameters in 'ST_Buffer' |
3995 | A function was called with arguments having incompatible character sets. | Character set 'utf8mb4' cannot be used in conjunction with 'binary' in call to CONCAT_WS. |
3996 | A setting could not be changed because it is not supported on the current platform. | Changing thread priority not supported on this platform. Falling back to the default. |
3997 | A time zone interval string has an invalid format or value. | Invalid time zone interval: '+25:00' |
3998 | A CAST operation failed because the value cannot be converted to the target type. | Cannot cast value to DATETIME. |
3999 | The hypergraph optimizer does not yet support a specific SQL feature. | The hypergraph optimizer does not yet support 'outer joins' |
4000 | A warning that the hypergraph optimizer is experimental and should not be used in production. | The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer. |
Error Code | Error Description | Example |
4001 | The error logging services ( log_error_services) do not include a log parser, preventing past error logs from being loaded into the performance_schema.error_log table. | - |
4002 | The current error logging services ( log_error_services) do not include a sink that writes to the Performance Schema, so current errors will not appear in the performance_schema.error_log table. | - |
4003 | A warning that using multiple log filters in log_error_services is discouraged because it makes it difficult to trace which filter affected a log event. | - |
4004 | The server could not open the specified file for error logging, likely due to an incorrect path or permissions. | Could not open file '/var/log/mysql/error.log' for error logging (OS errno 13 - Permission denied) |
4005 | An informational message indicating that a user account is the DEFINER for one or more stored objects (procedures, functions, views, etc.). | User 'app_user'@'localhost' is referenced as a definer account in procedure db1.proc1. |
4006 | An operation (like DROP USER or RENAME USER) failed because the target user is the DEFINER for a stored object. | Operation DROP USER failed for 'app_user'@'localhost' as it is referenced as a definer account in procedure db1.proc1. |
4007 | A number used in a regular expression (e.g., in a quantifier like {n}) is too large to be processed. | - |
4008 | An operation expected a variable to be of an integer type, but it was not. | The variable "my_var" has a non-integer based type |
4009 | Locking reads ( SELECT ... FOR SHARE) and reads with SERIALIZABLE isolation level are not permitted on internal Access Control List (ACL) tables (e.g., mysql.user). | - |
4010 | A statement is marked as unsafe for statement-based replication because it updates a table based on a read from an ACL table, which can lead to different outcomes on the source and replica. | - |
4011 | An informational message indicating that the STOP REPLICA command has been received, but the replica monitor thread is busy and will stop after completing its current task. | - |
4012 | The replica monitor thread, which checks the health of the replication connection, could not be started. | - |
4013 | The ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS option cannot be used because the server's gtid_mode is not ON. | - |
4014 | The replication options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS and SOURCE_AUTO_POSITION=1 cannot be used at the same time. | - |
4015 | The ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS option cannot be set because the server's gtid_mode is not ON. | - |
4016 | A warning that sql_replica_skip_counter will have no effect unless the channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS. | - |
4017 | A warning explaining the limitations of using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS, advising that enabling GTIDs on the source is the preferred method. | - |
4018 | The WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS function cannot be used on a replication channel that uses ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS. | - |
4019 | The SQL_AFTER_GTIDS and SQL_BEFORE_GTIDS clauses of START REPLICA cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS. | - |
4020 | The UUID specified in ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS cannot be the same as the group_replication_group_name. | - |
4021 | The UUID for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS cannot be set to the same value as group_replication_group_name. | - |
4022 | The Group Replication recovery channel is blocked and cannot stop, likely due to a pending database or table lock. | - |
4023 | The AUTOEXTEND_SIZE value for a tablespace must be a multiple of the InnoDB buffer pool page size. | AUTOEXTEND_SIZE should be a multiple of 1M |
4024 | A specific table option (e.g., COMPRESSION) is not compatible with general tablespaces. | InnoDB: "COMPRESSION" not allowed with general tablespaces |
4025 | The specified AUTOEXTEND_SIZE value is outside the permitted minimum and maximum range. | AUTOEXTEND_SIZE value should be between 4M and 65536M |
4026 | The AUTOEXTEND_SIZE clause cannot be used with the specified type of tablespace. | AUTOEXTEND_SIZE clause is not valid for undo tablespace. |
4027 | A GRANT statement was rejected because it would create a circular dependency between roles (e.g., granting role A to user B, who is already granted role A). | User account 'user_b'@'localhost' is directly or indirectly granted to the role 'role_a'. The GRANT would create a loop |
4028 | An operation failed because it would result in a table having no visible columns. | - |
4029 | A data compression operation failed for a specific reason. | Compression failed with the following error : zlib error |
4030 | A warning that the network_namespace parameter is reserved and should be set using the CHANGE REPLICATION SOURCE command. | - |
4031 | The server closed the client connection because it was idle for longer than the configured wait_timeout or interactive_timeout. | - |
4032 | An invalid cast was attempted between two different geometry types. | Invalid cast from POINT to POLYGON. |
4033 | A cast to a polygon type failed because a ring within the polygon has an incorrect orientation (e.g., clockwise instead of counter-clockwise). | Invalid cast from GEOMETRY to POLYGON. A polygon ring is in the wrong direction. |
4034 | A geospatial function was called with geometry arguments that have different Spatial Reference System IDs (SRIDs). | Arguments to function ST_Intersects contains geometries with different SRIDs: 4326 and 3857. All geometries must have the same SRID. |
4035 | The keyring could not be reloaded ( ALTER INSTANCE RELOAD KEYRING). The error log will contain more details. | - |
4036 | The specified tablespace cannot be used for operations involving Serialized Dictionary Information (SDI). | Tablespace 'mysql' is invalid for SDI operations. |
4037 | The value provided for the SOURCE_COMPRESSION_ALGORITHMS option exceeds the maximum allowed length. | Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a 257 chars long string for channel ''. |
4038 | A warning that a replication channel is configured to use a deprecated TLS version (e.g., TLSv1.0, TLSv1.1). | A deprecated TLS version TLSv1.1 is enabled for channel ''. Please use TLSv1.2 or higher. |
4039 | The UUID for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS cannot be set to the same value as group_replication_view_change_uuid. | - |
4040 | A replication channel is configured with an ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS UUID that is the same as the group_replication_view_change_uuid. | - |
4041 | An internal error occurred where the server was unable to retrieve the group_replication_view_change_uuid variable during a replication operation check. | - |
4042 | A warning that both audit_log_max_size and audit_log_prune_seconds are configured, and that audit_log_max_size will take precedence. | - |
4043 | The value of audit_log_rotate_on_size is too large in relation to audit_log_max_size to allow for proper log rotation and pruning. | audit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least 10 times smaller. |
4044 | A CREATE or ALTER USER statement failed because the authentication string, which is required as a user realm by the authentication plugin, was empty. | - |
4045 | A plugin cannot be installed because it conflicts with another plugin that is already installed. | Cannot install the 'keyring_file' plugin when the 'keyring_encrypted_file' plugin is installed. |
4046 | Flushing error logs failed for one or more logging components, which can affect log rotation. | 1 error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. |
4047 | A warning that UNTIL SQL_AFTER_MTS_GAPS is being used on a GTID-based channel where it is ineffective; SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS should be used instead. | - |
4048 | The target of an assignment in an INSERT or UPDATE statement is invalid (e.g., trying to assign a value to an expression). | Invalid target for assignment in INSERT or UPDATE statement 'col1 + 1'. |
4049 | The attempted operation can only be executed on the primary member of a Group Replication cluster, not on a secondary member. | - |
4050 | An attempt to propagate the SOURCE_CONNECTION_AUTO_FAILOVER setting to other members of a Group Replication cluster failed. | - |
4051 | The audit_log_format_unix_timestamp option is only effective when audit_log_format is set to JSON. | - |
Error Code | Error Description | Example |
7000 | The query cannot be executed because another session holds a backup lock ( LOCK INSTANCE FOR BACKUP). | - |
7001 | A column defined with COLUMN_FORMAT COMPRESSED cannot be included in an index key. | Compressed column 'c1' is not allowed in the key list |
7002 | The COLUMN_FORMAT COMPRESSED attribute cannot be applied to a column of this data type (e.g., BLOB, TEXT). | Can not define column 'my_text_col' in compressed format |
7003 | An attempt was made to create a compression dictionary with a name that is already in use. | Compression dictionary 'my_dict' already exists |
7004 | An operation was attempted on a compression dictionary that does not exist. | Compression dictionary 'old_dict' does not exist |
7005 | The name provided for a compression dictionary exceeds the maximum allowed length. | Compression dictionary 'a_very_long_name_for_a_dictionary' is too long (max length = 64) |
7006 | The sample data provided to create a compression dictionary is larger than the maximum allowed size. | Data for compression dictionary 'my_dict' is too long (max length = 16384) |
7007 | An attempt was made to drop a compression dictionary that is currently being used by one or more tables. | Compression dictionary 'my_dict' is in use |
7008 | The redo log encryption setting cannot be changed while the server is running. It requires a server shutdown and recreation of the redo logs. | Redo log encryption mode can't be switched without stopping the server... Current mode is OFF, requested ON. |
7009 | The server failed to generate a new encryption key for the redo log, likely due to a keyring issue. | - |
7010 | The server could not load a specific version of the redo log encryption key from the keyring. | Failed to load redo key version 2 |
7011 | After generating a new redo log key, the server was unable to retrieve it from the keyring. | - |
7012 | An internal error occurred while parsing a system encryption key. | Couldn't parse system key: invalid format |
7013 | Redo log encryption cannot be enabled because no keyring plugin is loaded. | - |
7014 | Undo log encryption cannot be enabled because no keyring plugin is loaded. | - |
7015 | The server failed to decrypt an encrypted table, likely because the key in the current keyring is incorrect. | Table db1.t1 is encrypted but decryption failed. ... Are you using the correct keyring? |
7016 | An operation to exclude a tablespace from background encryption failed because it is already being processed by the encryption threads. | Tablespace ts1 is fully or partially encrypted by encryption threads and thus cannot be excluded from encryption threads... |
7017 | An explicit decryption ( ALTER TABLE ... ENCRYPTION='N') is not allowed for a tablespace encrypted by background threads. | Tablespace ts1 is encrypted by encryption threads and cannot be explicitly decrypted... |
7018 | A tablespace encrypted by background threads cannot be directly altered to use Master Key encryption; it must be decrypted first. | Tablespace ts1 is encrypted by encryption threads and cannot be ALTERed to Master Key encryption... |
7019 | A conflict between settings: The database default cannot be Master Key encryption if the global default is to convert tables to keyring encryption. | - |
7020 | A conflict between settings: The database default cannot be unencrypted if the global default is to convert tables to keyring encryption. | - |
7021 | An ALTER TABLE ... ENCRYPTION command failed because background encryption threads are currently working on that tablespace. | Tablespace ts1 cannot have its ENCRYPTION altered as it is being currently encrypted/decrypted by encryption threads... |
7022 | The ENCRYPTION clause was used in a context where it is not permitted. | Encryption option is not allowed. The storage engine does not support it. |
7023 | The SEQUENCE_TABLE() function was requested to generate more rows than the tf_sequence_table_max_upper_bound variable allows. | The number of records generated by SEQUENCE_TABLE() cannot exceed 1000 (1001 requested)... |
7024 | An attempt to rotate an InnoDB system key failed because the specified key version does not exist in the keyring. | InnoDB system key 5 cannot be rotated, because it does not exist. |
7025 | The version number for an InnoDB system key exceeds the maximum value of 4,294,967,294. | - |
7026 | Rotation of an InnoDB system key failed because the keyring service reported an error. | Cannot generate new version of system key 1. Keyring reported an error. Please check if keyring is available. |
7027 | The default_table_encryption variable cannot be changed while background encryption threads (innodb_encryption_threads) are active. | - |
7028 | The encryption_key_id specified in a statement is higher than the maximum allowed value. | The requested value 5000000000 for the encryption_key_id exceeds the maximum allowed 4294967295 |
7029 | A User-Defined Function (UDF) threw an exception, which was caught and reported by the server. | Wrapped UDF exception in function 'my_udf'; Division by zero |
7030 | Dropping multiple tables in a single DROP TABLE statement is not supported when a specific conflicting feature is enabled. | Multi table drop is not supported when 'some_feature' option is enabled |
Error Code | Error Description | Example |
8000 | A MyRocks bulk load operation failed because the input data was not sorted by the primary key. | - |
8001 | A MyRocks bulk load operation failed because the key range of the input data overlaps with data that already exists in the table. | - |
8002 | A write operation was blocked because the MyRocks storage engine requires row-based replication ( binlog_format=ROW) for data safety. | - |
8003 | The current transaction isolation level is not supported by the MyRocks storage engine, which only supports READ COMMITTED and REPEATABLE READ. | MyRocks supports only READ COMMITTED and REPEATABLE READ isolation levels. Please change from current isolation level SERIALIZABLE |
8004 | A statement like INSERT ... ON DUPLICATE KEY UPDATE or REPLACE was blocked because it is unsafe to use when unique checks are disabled in MyRocks. | ...Query: INSERT INTO t1 VALUES (1) ON DUPLICATE KEY UPDATE c1=2; |
8005 | A write operation was blocked because it was attempted within a read-only START TRANSACTION WITH CONSISTENT SNAPSHOT. | - |
8006 | The current transaction has encountered an error and has been implicitly rolled back; it can no longer be committed. | - |
8007 | The MyRocks storage engine does not support rolling back to a savepoint if the transaction has already modified data. | - |
8008 | The START TRANSACTION WITH CONSISTENT SNAPSHOT feature in MyRocks can only be used with the REPEATABLE READ isolation level. | - |
8009 | An index was created on a string column with a collation that is not supported by MyRocks. A binary collation is required. | Unsupported collation on string indexed column t1.c1 Use binary collation (utf8mb4_bin). |
8010 | A data dictionary inconsistency was detected where MyRocks has internal metadata for a table that no longer exists in the MySQL data dictionary. | Table 't1' does not exist, but metadata information exists inside MyRocks. This is a sign of data inconsistency. |
8011 | An internal MyRocks error occurred during an ALTER TABLE operation while trying to create new index definitions. | - |
8012 | An internal MyRocks error occurred during an ALTER TABLE operation while populating a new secondary index. | - |
8013 | An attempt was made to define a MyRocks Column Family with a name that already exists but with a different configuration flag. | Column family ('cf1') flag (1) is different from an existing flag (0). ... |
8014 | The Time-To-Live (TTL) feature in MyRocks cannot be used on a table that has a hidden (system-generated) primary key. | - |
8015 | The column specified for MyRocks TTL has an invalid data type or attribute; it must be a BIGINT UNSIGNED NOT NULL. | TTL column (created_at) in MyRocks must be an unsigned non-null 64-bit integer... |
8016 | The TTL duration specified in the table comment is not a valid unsigned 64-bit integer. | TTL duration (oneweek) in MyRocks must be an unsigned non-null 64-bit integer. |
8017 | A deprecated syntax was used to assign a MyRocks Column Family to a specific index. | - |
8018 | An informational message or error indicating that a specific MyRocks Column Family is being dropped. | Column family ('cf_archive') is being dropped. |
8019 | An attempt to drop a MyRocks Column Family failed because it is either still in use by a table or the specified name does not exist. | Cannot drop Column family ('cf_default') because it is in use or does not exist. |
Error Code | Error Description | Example |
8500 | A generic error reported from the underlying TDStore (RocksDB) storage engine. The message provides the specific internal error code and text. | 'RocksDB' error, error code:'NotFound(4)', error msg:'Column family not found'. |
8501 | An informational message indicating that TDSQL is designed to work only with the TDStore/RocksDB engine and will automatically switch to it. | - |
8502 | A write operation failed due to a "write fence" conflict, a concurrency control mechanism to prevent stale writes. | Query failed for write fence error. ... on table(db1.t1), tindex_id:'1005', sent wf:'1234', current write fence: '1235'. |
8503 | A DDL operation was interrupted by an automated DDL recovery process. The operation should be retried. | - |
8504 | A node failed to update its local table schema version, which is older than the globally consistent version. | Update newest table(db1.t1) version failed, local sv:'1648123456', glsv:'1648123459'. |
8505 | A query failed because it is using a stale (outdated) version of the table's schema or metadata. | Table(db1.t1)-tindex_id(1005) version is too old:'5', current version:'6'. current tindex id: 1005 |
8506 | A DDL operation could not start because a conflicting DDL job is already in progress on the same database or table. | A conflict DDL job(id 123) is on going...: db is 'db1', table is 't1'. Please wait and retry later. |
8507 | A CREATE TABLE operation failed because the table's metadata was lost or became inconsistent during the creation process. | Failed to create table 'db1'.'t1' cause the metadata get lost while creating table. Please wait and retry later. |
8508 | An internal error occurred where the system tried to register an auto-increment ID that was already in use. | Regist AutoInc IndexId 1005 duplicate |
8509 | The system has run out of available internal IDs to assign to new tables with auto-increment columns. | - |
8510 | A generic system error occurred within the SQL Engine layer of TDSQL. | SQLEngine system error 'Failed to acquire lock' |
8511 | An internal error where an operation was performed on an auto-increment ID that was not properly registered. | AutoInc IndexId 1005 not regist |
8512 | The TDStore engine failed to create a data iterator, which is necessary for scanning rows. | TDStore can't setup iterator obj. error code:'5', error msg:'Invalid argument' |
8513 | The storage engine failed to allocate a new value for an AUTO_INCREMENT column. | Could not allocate auto increment value from tdstore, request_id: '5678', error code: '7', error msg: 'Timed out' |
8514 | An INSERT statement provided a value for the AUTO_INCREMENT column when one was not expected or defined. | - |
8515 | An operation that requires a transaction was executed outside of a transaction context, or the context was lost. | TDStore can't find transaction context. ... error code:'1', error msg:'Not in a transaction' |
8516 | A transaction failed because the transaction context was lost, possibly due to a leadership change in the underlying distributed cluster. | TDStore can't find transaction context and it may be caused by a leader-transferring... |
8517 | The server failed to initialize the global region cache during startup. | - |
8518 | The current user does not have the necessary privileges to set the specified system variable. | User 'app_user'@'%' has no privilege to set variable read_only. |
8519 | The STORAGE_FORMAT() function was called with an invalid argument type; it requires a 32-bit unsigned integer. | - |
8520 | A transaction commit failed and was automatically aborted by the TDStore engine. | Transaction commit failed and is aborted by tdstore. error code:'10', error msg:'Conflict', coordinator:'192.168.1.10:3306' |
8521 | The transaction has entered an unrecoverable state and must be rolled back. | - |
8522 | The server cannot perform operations because the distributed cluster has not been properly initialized (bootstrapped). | - |
8523 | The background thread responsible for keeping distributed transactions alive failed to start. | - |
8524 | An ALTER TABLE ... ENGINE= statement failed because converting between the RocksDB engine and other engines is not supported. | - |
8525 | Direct INSERT, UPDATE, or DELETE operations on internal system privilege tables are not allowed. Use GRANT/REVOKE instead. | Raw DML operations on system privilege table mysql.user is not allowed |
8526 | The table is in an unusable state, possibly due to a concurrent DDL operation. Restarting the transaction may resolve the issue. | Unusable table db1.t1. Table is being altered. Please restart the transaction |
8527 | An internal error occurred while processing a correlated subquery. | Correlate table error (err_code: 1, err_msg: Subquery returned more than 1 row) |
8528 | An online ALTER TABLE operation failed. The error suggests retrying with an offline algorithm if write downtime is acceptable. | Online alter table db1.t1 failed with 'lock conflict', please set variable 'tdsql_use_online_copy_ddl' to 'false'... |
8529 | A SET PERSIST or SET PERSIST_ONLY command failed because the server's local cache of persisted variables is out of sync. | - |
8530 | SET PERSIST_ONLY can only be used on read-only variables, but was attempted on a dynamic (writable) variable. | SET PERSIST_ONLY syntax on variable 'max_connections' is not allowed, which is not a read only variable |
8531 | New DDL jobs are temporarily blocked for a specific reason, such as a system upgrade or maintenance task. | Start new ddl job is not allowed currently, because cluster is in read-only mode |
8532 | A single DDL statement is too complex (e.g., adds too many columns/indexes at once) and must be split into multiple, simpler statements. | - |
8533 | A warning that the LOCK TABLES and UNLOCK TABLES statements are parsed for compatibility but have no actual effect in TDSQL. | - |
8534 | A call to a native (internal) stored procedure was made with incorrect parameter types or count. | The 1st parameter didn't match for native procedure sp_do_something |
8535 | The system failed to add a new statement outline rule (query plan hint). | Could not add statement outline rule: "Syntax error in rule definition". |
8536 | The system failed to delete an existing statement outline rule. | Could not delete statement outline rule: "Rule ID 123 not found". |
8537 | The system failed to enable or disable an existing statement outline rule. | Could not enable or disable statement outline rule: "Rule ID 123 not found". |
8538 | An invalid or corrupt statement outline rule was found in the system table. | Invalid statement outline rule 123 in rules table: missing query pattern |
8539 | An error occurred while reloading the statement outline rules from the system table into memory. | Error when refreshing statement outline rules: Failed to parse rule table |
8540 | A query failed because applying a specific statement outline rule resulted in an invalid execution plan. | The statement fail to apply rule 123: hint forces a non-existent index 'idx_name' |
8541 | The server failed to propagate a flush of statement outline rules to other nodes in the cluster. | Error when flush statement rules for others: RPC timeout |
8542 | A request to lock a distributed object (like a table for DDL) timed out while waiting for the Meta Cluster. | Acquire object lock 'table/db1/t1' from MC wait timeout |
8543 | A generic error message. The specific error text will be provided in the message itself. | Failed to get table schema |
8544 | A generic error message. The specific error text will be provided in the message itself. | Invalid argument for parallel execution |
8545 | An internal error occurred while trying to create a data object in the distributed metadata service. | Failed to create data object. Object already exists |
8546 | The server failed to start the necessary background threads to execute a query in parallel. | The parallel query worker threads failed to start. (errno: 11 - Resource temporarily unavailable) |
8547 | The degree of parallelism specified (e.g., via a hint) is invalid (e.g., 0, 1, or too large). | - |
8548 | The PARALLEL hint was used on a statement that does not support parallel execution. | - |
8549 | An error occurred in the RPC application stream used for communication between nodes in a distributed query. | RPC application stream failure. Connection reset by peer |
8550 | An internal operation to get or change a table's data distribution policy (sharding) failed. | - |
8551 | An informational message from the optimizer indicating that an INSERT, REPLACE, or LOAD statement was converted into a more efficient batch operation. | Force optimize INSERT/REPLACE/LOAD into BatchPut. Using clustered index. |
8552 | A parallel query failed because a single row was too large to be transmitted over the network between worker nodes. | - |
8553 | An internal error occurred within the distributed event notification service. | Event service can not add or remove an event. (errno: 2 - No such file or directory) |
8554 | A parallel query failed due to a network error while sending or receiving rows between worker nodes. | Parallel query operator failed to send or receive row. (errno: 32 - Broken pipe) |
8555 | A parallel query failed because a worker node received a corrupted or unknown data packet from another node. | - |
8556 | A generic error message. The specific error text will be provided in the message itself. | Failed to deserialize plan fragment |
8557 | An internal server function ( extract_int_from_str) was used incorrectly by another part of the server code. | Wrong use of extract_int_from_str. Input is not a number |
8558 | The statement is not allowed because it affects multiple tables, which is a current limitation of the underlying log service. | RENAME TABLE contains multi tables is not allowed currently, because of log service restriction |
8559 | An error occurred on a remote worker node during the execution of a parallel query. | Parallel query remote worker error. Table not found |
8560 | An error occurred in the remote executor component responsible for running a query fragment on a worker node. | Parallel query remote executor error. Out of memory |
8561 | A "Stale Read" (reading data from a past point in time) was attempted in a context that is not supported, such as within an explicit transaction. | Stale Read only supports non-locking read only autocommit transaction. Current transaction is not autocommit. |
8562 | A "Stale Read" query failed because the system could not obtain a valid data snapshot for the requested timestamp. | Stale Read failed to get a snapshot. Timestamp is too old |
8563 | Dropping a table immediately after locking it in the same session is not supported. | - |
8564 | An attempt to dynamically change bulk-load mode settings failed. | Update bulk-load mode settings failed. Invalid mode specified |
8565 | An attempt to dynamically change TDStore configuration options failed. | Update tdstore options failed. Option 'max_open_files' is not changeable |
8566 | A warning issued when changing TDStore options, indicating a potential issue or non-optimal setting. | Update tdstore options WARN. Value for 'write_buffer_size' is too low |
8567 | An internal, informational message indicating that a "hyper node id" was retrieved from a local cache. | - |
8568 | A generic error indicating that a required lock could not be acquired. | - |
8569 | A table cannot be created in or moved to a database because they belong to different "dataspaces" (a logical grouping of data). | Can't create/move table in/to the db. DB(db_A) and table(db_B.t1) are in different dataspaces |
8570 | An internal type mismatch was detected within the TDSQL server code. | Tdsql identify type mismatch, need 'TABLE' but get 'VIEW' |
8571 | A function or procedure was called with the wrong number of parameters. | Incorrect number of parameter 'MY_FUNC', need '3' but get '2' |
8572 | A function or procedure was called with too few parameters. | Incorrect number of parameter 'MY_FUNC', need more than '2' but get '1' |
8573 | An unknown argument or option was provided to an internal command or function. | Unknown arg: '--invalid-option' |
8574 | A request to submit a job (like a DDL task) to the distributed scheduler failed. | Submit job failed: 'DDL', err_msg: 'Queue is full' |
8575 | An operation to purge old Raft consensus logs failed. | Purge raft log failed: 'Region 123' |
8576 | A generic error indicating that a parallel query failed because one of its worker processes reported an error. | - |
8577 | An operation to create a new data partitioning policy failed. | Failed to create partition policy. Invalid range definition |
8578 | An operation to bind a partitioning policy to a table failed. | Failed to bind partition policy. Table is not empty |
8579 | An informational message indicating that a query's execution plan was changed by a statement outline rule. | Statement outline rule 123 was applied, it may have changed the query plan. |
8580 | An internal operation to flush a memtable (in-memory writes) to persistent storage failed. | Flush memtable failed: 'Region 123' |
8581 | An online ALTER TABLE with ALGORITHM=COPY is not allowed when tdsql_ddl_fillback_mode is set to BulkLoadLock. | - |
8582 | An attempt was made to change a global variable that is protected and cannot be modified at the cluster level. | Some cluster global variables are not allowed to change: 'version' |
8583 | A parallel query failed because different worker nodes are using incompatible data formats for exchanging rows. | - |
8584 | A FLASHBACK TABLE or similar operation failed because the specified dropped table was not found in the recycle bin. | - |
8585 | The operation could not complete because it would cause the total size of the recycle bin to exceed its configured limit. | Exceed limit size 1073741824 of recycle bin |
8586 | A DROP TABLE statement cannot mix tables that are in the recycle bin with tables that are not. | - |
8587 | A generic error occurred during an operation involving the recycle bin. | Error occurred in recycle_bin : Table is locked. |
8588 | The server failed to read the internal file or table that stores information about the contents of the recycle bin. | - |
8589 | After a table was dropped, the server failed to write a corresponding record to the recycle bin log. | - |
8590 | The specified database was not found in the recycle bin. | The recycle_bin_db_12345 database was not found. |
8591 | An internal check found that a required INFORMATION_SCHEMA view is missing. | Not found I_S view TABLES. |
8592 | An internal check found that multiple INFORMATION_SCHEMA views are missing. | Lost 3 I_S views. |
8593 | An internal error occurred while trying to create or dump the definition of an INFORMATION_SCHEMA view. | Failed dump I_S view in :TABLES. |
8594 | A table created with a sync or broadcast distribution policy (replicated to all nodes) cannot have partitions. | - |
8595 | An unexpected internal error occurred during a "Stale Read" operation. | Stale Read Unexpected. Failed to find region leader |
8596 | The specified partition policy name does not exist. | Unknown partition policy 'my_policy' |
8597 | An attempt to drop a partition policy failed, likely because it is still in use by a table. | Failed to drop partition policy 'my_policy' |
8598 | An attempt was made to create a partition policy with a name that already exists. | Partition Policy 'my_policy' already exists |
8599 | An INSERT or UPDATE failed because the next AUTO_INCREMENT value would exceed the maximum value for the column's data type (e.g., INT UNSIGNED). | - |
8600 | The server could not find the location (route) of a data object, possibly because a concurrent DDL operation (like DROP TABLE) removed it. | - |
Error Code | Error Description | Example |
8601 | The system is forcibly terminating a thread, which will close the associated user connection. This is often an administrative action. | Forcing close of thread 12345. Should close user connection. Killed by admin. |
8602 | A generic error occurred in the proxy layer that routes client connections to backend SQL nodes. | Proxy ERROR. No available backend connection. |
8603 | A cluster upgrade process cannot proceed due to a specific blocking condition. | Cluster is not healthy, can't upgrade now. |
8604 | A data loading operation using the stream load feature failed for the specified reason. | Stream load data failed, table not found, err_code:404 |
8605 | A transaction was aborted because the total size of its write operations exceeded the configured limit ( tdsql_max_memory_per_transaction_bytes). | - |
8606 | An internal sub-worker thread for a data ingestion process has failed. The error provides details about the location and cause. | Ingestbehind sub worker failed, error_addr:10.0.1.5:3306, sub_worker_tid:9876, err_code:1062, err_msg:Duplicate entry '1' for key 'PRIMARY' |
8607 | An operation specified a proxy node ID that does not exist. The message lists the available, valid node IDs. | Invalid proxy node id, Available node IDs: 1, 2, 3 |
8608 | An ALTER PARTITION POLICY statement failed for the specified reason. | Failed to alter partition policy. Policy is in use by table 'db1.t1' |
8609 | The statement outline (plan hinting) feature was not applied to the current query for the reason given. | Statment outline is disabled for current query: query is from a stored procedure. |
8610 | An informational or error message reporting the current internal schema status of a table (e.g., public, write-only, being altered). | Table db1.t1 schema status is WRITE_ONLY |
8611 | An informational or error message reporting the current internal schema status of a specific index on a table. | Key idx_c1 of table db1.t1 schema status is DELETED |
8612 | The SET PERSIST or SET PERSIST_ONLY command cannot be executed on a node configured for Change Data Capture (CDC). | - |
8613 | The server failed to flush a specific object from its in-memory data dictionary (DD) cache to persistent storage. | Failed to flush dd cache object:TABLE/db1/t1 |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan