All pages
Powered by GitBook
1 of 14

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

MariaDB Error Codes 4200 to 4299

Error 4200: ORDER BY

Error Code
SQLSTATE
Error
Description

4200

ER_SEQUENCE_TABLE_ORDER_BY

ORDER BY

Possible Causes and Solutions

Error 4204: Invalid binary vector format

Error Code
SQLSTATE
Error
Description

Error 4201: The variable is ignored

Error Code
SQLSTATE
Error
Description

Error 4203: Values were longer than max_sort_length. Sorting used only the first bytes

Error Code
SQLSTATE
Error
Description

Error 4226: Slave SQL thread aborted

Error Code
SQLSTATE
Error
Description

Error 4222: Unresolved index name for hint

Error Code
SQLSTATE
Error
Description

Possible Causes and Solutions

Argument is not a Valid Binary Vector

For example, the VEC_ToText function expects a binary vector. If not given one, this error will result:

The solution is to provide a valid binary vector:

4204

ER_VECTOR_BINARY_FORMAT_INVALID

Invalid binary vector format. Must use IEEE standard float representation in little-endian format. Use VEC_FromText() to generate it.

SELECT VEC_ToText(x'aabbcc');
+-----------------------+
| VEC_ToText(x'aabbcc') |
+-----------------------+
| NULL                  |
+-----------------------+
1 row in set, 1 warning (0.000 sec)

Warning (Code 4204): Invalid binary vector format. Must use IEEE standard float 
  representation in little-endian format. Use VEC_FromText() to generate it.
Possible Causes and Solutions

4201

ER_VARIABLE_IGNORED

The variable '%s' is ignored. It only exists for compatibility with old installations and will be removed in a future release

Possible Causes and Solutions

4203

WARN_SORTING_ON_TRUNCATED_LENGTH

%llu values were longer than max_sort_length. Sorting used only the first %lu bytes

Possible Causes and Solutions

Prior to the introduction of this error, there were multiple error codes reported for the issue 'Can't execute init_slave query'. Those errors are the underlying reason the init_slave query cannot be executed, but this made it difficult to detect the issue in an automated way.

This error code, ER_INIT_SLAVE_ERROR, unifies all the errors related to the init_slave query. The ER_INIT_SLAVE_ERROR error is raised for any issue related to the init_slave query, and the underlying error code and message are included in the Last_SQL_Error field. See those specific errors for more details.

4226

ER_INIT_SLAVE_ERROR

Slave SQL thread aborted. Can't execute init_slave query due to error code %u: %s

Possible Causes and Solutions

4222

ER_UNRESOLVED_INDEX_HINT_NAME

Unresolved index name %s for %s hint

Error 4205: Invalid vector format at offset

Error Code
SQLSTATE
Error
Description

4205

ER_VECTOR_FORMAT_INVALID

Invalid vector format at offset: %d for '%-.100s'. Must be a valid JSON array of numbers.

Possible Causes and Solutions

Error 4221: Unresolved table name for hint

Error Code
SQLSTATE
Error
Description

4221

ER_UNRESOLVED_TABLE_HINT_NAME

Unresolved table name %s for %s hint

Possible Causes and Solutions

Error 4202: Incorrect column name count for derived table

Error Code
SQLSTATE
Error
Description

4202

ER_INCORRECT_COLUMN_NAME_COUNT

Incorrect column name count for derived table

Possible Causes and Solutions

Error 4223: Optimizer hints are not supported inside view definitions

Error Code
SQLSTATE
Error
Description

4223

ER_HINTS_INSIDE_VIEWS_NOT_SUPPORTED

Optimizer hints are not supported inside view definitions

Possible Causes and Solutions

Error 4225: Optimizer hints at the INSERT part of a INSERT..SELECT statement are not supported

Error Code
SQLSTATE
Error
Description

4225

ER_WARN_HINTS_ON_INSERT_PART_OF_INSERT_SELECT

Optimizer hints at the INSERT part of a INSERT..SELECT statement are not supported

Possible Causes and Solutions

SELECT VEC_ToText(x'e360d63ebe554f3fcdbc523f4522193f5236083d');
+---------------------------------------------------------+
| VEC_ToText(x'e360d63ebe554f3fcdbc523f4522193f5236083d') |
+---------------------------------------------------------+
| [0.418708,0.809902,0.823193,0.598179,0.033255]          |
+---------------------------------------------------------+

This page is licensed: CC BY-SA / Gnu FDL

This page is licensed: CC BY-SA / Gnu FDL

This page is licensed: CC BY-SA / Gnu FDL

This page is licensed: CC BY-SA / Gnu FDL

This page is licensed: CC BY-SA / Gnu FDL

This page is licensed: CC BY-SA / Gnu FDL

This page is licensed: CC BY-SA / Gnu FDL

This article doesn't currently contain any content.

This article doesn't currently contain any content.

This article doesn't currently contain any content.

This article doesn't currently contain any content.

This article doesn't currently contain any content.

This article doesn't currently contain any content.

This article doesn't currently contain any content.

This article doesn't currently contain any content.

This article doesn't currently contain any content.

You can help!
You can help!
You can help!
You can help!
You can help!
You can help!
You can help!
You can help!
You can help!

Error 4206: Cannot determine distance type for VEC_DISTANCE, index is not found

Error Code
SQLSTATE
Error
Description

4206

ER_VEC_DISTANCE_TYPE

Cannot determine distance type for VEC_DISTANCE, index is not found

Possible Causes and Solutions

Table is Built Without a Vector Index

To solve, add a vector index to the table:

CREATE OR REPLACE TABLE v (id INT PRIMARY KEY, v VECTOR(5) NOT NULL);

INSERT INTO v VALUES                                              
    (1, x'e360d63ebe554f3fcdbc523f4522193f5236083d'),
    (2, x'f511303f72224a3fdd05fe3eb22a133ffae86a3f'),
    (3,x'f09baa3ea172763f123def3e0c7fe53e288bf33e'),
    (4,x'b97a523f2a193e3eb4f62e3f2d23583e9dd60d3f'),
    (5,x'f7c5df3e984b2b3e65e59d3d7376db3eac63773e'),
    (6,x'de01453ffa486d3f10aa4d3fdd66813c71cb163f'),
    (7,x'76edfc3e4b57243f10f8423fb158713f020bda3e'),
    (8,x'56926c3fdf098d3e2c8c5e3d1ad4953daa9d0b3e'),
    (9,x'7b713f3e5258323f80d1113d673b2b3f66e3583f'),
    (10,x'6ca1d43e9df91b3fe580da3e1c247d3f147cf33e');

SELECT id FROM v ORDER BY VEC_DISTANCE(v, x'6ca1d43e9df91b3fe580da3e1c247d3f147cf33e');          
ERROR 4206 (HY000): Cannot determine distance type for VEC_DISTANCE, index is not found

This page is licensed: CC BY-SA / Gnu FDL

ALTER TABLE v ADD VECTOR INDEX(v);

SELECT id FROM v ORDER BY VEC_DISTANCE(v, x'6ca1d43e9df91b3fe580da3e1c247d3f147cf33e');
+----+
| id |
+----+
| 10 |
|  7 |
|  3 |
|  9 |
|  2 |
|  1 |
|  5 |
|  4 |
|  6 |
|  8 |
+----+

Error 4224: Hint is ignored as malformed

Error Code
SQLSTATE
Error
Description

4224

ER_WARN_MALFORMED_HINT

Hint %s is ignored as malformed

Possible Causes and Solutions

This article doesn't currently contain any content.

You can help!