Troubleshooting MYSQL or MariaDB Errors from Error 1721 to 1727

SQLServerF1

MariaDB ERROR Code 1721
MySQL SQL State HY000
ER_PLUGIN_NO_INSTALL Plugin ‘%s’ is marked as not dynamically installable. You have to stop the server to install it.
MariaDB ERROR Code 1722
MySQL SQL State HY000
ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT
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.

MariaDB ERROR Code 1723
MySQL SQL State HY000
ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC
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.
MariaDB ERROR Code 1724
MySQL SQL State HY000
ER_BINLOG_UNSAFE_INSERT_TWO_KEYS
INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe

MariaDB ERROR Code 1725
MySQL SQL State HY000
ER_TABLE_IN_FK_CHECK
Table is being used in foreign key check.
MariaDB ERROR Code 1726
MySQL SQL State HY000
ER_UNSUPPORTED_ENGINE
Storage engine ‘%s’ does not support system tables. [%s.%s]
MariaDB ERROR Code 1727
MySQL SQL State HY000
ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST
INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1721 to 1727 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1711 to 1720

SQLServerF1

MariaDB ERROR Code 1711
MySQL SQL State HY000
ER_ERROR_IN_UNKNOWN_TRIGGER_BODY
Unknown trigger has an error in its body: ‘%s’
MariaDB ERROR Code 1712
MySQL SQL State HY000
ER_INDEX_CORRUPT
Index %s is corrupted
MariaDB ERROR Code 1713
MySQL SQL State HY000
ER_UNDO_RECORD_TOO_BIG
Undo log record is too big.

MariaDB ERROR Code 1714
MySQL SQL State HY000
ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT
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.
MariaDB ERROR Code 1715
MySQL SQL State HY000
ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE
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.
MariaDB ERROR Code 1716
MySQL SQL State HY000
ER_BINLOG_UNSAFE_REPLACE_SELECT
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.

MariaDB ERROR Code 1717
MySQL SQL State HY000
ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT
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.
MariaDB ERROR Code 1718
MySQL SQL State HY000
ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT
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.
MariaDB ERROR Code 1719
MySQL SQL State HY000
ER_BINLOG_UNSAFE_UPDATE_IGNORE
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.
MariaDB ERROR Code 1720
MySQL SQL State HY000
ER_PLUGIN_NO_UNINSTALL
Plugin ‘%s’ is marked as not dynamically uninstallable. You have to stop the server to uninstall it. .

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1711 to 1720 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1701 to 1710

SQLServerF1

MariaDB ERROR Code 1701
MySQL SQL State 42000
ER_TRUNCATE_ILLEGAL_FK
Cannot truncate a table referenced in a foreign key constraint (%s)
MariaDB ERROR Code 1702
MySQL SQL State HY000
ER_PLUGIN_IS_PERMANENT
Plugin ‘%s’ is force_plus_permanent and can not be unloaded
MariaDB ERROR Code 1703
MySQL SQL State HY000
ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN
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.

MariaDB ERROR Code 1704
MySQL SQL State HY000
ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX
The requested value for the heartbeat period exceeds the value of slave_net_timeout seconds. A sensible value for the period should be less than the timeout.
MariaDB ERROR Code 1705
MySQL SQL State HY000
ER_STMT_CACHE_FULL
Multi-row statements required more than ‘max_binlog_stmt_cache_size’ bytes of storage; increase this mysqld variable and try again
MariaDB ERROR Code 1706
MySQL SQL State HY000
ER_MULTI_UPDATE_KEY_CONFLICT
Primary key/partition key update is not allowed since the table is updated both as ‘%s’ and ‘%s’.

MariaDB ERROR Code 1707
MySQL SQL State HY000
ER_TABLE_NEEDS_REBUILD
Table rebuild required. Please do “ALTER TABLE `%s` FORCE” or dump/reload to fix it!
MariaDB ERROR Code 1708
MySQL SQL State HY000
WARN_OPTION_BELOW_LIMIT
The value of ‘%s’ should be no less than the value of ‘%s’ Note: Introduced in 5.5.12.
MariaDB ERROR Code 1709
MySQL SQL State HY000
ER_INDEX_COLUMN_TOO_LONG
Index column size too large. The maximum column size is %lu bytes. Note: Introduced in 5.5.14.
MariaDB ERROR Code 1710
MySQL SQL State HY000
ER_ERROR_IN_TRIGGER_BODY
Trigger ‘%s’ has an error in its body: ‘%s’ Note: Introduced in 5.5.15.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1701 to 1710 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1691 to 1700

SQLServerF1

MariaDB ERROR Code 1691
MySQL SQL State HY000
ER_WRONG_SPVAR_TYPE_IN_LIMIT
A variable of a non-integer based type in LIMIT clause Note: Introduced in 5.5.5.
MariaDB ERROR Code 1692
MySQL SQL State HY000
ER_BINLOG_UNSAFE_MULTIPLE_ENGINES _AND_SELF_LOGGING_ENGINE
Mixing self-logging and non-self-logging engines in a statement is unsafe. Note: Introduced in 5.5.5.
MariaDB ERROR Code 1693
MySQL SQL State HY000
ER_BINLOG_UNSAFE_MIXED_STATEMENT
Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Note: Introduced in 5.5.5.

MariaDB ERROR Code 1694
MySQL SQL State HY000
ER_INSIDE_TRANSACTION_ PREVENTS_SWITCH_SQL_LOG_BIN
Cannot modify @@session.sql_log_bin inside a transaction Note: Introduced in 5.5.5.
MariaDB ERROR Code 1695
MySQL SQL State HY000
ER_STORED_FUNCTION_ PREVENTS_SWITCH_SQL_LOG_BIN
Cannot change the sql_log_bin inside a stored function or trigger Note: Introduced in 5.5.5.
MariaDB ERROR Code 1696
MySQL SQL State HY000
ER_FAILED_READ_FROM_PAR_FILE
Failed to read from the .par file Note: Introduced in 5.5.5.

MariaDB ERROR Code 1697
MySQL SQL State HY000
ER_VALUES_IS_NOT_INT_TYPE_ERROR VALUES
value for partition ‘%s’ must have type INT Note: Introduced in 5.5.7.
MariaDB ERROR Code 1698
MySQL SQL State 28000
ER_ACCESS_DENIED_NO_PASSWORD_ERROR
Access denied for user ‘%s’@’%s’ Note: Introduced in 5.5.7.
MariaDB ERROR Code 1699
MySQL SQL State HY000
ER_SET_PASSWORD_AUTH_PLUGIN
SET PASSWORD has no significance for users authenticating via plugins Note: Introduced in 5.5.7.
MariaDB ERROR Code 1700
MySQL SQL State HY000
ER_GRANT_PLUGIN_USER_EXISTS
GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists Note: Introduced in 5.5.7.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1691 to 1700 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1681 to 1690

SQLServerF1

MariaDB ERROR Code 1681
MySQL SQL State HY000
ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT
‘%s’ is deprecated and will be removed in a future release. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1682
MySQL SQL State HY000
ER_WRONG_NATIVE_TABLE_STRUCTURE
Native table ‘%s’.’%s’ has the wrong structure Note: Introduced in 5.5.3.
MariaDB ERROR Code 1683
MySQL SQL State HY000
ER_WRONG_PERFSCHEMA_USAGE
Invalid performance_schema usage. Note: Introduced in 5.5.3.

MariaDB ERROR Code 1684
MySQL SQL State HY000
ER_WARN_I_S_SKIPPED_TABLE
Table ‘%s’.’%s’ was skipped since its definition is being modified by concurrent DDL statement Note: Introduced in 5.5.3.
MariaDB ERROR Code 1685
MySQL SQL State HY000
ER_INSIDE_TRANSACTION _PREVENTS_SWITCH_BINLOG_DIRECT
Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Note: Introduced in 5.5.3.
MariaDB ERROR Code 1686
MySQL SQL State HY000
ER_STORED_FUNCTION_PREVENTS _SWITCH_BINLOG_DIRECT
Cannot change the binlog direct flag inside a stored function or trigger Note: Introduced in 5.5.3.

MariaDB ERROR Code 1687
MySQL SQL State 42000
ER_SPATIAL_MUST_HAVE_GEOM_COL
A SPATIAL index may only contain a geometrical type column Note: Introduced in 5.5.2.
MariaDB ERROR Code 1688
MySQL SQL State HY000
ER_TOO_LONG_INDEX_COMMENT
Comment for index ‘%s’ is too long (max = %lu) Note: Introduced in 5.5.3.
MariaDB ERROR Code 1689
MySQL SQL State HY000
ER_LOCK_ABORTED
Wait on a lock was aborted due to a pending exclusive lock Note: Introduced in 5.5.4.
MariaDB ERROR Code 1690
MySQL SQL State 22003
ER_DATA_OUT_OF_RANGE
%s value is out of range in ‘%s’ Note: Introduced in 5.5.5.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1681 to 1690 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1671 to 1680

SQLServerF1

MariaDB ERROR Code 1671
MySQL SQL State HY000
ER_BINLOG_UNSAFE_AUTOINC_COLUMNS
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. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1672
MySQL SQL State HY000
ER_BINLOG_UNSAFE_UDF
Statement is unsafe because it uses a UDF which may not return the same value on the slave. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1673
MySQL SQL State HY000
ER_BINLOG_UNSAFE_SYSTEM_VARIABLE
Statement is unsafe because it uses a system variable that may have a different value on the slave. Note: Introduced in 5.5.3.

MariaDB ERROR Code 1674
MySQL SQL State HY000
ER_BINLOG_UNSAFE_SYSTEM_FUNCTION
Statement is unsafe because it uses a system function that may return a different value on the slave. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1675
MySQL SQL State HY000
ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS
Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction. Note: ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS was introduced in 5.5.3.
MariaDB ERROR Code 1676
MySQL SQL State HY000
ER_MESSAGE_AND_STATEMENT
%s Statement: %s Note: Introduced in 5.5.3.

MariaDB ERROR Code 1677
MySQL SQL State HY000
ER_SLAVE_CONVERSION_FAILED
Column %d of table ‘%s.%s’ cannot be converted from type ‘%s’ to type ‘%s’ Note: Introduced in 5.5.3.
MariaDB ERROR Code 1678
MySQL SQL State HY000
ER_SLAVE_CANT_CREATE_CONVERSION
Can’t create conversion table for table ‘%s.%s’ Note: Introduced in 5.5.3.
MariaDB ERROR Code 1679
MySQL SQL State HY000
ER_INSIDE_TRANSACTION _PREVENTS_SWITCH_BINLOG_FORMAT
Cannot modify @@session.binlog_format inside a transaction Note: Introduced in 5.5.3.
MariaDB ERROR Code 1680
MySQL SQL State HY000
ER_PATH_LENGTH
The path specified for %s is too long. Note: Introduced in 5.5.3.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1671 to 1680 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1661 to 1670

SQLServerF1

MariaDB ERROR Code 1661
MySQL SQL State HY000
ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE
Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1662
MySQL SQL State HY000
ER_BINLOG_ROW_MODE_AND_STMT_ENGINE
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. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1663
MySQL SQL State HY000
ER_BINLOG_UNSAFE_AND_STMT_ENGINE
Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s Note: Introduced in 5.5.3.

MariaDB ERROR Code 1664
MySQL SQL State HY000
ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE
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. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1665
MySQL SQL State HY000
ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s Note: Introduced in 5.5.3.
MariaDB ERROR Code 1666
MySQL SQL State HY000
ER_BINLOG_ROW_INJECTION_AND_STMT_MODE
Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT. Note: Introduced in 5.5.3.

MariaDB ERROR Code 1667
MySQL SQL State HY000
ER_BINLOG_MULTIPLE_ENGINES _AND_SELF_LOGGING_ENGINE
Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1668
MySQL SQL State HY000
ER_BINLOG_UNSAFE_LIMIT
The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1669
MySQL SQL State HY000
ER_BINLOG_UNSAFE_INSERT_DELAYED
The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1670
MySQL SQL State HY000
ER_BINLOG_UNSAFE_SYSTEM_TABLE
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. Note: Introduced in 5.5.3.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1661 to 1670 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1651 to 1660

SQLServerF1

MariaDB ERROR Code 1651
MySQL SQL State HY000
ER_QUERY_CACHE_DISABLED
Query cache is disabled; restart the server with query_cache_type=1 to enable it
MariaDB ERROR Code 1652
MySQL SQL State HY000
ER_SAME_NAME_PARTITION_FIELD
Duplicate partition field name ‘%s’
MariaDB ERROR Code 1653
MySQL SQL State HY000
ER_PARTITION_COLUMN_LIST_ERROR
Inconsistency in usage of column lists for partitioning

MariaDB ERROR Code 1654
MySQL SQL State HY000
ER_WRONG_TYPE_COLUMN_VALUE_ERROR
Partition column values of incorrect type
MariaDB ERROR Code 1655
MySQL SQL State HY000
ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR
Too many fields in ‘%s’
MariaDB ERROR Code 1656
MySQL SQL State HY000
ER_MAXVALUE_IN_VALUES_IN
Cannot use MAXVALUE as value in VALUES IN

MariaDB ERROR Code 1657
MySQL SQL State HY000
ER_TOO_MANY_VALUES_ERROR
Cannot have more than one value for this type of %s partitioning
MariaDB ERROR Code 1658
MySQL SQL State HY000
ER_ROW_SINGLE_PARTITION_FIELD_ERROR
Row expressions in VALUES IN only allowed for multi-field column partitioning
MariaDB ERROR Code 1659
MySQL SQL State HY000
ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD
Field ‘%s’ is of a not allowed type for this type of partitioning
MariaDB ERROR Code 1660
MySQL SQL State HY000
ER_PARTITION_FIELDS_TOO_LONG
The total length of the partitioning fields is too large

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1651 to 1660 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1641 to 1650

SQLServerF1

MariaDB ERROR Code 1641
MySQL SQL State 42000
ER_DUP_SIGNAL_SET
Duplicate condition information item ‘%s’
MariaDB ERROR Code 1642
MySQL SQL State 01000
ER_SIGNAL_WARN
Unhandled user-defined warning condition
MariaDB ERROR Code 1643
MySQL SQL State 02000
ER_SIGNAL_NOT_FOUND
Unhandled user-defined not found condition

MariaDB ERROR Code 1644
MySQL SQL State HY000
ER_SIGNAL_EXCEPTION
Unhandled user-defined exception condition
MariaDB ERROR Code 1645
MySQL SQL State 0K000
ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER
RESIGNAL when handler not active
MariaDB ERROR Code 1646
MySQL SQL State HY000
ER_SIGNAL_BAD_CONDITION_TYPE
SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE

MariaDB ERROR Code 1647
MySQL SQL State HY000
WARN_COND_ITEM_TRUNCATED
Data truncated for condition item ‘%s’
MariaDB ERROR Code 1648
MySQL SQL State HY000
ER_COND_ITEM_TOO_LONG
Data too long for condition item ‘%s’
MariaDB ERROR Code 1649
MySQL SQL State HY000
ER_UNKNOWN_LOCALE
Unknown locale: ‘%s’
MariaDB ERROR Code 1650
MySQL SQL State HY000
ER_SLAVE_IGNORE_SERVER_IDS
The requested server id %d clashes with the slave startup option –replicate-same-server-id

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1641 to 1650 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Troubleshooting MYSQL or MariaDB Errors from Error 1631 to 1640

SQLServerF1

MariaDB ERROR Code 1631
MySQL SQL State HY000
ER_DATABASE_NAME
Database
MariaDB ERROR Code 1632
MySQL SQL State HY000
ER_TABLE_NAME Table
MariaDB ERROR Code 1633
MySQL SQL State HY000
ER_PARTITION_NAME
Partition

MariaDB ERROR Code 1634
MySQL SQL State HY000
ER_SUBPARTITION_NAME
Subpartition
MariaDB ERROR Code 1635
MySQL SQL State HY000
ER_TEMPORARY_NAME
Temporary
MariaDB ERROR Code 1636
MySQL SQL State HY000
ER_RENAMED_NAME
Renamed

MariaDB ERROR Code 1637
MySQL SQL State HY000
ER_TOO_MANY_CONCURRENT_TRXS
Too many active concurrent transactions
MariaDB ERROR Code 1638
MySQL SQL State HY000
WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED
Non-ASCII separator arguments are not fully supported
MariaDB ERROR Code 1639
MySQL SQL State HY000
ER_DEBUG_SYNC_TIMEOUT
debug sync point wait timed out
MariaDB ERROR Code 1640
MySQL SQL State HY000
ER_DEBUG_SYNC_HIT_LIMIT
debug sync point hit limit reached

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1631 to 1640 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 
1 2 3 17